I have loaded DCD's 2.3.1 and radio rom 3.27 and everything seems to work except for exchange mail. I am receiving activesync error 0x85010013.
Using same settings and SSL certificate as when the device had carriers rom on it.
Edited for version info. Using 2.3.1 not 2.2.6, and on Bell network
Found a workaround, what about a fix.
I have managed to get Exchange working, I had to check "allow Non-Provisional devices" in exchange. Does anyone know what is missing in DCD's rom, to make the server think it is Non-Provisional?
I'm having exactly the same problem with DCD 3.2.6. I don't have access to the Exchange server, so I can't use your fix. Are there any other solutions to this problem?
I had the the same problem, and had to go back to the carrier ROM as a temporary measure. Has anybody tried with DCD latest roms and/or have any ideas of the root cause of the issue?
Thanks!
I've not had this issue.
I've used several 2.x builds, all the 3.x builds, and 4.1.2
Never had this problem on exchange 2003 or 2007.
Related
Had dcd 3.1.1 installed running fine. This morning decided to upgrade to 3.1.2. Another post advised it was easy to upgrade using sprite backup (new version allows restores across dif device platforms and OS) so I wouldn't spend several hours...again...tweaking my device. Made a backup and flashed dcd 3.1.2. Installed fine and then I used Sprite to reinstall my software. Device appeared to be restored back to dcd 3.1.1 and Activesync would not connect. Sooo I figured I would start from scratch again and did hard reset. Rom is dcd3.1.2...phone works...boots....everything appears normal but still no activesync. Tried disabling 'advanced network funtionality' on device...several reboots...uninstall activesync...reinstall...etc etc...still no connection. I've searched and tried the suggestions mentioned but I'm at a loss. Does anyone have any ideas how to get activesysnc to connect. BTW...when I connect via USB I hear 'chime' and the activesync icon spins but then times out with no connection. Sorry for lengthy popst but I wanted to try and provide all info....help please!?!?
I'm having this same exact problem. On top of that since I can't get activesync to work, I can't copy the verizon carrier cab to the device and run it. I can't even run it from an SD card so I've got a brick of a phone.
I'm trying to reflash to dcd 3.0.4 verizon-specific to see if I can get a working phone. Yesterday when I tried it, I was able to go back to stock by running the relocker and all that but I can't anymore for some reason. The relocker won't work.
Well..I fixed it...sorta....reflashed 3.1.1 with SD card and all is well again...I think I borked up something when I used Sprite....not gonna do that again. Will try 3.1.2 again and tweak for a few hours.
edsai said:
I'm having this same exact problem. On top of that since I can't get activesync to work, I can't copy the verizon carrier cab to the device and run it. I can't even run it from an SD card so I've got a brick of a phone.
I'm trying to reflash to dcd 3.0.4 verizon-specific to see if I can get a working phone. Yesterday when I tried it, I was able to go back to stock by running the relocker and all that but I can't anymore for some reason. The relocker won't work.
Click to expand...
Click to collapse
if you have data you can always download it from the thread but I suppose that wouldn't work without verizon customization...hm...I was going to flash to this (sorry nochem dcd comes out with a really stable and fast rom, now about that kitchen...)
at any rate...I hope the problem gets settled
Well 3.1.1 works great...flashed 3.1.2 via SD card and back to same problem...no activesync and no data. Strange...I have the updated Alltel radio on my device. Anyone else experiencing this. I'm on Alltel
Are you installing the alltel carrier cab everytime you flash? It is REQUIRED with these roms.
gcincotta said:
Are you installing the alltel carrier cab everytime you flash? It is REQUIRED with these roms.
Click to expand...
Click to collapse
Yes...installed the proper alltel carrier cab...still didn't work. Am considering downloading 3.39 radio and see if dcd 3.1.2 will work with that radio...currently I have the new alltel radio.
Last month I posted about a problem I was having after updating from DCD 3.1.1 to 3.1.2.....I couldn't get Active sync to work no matter what I tried. At that time I was still on the new Alltel radio and I was considering trying the newer 3.39 radio. Well, a day or so after posting I upgraded to the new radio and stayed with DCD 3.1.1. Today, I tried updating to DCD 3.1.2 again (carrier cab installed BTW) but still no activesync. I'd really like to figure this out since I noticed DCD had rolled back the OEMXIPKernel and I'm assuming his future builds will be based on that....so, does anybody have any ideas on why activesync would work on 3.1.1 and not on 3.1.2....both roms cooked in DCD kitchen using identical selections. Thanks
blueglide said:
Last month I posted about a problem I was having after updating from DCD 3.1.1 to 3.1.2.....I couldn't get Active sync to work no matter what I tried. At that time I was still on the new Alltel radio and I was considering trying the newer 3.39 radio. Well, a day or so after posting I upgraded to the new radio and stayed with DCD 3.1.1. Today, I tried updating to DCD 3.1.2 again (carrier cab installed BTW) but still no activesync. I'd really like to figure this out since I noticed DCD had rolled back the OEMXIPKernel and I'm assuming his future builds will be based on that....so, does anybody have any ideas on why activesync would work on 3.1.1 and not on 3.1.2....both roms cooked in DCD kitchen using identical selections. Thanks
Click to expand...
Click to collapse
well if you mean that activesync wont connect in bootloader, then yes. i had this happen to me during reflashing. just run the RUU while the device is connected to your computer. should work fine. also, if you hard reset, make sure you let it boot before entering bootloader.
Problem solved...but i have no idea why!! I downloaded and installed the 3.1.2 ROM already cooked in the original post and flashed that. Hooked up my PPC6800 via USB and instantly Activesync saw my device and synced. Everything is working fine. Still have no idea what could be the difference as I used DCD's 3.1.2 kitchen for my cooked ROM. I did not add anything other than what was in his kitchen but at least it upgraded this time.
Hello all!
I'm running dcd 3.2.6 with 3.42.40 radio and a Titan on Verizon. The GPS was working with Google Maps with the Verizon 6.1 update, but the phone was so slow to use (and no BT ICS), so I went to dcd. Since then, I get BT ICS, and the phone is much faster, but the GPS cannot lock on any sats. Any ideas?
I'd check to make sure all your aGPS settings are correct using QPST.
Already did that, but I checked them again to confirm.
What next? Is there a CAB I need to install? Should it just work out of the box?
it should work fine. Makesure it's set for com4 in google.
Actually I got my gf a touch and it was working fine til earlier this week now its back to the slow non aGPS where we have to wait 15 mins to get a lock. and i just got a new titan and cannot get gps working on the nuerompre3 rom. Maybe they blocked it?
did you make sure the location setting was set to on and not to 911 only?
It is on COM4, and it is set for Location Only. It was working with the Verizon MR1 release...
Did you reflash back to a pre 6.1 Verizon rom first? You have to do that or MR1 breaks the GPS. Once you flash back to an older rom, then the normal update flashes for custom roms works fine.
BTC
BillThyCat said:
Did you reflash back to a pre 6.1 Verizon rom first? You have to do that or MR1 breaks the GPS. Once you flash back to an older rom, then the normal update flashes for custom roms works fine.
BTC
Click to expand...
Click to collapse
That was it! I re-locked and flashed with a stock Verizon rom, and then installed SPL 2.47, dcd 3.2.6, and radio 3.42.40 and everything works perfectly! GPS, BT tethering / internet sharing, and it's quite responsive. Thanks for the tip!
No verizon ROM, but still the same problem
Well, I've never used a Verizon ROM (I'm in Mexico city, my carrier's IUSACELL), but I have the same problem. I got GPS working with DCD 3.2.5 and after upgrading to Radio 3.42.30 and DCD 3.2.6 (same day, one after the other), I've been unable to lock onto a satellite in spite of leaving the unit in the open for over half an hour and prepping the unit with toggleGPS.
I've tried flashing back the radio and ROM to the working versions and even cooked several ROMS using PPCKitchen, to no avail. The system can open the port, does read up to 7 satellites, but cannot lock onto them.
I tried setting the GPS up with the QPST tool and Verizon settings, and got nowhere.
I'll try and relock and unlock tip that eclipse used, but maybe I'm missing something here...
any help will be mucho appreciated.
Thanks
Hey there. I found the aGPS settings for IUSACELL here (site is in spanish and the info is on post 27 of this thread). I'll reproduce them here for quick reference:
PDE IP: 207.83.200.238
PDE Port: 8888
PDE Transport: IP
Position Calculation: PDE
I've tested them using dcd radio 3.42.50 and they work like a charm
Anyone know if/how we can get them listed in the tutorial and/or included in the Iusacell carrier cab?
I know I'm a senior member..and as a senior member I should know better than to ask something nooby like this: so please excuse my noobness and help me out!
I'm considering on flashing to dcd's 3.2.6 ROM but I had a couple of questions in mind first:
1) I'm on Sprint running on Evdo Rev. A speeds, I was wondering if I'd still have these speeds after flashing to dcd
2) I read about several GPS problems after flashing to dcd..but most of them came from Verizon devices..will this happen to me if I did the same?
3) Does it have MS Office Mobile in it as well?
Thanks a lot to whoever answers me! I really appreciate it!!
Answers for you:
a) yes, EVDO-A is supported
b) The problem stems from the official Verizon update. There is now an entire section in the Titan wiki related to fixing those problems.
c) Yes, it does have Office 6.1 in it.
Hope that helps.
drnoir said:
Answers for you:
a) yes, EVDO-A is supported
b) The problem stems from the official Verizon update. There is now an entire section in the Titan wiki related to fixing those problems.
c) Yes, it does have Office 6.1 in it.
Hope that helps.
Click to expand...
Click to collapse
Helps a lot drnoir! Appreciate it, will flash to dcd tonight
So, I'm using a Verizon XV6800. I have DCD 3.3.4 and Radio 3.42.50 on it. No GPS satellites every triger when using something like "GPS Viewer."
So i saw http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
now, I was willing to try it, but none of the links work. So, what am I to do?
Did you try installing the stock rom (pre MR1) first? If your phone came with MR1 and then you flashed to DCD it will not work. You must flash back to an older Verizon stock rom, and then update to DCD.
Also check your location settings, and verify that your GPS settings are set to Com4 and hardware Com0 or None, some work with one or the other.
BTC
I have spent hours trying to fix this GPS thing. I followed this tutorial (http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix) to the letter. Everything on the phone works fine except this gps. What am I doing wrong???
-I upgraded to the VZW MR1
-Then switched to DCD3.2.5 (Radio 3.42.4)
-Then followed that above link
Nothing seems to work.
If you aren't going to use MR1, then don't upgrade to it. Downgrade back to official Verizon WinMo 6.0 stock rom, then unlock, flash to a newer radio and then flash DCD 3.2.6 and your GPS will work.
The Valhala cab thing only works if you are running MR1, if not, then you don't want to install MR1 or it will disable your GPS.
BTC
I have read so many of these xda and ppcgeek threads now my brain is spagetti. I have also come across MANY conflicting threads discussing the whole GPS issue - on a wide range of ROMS, radios etc. Is there a tutorial on how to do this?
The only reason I switched to DCD's ROM was I was hoping to get ICS working. Alls I want is a WM 6.1 ROM that will give me unrestricted use of my GPS, and ICS to work properly.
Go to Settings > System > Device Information...
What PRI (Not PRL) version are you running?
chs200123 said:
The only reason I switched to DCD's ROM was I was hoping to get ICS working. Alls I want is a WM 6.1 ROM that will give me unrestricted use of my GPS, and ICS to work properly.
Click to expand...
Click to collapse
Try my rom gps works and ICS (usb) the only conflict is mms but should be working soon
scrawnyb said:
Go to Settings > System > Device Information...
What PRI (Not PRL) version are you running?
Click to expand...
Click to collapse
Rom Version: 3.2.6
Radio Version: 1.42.40
Hardware Version: 0003
PRL Version: 51210
PRI Version: 1.35_002
ERI Version: 4
BillThyCat said:
If you aren't going to use MR1, then don't upgrade to it. Downgrade back to official Verizon WinMo 6.0 stock rom, then unlock, flash to a newer radio and then flash DCD 3.2.6 and your GPS will work.
The Valhala cab thing only works if you are running MR1, if not, then you don't want to install MR1 or it will disable your GPS.
BTC
Click to expand...
Click to collapse
Dude you are a genius!!!! Your quick instructions have finally ended a long hunt in searching for this solution. After I did what you told me, I have both blazing fast GPS connectivity, and fully working ICS. I want to mention a few things in case anyone else runs into the issue I did.
First, after I successfully downgraded, and then reinstalled DCD’s 3.2.6 (radio 3.42.50 & PRI 1.35_002), I did NOT follow the instructions to enable AGPS. I dont know if this is being overlooked somehow on all these forums, but after I installed my carrier cab, with DCD’s 3.2.6 ROM, everything worked as is. There was no need to install anything else. Also keep in mind, that I did exactly as BillThyCat instructed, and that was flashing directly from the stock WinMo 6.0 (no MR1 update) to DCD’s 3.2.6.
If I read your last response correctly, it sounds like you did not do the aGPS fix afterwards. It's not a requirement, but it will get you 15-20 second GPS locks almost every time you try. It's well worth it.
Glad you got everything else working tho. Your issue is a pretty common problem. With most carriers you want to load their latest stock rom then upgrade from, however Verizon being the bastages that they are, lock the GPS down. There have been a few work arounds found, named the Valhala cab, however if you are going to run a custom rom anyways, why even mess with all that. Just use a custom rom and work.
BTC
Yes, I did not do the AGPS fix posted on that wiki site. Im not sure I understand why doing that AGPS fix would give me 15-20 second GPS locks, when I have like 8-10 second GPS locks now. Perhaps the magic is just in the latest radio. Either way, I'm happy with the way it all worked out.
When I first programmed my phone I would get syncs instantly one day and 10 minutes or more the next. If you are consistantly getting them in 8-10 seconds don't mes with anything, just keep in mind if that nice feature goes away that aGPS is available in the future.
BTC