*** NOTE: For others that are coming to this thread because you have a similar issue, the problem is with the 3.27 radio ROM and is common to all custom ROMs and has nothing to do with dcd's ROMs. Hopefully will be fixed when new radio ROMs become available ***
I am running dcd's 2.3.2 ROM and it is great but I have found an issue with downloading files using IE or Opera. Opera seems to consistently freeze at around 172KB (+/- few KB) and then eventually says that the connection was interrupted.
If it helps, I also have 3.27.00 Radio ROM and Sprint PRL 60711 loaded.
Although I believe I recall this being discussed before, I could not find a thread so if one exists, please point me in the right direction.
Oh, and man is this ROM better than Sprint's ROM!
Update: I just tried to download Adobe Flash Player 7 for Pocket PC and it downloaded fine. However, I have tried to download Live Search for Windows Mobile from http://m.live.com and it consistently fails. Could it just be a problem on certain sites, like m.mobile.com, in the way they handle downloads?
As a side note, I tried www.dslreports.com/mspeed to test my internet speed and I was averaging about 600kb/s. I thought revision A should be faster than this? This got me to wondering, how do you know if you are in a revision A area? I mean, Sprint says that I am but the phone just shows Ev... is there supposed to be a different icon for revision A speeds version revision 0?
I'm beginning to wonder whether or not the problem with live search is not based on MS's site. I had a problem downloading it, but not a problem downloading anything else. I've seen quite a few problems downloading it (from phones, of course). Wouldn't surprise me if it was indeed on MS's side. They aren't known for being stable
The problem is a bug in the 3.27 Radio Rom, Not the stuff DCD has done.
The Radio (which is what enables the GPS and Rev A) is a leaked beta and will choke on large downloads.
Doubt DCD (or anyone else other than HTC) will be able to fix this. It is also likely the reason the official release of the GPS Rev A Rom from sprint has been delayed.
Asphyx said:
The problem is a bug in the 3.27 Radio Rom, Not the stuff DCD has done.
The Radio (which is what enables the GPS and Rev A) is a leaked beta and will choke on large downloads.
Doubt DCD (or anyone else other than HTC) will be able to fix this. It is also likely the reason the official release of the GPS Rev A Rom from sprint has been delayed.
Click to expand...
Click to collapse
I hope someone 'leaks' a better radio soon.
BTW, it isn't directly size related. I have downloaded very large files, and I have had it hang on smaller files.
I didn't want to make it seem like I was placing blame with dcd... his roms are so much better than Sprints that it is not even a competition. I really just wanted to confirm that the problem existed on other phones besides my own that are running dcd's 2.3.2 rom. It sounds like my suspicions of the 3.27 radio being the culprit are correct. I am happy... in a tongue in cheek way... to know that you are all having the same problems.
Yep.. Cannot download microsoft live on mine and I using a different rom but the same radio.
I am still wondering how you know if you are using EVDO rev. A verses rev. 0. My icon always shows Ev... is there a different icon for rev. A and I am just not getting it? How do you know your phone is using rev. A besides testing your download speeds?
I noticed that you can't download the cab from wls.live.com on a laptop if you teather through the PDA either. Very odd.
I haven't seen anything to indicate rev A either.
Confirmed that it does not work for me tethered to my laptop either. I am not really surprised though, it is still using the same radio. I definitely would not go back to a stock ROM for this minor issue though.
Still waiting for someone to confirm or deny that a separate indicator exists for EVDO revision A coverage. Mine always shows Ev or 1X.
Related
... for battery life, reception and overall usability in Japan?
I currently have radio version 1.16.00.00 and seem to get great reception
and a full day's use while doing a lot of stuff on my X01HT and still get home
at the end of the day with anywhere from 30~50% left on the battery.
Is there one radio version that better than another for Japan's coverage
areas?
TIA
AquiEsta! said:
... for battery life, reception and overall usability in Japan?
I currently have radio version 1.16.00.00 and seem to get great reception
and a full day's use while doing a lot of stuff on my X01HT and still get home
at the end of the day with anywhere from 30~50% left on the battery.
Is there one radio version that better than another for Japan's coverage
areas?
TIA
Click to expand...
Click to collapse
Definatly update your Radio atleast to 1.27.00.00. Radio versions below that have been pretty much invalidated by updates now.
If you Update to the latest radio, and see how that goes...you can swap between versions aslong as they use BL 107 or higher.
mrvanx said:
Definatly update your Radio atleast to 1.27.00.00. Radio versions below that have been pretty much invalidated by updates now.
If you Update to the latest radio, and see how that goes...you can swap between versions aslong as they use BL 107 or higher.
Click to expand...
Click to collapse
Thank you for the information and the link.
I was actually thinking of going to the 1.41.0.10 radio since the X01HT
would be at 1.41.1.10 if it were "locked-up" by SoftBank's 0182.exe file.
I was just not sure if that was a wise idea because I had heard some
complaining of short battery life with certain radio versions and ROM
combos.
It's odd that after installing dutty's WM6 v2 my radio version seems to have
gone done to 1.16.00.00. I just thought that was suppose to happen due to
better performance but then I know very little about radio versions.
Thanks again for the info.
mrvanx said:
Definatly update your Radio atleast to 1.27.00.00. Radio versions below that have been pretty much invalidated by updates now.
If you Update to the latest radio, and see how that goes...you can swap between versions aslong as they use BL 107 or higher.
Click to expand...
Click to collapse
I'm not sure why I keep getting a warning from the "Mega" site claiming that
I'm already downloading something when I'm not. It won't allow me to down
load the 1.41.00.10 radio until I finish downloading the "other" file. I guess
it must be the fact that I'm using a cable internet provider and the IP
address is 'shared' through their system so that it appears as though I'm
already downloading something.
Do you know of any other 'safe' locations to get that file?
Ahh, found it after a bit of searching here. Funny thing when you do a
search here on xda-developers for '1.41.00.10' you will get nothing but
when you try that on the XDA-Wiki you still get nothing until you search
again under the 'find page' page and in the FullTextSearch field.
So I did find the link to the 1.41.00.10 radio for the MegaUpload site again
but also the XDA FTP site as well.
Flashed the radio and I'm up at 1.41.00.10 now.
Thank you for the help!
Now onto trying to kill off that nagging welcome.exe that keeps showing
me the white screen requesting the SIM unlock code everytime I put my
Rogers SIM card in when I travel back to Canada.
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'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.
Ok, so I have searched and read thru the current radio treads. But havent seen much on 2.41.04.02.02, which i currently have. But my signal is not to great in Brooklyn. Should I try to flash to a different radio, and if so which one? Can you go down, or only flash up? Thx
Radio Search
It was about 3 pages back in the thread July Radio?, This is the radio from the Verizon 2.1 OTA update back in July. I can't attest to how well it will work but since it is the most recent radio that Verizon has issued I would assume it should be good 2 go.
July OTA Radio Post-XDA
alphawolf36 said:
Ok, so I have searched and read thru the current radio treads. But havent seen much on 2.41.04.02.02, which i currently have. But my signal is not to great in Brooklyn. Should I try to flash to a different radio, and if so which one? Can you go down, or only flash up? Thx
Click to expand...
Click to collapse
Appearances are that you can use any radio version with any ROM (on the Eris, at least). I've mixed-n-matched all sorts of combinations, with no apparent (i.e., readily-observed) troubles.
IMO, it is somewhat unlikely that you will see any difference in signal strength. The radio firmware codes are pretty mature, and the minor revisions in their behavior are things which are probably only detectable by the carrier. (There is not a shred of credible evidence of people observing "beter signal" as a result of radio firmware upgrades on the Eris.)
bftb0