I noticed that myself and a few other people are having problems getting a quick lock (or at all) over the past few days. It took me a few minutes today to get a lock and I am wondering if anyone (GC you still out there?) can test if the aGPS server was changed or if there is a reason this is different. I went through and nothing has changed for me.
I am willing to reflash to test but wanted to see if anyone on verizon could verify problems or an IP change for the server.
I noticed the same thing today..Took a long time.
I had problems too yesterday. Later towards the day I got it real fast again. Today still fast. Glad to see I wasn't the only one.
What is the current IP for the QPST method fix?
I tried the tutorial by GC14 for the first time, today, and I couldnt get a lock at all
Was is the same issue you guys had? Or did I do something wrong.
I have now tried this with a DCD rom/radio and the MR1 rom/radio, both gets no fix at all, and I tried it outdoors in open area away from buildings.
Whats the deal? (and what's the current IP please)
Thanks
I noticed it yesterday (3/4) but I just saw this thread and figured I would try it again. Got a lock in 3secs.
As of yesterday I can no longer get GPS locks at all. No matter what the application they sit there waiting for the GPS forever. Before yesterday it would work flawlessly and under 5-10 second locks. now .. nothing.
Anyone else still having trouble?
Also, does anyone have a link to any updated configuration requirements, such as the newest IP, etc? I can't find the instructions page on the wiki.
Thanks!
Soft-reset your phone.
No problems here, usually in under 10 sec
abuttino said:
Soft-reset your phone.
Click to expand...
Click to collapse
That is always the first thing I do after checking settings for any problem. I have been around for a while and try not to start threads unless I believe that it may be a situation that is not just me floundering around. I saw some other people complaining here and on PPC geeks about how it seemed that aGPS wasn't helping to lock, and it was confirmed by a few, for whatever reason.
I think it may have been a regional problem, or something to do with the towers that was isolated to the past couple of days. Today this evening it was back to normal.
Things have changed a bit after VZW picked up Alltell towers. Someone correct me if I am wrong, but VZW was previously paying Sprint or other providers to use their towers and then picked up Alltell towers that had some of the same coverage, VZW discontinued paying Sprint to borrow the signal for that area even if the Alltell signal is weaker.
I have driven an hour to work for seven years and days after the acquisition there are new dead spots in places that always had great reception, now it drops like clockwork in the same exact spot. It may be that the technology for those towers are being upgraded and they are working out some of the bugs, but what do I know.
HELP - No satellites, no lock, nothing!
ARGG! Someone please help. Here is the deal...
I have a Verizon Titan, and was running DCD 3.2.6 with 3.42.50 Radio. I decided I wanted to try the MR1 Verizon stock rom, so I upgraded to it and it's included radio. Then I did GC14's QPST tutorial for Verizon on his wiki page. It found satellites in TomTom, but would NEVER get a lock. I didn't like it, and the ROM was kinda slow anyway, so I flashed back to the previous DCD 3.2.6/radio setup.
I now do not even get an attempt at connecting. When I run TomTom is just searches for satellites for ever, but never even finds one. So I am not even finding the satellites, much less locking on. What happened? Before I did any of this I would gte a lock in about a minute or two. Now I cannot even find satellites!
HELP
Hmm, I misread your first post, I swore I saw you say you had Qwest, oh well.
Anyways, install an older Verizon rom that was pre-gps and then go thru the normal steps to unlock, and update the phone. Never install MR1 or MR2 again unless you want to have to do this all over again.
MR1 and MR2 both disable GPS via a PRI update that prevents any non authorized app from accessing GPS, tho there is a tool you can add that will allow some gps apps to work, but it only works if you leave MR1 installed, if you downgrade back to 3.2.6 without following my instructions above, then it won't work, period.
BTC
BillThyCat said:
Hmm, I misread your first post, I swore I saw you say you had Qwest, oh well.
Anyways, install an older Verizon rom that was pre-gps and then go thru the normal steps to unlock, and update the phone. Never install MR1 or MR2 again unless you want to have to do this all over again.
MR1 and MR2 both disable GPS via a PRI update that prevents any non authorized app from accessing GPS, tho there is a tool you can add that will allow some gps apps to work, but it only works if you leave MR1 installed, if you downgrade back to 3.2.6 without following my instructions above, then it won't work, period.
BTC
Click to expand...
Click to collapse
Quest? hmm, no not me, been Verizon for the past 5 years.
Anyway, I relocked and downgraded to the 2.09 stock verizon ROM and old SPL. Now, I upgraded to the 3.42.50 radio and 3.2.6 DCD ROM. I discovered that there is a new TomTom version out, so I am currently aquiring that with new maps and all, but is there a program I can use NOW just to see if I get a fast GPS fix? one that doesnt have maps or anything, just a satellite status application basically?
-thanks, crobs808
I remembered I could use GPS Tuner, so nevermind on the request. I will post what happens after I figure out the new TomTom 7.915
Holy Flippin Cow!
I have a GPS fix deep inside a building, lol. WOW. Thanks everyone for the help, you guys are truly amazing at what you do, and give without reward. Thank you
Now using Tomtom 7.915 with USA+Canada maps 825.2159
crobs808 said:
Holy Flippin Cow!
I have a GPS fix deep inside a building, lol. WOW. Thanks everyone for the help, you guys are truly amazing at what you do, and give without reward. Thank you
Now using Tomtom 7.915 with USA+Canada maps 825.2159
Click to expand...
Click to collapse
GPS issues are resolved for me too, and the new Tomtom is faster.
Related
I installed the dcd 2.1.0 verizon rom with the v3.27.0 radio (following these instructions:
http://www.phonenews.com/how-to-add-gps-to-htc-mogul-xv6800-p4000-titan-2663/)
and everything went fine but now my device is freezing up and generally not acting healthy. Can anyone vouch for this set up and/or recommend the best current rom for verizon? Im not too concerned with having GPS available (but would be nice), I would really like to have a nice no junk rom above all else. Thanks for any advice.
I haven't had good luck with any of the gps/reva roms on verizon... Seems every rom combination has it's share of quirks/bugs it's just a matter of finding the one that has some u can live with
I'm yet to find one that is FLAWLESS... if you find one let me know!
I have flashed several VZW xv6800s. If you have the 3.35 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Edit: sorry guys, was not thinking as i typed. I meant 3.35 radio (the one from the sprint update). Flash the 3.35 or 3.37 radio!
I would suggest using the latest ROM as well. Seems to have made a difference with battery life to me.
mdjkim said:
I would suggest using the latest ROM as well. Seems to have made a difference with battery life to me.
Click to expand...
Click to collapse
interesting how u guys on vzq have no problems with the reva radios... I was running 3.0.4 for quite a while until I finally canned it because I couldn't deal with apps crashing when switch to other procs... I went back to 1.7 to see if there was a problem there too but everything runs good it seems... am having bluetooth problems locking up device sometimes though so now I'm back to vzw stock radio to see if that fixes things? Actually I have no idea if bluetooth would be affected by radio or not but I'm desperately trying to find a stable setup.
I have flashed several VZW xv6800s. If you have the 3.27 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Click to expand...
Click to collapse
This is VERY bad advice and will only screw your phone up even more. It says in numerous places on these boards that 3.27 radio is NOT compatible with 3.x.x roms. The only roms that will work with the 3.27 radio are the 2.x.x roms.
My question to you though is why on god's green earth are you still wanting to run a 2.x.x rom with the old crappy buggy beta radio 3.27? Just update with the alltel updater to get radio 3.37.20, don't let customizations run, then flash dcd 3.0.4...much much better and will probably fix your gps problems.
corey113888 said:
I have flashed several VZW xv6800s. If you have the 3.27 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Click to expand...
Click to collapse
Danger!
radio 3.27 is NOT compatible with dcd 3.0.4 rom!!!
1) radio 1.30 or radio 1.40 = use dcd 1.7 (non gps rom)
2) radio 3.27 radio = use ONLY dcd 2.x.x series roms (with gps , revA - experimental)
3) radio 3.37 radio = use dcd 3.0.1 or 3.0.4. (gps and revA official)
my recommendation would be option 1 or 3. Depending on whether you want gps or not.
Zenoran said:
interesting how u guys on vzq have no problems with the reva radios... I was running 3.0.4 for quite a while until I finally canned it because I couldn't deal with apps crashing when switch to other procs... I went back to 1.7 to see if there was a problem there too but everything runs good it seems... am having bluetooth problems locking up device sometimes though so now I'm back to vzw stock radio to see if that fixes things? Actually I have no idea if bluetooth would be affected by radio or not but I'm desperately trying to find a stable setup.
Click to expand...
Click to collapse
Zen,
I think you might be the victim of a dodgy titan. I was, like you, using 1.7 for the longest time because I couldnt put up with the buggy 3.27 radio. So i just stayed non gps until the new radion 3.35 came out and dcd released 3.x.x series of roms. Since then I bit the bullet and went back to gps rom. I didn't look back. So far dcd rom 3.0.4 + radio 3.37 (alltel) has been the best (i.e reliable) rom setup I have experienced since I was on dcd 1.7.0. I think they are both equal now, except that I have gps enabled now and I dont need to carry my gps with me all the time.
The internal gps does SUCK the battery down kinda fast, but it is reliable. No bluetooth issues that I can see except that call quality is still sub-par but at least it connects without any trouble. If I am using the gps function in the car i use my BT gps because the BT radio uses a lot less juice than the internal gps receiver.
I have VZW just like you and gc, az clown etc and we all have similar good experience with the new setup. So the only other thing I could say about your titan problems is that it must be hardware. Try stock again and see if it clears up the problems then I would say that my reading of your situation is wrong. But from what you have said it seems right.
maccaberry said:
Zen,
I think you might be the victim of a dodgy titan. I was, like you, using 1.7 for the longest time because I couldnt put up with the buggy 3.27 radio. So i just stayed non gps until the new radion 3.35 came out and dcd released 3.x.x series of roms. Since then I bit the bullet and went back to gps rom. I didn't look back. So far dcd rom 3.0.4 + radio 3.37 (alltel) has been the best (i.e reliable) rom setup I have experienced since I was on dcd 1.7.0. I think they are both equal now, except that I have gps enabled now and I dont need to carry my gps with me all the time.
The internal gps does SUCK the battery down kinda fast, but it is reliable. No bluetooth issues that I can see except that call quality is still sub-par but at least it connects without any trouble. If I am using the gps function in the car i use my BT gps because the BT radio uses a lot less juice than the internal gps receiver.
I have VZW just like you and gc, az clown etc and we all have similar good experience with the new setup. So the only other thing I could say about your titan problems is that it must be hardware. Try stock again and see if it clears up the problems then I would say that my reading of your situation is wrong. But from what you have said it seems right.
Click to expand...
Click to collapse
Well, that's the thing.. when I go to stock everything I have no problems but am stuck with crappy wm6.0... I don't mind not having the gps so much but it def would be nice... However, I do hate having to run an older rom that isn't community-supported any longer due to newer releases...
I think my problem with 3.0.4 might have been the way I flashed the radio.. I was one of the original ones to actually get the dcd released radio installation to work and hadn't really looked back.... im wondering if maybe that was the problem... I might consider trying the sprint rom method to get the radio and then trying 3.0.4 again...
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Click to expand...
Click to collapse
Now I'm not saying I condone this, but man...there are definitely ways to get warranty replacements even if everything works fine...
Just need to "screw things up" on your own Make it so your phone won't boot, bring it to a vzw tech center...cuz they won't know what the hell is wrong with it trust me...and bam they'll swap it out.
Edited my original post...
Also, i have had 2 replacement xv6800s. One was for white spot in the bottom left part of the screen. I had to call VZW and tell them they were out of replacements at the store. The other was replaced a week later for data not working.
Zenoran said:
Well, that's the thing.. when I go to stock everything I have no problems but am stuck with crappy wm6.0... I don't mind not having the gps so much but it def would be nice... However, I do hate having to run an older rom that isn't community-supported any longer due to newer releases...
I think my problem with 3.0.4 might have been the way I flashed the radio.. I was one of the original ones to actually get the dcd released radio installation to work and hadn't really looked back.... im wondering if maybe that was the problem... I might consider trying the sprint rom method to get the radio and then trying 3.0.4 again...
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Click to expand...
Click to collapse
Zen,
go the 'official' route from stock. olipro 2.40. sprint 3.35 official (without allowing customizations) then flash dcd 3.0.4. If you still then have problems then we can isolate your flash before as a potential problem.
if you still have all the same issues then i really think its time for a new titan. If all is well then you can finally relax and enjoy the device.
Good luck
maccaberry said:
Zen,
go the 'official' route from stock. olipro 2.40. sprint 3.35 official (without allowing customizations) then flash dcd 3.0.4. If you still then have problems then we can isolate your flash before as a potential problem.
if you still have all the same issues then i really think its time for a new titan. If all is well then you can finally relax and enjoy the device.
Click to expand...
Click to collapse
Ya, I actually did the Sprint Flash this time around and things seem to be working better, to my surprise... Things seem to be running a lot better now compared to the radio hack I was using before... I imagine that's the reason dcd killed that link off the forums... although it didn't brick my phone, it obviously was crippling my device quite a bit.
Only thing that worries me (somewhat) about the sprint rom was that it changed the bootup screen (pre os load).. it's now black screen with red lettering showing versions... I have NO idea how that can be reverted back if I ever need to have this thing serviced. That sprint rom appears to totally changed the device.
Zenoran said:
Ya, I actually did the Sprint Flash this time around and things seem to be working better, to my surprise... Things seem to be running a lot better now compared to the radio hack I was using before... I imagine that's the reason dcd killed that link off the forums... although it didn't brick my phone, it obviously was crippling my device quite a bit.
Only thing that worries me (somewhat) about the sprint rom was that it changed the bootup screen (pre os load).. it's now black screen with red lettering showing versions... I have NO idea how that can be reverted back if I ever need to have this thing serviced. That sprint rom appears to totally changed the device.
Click to expand...
Click to collapse
Flashing of the pre-windows boot screens (i.e. the ones that show up around the time that the red lettered rom versions appear) are not part of the rom. You can't modify them with dcd's kitchen.
There are three options that you have.
1. You can create a mini rom with the splash screens in it that you can flash to the device. I dont know how to do it and dont really care to find out, but gcincotta knows how to do it and posted instructions a few days ago in another post. He can tell you how to do it.
2. You can use the ppcgeeks kitchen to create boot screens and then flash your dcd rom over the top.
3. Flashing a stock verizon, sprint, alltel etc rom will contain the splash screens and put them back on along with the correct (stock) radio and roms. Then you can take your very clean 'stock' titan back to the store for repairs or replacement without fear.
maccaberry said:
Flashing of the pre-windows boot screens (i.e. the ones that show up around the time that the red lettered rom versions appear) are not part of the rom. You can't modify them with dcd's kitchen.
There are three options that you have.
1. You can create a mini rom with the splash screens in it that you can flash to the device. I dont know how to do it and dont really care to find out, but gcincotta knows how to do it and posted instructions a few days ago in another post. He can tell you how to do it.
2. You can use the ppcgeeks kitchen to create boot screens and then flash your dcd rom over the top.
3. Flashing a stock verizon, sprint, alltel etc rom will contain the splash screens and put them back on along with the correct (stock) radio and roms. Then you can take your very clean 'stock' titan back to the store for repairs or replacement without fear.
Click to expand...
Click to collapse
Interesting.. I've never seen that changed other than this sprint rom... the stock VZW rom images I have just do the OS and Radio separately... I guess when/if I run into a situation where I need to revert back I'll worry about it then.. Until then, the newer boot screen is def cooler
gcincotta said:
Now I'm not saying I condone this, but man...there are definitely ways to get warranty replacements even if everything works fine...
Just need to "screw things up" on your own Make it so your phone won't boot, bring it to a vzw tech center...cuz they won't know what the hell is wrong with it trust me...and bam they'll swap it out.
Click to expand...
Click to collapse
gc, this is so true. The 'techs' at the verizon stores (bless their hearts) know nothing at all about the titan. you could go in there with a fully "sprintized' titan and seriously they wouldn't notice.
I found this out the first time I tried to flash. I thought I had bricked the device and took it to the "service center" verizon store near my location to get the data back working (yeah that's all the problem was, but I was a noob and didnt know better). They didnt have the slightest idea what to do to solve the problem. They screwed around with it for a while and gave it back, basically the same. they offered to switch it out for me, but I said i will try just a bit longer (and it had a customized 'colonel - ppcgeeks' rom on it - if you have ever seen one it is completely unmistakable - looks nothing like a verizon rom).
I went outside, called *8899 and got a service support tech to fix the phone over the air. The problem had just been the data account needed to be reset at their end. Not only did the guys in the store have no idea how to fix it, they didnt even notice that my device was clearly not stock.
Zenoran said:
Interesting.. I've never seen that changed other than this sprint rom... the stock VZW rom images I have just do the OS and Radio separately... I guess when/if I run into a situation where I need to revert back I'll worry about it then.. Until then, the newer boot screen is def cooler
Click to expand...
Click to collapse
Yeah, if you do the flashes separately the boot screen never change. I still had the original verizon boot screens until just recently when I did the upgrade to dcd 3.0.4. Its the running of the sprint installer that overwrites your verizon splash, not the rom or the radio themselves.
Anyway, i used the dcd kitchen to create my 3.0.4 rom and selected HTC animation. That creates a HTC splash to overwrite the sprint stuff, and then I did this and this and my machine looks sweet when it boots.
The instructions of how to load them is explained in the thread http://forum.xda-developers.com/showthread.php?t=379822
Enjoy. (I cant post pics of the screens because the xda database is busted at the moment)
Hi
whenever i open google maps and enable GPS
it'll stay as "seeking GPS satellites (0)" for like 5 minutes.
After..it'll say "GPS Active (0)"
well how can it be active if it's 0?
2 seconds later it goes back to the seeking message.
The weird thing is...when it says "GPS Active (0)" it brings me to random places in my city. Meaning it DID detect something, but then lost it immediately again.
i read the GPS guide and did whatever it said already. I had the GPS working a few weeks ago...now it's not working...even after reflashing with different ROMs.
Any help?
I am also unable to get a lock. I have Alltel and today I have tried going all the way back to stock and tried everything from 3.35, 3.39 and now I am back at 3.37 trying out ppcgeeks Titan_3.49. Everything is working great except no GPS. Using the GPS Viewer if I do a scan it does find the GPS radio on com4 but when I start it I never get a lock. I have also tried using BAF's and QuickGPS. Anyone have any idea how to get this working. At one time a while back I did have GPS working on this device.
Thanks,
mr.ellsworth
edit: I forgot to mention I also have tried out several of the differnt kitchens today in my quest to get the GPS working again including dcd 3.1.2
mr.ellsworth said:
I am also unable to get a lock. I have Alltel and today I have tried going all the way back to stock and tried everything from 3.35, 3.39 and now I am back at 3.37 trying out ppcgeeks Titan_3.49. Everything is working great except no GPS. Using the GPS Viewer if I do a scan it does find the GPS radio on com4 but when I start it I never get a lock. I have also tried using BAF's and QuickGPS. Anyone have any idea how to get this working. At one time a while back I did have GPS working on this device.
Thanks,
mr.ellsworth
edit: I forgot to mention I also have tried out several of the differnt kitchens today in my quest to get the GPS working again including dcd 3.1.2
Click to expand...
Click to collapse
I'm not sure if this will help - but I recently discovered that if ActiveSync is running while you are trying to get a lock - it will not lock. Stop ActiveSync with task manager and try again. I've been doing this for the last three days and get a lock every time now.
Try a free diagnostic's app such as VisualGPSce that will display the satellite status. Goggle Maps leaves you rather blind as to what is going on.
Sadly, we have discovered that not all Titans are equal and some have a hardware discrepency that greatly hinders the ability to clearly receive and lock onto the satellites. I've played with a few and my personal device consistently locks to 5 or more within seconds while another with identical software settings rarely if ever locks onto 3. Others have realised the same. Try waiting up to 30 minutes to see if any locks can be achieved -- if not then there's likely no software solution.
My kids are using the Moguls in our family. I removed a bunch of junk from the Sprint ROM but it is mainly as shipped. I cannot believe how fast the Moguls on Sprint acquire the satellites. It usually takes less than a minute and is often just a few seconds.
I use the Kaiser. It takes about 3 to 5 minutes sometimes to find the satellites. Sometimes I have to use the QuickGPS program to nudge it along.
With the Mogul, the fix is extremely quick. I wish my Kaiser was as quick.
I'm running a Mogul on Sprint w/ DCD 3.04. Locks take 10+ minutes, GPSViewer shows satellites immediately, but the lock just takes a while. I verified that ActiveSync is not running.
The Mogul was purchased in Nov/Dec last year.
wizzy99 said:
I'm running a Mogul on Sprint w/ DCD 3.04. Locks take 10+ minutes, GPSViewer shows satellites immediately, but the lock just takes a while. I verified that ActiveSync is not running.
The Mogul was purchased in Nov/Dec last year.
Click to expand...
Click to collapse
radio 3.35.04 took me 10+ minutes at times, 3.39.10 takes me 10 seconds.
It still takes me 10 mins to get a lock with 3.39.10, i use the GPS viewer to check for the lock.. Even with QuickGPS it takes about 10 mins.. Once it only took 6 seconds after that everything went to hell haha..
dcd1182 said:
radio 3.35.04 took me 10+ minutes at times, 3.39.10 takes me 10 seconds.
Click to expand...
Click to collapse
I just upgraded to 3.1.2/3.39.10 and google maps locks very quickly. GPSViewer still isn't very fast.
I upgrade to 3.1.2 and 3.39.10 and now my GPS is out by nearly 5 miles
Guys, 3.1.2 / 3.39.10 is not your issue if gps isn't working as good as you'd like it to. If anything, 3.39.10 is MUCH better in acquiring a fix. It's pretty much an unspoken fact that the gpsone chips inside these titans are spotty and some just work better than others. Sometimes mine gets a fix within seconds, sometimes it's 2 minutes. It's a combination of weather conditions, location of the satellites, and the gps hardware. These phones do not have SIRF chips in them...let's get over it.
It's np, I reinstall 3.35 radio and now gps work fine
Something about 3.39.10 and my gps chip doesn't like each other...
My inability to get over something not working correctly has led to getting things working correctly at least for now. Since I had had GPS working quite well under the 3.35 radio and knowing that I had been jumping all over the place with flashing different radios and kitchens in my never ending quest to try things out it occurred to me that I don't know all that much about what actually goes on during a reflash of a kitchen or radio etc... I thought it could be possible that during all the reflashes that not everything is cleanly removed and reflashed. Being an Alltel user I took my phone all the way back to stock which for me was the Alltel ROM “RUU_TITAN_ALLTEL_WWE_2.14.671.3_1.40.00_Altel_0816_NV132_Ship”. I got everything back up and running on this ROM. I ended up having to enter the MSID and MDN etc... I then unlocked the phone using "titan_SPL_2.40-olipro" next having had success using Sprints 3.35 radio I flashed “RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship” that radio back onto my phone and then flashed dcd's 3.01 kitchen. I then tried out the GPS and everything was working great. Having finally received my 2 gig micro sd card I reformatted it to fat32 with 1024 clusters and proceeded to flash the 3.39 radio using this method instead of using the test sprint ROM as I did before. I decided to try out a different kitchen this time and I put on ppcgeeks "Titan_3.49_WM6" then installed “dcd QuickGPS.cab” and "dcd VisualGPSce.cab" and my GPS is working better than ever. For all of you out there that still are having GPS problems I would recommend doing something similar to what I did here. I would be interested to hear if this helps.
mr.ellsworth
mr.ellsworth said:
My inability to get over something not working correctly has led to getting things working correctly at least for now. Since I had had GPS working quite well under the 3.35 radio and knowing that I had been jumping all over the place with flashing different radios and kitchens in my never ending quest to try things out it occurred to me that I don't know all that much about what actually goes on during a reflash of a kitchen or radio etc... I thought it could be possible that during all the reflashes that not everything is cleanly removed and reflashed. Being an Alltel user I took my phone all the way back to stock which for me was the Alltel ROM “RUU_TITAN_ALLTEL_WWE_2.14.671.3_1.40.00_Altel_0816_NV132_Ship”. I got everything back up and running on this ROM. I ended up having to enter the MSID and MDN etc... I then unlocked the phone using "titan_SPL_2.40-olipro" next having had success using Sprints 3.35 radio I flashed “RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship” that radio back onto my phone and then flashed dcd's 3.01 kitchen. I then tried out the GPS and everything was working great. Having finally received my 2 gig micro sd card I reformatted it to fat32 with 1024 clusters and proceeded to flash the 3.39 radio using this method instead of using the test sprint ROM as I did before. I decided to try out a different kitchen this time and I put on ppcgeeks "Titan_3.49_WM6" then installed “dcd QuickGPS.cab” and "dcd VisualGPSce.cab" and my GPS is working better than ever. For all of you out there that still are having GPS problems I would recommend doing something similar to what I did here. I would be interested to hear if this helps.
mr.ellsworth
Click to expand...
Click to collapse
I've tried your recommendation...however it did not make a difference
I don't know exact how you look at VisualGPSce.
On my "sig/nav" tab, there are a few vertical bars...all says 0...except two, which says 20 and 15.
Satellites in use: 0 (rarely 1)
Satellites in view: 0
Try resetting, or pull battery
After some experimentation, I now think that I can get out of the loop of not locking onto satalights buy resetting. Sometimes just turning off, other times a soft reset, and if that does not work, a shutdown plus remove battery seems to do the trick.
So, I downloaded the visual gps and I have good news and bad news. The good news is it is finding satellites so we know the GPS in my phone is working, the bad news is is isn't USING any of the damn satellites. When i'm inside my house it is only finding 1 but, when I go outside it is normally finding 3 with very strong signals and then picks up a few other ones that arn't very strong signals.
What do I do from here? We know the GPS is working, but it isn't locking. Maybe if I get it to lock somewhere other then my house and then come back it might work? I'm still under my 30 day free trial with Alltel and if I can't get this fixed I might return the phone. It is one of the main reasons I bought it and it's really pissing me off that it's not working right!!!
leepoffaith said:
What do I do from here? We know the GPS is working, but it isn't locking. Maybe if I get it to lock somewhere other then my house and then come back it might work? I'm still under my 30 day free trial with Alltel and if I can't get this fixed I might return the phone. It is one of the main reasons I bought it and it's really pissing me off that it's not working right!!!
Click to expand...
Click to collapse
Sounds like you've got a bad GPS chip. If the phone is otherwise working out for you, you should bring it back to Alltel for a swap-out due to defective hardware. Do it while you are in your 30 day period to minimize any hassles with them.
-Doc
Verizon 6800
ROM: DCD 3.2.0
Radio: 3.42.30
I've used multiple GPS apps so far such as HTC GPS Tool, GPS Viewer, etc and sometimes they see 1 sat, sometimes none. I live in Portland, OR .. there's definitely satellites above =)
I've let it scan for 30+ minutes.
I have gone through all the guides so far .. soft resets, turning on and off the GPS location, using astrogos loader before trying Google Maps, Navizon, Live Search, etc.
No dice.
Any ideas?
ever since I loaded this radio I have not been having luck getting gps locks either.
exact config as yours.
I also did the gps fix that GC posted
Would like to figure this out also
Well, if multiple people have the issue with this radio, maybe its a bunk release and we need to downgrade to something like 3.24.02.
I might try it later tonight if I get the chance.
EH, nm ...
http://forum.xda-developers.com/showthread.php?t=403280
Thats the release thread for the radio version we're on and people are obviously not having issues with it ... hmmmmm
Updates after more forum reading ...
I've done the GPS fix @: http://forum.xda-developers.com/showthread.php?t=400975
I'm set to GPS Mode 2.
Still no locks.
Edit:
Another question ... if when using QPST you see that your 7500 modem is on COM5 vs where on most people's its on COM4, does that mean I should set the External GPS option on the phone to COM5 and start using that for everything going forward? I've tested both with no discernable difference in results testing .. but thought I should ask.
This may sound stupid, but have you been trying it outside or inside?
When I first tried to get a GPS lock back when I did the 2.1.0 flash, I tried in my room for hours. Sat it by my window, and the battery eventually drained trying to get a lock, with no luck.
Once I went outside, it was a completely different story. Even having the phone by a window wasn't good enough... I had to be outside to get any kind of GPS lock with it.
Issue resolved. Must have been something wrong with the radio firmware I used because I loaded another one and it worked.
Would you mind sharing which radio revision worked for you?
i just did another update dialing #228 and option 2
After the reboot, I got a lock in less than 10 seconds. Might be a coincedence but oh well.
The gps in this is so sporadic, sometimes it locks immediately, most times it takes forever
????
3.42.30 works good with sprint. Actually i get fastest lock out there out of all radios!
NotLutzik said:
3.42.30 works good with sprint. Actually i get fastest lock out there out of all radios!
Click to expand...
Click to collapse
if ur on sprint you should have run the sprint gps fix, which includes updating the spring pri. you should be getting locks in under 10 seconds.
you should also be very thankful that u arent on verizon like me and happy when u get a 3 minutes gps lock.
(sometimes takes me alot more)
i still havent decided if its a phone problem or a location thing.
I live in NYC, so wherever i go im surrounded by buildings...big ones, and lots of em, so im sure this has alot to do with my crappy gps times.
anyone out there on verizon in NYC who gets good locking times?
just wondering
thanks
I was in NYC for a week and never got my GPS to work the whole time I was there. Otherwise my GPS works fine.
Please post all discussion/issues/comments regarding Verizon Wireless GPS/aGPS in this thread.
VZW GPS Discussion Thread
I finally got it.
VZW AGPS INSTANT LOCKS.
Tested to work on any custom GPS rom/radio pair. Now also working with the MR1 update thanks to Skywing.
Persists through all flashes of the OS Rom and Radio. Works with both PRI 1.35_002 and 2.03_002, though it does NOT persist through a PRI change. It will have to be re-applied after, and Location On will have to be reset.
Complete tutorial can now be found in the wiki here:
http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
Well done!
What is the default IP for Verizon? I changed that IP so many times
Edit: Instant lock 6 - 8 satellites in a building where I would never get any. Outside my phone connected fine after 15 - 20 seconds. No I am getting instant locks. Excellent GC, very good work on this one!
You are the man gc, patience is a virtue
LOL you had to ask for this just AS I FLASHED UP!
im such a good tester too
Great job.
That's amazing!! Well done and thank you for all the hard work. I would love to test it out!
You have PM.
Quick Question
For the less then patient of us who were dumb enough to flash the new update with the PRI from hell, what is the best prep path for this long awaited aGPS update.
I have waited to see what the best cure is and I am less then convinced which method to use.
GC Rules!!!!
I am humbled by your wisdom.
For those needing the stock info look to the GPS FAQ on this site.
No need to pm me anymore...I've posted the instructions.
A lil bit of an acknowledgement would have been nice unless you got the PDE addressing information from someone else
That being said, can you verify for certain that there is a difference from using the nvram-supplied PDE data? My testing on the MR1 firmware has not yielded any differences yet on the standard interface. I suspect that it might be worth a try putting on the GPS intermediate driver module from that ROM instead of the one with the challenge/handshake obfuscation built into it.
Before I poke around with that, however, it would be nice to verify that the PDE I gave you does indeed have an effect that cannot be written off as warm-start standalone GPS, and that it doesn't require a VZ Navigator provisioning.
Edit:
You may be able to test this by putting the phone on Wi-Fi and seeing if there's any change, as the PDE is not accessible out of Verizon IP ranges (furthermore, VZ Navigator chokes if you put it on Wi-Fi).
works great! no surprise though. thanks GC youre the man
A lil bit of an acknowledgement would have been nice unless you got the PDE addressing information from someone else
That being said, can you verify for certain that there is a difference from using the nvram-supplied PDE data? My testing on the MR1 firmware has not yielded any differences yet on the standard interface. I suspect that it might be worth a try putting on the GPS intermediate driver module from that ROM instead of the one with the challenge/handshake obfuscation built into it.
Before I poke around with that, however, it would be nice to verify that the PDE I gave you does indeed have an effect that cannot be written off as warm-start standalone GPS, and that it doesn't require a VZ Navigator provisioning.
Edit:
You may be able to test this by putting the phone on Wi-Fi and seeing if there's any change, as the PDE is not accessible out of Verizon IP ranges (furthermore, VZ Navigator chokes if you put it on Wi-Fi).
Click to expand...
Click to collapse
I obtained the PDE information for VZW a couple weeks ago. I've just been testing **** out since. I can confirm though that it IS using agps and not just warm standalone.
Where does one best obtain pri 1.35_002? I have 1.24_002 right now, but have the other two pieces already.
work perfectly. first time I've ever get a fix in mahanttan within 10 seconds.
It works great. Also, I changed GPSMode to 4 (instead of 2) in:
HKLM/SOFTWARE/HTC/supl agps
8 - 9 locked satellites indoors!
Thanks again, gc14.
Ignore missed post earlier in the thread.
SOLORIDER said:
work perfectly. first time I've ever get a fix in mahanttan within 10 seconds.
Click to expand...
Click to collapse
good to hear, im outside of the city right now, up in binghamton, but live in Manhattan. always been frustrated by slow lock times with all the buildings. cant wait to get back and finally have quick gps.
btw, im also at about 10 seconds or less up here.
thanks to all who helped
Works awesome. I'm using GPS Viewer, and it now pre-populates 12 sats and instantly locks to 7.
Thanks, I appreciate all the hard work.
Is there a test result for someone who has gone from the MR1 firmware with the latest PRI to the dcd firmware mentioned by gc14, without poking around with trying to change back to the old PRI?
I would like to eliminate the GPS intermediate driver in MR1 as the roadblock here.
I'm not sure why using the 2.03 PRI instead of my 1.35 PRI would be advantageous? Can someone explain this to me? I'm not sure it's worth the update unless I'm going to get some functionality that I don't already have (already get GPS lock in 7-10 secs). Ideas?
fvultee said:
I'm not sure why using the 2.03 PRI instead of my 1.35 PRI would be advantageous? Can someone explain this to me? I'm not sure it's worth the update unless I'm going to get some functionality that I don't already have (already get GPS lock in 7-10 secs). Ideas?
Click to expand...
Click to collapse
Thx for asking what I wanted to ask...
anybody...?
Parcou, I think I may have asked a question nobody has the answer to! 94 views and not a single response! On a happier note, I'm now locking gps in about 7 seconds from a cold start, so at least my current config is doing what it's supposed to do. Only drawback now is that GPS Toggle, the program I use to prime the GPS, sucks the battery like a Tijuana prostitute. It does seem to lock ALOT faster than any of the other programs though, which is nice. I was suprised however that with GPS Toggle and iGO8 running that the battery runs down even while plugged in, how's that even possible!
more reliable gps lock
I took the risk and flash to the vzw official wm6.1 update and let the customization ran. The PRI 2.03_003 seems to stay with the phone even from flashing a custom rom.
With the new PRI 2.03_003, the GPS locking seems to be less spontaneous but more reliable. Previous PRI 1.35_002 let me see a lot of SATs but signals were bouncing back and forth. Overall, it's an improvement.
I have read quite a lot concerning the new Verizon update, and like the update itself, I see absolutely no reason to update to the new PRI. No gained functionality, just extra bloat and incompatibility.
The only reason people were excited about this update, was to hack aGPS support out of it, which has been done.
bmb2n said:
I took the risk and flash to the vzw official wm6.1 update and let the customization ran. The PRI 2.03_003 seems to stay with the phone even from flashing a custom rom.
With the new PRI 2.03_003, the GPS locking seems to be less spontaneous but more reliable. Previous PRI 1.35_002 let me see a lot of SATs but signals were bouncing back and forth. Overall, it's an improvement.
Click to expand...
Click to collapse
The sat signal bouncing has mostly to do with the Radio rom installed.
I have a related question. I followed GC14's instructions for updating the PRI without having to flash the new MR1 ROM (I wanted to stick with my custom). However, upon executing the WriteDMData.exe step, I didn't get any definitive response. I waited a while and File Explorer never seemed to reset to the top of the file list as mentioned in the included .txt file. I did confirm, however, that I needed to redo the GPS settings in QPST, so I know that something took place.
Which brings me to my question: how do I tell what PRI is currently installed? It's not among the data displayed on the bootup screen.
Thanks,
David
drgreenberg said:
I have a related question. I followed GC14's instructions for updating the PRI without having to flash the new MR1 ROM (I wanted to stick with my custom). However, upon executing the WriteDMData.exe step, I didn't get any definitive response. I waited a while and File Explorer never seemed to reset to the top of the file list as mentioned in the included .txt file. I did confirm, however, that I needed to redo the GPS settings in QPST, so I know that something took place.
Which brings me to my question: how do I tell what PRI is currently installed? It's not among the data displayed on the bootup screen.
Thanks,
David
Click to expand...
Click to collapse
Use the settings | Device Information app. It has most all version numbers for your phone.
just checking back on this thread....I am still on 1.35 and all is great on the gps... I still see no real answer as to why I need to go to 2.03 but I will if I can get a solid answer as to why...I have gps'd after the fix in many spot across the US already...all is smooth...
I'm running dcd 3.0.4 with radio 3.35.04, pri 1.35_002. I haven't been up here in awhile and just noticed the VZW official ROM. I have been using the GPS with Google and LIve and love it, it works when it wants to work is the most annoying part. Sometimes I have to reset a few times, but it rocks. I tried the priming method, but didn't notice any difference.
So on to the question. I don't have an external GPS, I don't want the verizon navigator stuff. I'd like to get my 6800 to lock in on GPS more quickly and not having to reset the phone. What/which stuff should I use?
Everybody should be using the newest PRI available. The PRI isn't JUST GPS related, and ISN'T bloat by any means. The PRI provides instructions for the radio (where the 'RI' comes from in PRI) and affects all aspects of the radio, including 1xRTT and 1xEVDO. There shouldn't be any reason why anyone should still be using PRI 1.35_002.
Same here parcou. I travel all over the place and my GPS works GREAT with the 1.35_002 PRI, so I'm not going to mess with it. Outside I get a lock within 10 seconds every time.
I'm having trouble finding the info on updating the PRI. Anyone have a link? Thanks!
Me too Panth. I'm been browsing through the Wiki's and sticky postings and have found nothing.
Here's the answer you've all been waiting for, seriously
The 2.XX PRI (from a SPRINT standpoint anyway) allows your phone to utilize the aGPS (assisted GPS) towers that Sprint has. The 1.XX pri does not do that, so your phone WILL take longer to acquire a GPS signal. In essence, your phone on a 1.XX PRI is only using the standalone GPS, whereas with 2.XX it utilizes aGPS to get a faster lock.
Your GPS may work great, I thought mine did too until I updated my PRI, and now get locks faster (~ 5 seconds) and I get more satellites than before. Even inside, I can get 9-11 satellites in very little time.
There's your answer, and you can completely trust it.
Panth said:
I'm having trouble finding the info on updating the PRI. Anyone have a link? Thanks!
Click to expand...
Click to collapse
If you have the newest DCD rom, there is a link in the connections folder that will allow you to update your PRI. However, you can also do it (on Sprint) by going to your Windows directory and running PPST.exe
You will need the following for it to work:
(I've attached everything you need in this post so you don't have to search)
1. You will need your ESN number, by getting the HEX off of underneath your battery or by going to Settings --> Device Information and finding ESN (towards the bottom)
When you have this, enter it into GetSPC.exe (run from your titan) to get your unlock code for your phone.
2. Install the attached PRI Cab for 2.03_003 (the most stable right now)
3. Once you have your unlock code and you've installed the PRI cab, run PPST.exe from the windows directory. It will say "Proceed with the update?"
Say OK....that should be it.
When I tested this on my phone, it didn't ask me for the unlock code, but I stress to every one of you, it's crucial to have this if you ever need to do anything with your phone as far as programming is concerned, so it's not bad to have...write it down in a safe place, or put it on a .txt file on your storage card.
That should help you get to where you need to be....
If it says it failed, then you forgot to install the cab file first. Good Luck!
Blank.....
kmartburrito said:
If you have the newest DCD rom, there is a link in the connections folder that will allow you to update your PRI. However, you can also do it (on Sprint) by going to your Windows directory and running PPST.exe
You will need the following for it to work:
(I've attached everything you need in this post so you don't have to search)
1. You will need your ESN number, by getting the HEX off of underneath your battery or by going to Settings --> Device Information and finding ESN (towards the bottom)
When you have this, enter it into GetSPC.exe (run from your titan) to get your unlock code for your phone.
2. Install the attached PRI Cab for 2.03_003 (the most stable right now)
3. Once you have your unlock code and you've installed the PRI cab, run PPST.exe from the windows directory. It will say "Proceed with the update?"
Say OK....that should be it.
When I tested this on my phone, it didn't ask me for the unlock code, but I stress to every one of you, it's crucial to have this if you ever need to do anything with your phone as far as programming is concerned, so it's not bad to have...write it down in a safe place, or put it on a .txt file on your storage card.
That should help you get to where you need to be....
If it says it failed, then you forgot to install the cab file first. Good Luck!
Click to expand...
Click to collapse
Is this is the same procedure from Verizon?
Panth said:
Is this is the same procedure from Verizon?
Click to expand...
Click to collapse
That's why I only mentioned Sprint...I'm pretty sure the PRI's don't work across carriers, I'll let someone step in and correct me if they know more about that.
I'd imagine it's specific though.
However, the procedure SHOULD in essence be the same.
I do know for a fact that the PRL's are carrier specific, so that would lead me to believe that the PRI is as well.