Havent really seen this talked about lately... is anyone still getting it where the internet drops connection on the hour every hour with 3.16? Is there a work around for this yet, or is this as I suspect a "bug" with the test rom and is possibly meant for this to do it until an official release?
i have the 3.16 rom but *knock on wood* havent had any problems with it yet....been using it for 2 weeks so im not too sure.
I've had the same problem and apparently a fews others too. But I don't think enough people are having issues to warrant a "fix". Sucks to be us...
I've seen similar behavior (although with not such regularity that you're reporting.) From what I've read here and at ppcgeeks.com it sounds like an issue with the radio rom and not with any of the builds. I'm hoping that a new radio rom is released soon that will eliminate this behavior.
Of course I'm tethered right now posting this so it's not behaving too badly for me.
I have also found that some websites (when tethered) will not open at all for me. Yahoo mail and hotmail are the two the immediately come to mind. They resolve in DNS, I can ping them but they won't open in my browser when I'm tethered.
Yeah, when I use the 3.27 radio I have internet problem. It cannot keep connection so I will have to restart connection often. This cause me trouble with corporate VPN so it cannot use WinMo 6.1 + 3.27 radio. I wish I can use WinMo 6.1 with 1.40 radio, but I think it isn't possible, maybe. WinMo 6.1 is no crash at all in one week... so stable, but WinMo 6.0 crash five time a day. Still, can't use 6.1 cause I can't use my VPN.
We need a better radio, I think radio is trouble with internet. Maybe use 6.0 WinMo and 1.40 radio instead. Until work around anyway.
Hiromitsu
illuminarok said:
Yeah, when I use the 3.27 radio I have internet problem. It cannot keep connection so I will have to restart connection often. This cause me trouble with corporate VPN so it cannot use WinMo 6.1 + 3.27 radio. I wish I can use WinMo 6.1 with 1.40 radio, but I think it isn't possible, maybe. WinMo 6.1 is no crash at all in one week... so stable, but WinMo 6.0 crash five time a day. Still, can't use 6.1 cause I can't use my VPN.
We need a better radio, I think radio is trouble with internet. Maybe use 6.0 WinMo and 1.40 radio instead. Until work around anyway.
Hiromitsu
Click to expand...
Click to collapse
WM6.1 runs fine with 1.40 radio if you use the 2.17 ROM as base
dcd1182 said:
WM6.1 runs fine with 1.40 radio if you use the 2.17 ROM as base
Click to expand...
Click to collapse
I wish I know how to cook a ROM so I can do that lol
I know this might be a long shot but do you think the radio version and the earlier models of the Mogul could have the effect... I ordered and got mine the first day it came out.... maybe the newer ones are coopertaing better with the new radio? This is a far shot as I would think all the parts/chipsets are the same...
Got mine in late summer. With the "stock" 3.16 beta streaming audio is almost impossible. In both Resco and Mundu radio I can't stream for longer than a couple minutes before that wicked "buffering" message appears.
Before I was using my Mogul with few interruptions for 8 hours a day since we're not supposed to stream on the office network. I'm hoping for a fix soon since the stock 2.17 doesn't seem to want to flash over 3.16.
PRL 60711 seems to have helped the streaming problem. Funny I've been running it on my air card for weeks now.
Yes prl 60711 fixed my 6800 too.
Fix streaming issue or losing internet connection on the hour?
Related
Title says it all. I had tried the HTC South African ROM, and liked it, but I couldnt get the keyboard to correspond with the 8525 symbols. Searched all day and decided that it wasn't worth the minimal speed increase. Instead of going back to the ROM I had, the 1.34...ROM, I decided to go with this one since it has AKU 2.6. I am so glad I did!
I live in Queens, and 3G has NEVER worked in my house. Only certain times throughout my day I would see the U symbol on my phone. And it was in south Middle Village, not near my house. Since I upgraded/downgraded the ROM, not only do I have U in my house, but after 8 dslreports.com tests, I averaged over 800 kbps and peaked at 972Kbps! Perhaps its a coincidence that U is up and running here today, but I seriously doubt it! I also upgraded the radio to 1.20 and noticed a slightly less wait time for 'locating" in PIE. The OS seems faster as well, but not much faster, than the newer Cingular ROM. To any Cingular 8525 owners out there this ROM is definitely worth a look!
There must be a reason that they decided 3 WEEKS LATER to go back to AKU 2.3. Is there a bug in this ROM that I haven't discovered yet?
The radio upgrade is what made UMTS more accessible. The OS portion of the ROM didn't have any effect on your wireless. AKU 2.6 is reported to have problems, but I never personally tried it or tried to track them after I read MS Voice Command wouldn't work with it. There was a lot of discussion about AKU 2.6 in the Wizard forum, you might find some info there.
Did you install the newer radio code independently, or did it come with the South Africa ROM?
I noticed the increase in UMTS accessibility after upgrading the ROM. I upgraded the radio only to minimize the "locating" delay in PIE, activesync, etc. It mihgt be a coincidence, who knows.
Cyberon works fine w/this ROM. I never really cared fpr VC, it uses too much RAM and is a lot slower than cyberon IMO
The reason for the thread was to hopefully find out what the problems are that have been reported. Seemse strange that Cingular made a new ROM a few weeks after and went back to 2.3
I don't know why they went back to aku 2.3, but for the problem you where having with the keyboard, you could have solved it by installing a cab in the cingular's extrom (don't remember now exactly wich one).
pof said:
I don't know why they went back to aku 2.3, but for the problem you where having with the keyboard, you could have solved it by installing a cab in the cingular's extrom (don't remember now exactly wich one).
Click to expand...
Click to collapse
Yeah, I had searched, and searched, and found one of your posts that spoke about a cab with "keypad.." in the name, but I downloaded TWO Cingular ExtROMS and that file was not in either of them. When I first installed the 1.35 ROM, I replaced its extrom with the newest Cingular extROM, to no avail. I don't mind though, I like this ROM so far and it hasn't caused any issues for me. And its Cingular-issued, so all of the settings were there for me.
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 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 recently upgraded from Titan Radio ROM 3.42.30 to Titan Radio ROM 3.42.50 along with DCD 2.3.6.
I noticed my GPS is ALOT more jumpy around buildings when I'm downtown.
Is it possible that an older Radio allows a GPS chip to work better than a newer one? I'm asking because I see alot of people stay with old Radios and I always wonder why.
Anyone at all?
240sxer said:
Anyone at all?
Click to expand...
Click to collapse
Not sure. Some say the earlier ones do. You can downgrade anytime. won't hurt any of your other software.
Well, 3.42.50 is ported from a Vogue, so maybe you should try 3.42.40 which is the newest native titan radio.
The radios do not make any difference.... Just find one that "you" perceive to be the best one for you......
indagroove said:
Well, 3.42.50 is ported from a Vogue, so maybe you should try 3.42.40 which is the newest native titan radio.
Click to expand...
Click to collapse
Interesting, I just did some more searching and it seems like alot of titan owners are complaining from x.50. Gonna switch to x.40 tonight
azclown said:
The radios do not make any difference.... Just find one that "you" perceive to be the best one for you......
Click to expand...
Click to collapse
I'm not the only one complaining about x.50 and GPS.
I"ve had the same issue with both .40 and .50. From what I remember, .50 skipped so much in some places that it would lose the satellite lock completely for a few seconds to a minute or more when I was using it while in the car. .40 is a little better, it doesn't seem to lose the lock nearly as much, if at all, but it does seem more "jumpy" than .30 was. I am testing .50 again right now to see if anything has changed.
I started with .30 had decent GPS locks, tho it was never under 2 minutes. .50 next, it's GPS was about the same on lock time but did disconnect from time to time, now on .40, still long locks, and in some cases 10+ minutes before it locks, a lot less disconnects.
Why was it we upgraded from .30? Did .40 or .50 offer anything other than slightly better signal? Where I live I can't tell a difference in signal, it just works. Anywhere in my town, even 8 miles out into the county, it just worked.
What would be any downsides with me rolling back to .30? At least it was more consistent on GPS locks.
BTC
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.