Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) Bugs/Patches

[scotbotmosh]

Originally Posted by zachspda

Under server configuration in mms you need to change mms.sprintpcs.com to 63.215.195.152 leave the rest the same

mms.sprintpcs.com and 63.215.195.152 are the same thing, it's nothing more than a DNS resolution. They are both mms.sprintpcs.com if it was a DNS issue it would be on Sprint's side and everyone here would be complaining.

[imnuts]

I can't run the kitchen to see if things work. I tried both the default "install" folder and a seperate one and both give me the same error (see below). I tried to start just the app itself, but it gave me a big list of missing files. Any help to get this fixed would be great.



I'm running on Vista x64, if that makes any difference

[lennysh]

Originally Posted by imnuts

I can't run the kitchen to see if things work. I tried both the default "install" folder and a seperate one and both give me the same error (see below). I tried to start just the app itself, but it gave me a big list of missing files. Any help to get this fixed would be great.



I'm running on Vista x64, if that makes any difference

I know this was tested on Vista 32, not sure about 64. But we're looking at it now.. So maybe, a resolution will be posted shortly..

[gguruusa]

Originally Posted by imnuts

I can't run the kitchen to see if things work. I tried both the default "install" folder and a seperate one and both give me the same error (see below). I tried to start just the app itself, but it gave me a big list of missing files. Any help to get this fixed would be great.



I'm running on Vista x64, if that makes any difference

Yes, the x64 part makes a difference. Try running in compatibility mode.

[imnuts]

Originally Posted by gguruusa

Yes, the x64 part makes a difference. Try running in compatibility mode.

Tried compatibility mode for XP SP2, didn't work, also tried running as administrator with and without compatibility mode, neither work and I'm still getting the same error.

[jbrianj]

Originally Posted by imnuts

I can't run the kitchen to see if things work. I tried both the default "install" folder and a seperate one and both give me the same error (see below). I tried to start just the app itself, but it gave me a big list of missing files. Any help to get this fixed would be great.



I'm running on Vista x64, if that makes any difference

Same thing here. *sigh*
But if you run the app without the Arguments from the shortcut it at least runs the app.

Also if you load it with just the Config.txt as an argument it works fine. but errors as soon as you try to open the Selection.txt

The Error Occurs once you add in the KitchenDir=Apache_Helmi_WM6\Apache_Helmi_WM6.rar: Line to the Selections.txt

Hope that helps.

I'm really excited about this project.

[Krazy4Real]

After making a rom from the kitchen and flashing it to my device, I reboot the phone and it shows the boot screen as normal, but then it goes to a blank white screen instead of the initial setup screen to do screen alignment. Any ideas?

[TMB_XV6700]

Originally Posted by Krazy4Real

After making a rom from the kitchen and flashing it to my device, I reboot the phone and it shows the boot screen as normal, but then it goes to a blank white screen instead of the initial setup screen to do screen alignment. Any ideas?

Krazy, like it said in the tips doc, try building a smaller rom....

[luv2chill]

Originally Posted by Krazy4Real

After making a rom from the kitchen and flashing it to my device, I reboot the phone and it shows the boot screen as normal, but then it goes to a blank white screen instead of the initial setup screen to do screen alignment. Any ideas?

Nine times out of ten that indicates your ROM is too full. What version of the bootloader are you running?

Try building that config again, except this time uncheck office (which is by far the largest OEM in the whole kitchen). Flash it and see if you get the white screen--if so then ROM size isn't the issue. If it does boot properly (and you want office installed) then you'll need to try unchecking other OEMs until you get to the point where your device will boot.

But do report your bootloader version please.

[Krazy4Real]

My bootloader version is 2.02. I changed some things around and it boots up fine. Thanks.