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

[schettj]

Originally Posted by obsidian440

To be more specific, without the registry change, I get a message stating the server is the wrong name, with the registry it just tells me the certificate is wrong. I have checked all date/time settings on both my server and my phone, both match exactly. I have full access to the exchange server and phone. Any ideas ? Are there any new registry tweaks that can be done ?
Or is this just a case of having a self-signed cert and I should buckled down and buy a real one ?

Did you select the enterprise protocols OEM? I have no idea if it comes into play there or not, but its something to try - I use a self-signed cert for ssl via email/imap, and my ROM build (with that oem included) was able to handle it as usual by popping up the warning and proceeding when I hit OK.

[bobonit]

Originally Posted by gguruusa

Thanks, that was just the data I needed. A fixed BuildOS will be available shortly.

Just Downloaded BuildOS 071120 Build, images come out the same. See attachments. First attachment is from buildos/splashimages/qvga, second is from buildos/temp just prior to flashing phone.

[StarDestroyer]

Originally Posted by obsidian440

That said, I'm having trouble getting my direct push to work again with my exchange server. We are using 2007 with a self-signed ssl cert. On wm5 I was able to use the registry changes along with importing the cert manually to make it work. With my new upgrade I am now getting the message "server cert is wrong". I was unable to find any real answer searching google and these forums. I have tried to manually import the cert and doing the registry change but I'm still running into the same problem.

I run Exchange 2003 and use CAcert for my certificates. Unfortunately, CAcert's root certificates aren't included in mainstream browsers or in Windows mobile by default. So I found a way around it... I found instructions on an MS blog about how to create a .cab file for importing a certificate. I also managed to make an OEM for the CAcert root certificates. You can either sign up with CAcert and put one of the certificates on your exchange server or use the instructions to create a .cab or OEM of your self signed cert and try that... I am using the OEM method successfully on the latest kitchen.

[tr2518]

Is anyone having problems when running S2U2 .85? It seems to cause issues for me like the phone answering on it's own after one ring and the speakerphone turns on. I went back to version .83 and it seems to have fixed the problems I was having.

[Trident]

Originally Posted by bobonit

Just Downloaded BuildOS 071120 Build, images come out the same. See attachments. First attachment is from buildos/splashimages/qvga, second is from buildos/temp just prior to flashing phone.

Where are you guys getting build 071120 from?
This is the second post I've seen mentioning a build out today, but I don't see anything after 071117.

[hefman]

Originally Posted by tr2518

Is anyone having problems when running S2U2 .85? It seems to cause issues for me like the phone answering on it's own after one ring and the speakerphone turns on. I went back to version .83 and it seems to have fixed the problems I was having.

I haven't had those problems, but I have had trouble with .85 occasionally reverting back to a short (10s) backlight delay. I also sometimes get a blank screen after unlocking, but that might be something else.

Oddly enough, I just installed PhoneAlarm and the backlight problem seems to have gone away. Go figure...

[bobonit]

Originally Posted by Trident

Where are you guys getting build 071120 from?
This is the second post I've seen mentioning a build out today, but I don't see anything after 071117.

From the "New BuildOS" thread.

[obsidian440]

Originally Posted by schettj

Did you select the enterprise protocols OEM? I have no idea if it comes into play there or not, but its something to try - I use a self-signed cert for ssl via email/imap, and my ROM build (with that oem included) was able to handle it as usual by popping up the warning and proceeding when I hit OK.

I'll give this a shot, didn't even notice it when I was building the OS.

Originally Posted by StarDestroyer

I run Exchange 2003 and use CAcert for my certificates. Unfortunately, CAcert's root certificates aren't included in mainstream browsers or in Windows mobile by default. So I found a way around it... I found instructions on an MS blog about how to create a .cab file for importing a certificate. I also managed to make an OEM for the CAcert root certificates. You can either sign up with CAcert and put one of the certificates on your exchange server or use the instructions to create a .cab or OEM of your self signed cert and try that... I am using the OEM method successfully on the latest kitchen.

This is just another way of adding the cert into the phone right ? Because I have had success in past versions by just dumping the cert onto my SD card and then opening it in file explorer. I checked where it installed on the device and it was put into the trusted root certs.

I moved back down to the 3.5 AKU but I'll give it another shot today. Gives me an excuse not to answer emails at night!

[hefman]

Originally Posted by bobonit

Just Downloaded BuildOS 071120 Build, images come out the same. See attachments. First attachment is from buildos/splashimages/qvga, second is from buildos/temp just prior to flashing phone.

I have this problem with pretty much any color picture I try to use (.nb or .png). Greyscale screens convert fine though (I'm using the ApacheAndril screen).

It seems like the patchlogo converter is somehow mishandling the color pallette in its conversion. Don't know what would be different about it being embedded in the BuildOS though...

Haven't tried the new BuildOS yet though. I'll test it shortly.

[gguruusa]

Originally Posted by hefman

I have this problem with pretty much any color picture I try to use (.nb or .png). Greyscale screens convert fine though (I'm using the ApacheAndril screen).

It seems like the patchlogo converter is somehow mishandling the color pallette in its conversion. Don't know what would be different about it being embedded in the BuildOS though...

Haven't tried the new BuildOS yet though. I'll test it shortly.

Try with the latest BuildOS. If it still fails, post the file it fails with for me, please.