more on non-functional voip. even if my sip settings (under voip setup) are incorrect, I should be seeing a line in the today screen that says it is searching for my provider (when my wifi is on). this is not happening... nothing is showing up... even though I have internet calling checked on the today items. could someone please look into this?

Glad I could help, and awesome job on the OEM -- about to test it out here... :headbang:

Just to check though on putting the registration key into the registry -- The value of "Application" is different on my PPC, using Pocket Plus 4.0.1. You said:

"Application"=dword:a9401b68

But I've got:

"Application"=dword:a938e898

It's just a guess, but it may be the case that the value of Application actually comes from some calculation based on Owner Info, and that your registration code will only work with the correct value here as well.

Not sure if it makes any difference though. FWIW, I'm going to test using my value instead of the one in your post. I'll post here again if I run into any problems.

Cheers, and thanks again!
-Jake

The today plugin only works for GSM phones. You're on a CDMA network.
The only indication that it's "on" is that you will see your VoIP server name in the dialer instead of your carrier.

ok, thats good to know... but it seems it doesnt appear in my dialer either. i have checked there since i have read (from xda developers) that it is in fact supposed to function within the normal dialer. but in my case, even with wifi on, bluetooth off, sip settings correct, it never is available. has anyone gotten it to work via wifi on a cdma phone?

LennySh and I have both had it working fine. You need to make sure the setting to enable it is actually sticking in the VoIP Setup app.

I was using VoIPcheap.com which he also tested along with another provider (can't remember which he has).

the setup is sticking. so i guess i am at a loss. i am able to connect just fine if i use a service like Fring... but i would rather use the WM6 native voip. maybe you can point me to a document that clearly outlines what i should be doing to make it take? it would be nice if the VOIP setup program had a "test settings" function to tell me if the problem is there or elsewhere. unfortunately, the native system is not reporting anything.

SPB Plus: You are probably right
 

You are probably right, I use the same Owner on my wife's and mine phone for that kind of issue, also i notice if I left that in the OEM the trial expired immediately so it could be a date code also... It has been SO long since I origianlly purchased SPB plus that I can't rememember if they asked for Owner field.

I guess to be sure one would have to quickly bake with my OEM, then Install from cab, register, then record what they found at that registry setting, then add that info to their RGU and bake again. Luckily for me :) I have that hahahaha....

--ajgalbraith98

I want to say thanks to everyone who worked on the wm6 upgrade and the kitchen, I really appreciate your work in bringing this update to those of us who love our phones but our carriers don't.

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.

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 ?

Thought I'd post this here...I'm loving this rom but just one issue... hopefully this will be a simple fix for someone here. I cooked my first rom(s) --serveral tries to get it just right. I seem to have lost the ability to 'back out' of a menu by pressing left on the d-pad. This used to close any menu on the screen but now the menu will stay until i either press the soft key again or physically close it with the stylus. I had no idea how such a simple movement sped up my use of the phone till it was gone. I know someone here can help me get it back... i'm thinking this may be a job for a rededit but my searching has turned up nothing.

Thanks in advance, awesome work on the latest kicthen!

I seem to have an odd issue with typing. When running WM5, my typing was fine. But with WM6, it seems that characters get missed, or the wrong character is entered sometimes. There also appears to be a slight delay when texting. It also happens when running Skype on the XV6700. Anyone else experience this?

I previously used a self signed cert on my exchange box, and ran into all sorts of head aches. I am not sure how to fix the problem you are having, but I can tell you that GoDaddy's $20 per year SSL cert is the best $20 you could ever spend. Especially if you are supporting multiple people using WM5 or WM6 with direct push. I have users that are using Motorola Q's and self-signed certs are terrible when trying to make a Q happy.

Certificate issue mainly happened on WM5 Smartphone device (correct me if i am wrong). I think there are 2 ways to load the certificate onto your phone.
1. Load certificate with the certificate loader (you can download certificate loader from Microsoft website) http://technet.microsoft.com/en-us/l.../aa997575.aspx
2. Load certificate manually by using cab method. http://blogs.msdn.com/windowsmobile/..._cab_file.aspx

However, your problem looks like you can load certificate, but you are loading the wrong certificate onto your phone. Maybe try to request a new certificate and load it again? Sorry I am not expert on this... :(

just cooked my rom, and my nice simple boot screen turned green :(
anyone know what i can do to fix the color issue?

you can post (or pm) the bootscreen file you used for me to analyze.

ive noticed it has happend to someof my bootscreens also including the apache ones in the rom. part od them, like a specific color in the pic, turn to a lime green.

already in my post. i used gimp to make the image, and its a png when i choose it. do i need to change it to a .nb?

seems like no matter what i design... simple or not, the splash screen comes out looking like crap.

Your image is the wrong size. It should be 240x320 (for boot splash), or 320x320 (for main splash).

Provide an example of simple, edufur.

Thanks for the try guys! I figured it might be an easy registry fix like wm5. I tried updating the self-signed last night before posting, I even double check ed that it was a certified trusted root , right from the server, but still no good. I guess I gotta convince the company to buy certs, or just go back to 5.

Not sure if this helps but I have VoIP working (well, sort of working) with voiptalk.org.

I selected "whenever available" for "outgoing calls using VoIP", and the "Enable VoIP over 3G" option is checked. Once these two options and the SIP settings have stuck (i.e. after a reboot the options I chose are still entered), I can see that voiptalk appears in the dialer screen when the data connection is alive. If the data connection is not alive, I see the regular Sprint graphic.

When voiptalk is visible I can dial the test numbers and can confirm that both incoming and outgoing codecs work with two caveats:

- the audio comes from the rear speaker of the device
- the audio is too quiet to be usable.

Voiptalk.org offer a free trial (you get 20p credit). With this you can dial the test numbers, test incoming calls, etc.

Guru, It happens even if I use the htc.nb that is included in the Kitchen. If I use the splashimage converter to just VIEW the file in the buildos\splashimages\QVGA folder, it looks fine. However, if I use the splashimage converter to VIEW the file in the buildos\temp folder after the ROM is built, it has the green artifacts in it. That is my example of simple. If I use something nicer like a photo, it almost looks like a photo negative the output is so bad.

Has this issue been resolved yet?
 

Sorry if I missed this, but has this bluetooth issue been resolved yet?
I also use bluetooth quite often - mostly in the car - and have had my bluetooth shut off (but the call remain live) with my hands free Raytel 4200.
Any and all help would be appreciated. THanks in advance.

i have never had bluetooth problems in the phonecalls. i have had skipping issues with bluetooth stereo, but it seems everyone has that. if you are getting lost connections with phone call links, you may want to try a different headset. i am assuming you have already been through all the re-pairing business... so another headset might be worth a shot.

Here's my report:

Fixed Bugs:
- Final message "error downloading rom"
- When I include my old mms 3.0.6.24 appear the file exists error (not anymore!)
- Live messenger hangs when I forward a email with attached file, having htc today in any version installed
- Skipping mp3s when played from miinisd onto wmp
- Standard RUU generating a country error code when choose movistar venezuela
- Ir file transfer pc-pda (I guess, not yet tested)
- Drainy battery (still with bluetooth, wifi, ir and beam off, I hope)

Still Bugs:
- Newer MMS applet not invoke camera from inside (I guess that I'ts not made for apache)
- Additional -4 hours on displayed time (have to syncronize with network and soft reset)

Recently observed bugs:
- When first time buildos run, generates a carrier error, when saved the own selections, closed and open again, the error goes away
- Standard RUU generates a application error when launching and choosing next when run on vista, solution: goto upgrade/ruu and make ROMUpgradeUt app compatible with xp sp2
- Recording a video at 320x240 and zoom 2x in a sunny day at minisd produces a interlaced ugly random horizontal bands and get recorded too Solution: With a registry editor make the following:
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class
SingleBlockWrites 0x1 (non extisting dword)
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass
SingleBlockWrites 0x1 (non extisting dword)

That's all for now

Looks like that have fewer colors than original, (256 or 8 bits), just a matter of conversion

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

Awesome, thanks !!!

Im using arcsoft 4.2.8.1 and seems to work fine. when you say, wont invoke camera, if i open MMS, new, ten tap the place to put a pic, then click the little camera, my camera does open.

And about the video, i was having that problem too, but only when i saved to my memory card, if i saved to the phone it worked fine. So those make it so i can record to the memory card, does it change anything else about the memory card, write/read time stuff. I run some programs off my card sometimes so just curious. thanks!

ok the only issue i have found with this is the following:

when triing to send a text message I get the following error
Error Class: Permanent
Cause Code: SMS Org.D.
Delivery Failed

when triing to send MMS message I get the following error
Error
Originator Address Not Found

I would apprecate any help on this please.

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.

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 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.

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.

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.
:???:

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...

From the "New BuildOS" thread.

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

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!

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.