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

[guitardoc64]

Originally Posted by gguruusa

The next release will be WM6.1. PPCgeeks_OEM will be updated at the same time.

We'll probably re-release WM6, unchanged other than to work with the latest buildos.

All I can say is-Yesyesyesyesyesyes!!!!!!

[delosky]

Originally Posted by sntehran

I installed cyberon voice commander 2.0. lunching the app with the bluetooth button doesn't work. Is there a way to do this by modifying the registry or any way to get this to work?

I'm having the same problem. Can Cyberon VC 2.0 be launched from a BT headset or will I need to downgrade to Voice Dialer?

[GundamWZero]

Guys I am sorry.

You guys made this SO hard. I got another PPC (phone is still under warranty) and I an trying to upgrade the phone again. The first time I did this, it was a simple install. Now, as I read the tips, it tells me to unzip the Apache Helmi WM6 .rar file, but the walkthrough says not to. I cannot unzip the Apache Helmi .rar file, it requires a password, and the Apache Helmi PPC-BuildOS shortcut will say that the OEM.rar file and its modules cannot be found. I believe that this was the reason why my last phone was stuck in bootloader mode; none one the packs were opened to load the necessary files. I'd sure like to have some help on this one. I don't want to do this and screw up this phone.

[GundamWZero]

Well. it took me all night and I got the Build OS to work, but I get the "error building file system". The last string says, "Compiled Size (0x395ffc)) greater than Max Rom Size (0x38e5800). Is anyone available to help? Or do I have to wait another month?

[fredcatsmommy]

Originally Posted by GundamWZero

Well. it took me all night and I got the Build OS to work, but I get the "error building file system". The last string says, "Compiled Size (0x395ffc)) greater than Max Rom Size (0x38e5800). Is anyone available to help? Or do I have to wait another month?

First, I'd take a deep breath and tame it down a bit. Speaking for myself, I'm always happy to help without the sarcasm. As for your "compiled size" message, it just means you tried building too much into your rom. Until the new kitchen comes out (soon it is rumored), you'll just have to try building with the programs you want, and if it's too big, take out an OEM at a time. At least that's what I've done in the past. Also, you might want to check the list that has the size of each of the OEMs in the kitchen; I think there's a link somewhere near the first post. Once you've played with it a while, you'll be laughing at yourself. Have fun!

[GundamWZero]

Thanks guy....let me try that. Just before you posted, I finally managed to reboot the stuck phone. So I will test the software on it before I send it back to Verison, and put the final product on the new phone.

[GundamWZero]

Managed to get the program to work, however, when I tried to upload the new OS to my phone, the RUU stopped working. I tried to fix it by following a guide from http://www.modaco.com/content/Window...ltimate-guide/ , but it still won't work; the RUU still stop working. At least I now can recover a stuck bootloader.

[GundamWZero]

I tried numerous ways to get this to work....and each time I run into that RUU stopped working issue.... I thought someone found a way around it but I guess no one has yet. This is starting to be a very big waste of time.......

[guitardoc64]

Originally Posted by GundamWZero

I tried numerous ways to get this to work....and each time I run into that RUU stopped working issue.... I thought someone found a way around it but I guess no one has yet. This is starting to be a very big waste of time.......

You'll have to give more info, like posting the logfile with the errors instead of just saying "it didn't work".

[GundamWZero]

Man I can't even FIND the build log anymore. I had to hard reset the phone three times already and the new OS wasn't installed.
Where is this log file? Now when I use try to get the device data, it won't even let me do that!!!