Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) - UPDATED 20071217

[hunter]

Have xv6700 bootloader 1.04, hooked up to Vista Business 32bit, mobile center usb is off, driver fix for vista has been applied. Run BuildOS all seems to be going fine when i receive error RUU Device has stopped responding?

What Next?

[luv2chill]

Originally Posted by hunter

Have xv6700 bootloader 1.04, hooked up to Vista Business 32bit, mobile center usb is off, driver fix for vista has been applied. Run BuildOS all seems to be going fine when i receive error RUU Device has stopped responding?

What Next?

You have the new bootloader. Bootloader versions 1.04, 2.04, and 2.05 require a different ROM Upgrade Utility than earlier versions. The way you select that is from the BuildOS window, look at the top toolbar where it says "Standard". Click that and a drop-down menu will come up... choose X.04+ from that menu and build your ROM again. That will cause it to flash with the correct RUU for your device.

Edit: Also you should turn Mobile Device Center USB back on. That should only be off while replacing the driver for Vista. You could also put your phone into bootloader mode (Power + Notes + Soft reset) first before connecting to USB to save a step.

[nico4k]

Luv2Chill,
(sorry for being so picky) i think it is a good idea to add under "tweaks" to anable Smartskeys so we dont have to do it manually everytime we have to perform a hard-reset. Hope to see this in the update of the kitchen...

Thanks for everything, you guys are the best! period!

[daveedem]

Tiermann....

I think I know the answer to this one... I'm using your dialer skin. In the new kitchen I've basically just copied all my dialer skin images to the windows folder and overwrote what is there... when I do this, the numbers and lines disappear and all I see are my images.

I install the touch dialer in the kitchen.

Should I just redo the dialer skin through your app?

Thanks.

[luv2chill]

Originally Posted by nico4k

Luv2Chill,
(sorry for being so picky) i think it is a good idea to add under "tweaks" to anable Smartskeys so we dont have to do it manually everytime we have to perform a hard-reset. Hope to see this in the update of the kitchen...

Thanks for everything, you guys are the best! period!

Can you clarify what you mean? If you select smartskey in buildos it should be enabled automatically.

Or are you referring to the setting to make it scroll using the volume key?

[nico4k]

Originally Posted by luv2chill

Can you clarify what you mean? If you select smartskey in buildos it should be enabled automatically.

Or are you referring to the setting to make it scroll using the volume key?

Yes, exactly. volume key scrolling is disabled by default (yes, i read why is disabled). But i wish there was a way to enable it before the rom is cooked. (so, i guess under "Tweaks" category or something should be "enable volume key as scroll" or somehting along those lines).

let me know if it is possible. thanx!

[scotbotmosh]

Originally Posted by Trident

I believe it had something to do with an incompatibility with one of the dialer skins. Vogue, I think.
It's working fine for me.

I believe I am using the iBliss dialer...the pretty one with the tree and the grass..

[jhonny11]

You guys are awesome! But it seems like I'm rebuilding every day

[TMB_XV6700]

This is really just an FYI.
Not sure if this registry entry was modified by Microsoft, Helmi, or the kitchen staff (or anybody), but I came across the consequences this week while standing at a rental car counter in a distant city. As a habit, when I travel I just paste relevant flight, hotel, and rental car information into the notes section of a calendar entry. This time, my information included some internet tags that made the size balloon up a little, and the note was truncated with a reminder that if I edited the appointment on the device all the associated notes on the server would be overwritten. Up to WM2003, there was no limit on the notes size, but WM5 supposedly introduced a 5kB default limit. Turns out my limit coming out of the kitchen was 1kB.

The associated key is
[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync]
"BodyTruncation"=dword: Change from 1020 to 5120 (Decimal)

This change worked fine for me, as does bumping the dword value up to 20480 (Decimal),
supposedly the absolute upper limit in WM5.

[hunter]

Originally Posted by luv2chill

You have the new bootloader. Bootloader versions 1.04, 2.04, and 2.05 require a different ROM Upgrade Utility than earlier versions. The way you select that is from the BuildOS window, look at the top toolbar where it says "Standard". Click that and a drop-down menu will come up... choose X.04+ from that menu and build your ROM again. That will cause it to flash with the correct RUU for your device.

Edit: Also you should turn Mobile Device Center USB back on. That should only be off while replacing the driver for Vista. You could also put your phone into bootloader mode (Power + Notes + Soft reset) first before connecting to USB to save a step.

Does that mean i'll have to limit the size of the rom like in 2.04 and 2.05?

thanks ahead of time