Related
Lets face it. The new radio sucks horribly. The leaked Rom is very bad as well. Countless problems for almost everyone. Has anyone extracted the gps drivers? I would kill to go back to the 2.17 sprint rom with the gps added on.
Won't work you need the new radio, and rom.
Mine is working without any problems, and the radio is great.
stevenewjersey said:
Lets face it. The new radio sucks horribly. The leaked Rom is very bad as well. Countless problems for almost everyone. Has anyone extracted the gps drivers? I would kill to go back to the 2.17 sprint rom with the gps added on.
Click to expand...
Click to collapse
well, the new radio is a BETA after all. and i havent had any problems with it. The new radio is what enables the GPS in the phone, and the 3.16 based roms have the drivers that are needed for gps. so these go hand in hand. you need em both for gps.
stevenewjersey said:
Lets face it. The new radio sucks horribly. The leaked Rom is very bad as well. Countless problems for almost everyone. Has anyone extracted the gps drivers? I would kill to go back to the 2.17 sprint rom with the gps added on.
Click to expand...
Click to collapse
No problems for me, works great and couldn't be happier with everyones work on getting the GPS and Rev A to work. I appreciate all the work that people are putting in to get all this going. I guess you'll just have to wait until your carrier releases their updated ROM with GPS enabled, maybe that will be less problematic for you.
I am betting when this is released there will be a newer radio, this is a beta and the radio is at least a couple of months old, I am sure they have done some tweaking since then, at least if they are seeing the same issues one would hope they have tweaked a bit more here and there.
Same goes for the rom piece of it it is an old beta as well they are both 2 months old, so whatever Sprint and/or HTC has been doing for the past 2 months is unknown.
You Sprint folks should all be happy to me it seems Sprint is the only provider that gives half a rats ass. On Telus the last rom came out back in the beginning of July and none of the other Canadian providers that carry this phone have provided any updates whatsoever.
As Fallingup said this is a beta and the issues we are seeing from the radio patch exhibit normal BETA behavior...
Hell even HTC is convinced the Radio isn't ready for Primetime and keep delaying the release! That says to me they have hit some roadblocks they are having trouble dealing with.
It would not surprise me at all if HTC consciously decided to leak this radio so that the community could take a crack at solving those issues and give them some ideas on how to fix the patch.
I am hoping someone in the community is looking at this beta version of radio and looking for ways to improve that....
Cause I'm betting the second someone can tweak that radio to work well, HTC will take that file and use it as a roadmap for an official release!
stevenewjersey said:
Lets face it. The new radio sucks horribly. The leaked Rom is very bad as well. Countless problems for almost everyone. Has anyone extracted the gps drivers? I would kill to go back to the 2.17 sprint rom with the gps added on.
Click to expand...
Click to collapse
Some people have terrrible issues. Some have none at all. I have no problems at all. This is the best set up I have had. I am using the new Radio and Bootloader with a variation of DCD 2.2.0 ROM. Working great. What specific ROM are you using?
scrosler said:
Some people have terrrible issues. Some have none at all. I have no problems at all. This is the best set up I have had. I am using the new Radio and Bootloader with a variation of DCD 2.2.0 ROM. Working great. What specific ROM are you using?
Click to expand...
Click to collapse
the actual results are somewhere in between...the ones with zero issues either don't use data connect extensively or haven't really run everything through it's paces. How could they the ROM is only a day old! LOL
Others just have issues with the 6.1 OS and still others have issues just flashing. The latter is simply user error and that will always be there no way around that. You have to know those issues will show up even if the perfectly stable ROM gets released.
The Radio is IMO definitly not ready for prime time. between the BT issues, Data Connect and the problem of having to prime the GPS before a navigation software like TomTom can use it there will have to be another update to the radio ROM before we can be sure we gain GPS capability without losing anything else...
Right now Radio appears to be a bit of a tradeoff as opposed to a simple feature addition.
Once an official (as opposed to leaked) radio comes out I think all the REAL problems people are having will go away.
Asphyx said:
Cause I'm betting the second someone can tweak that radio to work well, HTC will take that file and use it as a roadmap for an official release!
Click to expand...
Click to collapse
That would be funny as hell. Imagine if they ended up using a Radio that someone here on XDA-Dev was tweaking!! I hope they get commisisons
rajuabju said:
That would be funny as hell. Imagine if they ended up using a Radio that someone here on XDA-Dev was tweaking!! I hope they get commisisons
Click to expand...
Click to collapse
As far as I know nobody here on XDA Dev has actually tweaked a Radio. People put together firmware files from other stuff, and bundle them all together, but to actually fix and recompile a radio file goes much deeper than anyone here handles.
I have had only one problem running dcd 2.10 and 2.20. I have run critically low on memory once. This has never happened before.
But as for the radio and OS, I think my call quality is noticably better than with the stock rom or any of dcd's 1.x rom/radio setups that I have tested.
Oh, just FYI, I'm in Utah. I wonder if the radio issues have to do with a difference in radio hardware on the towers in New Jersey.
After reading for several days and hearing the good the bad and the ugly I opted for the straight leaked rom. No unlocking and all that.
Well so far so good. GPS works, RevA not a real difference so far
Fairly stable. Happy with my beta software until the official release
vetvito said:
Won't work you need the new radio, and rom.
Mine is working without any problems, and the radio is great.
Click to expand...
Click to collapse
Yup, me too.
As a matter of fact, I'm not going to go to DCD's 2.2.1 until this current flash (on my phone) bombs. 2.2.0 is working great for me.
For those who claim to have no problems...
Try downloading a file larger than 1 MB in PIE or Opera...
The issue has NOTHING to do with DCD's work...
Definitly the Radio...
There only problems I have seen with the 2.2X Roms DCD has put out is some issues with installing programs on the storage card...
But if I know DCD that will be fixed rather quickly.
I'm very new to this flashing thing. I'm familiar with pretty much everything else, however. Having just sold my GPS, having a handheld GPS would be infinitely useful (Especially since I get service on a mountain that I frequently go biking on and get lost).
That said, I can't make heads or tales of some of the threads going on with the 3.0.2 ROM, flashing it, flashing the radio, and getting the PRL or... Whatnot.
I have an Alltel PPC-6800, it's using the stock ROM and radio (2.14.671.3 ROM and 1.4 radio), so basically I haven't changed anything. I don't really understand the steps involved coherently, so if someone could kinda give me some hints or whatnot I'd much appreciate it.
Thanks!
Tyorik said:
I'm very new to this flashing thing. I'm familiar with pretty much everything else, however. Having just sold my GPS, having a handheld GPS would be infinitely useful (Especially since I get service on a mountain that I frequently go biking on and get lost).
That said, I can't make heads or tales of some of the threads going on with the 3.0.2 ROM, flashing it, flashing the radio, and getting the PRL or... Whatnot.
I have an Alltel PPC-6800, it's using the stock ROM and radio (2.14.671.3 ROM and 1.4 radio), so basically I haven't changed anything. I don't really understand the steps involved coherently, so if someone could kinda give me some hints or whatnot I'd much appreciate it.
Thanks!
Click to expand...
Click to collapse
Checkout the Titan Upgrades forum at http://forum.ppcgeeks.com/
They have some helpful step-by-step guides over there.
With Alltell because you first have to upgrade to the new Sprint ROM to get the new radio and then install a custom ROM. But make sure you read up because there are few other steps involved.
So I am supposed to use the Sprint ROM? Hmm. I guess I'll read up some more then and try to piece it together, thanks though!
Tyorik said:
So I am supposed to use the Sprint ROM? Hmm. I guess I'll read up some more then and try to piece it together, thanks though!
Click to expand...
Click to collapse
You need the new Sprint ROM simply to get the new Radio (with GPS capability)... then you have to load a custom ROM that is meant for Alltel
This might be something worth reading:
http://forum.ppcgeeks.com/showthread.php?t=21189
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)
I have to give DCD all the credit in the world. His work has been awesome and I really love that he is in this forum working hard all the time. However, I had many problems with 3.1.2 and radio 3.39. Slow GPS among a lot of other things. I am a sprint user and I did everything properly with flashing etc. My phone worked great except for the GPS which was extremely slow. I decided to revert back.
I put virtually all of the blame on radio 3.39. I think that it is still in development therefore it is not ready for release. Also I think that the carrier cabs that need to be installed with 3.1.2 are also an issue.
After reverting back to 3.0.4 and radio 3.35 I can say that things are dramatically improved. My GPS locks in seconds everytime. 3.39 took so long that it was useless. I do not have internet issue nor outlook issues with 3.35 either.
So... I suggest that anyone who is having problems with 3.39 go back to 3.35 radio and also back to dcd3.0.4
I highly suggest that you first install the official sprint 3.35 release and make sure you let the customizations run as well for carrier cabs. Then flash 3.0.4. After flashing do a hard reset to make sure all kinks are out. Stick with radio 3.35 and 3.0.4 if you are having issues with 3.39 and 3.1.2.
I hope any of this made sense. If you do not know what 3.39, 3.35, 3.0.4, or 3.1.2 means then dont touch a thing
I have to give DCD all the credit in the world. His work has been awesome and I really love that he is in this forum working hard all the time. However, I had many problems with 3.1.2 and radio 3.39. Slow GPS among a lot of other things. I am a sprint user and I did everything properly with flashing etc. My phone worked great except for the GPS which was extremely slow. I decided to revert back.
I put virtually all of the blame on radio 3.39. I think that it is still in development therefore it is not ready for release. Also I think that the carrier cabs that need to be installed with 3.1.2 are also an issue.
After reverting back to 3.0.4 and radio 3.35 I can say that things are dramatically improved. My GPS locks in seconds everytime. 3.39 took so long that it was useless. I do not have internet issue nor outlook issues with 3.35 either.
So... I suggest that anyone who is having problems with 3.39 go back to 3.35 radio and also back to dcd3.0.4
I highly suggest that you first install the official sprint 3.35 release and make sure you let the customizations run as well for carrier cabs. Then flash 3.0.4. After flashing do a hard reset to make sure all kinks are out. Stick with radio 3.35 and 3.0.4 if you are having issues with 3.39 and 3.1.2.
I hope any of this made sense. If you do not know what 3.39, 3.35, 3.0.4, or 3.1.2 means then dont touch a thing
Click to expand...
Click to collapse
Dude hold on a sec....before you go scaring everyone away from 3.1.2 and 3.39.10....did you say you were on Sprint and had extremely slow GPS?
Sprint users have NO excuse for not having instant locks with GPS. If you would have read the stickies at the top of this forum you would have found your answer for INSTANT GPS locks. It has nothing to do with what rom/radio you're using and EVERYTHING to do with what PRI version you have.
Personally, I have found absolutely nothing wrong with 3.1.2 and 3.39.10 and have used both for a while (no longer using 3.1.2 due to testing new builds, but STILL using 3.39.10).
A little reading of the important stuff goes a long way...
Not trying to scare anyone at all. I just saw that there were some posts about gps stuff and problems. I am in now way taking anything away from dcd or his kitchens/roms. DCD knows that I am a big fan of his and I have also tested his stuff. I am just trying to help those who are having issues, that is all.
Just the same way that we all have different programs that suit our needs, each of the current DCD Roms and other radio options offers some balance to some, and has drawbacks for others.
Some Roms have more beta feel, which gives some an edge and functionality that they can use. Some can't live with the buggy stuff (or figure out workarounds) so they keep what is familiar. This stuff is fun, lets keep it that way and let people brick their phone if they are talented enough to do it.
I went back to 304 myself because i couldn't get NoData working on 312. sounds like a chump reason but at 12$ a mb its a very important program to me. I kept radio 3.39 and have never had trouble with the GPS. Infact, when I compare the acquisition time of the titan to my Garmin Rhino and previous GPS units I'm still amazed at how fast all of the radio ROMs pick up GPS. Its totally comparable to a dedicated GPS unit. However, I'm on Telus.
All of the roms DCD has produced have been far better than stock, so this is in no way a complaint! Keep up the good work guys.
Ps. Is there a NoData like program that works on 3.12?
i've mentioned this before, but while 3.12 and radio 3.39 seem solid, i have experienced the same things. My GPS takes 5-7 minutes to lock, and when it does, it's normally 1/2-1 mile off. I didn't have these issues when i was with 3.04 and 3.37 (Alltel user here), but no complaints, the rest seems solid, so i've lived with GPS since i upgraded.
Like I said in the other thread...we've been working on a gps fix. Testing it now.
Yea I was going to test the GPS fix for 3.39 but I had to go back because I need the GPS too much.
gc14 said:
Like I said in the other thread...we've been working on a gps fix. Testing it now.
Click to expand...
Click to collapse
I guess people dont want to read you lol
Thanks for the info!
Yea I was going to test the GPS fix for 3.39 but I had to go back because I need the GPS too much.
Click to expand...
Click to collapse
Dude...you have Sprint!! You don't need to test that fix, you HAVE a fix that works. It's posted in the GPS sticky thread AND I made another thread dedicated to it....
My Sprint GPS is almost instant with DCD 3.1.2 and I didn't even have to read a sticky
My Sprint GPS is almost instant with DCD 3.1.2 and I didn't even have to read a sticky
Click to expand...
Click to collapse
What is your PRI Version in Device Information?
PRI Version: 2.03_003
PRI Version: 2.03_003
Click to expand...
Click to collapse
Ahh see...you have the updated PRI...
Now if all the Sprint users complaining about slow GPS would just read my post....
I've been on 3.04 and 3.35 radio for the whole time... I have no issues with anything. Phoen works great, reception is superb.
I'm sure DCD is cooking some crazy ****, and when he comes out with a major upgrade, but I dont see a need to reflash everytime there is a minor change made.
but I dont see a need to reflash everytime there is a minor change made.
Click to expand...
Click to collapse
You do read the changelog right? Did you not see the changes made in 3.1.2 from 3.0.4. I wouldn't say they're "minor"
gc14 said:
Ahh see...you have the updated PRI...
Now if all the Sprint users complaining about slow GPS would just read my post....
Click to expand...
Click to collapse
I'm running DCD 3.1.2 Radio 3.39.10 and PRI Ver. 2.00_003 and I get almost instant locks on GPS. I have no problems with GPS locking!!! Must be something in your machine.
I'm running DCD 3.1.2 Radio 3.39.10 and PRI Ver. 2.00_003 and I get almost instant locks on GPS. I have no problems with GPS locking!!! Must be something in your machine.
Click to expand...
Click to collapse
....... huh?
The USB port on my 6800 broke so insurance replaced it. I'm running DCD's 3.44 and 50 radio on Verizon. I have flashed and flashed over and over checked QPST and reg settings.
Can it be just be the GPS never worked in this phone? Could this have come with the MR1 update on it? Is there a way to check? I have dloaded every kind of primer app as well and they do see the GPS port. GPS gate seems to work but reports no data.
I'm out of ideas.
nylaw said:
The USB port on my 6800 broke so insurance replaced it. I'm running DCD's 3.44 and 50 radio on Verizon. I have flashed and flashed over and over checked QPST and reg settings.
Can it be just be the GPS never worked in this phone? Could this have come with the MR1 update on it? Is there a way to check? I have dloaded every kind of primer app as well and they do see the GPS port. GPS gate seems to work but reports no data.
I'm out of ideas.
Click to expand...
Click to collapse
My first guess, assuming you turned the GPS on, is that you did have the MR 1 update.
You may as well try reverting back to stock winMo6.0 then back up to 6.1 via the standard method.
Secondly you could flash stock MR1 update then install valhalla GPS server cab.
What PRI do you have. If its 2.xx then you prolly did have MR1.
How did you unlock and what ROM/radio etc did you use?
The PRI is 2.xx but I thought that was from DCD's Verizon cab? I believe I unlocked with 2.40 than 2.47 at least that is my current BL. The radio is 3.42.50 and the rom is DCD 3.3.4 I am just about ready to pull the trigger on reverting back to stock and starting over. I just wanted to make sure I hadn't missed something.
One odd thing. I still get the white Verizon splash screen.Whenever I loaded a new romDCD's always had an HTC splash screen so that also leads me to believe it may have the MR1 update on it but not sure. Does that mean anything to you?
nylaw said:
The PRI is 2.xx but I thought that was from DCD's Verizon cab? I believe I unlocked with 2.40 than 2.47 at least that is my current BL. The radio is 3.42.50 and the rom is DCD 3.3.4 I am just about ready to pull the trigger on reverting back to stock and starting over. I just wanted to make sure I hadn't missed something.
One odd thing. I still get the white Verizon splash screen.Whenever I loaded a new romDCD's always had an HTC splash screen so that also leads me to believe it may have the MR1 update on it but not sure. Does that mean anything to you?
Click to expand...
Click to collapse
Thanks for the info on the splash screen. Did not think of asking that. If you have the standard VZW splash screens then you didint update correctly wiht the sprint ROM and not knowing where the ROM was before you started I would hazzard a guess and say you were on MR1. If you were not on MR1 then you hosed something during the sequence of flashing but that usually leads to a phone that sticks booting... I would try this before I revert back.....
Keep phone unlocked, flash sprint firmware and be careful not to let the customizations run, apply aGPS fix for VZW, test. If it fails then I can certainly say you were on MR1 and must revert back to stock. There may be another way of doing it but I honestly think starting fresh is always best.
Good news to report. I couldn't sleep last night as this was really bothering me. I went back to the stock radio and rom then flashed the radio and rom back to 3.42.50 and DCD's 3.4.4. All is working now but I still have the Verizon splash screen. I would have to say this must have shipped with the MR1 update. There was one value in the regisrty that I missed with the agps settings but that shouldn't have had any effect on the GPS from just the sats.
My PRI is also at 2.xx. This must be in DCD's Verizon cab. I did check when I flashed back to stock and it was at 1.xx
Seems a lot of people have broken USB ports. That was the reason for this replacement. On my last one the voice record button broke. So this is my third 6800.
nylaw said:
My PRI is also at 2.xx. This must be in DCD's Verizon cab. I did check when I flashed back to stock and it was at 1.xx
Seems a lot of people have broken USB ports. That was the reason for this replacement. On my last one the voice record button broke. So this is my third 6800.
Click to expand...
Click to collapse
That PRI is a bastard to get of. I found the best way to get rid of it is to kitchen a ROM, and then add in the Extended ROM from the stock VZW rom (non-GPS) and it was able to finally get rid of the PRI.
If you are still having issues with that PRI, let me know, I might be able to supply my PRI killer ROM if I still have it around.
Thanks but I am all set. Everything is working fine. I believe the guru's feel the 2.xx PRI is the one to have, just not the rest of the update.