WM 6.5 Kitchen QVGA and VGA Developer Edition

[qball1616]

Originally Posted by joojoobee666

Yup, PPCK sure isn't. Does you kitchen implant an already packaged XIP or make it on the fly?

i believe it implants it. I have 2 options with it. I can dump the xip.bin and place the MSXIPKernel & MSXIPKernelLTK files in:
\ROM\SHARED\21820\MSXIPKernel

or I can just put the xip.bin in:
\ROM\SHARED\21820

their is another folder for ROM, but it is for all of the OEMXIPKernel for the device
\ROM\Herald\21820\OEMXIPKernel

if i only put the xip.bin in the appropriate folder the kitchen will automatically port the XIP.

[joojoobee666]

I DID find some missing icons that the 192 browsres dll has. I'll bet that's the issue. I'll manually fix. Anyone wanna give it a shot when I am done?

Update: Ok, does someone want to try this? Replace the SYS_23001_96DPI_0409\Browsing_DPI_96 with stuff in the below file.

Update 2:...whoops,the first file I posted wasn't the right one. Sorry.

[da_reeseboy]

So to update the wealth of info that was in this post, we could add:

230xx = COM3, continuing development of 6.5.0.60

right? Just trying to keep up here lol...

Originally Posted by Da_G

Let's see if I can recall the build naming convention...

212xx = AKU1, all builds leading up to and including WM 6.5
213xx = MOT motorola
214xx = forget
215xx = SAM samsung
216xx = HTC htc
217xx = COM1, continuing dev of 6.5.0.1 - 6.5.0.40
218xx = COM2, continuing dev of 6.5.0.50
219xx = MD, feature branch (unstable features are added here, backported to 218xx (this tree is based on COM1, so older base os code, but the UX code is newer [user experience])
22xxx = SEMC sony ericsson

almost all of the oem branches are based off 21234 (iirc SAM was based off an older build than that) - the oem's requested their modifications, and msft did them, incremented build number - some of these trees have stopped receiving modifications already.

For most of you, for the moment, 218xx is the branch to follow (but they might change the number now that COM2 is done as of 21820)

Most of the current focus is on UX as the backend code is mostly at the goal, so we should be seeing some nice changes to the theming api's etc. that will allow us much more modification of the UI (iirc the end goal is complete skinnability and finger friendliness - nothing left over from the old 6.1 interface that used a stylus, essentially)

They might be bandying about the idea of licensing resco keyboard to replace the stock non-finger-friendly keyboard.

Also, an interesting tidbit, any device that has a dpad and IE6 is *required* to have support in the display driver for a mouse pointer, and support in the dpad driver for a mouse pointer, to allow for things like javascript mouseovers that pull drop-down menus

[joojoobee666]

Originally Posted by da_reeseboy

So to update the wealth of info that was in this post, we could add:

230xx = COM3, continuing development of 6.5.0.60

right? Just trying to keep up here lol...

Yeah, that's right.

Quote from Da_G

"I heard the new branch replacing COM2 is COM3, and it's build 230xx, starting with 23001

Despite the drastic build number change, it's a continuation of 218xx COM2 tree

If I had to guess, the other 22xxx's are reserved for OEM builds (i know 220xx is SEMC sony ericsson)"

[joojoobee666]

Originally Posted by dsi76

I'm using the DPI 96 files from 21815 for my 23001 QVGA build. Did you guys have any issues with the toolbar in PIE? I don't see the Stop/Back buttons at the top.

Can you try the fix I posted here?

http://forum.ppcgeeks.com/showpost.p...postcount=5582

[randomelements]

The IE buttons is browsui.dll from what I recall. Replace it with an older one and you should be ok.

[corey1138]

Originally Posted by joojoobee666

As far as I know, YES. The 23000 build tree is a continuation of the 218xx tree. Just continue to use the tsk format and all will be well. (i.e. make sure you have the necessary reg keys in it)

Did we confirm that the reg edits in mxipcold_wpc_2.provxml are all we need? The fixed DIP Da_G posted is what fixed it for me.

[joojoobee666]

Originally Posted by randomelements

The IE buttons is browsui.dll from what I recall. Replace it with an older one and you should be ok.

The browseui.dll has NO resources in it. However, somewhere between 21815 and 21820 an additional resource was added to browsres.192.dll ,or browsres.96.dll, depending on your device, but there has been no official QVGA/96 DPI leak for a bit.

[ankit360]

Originally Posted by dsi76

I'm using the DPI 96 files from 21815 for my 23001 QVGA build. Did you guys have any issues with the toolbar in PIE? I don't see the Stop/Back buttons at the top.

did you try my DPI i shared in previous post ?

[joojoobee666]

Originally Posted by ankit360

did you try my DPI i shared in previous post ?

It's missing the same resource in the dll. So, if that IS indeed the problem, then it will be the same.