Related
hi there, i recently upgraded my rom from the orginal orange one, as my phone was playing up. it was always not wanting to wake up from going in to standby without doing a soft reset. so then i upgraded to the WM6 vinilla rom, the same thing happened then but it was alot worse, then upgraded to the 0.21 rom. and im still getting the problem, without having any new programs installed its still doing it, so im not to sure whats the cause?
heres some info about it. Im in the UK with the network Orange too.
Thanks.
Radio Version: 1.06.00.00
Protocol Version: 32.37.7010.01W
ROM Verion : 3.22.110.1
Hi,
I have also recently upgraded from the original Orange rom etc to XDA Live 0.2.1. I also had occasional (only occassional) failure to wake up issues.
Since upgrading I have not had this, and the ROM is much faster and seems more stable. Today I upgraded my radio to 1.27 as well, but too early to comment on that.
I also use Phone Alarm, SPB Time, SPB Weather, and Pocket Plus. I had an issue with PA not changng profiles automatically but reverted to an slightly earlier version and touch wood it seems to have resolved it.
Can't really advise much theefore, but maybe the fact mine works (so far) could rule out a few things.
its really annoying, i would of thought that flashing a new rom it would be fine. but its still playing up, alot worse, i have to soft rest the phone everytime i want to make a phone call or to check i have a text. cant stand much longer of this. where can i get that radio rom from?
just flashed it with xda live 0.10 this time see if thats any better.
still no luck, fronzen about 4 times since i last posted. just wont wake from sleep, even if i set it to stay on without the backlight it will still freeze, im testing without a sim card in atm to see if that makes a difference,
anyone what can be causing this?
thanks.
@bomber456
Your Problem With The Calls In WMXL Is That If You've Upgraded Straight From The Orange ROM Then You Have An Old Radio Installed. Upgrade You Radio After Installing The WMXL OS And That Should Help Iron Out Your Calling Problems.
Cheers
Are you using a micro sd card?
If so, try starting from scratch WITHOUT putting the card anywhere near the phone. (ie don't use the card at all until you can prove it has nothing to do with it.)
Just a thought. I am sure some cards caused problems. (although I am using one (sandisk).
EDIT: Just seen Mousey's post - definitely a good idea, although I had the same radio as you using WM6 till I upgraded the radio today, with no problems.
where can i get a good radio for the orange network in the uk?
also i tried it without putting the sd card in and it was still the same. one thing i tried was not to put the sim card in and it was much better, dont think it crashed atall, so its down to the phone side of it.
thanks.
oh another thing, when flashing the rom it said it would take 20 mins, it only took about 5-7 mins maybe less :S is that a problem?
No. The XDA Live install is quicker than a normal rom.
"where can i get a good radio for the orange network in the uk?"
I am using 1.27 - check the wiki for radio only upgrades - same process as upgrading rom to XDA live but with a different file.
I understand that 1.34 or 1.35 are supposed to be OK, but anything from 1.27 should be OK - I have been using 1.27 today with no issues yet, but still early.
I am struggling to find any notes etc to specify the differences or specific advantages of the different radios.
Try one and see - DOESN'T NEED A HARD RESET.
installed 1.34 and its worse. losing signal etc. but im still getting crashes. i dont know what the hell is the fault. its so unstable its unbelieveable.
update : the phone doesnt crash or freeze or anything, if there is no sim card in the device. but it will crash when there is one in, i think its due to switching from 3g to gsm. also ive notcied that sometimes when i boot the phone where its supposed to display the radio and protocol info, it says no GSM!
ive now installed radio 1.27
would any software beable to still be in my phone after a rom upgrade?
any help would be great.
Perhaps try with a different SIM? may be a dodgy SIM...
seemed to work fine with my gfs orange pay as you go sim. but crashed once in a few hours. ive now unlocked my phone and CID unlocked it, and it hasnt crashed once. i think the boot number has cahnged from 04 to 06 too, seems to be stable now, (hopefully)
Radio confirmed in 6 dead GSM cases : 1.54.30.10
Radio stated in 5 dead GSM cases : 1.54.7
1.54.30.10 and 1.54.00.10 are known to have stability issues
Other 1.54 varients may have issues which are killing the radio hardware
As has been mentioned in other threads elsewhere and on another forum (win4mobiles) - there is presently an epidemic of GSM problems that seem to be plaguing users and either killing or bricking Hermes.
There are at least 14 cases around the Hermes area on this board now of people running a varient of radio 1.54 as their last radio then ending up with intermittent GSM or no radio - many being unable to roll back when problems start or finding bad blocks when telnetting into their phone to try and unbrick it.
I also have just learnt of another case here running 1.54.30.10 that's just died over xmas.
For technical discussion on these issues - see this thread
This is the one thing they all have in common and it's starting to look suspiciously like there may either be an issue with this radio or an issue with the radio when used on certain networks or combination of issues. Certainly, up to the 1.50 dying GSM modules was a little more uncommon and now there has been a splurge of them.
Just to remind some of the more inexperienced ROM experimenters out there - Hermes has a firmware driven radio in a custom chip and the radio images change how the hardware within the chip functions. It is quite possible for a bug in a radio to damage the hardware over time.
If the radio hardware itself gets fried then the only cure is a new motherboard, if the flash goes bad but the hardware isn't damaged then using the unbricking guide in the wiki you may be able to get some life back into it or roll it back.
So experienced users be careful until we know more, and inexperienced users please bear in mind that once you've found a radio that is good for you and works there is not much further point in trying every other radio.
Especially use caution with any versions of 1.54 at the moment until there has been more information collected about this.
Good to know...I'm staying away from that bad boy! It was odd that so many were having radio issues lately. thx for the notice!
A little alarmist..... That being said, read this:
http://forum.xda-developers.com/showthread.php?t=349461
Boiling it down, it doesn't seem to have any reliance on specific radio rom versions...
Hello mikeapollo, why apollo do you live in beswick
Anyway back on topic ,i have upgraded to 1.54 and then down graded to 1.50 and have had no problems with either radio and i have flashed my device more times than i can remember over the last few months, so maybe i am just lucky.
What type of herme's are the ones that are being bricked hermes 100 or hermes 300?
mine died way before I upgraded to the 1.5x radio, I believe it first started showing problems with 1.38, or 1.4something.
I don't think it has anything to do with the radio, simply people upgrade, hoping the latest and greatest radio will solve or help their problems. Then the radio completly dies and they are stuck with the last radio flashed.
If the latest radio was 1.12, I think you would see the same thing happening.
CRCinAU said:
A little alarmist..... That being said, read this:
http://forum.xda-developers.com/showthread.php?t=349461
Boiling it down, it doesn't seem to have any reliance on specific radio rom versions...
Click to expand...
Click to collapse
Well, there is an implication from that thread that the problem is 1.54.xx based.
But the core of Mike's post is that programming/reprogramming radio ROMs is not the same as flashing the OS. The radio ROM drives the radio output directly so if it accidentally sets too high a level then it can be like turning up your home hifi amp too high. And just like your home hifi, you can blow it up.
So being more cautious with radio ROMs is sensible advice. If a radio works for you don't go seeking even better performance because that "better performance" might be at the cost of increased gain and eventual failure of the radio hardware.
Incidentally, my son works in radio design and tells me that radio circuits are very sensitive to heat and can be damaged by overheating.
Richard
eagercrow said:
mine died way before I upgraded to the 1.5x radio, I believe it first started showing problems with 1.38, or 1.4something.
I don't think it has anything to do with the radio, simply people upgrade, hoping the latest and greatest radio will solve or help their problems. Then the radio completly dies and they are stuck with the last radio flashed.
If the latest radio was 1.12, I think you would see the same thing happening.
Click to expand...
Click to collapse
I see your point - thats why this thread is labeled potential problems... It is a warning and is not an alarmist statement of "This will kill your device" it is merely a caution that there are well documented cases of instability with this radio and there are growing numbers of dead radio modules which have all been using 1.54.x at time of death - and that death has occured within a few weeks of starting to use it.
Again, if you think that there is a sudden spate of dead radios because "things have worn out" then look at the evidence - Not everyones device is dying at the same rate but users of 1.54.x are seeing their devices dead within a very close timescale - usually 6-8 weeks of use. We've had lots of dead radio threads here but the amount over recent time is unpresedented and it's affecting both "young" and "older" devices.
If you cross-reference posts from the threads about 1.54.x some posters from there also posted in other threads about "odd" problems - then a month later have posted in the bricking threads saying their phone one morning just said "No GSM". Some of these devices appear to have been "new" - so unless they were exceptionally heavy users I think the rules out the devices wearing out. Again tho - they could have just been runts as you can get a duff one out of the box...
Radios normally don't just fail like that - the normal thing that happens is they degrade over time. The PGA that holds the firmware is also very resilient - once it's written unless something dramatic happens it will rarely just "grow" bad blocks overnight on it's own - particularly if it's turned on at the time - as it's structure is different to NAND memory (where your OS image is held).
So while it is certainly true that flashing 1.54.x will not instantly kill the device unless you're seriously unlucky - it looks like there may be an issue that either grows over time (a progressive effect) or causes dramatic sudden failure under certain usage scenarios (which may or may not be common to all areas/networks/bands/etc).
So if you're in a strong signal area and the radio hardware never needs to be driven "hard" by the firmware you may never experience a problem with this radio - but if you're in an area of variable or weak coverage it may just be driving the whole shebang too hard.
As Ree-shar has correctly said, the programmable arrays (where the radio firmware is held) and the output drivers in radio hardware are effected by heat - and looking at the facts, driving a higher power (gain) will generate more heat and drain a battery faster - that heat could be a factor in either the GSM hardware simply failing or (as has also been seen) the blocks in the PGA where the firmware itself is stored going "bad" therefore making it impossible to flash another radio image to it.
Again, it's not being alarmist it's about exercising caution that there could be a problem for SOME people with this radio and reminding the casual users of this forum of the basics about the radio images - and in particular :
having the latest release is NOT always the best option for your device,
many radios are developed for certain countries/networks/etc so one developed for an AT&T device in the US may not quite perform as intended when used in Europe so try and use one at least that is roughly native to where you are first if you can
Problems with heat, battery life, long drop out periods or "odd" radio issues can be a warning that something may not be right.
It is very possible for firmware to kill actual hardware (something people often forget).
Changing your radio will NOT fix broken SIM cards, WiFi, Bluetooth or external GPS problems, Nor will it magic up a signal from nowhere if you live in a crap coverage area.
Using firmware that drives the hardware harder in order to increase the gain of both the transmit element and recieve element in any radio module is usually at the expense of the lifespan of the radio device.
Always experiment cautiously, be aware of the risks and minimise them and read other peoples experiences before just taking the latest image and flashing it (ie - read the wiki, cross reference posts and take some time to do some research BEFORE flashing that new radio/rom/whatever!.
scousemartin said:
Hello mikeapollo, why apollo do you live in beswick
Click to expand...
Click to collapse
LOL! Went to school in Beswick - but given the Apollo is in Ardwick...
It's a nickname that just stuck from yonks ago during a more theatrical time of my life.. (and I live in Moston now).
scousemartin said:
Anyway back on topic ,i have upgraded to 1.54 and then down graded to 1.50 and have had no problems with either radio and i have flashed my device more times than i can remember over the last few months, so maybe i am just lucky.
What type of herme's are the ones that are being bricked hermes 100 or hermes 300?
Click to expand...
Click to collapse
From what I've cross referenced so far, 3 deaths have been Herm300 and 1 was stated to be a Herm200.
I'm trying to collate as much info as possible on this to find out if there is a definite correlation between this radio and certain models/networks/areas,
We've had dodgy radios released before but never a potential "suicide-bomb" radio hence my interest - (I'm still on 1.43 here with over 500hrs talk on the life timer and it's still going strong).
<conspiracy> On the other hand... Could 1.54.x have leaked out to help sales of the TyTN II </conspiracy>
Mikeapollo said:
having the latest release is NOT always the best option for your device,
many radios are developed for certain countries/networks/etc so one developed for an AT&T device in the US may not quite perform as intended when used in Europe so try and use one at least that is roughly native to where you are first if you can
Problems with heat, battery life, long drop out periods or "odd" radio issues can be a warning that something may not be right.
It is very possible for firmware to kill actual hardware (something people often forget).
Changing your radio will NOT fix broken SIM cards, WiFi, Bluetooth or external GPS problems, Nor will it magic up a signal from nowhere if you live in a crap coverage area.
Using firmware that drives the hardware harder in order to increase the gain of both the transmit element and recieve element in any radio module is usually at the expense of the lifespan of the radio device.
Always experiment cautiously, be aware of the risks and minimise them and read other peoples experiences before just taking the latest image and flashing it (ie - read the wiki, cross reference posts and take some time to do some research BEFORE flashing that new radio/rom/whatever!.
Click to expand...
Click to collapse
Man, this should be put to the wiki or to the every new Radio ROM thread.
KarhU said:
Man, this should be put to the wiki or to the every new Radio ROM thread.
Click to expand...
Click to collapse
Updated the wiki page with general advice.
I have been using 1.54.07.00 pretty much since I got my 8525 a few months ago and haven't any issues...yet . I flashed the 1.54.x radio when I tried out the official AT&T WM6 ROM, but since have been using schap's ROMs (no radio update). My question: is the official 1.54.07.00 radio from the AT&T WM6 ROM the same as getting a 1.54.07.00 from elsewhere?
gnahc79 said:
I have been using 1.54.07.00 pretty much since I got my 8525 a few months ago and haven't any issues...yet . I flashed the 1.54.x radio when I tried out the official AT&T WM6 ROM, but since have been using schap's ROMs (no radio update). My question: is the official 1.54.07.00 radio from the AT&T WM6 ROM the same as getting a 1.54.07.00 from elsewhere?
Click to expand...
Click to collapse
Yes. The official AT&T 1.54.07.00 will be identical to the extracted 1.54.07.00 as thats where it was extracted from - the clue is in the numbers
Also, if you are using the official radio update for your device on your network you should nothave nothing to worry about - and of course if it turns out there is a problem with this bit of firmware you'll be well covered by your network & waranty anyway.
Incidentally, quite a few people who have suffered the mysterious sudden "NO GSM" death problem can still boot their phones to the OS but generally have been unable to re-flash the radio so in the event of death it still seems possible to "roll back" the OS ROM to "the proper one" for waranty reasons <ahem>
Latest update on research - and general advice
NO-GSM bricks - 28/11/07-03/01/08 (from forums)
Type Location Radio Sudden death info :
--------------------------------------------------------
H300 UK 1.54.00.10 Yes Problem from 1.50 T-Mob WM6
H200 unknown 1.54.00.10 yes Unable to reflash radio
H100 Netherlands 1.54.30.10 no Gradual loss of service
H100 unknown 1.54.00.10 yes Died on soft reset
H100 Netherlands 1.54.00.10 yes Died after 12 days
H300 Germany 1.54.00.10 yes Died after 4 weeks
H100 Iran 1.54 stated apparently Died on hard reset
H300 UK 1.54.7 yes Dropouts then dead
H300 UK 1.54.30.10 yes Died rolling to 1.38
H300 Germany 1.54.00.10 yes Died after soft reset
H100 Netherlands 1.54.00.10 Yes GSM increasingly unrealible
H100 Singapore 1.48 yes No GSM after flashing black PRO
H300 Germany 1.54.00.10 yes Died after soft reset (2wks in)
H200 Pakistan 1.50 yes died reverting to 1.48
H300 UK 1.54.30 yes Unable re-flash bad blocks
H100 unknown 1.57 (?????) yes died in use 2 days post flash
n/A Spain 1.51 yes batt hot / 1wk then GSM fail
n/a UK 1.54.7 unsure GSM bad - Died flashing 1.4x
There are another 12 which I don't have quite enough detail on yet to class as a "No-GSM brick" so am not presently including them in this table.
Stats so far :
12 x European found and confirmed failures of which :
* most unable to roll back radio
* if able to - failure still occurs or
* All died after some sort of 1.54.xx flash regardless of rollback
* Majority seem to be European failures many on T-Mobile in Germany/Netherlands and UK
Pakistan/Iran - Actual ROMs and circumstances not clear. 1.5x quoted but no confirmation.
Singapore 1.48 failure - Included in list as failed between 28/11 - present.
NB
Statistically, more people are likely to run the more-recent ROMS so while the
evidence here appears to show that there is a risk with the 1.5x radios - many people with a TyTN in a questionable state of health will be running them anyway so do bear this in mind. Use this info to make an informed choice!!!
The common trend appears to indicate problems starting after flashing a 1.5x radio and staying even if they roll back *OR* dying when trying to flash a lower radio - Again, not conclusive but building a picture.
OFFICIAL updates
Users who are downloading OFFICIAL updates from their network operator, HTC or any other "official" source should not need to worry - whether there is an issue or not with radios 1.5x your network should support you in the case of failure as you have an "official" update. Especially as the "official" updates containing radio 1.51.xx and above seem to be in areas where "no gsm bricks" are not being commonly reported (as of yet).
General radio issues
To clarify one point many seem confused about - Your signal lock, radio stability etc is generally unaffected by the OS ROM as the GSM stuff is handled by the RIL itself.
The issues of things like the "dialler going weird", applications locking up, etc are generally NOT related to the radio ROM and are related to the OS ROM or combination of 3rd party apps/hacks and OS ROM.
Issues with "lost calls" or "unconnected calls" or "bad data" can be caused by the network itself. The T-Mobile 3G network in the UK is a good example where it has "off" days in some areas where people miss calls (phone never rings) or need to make 10 attempts to dial out.
Switching to GSM for a while, trying another networks SIM card or moving area often magically "fixes" these issues and by the time the user puts their own SIM back in or moves back into area the network has got it's act together again ;-)
Radio roms themselves only affect the radio interface layer (RIL) - the OS "calls" this when it needs to use it and this is where many people seem to be mixing up the issue of "stability" of a radio and "stability" of an OS ROM/application. (remember, the dialler IS an application)
If a radio is unstable - you may experience GSM/3G dropouts, calls breaking up, slow dialling or long signal searches but your OS should on the whole function fine.
If an OS or application is unstable - you may experience dialler lockup or failed calls (remember, the RIL tells windows to tell YOU that you have a call!)
but your GSM/3G signal should be solid, switch between bands and log on and off the network without any fuss.
Overall stability is not just dependent on the OS ROM you are using but also 3rd party applications. Problem solve your device BEFORE just flashing a radio to try and fix an issue as it may give you a nasty surprise and introduce MORE issues - then troubleshooting becomes even harder still and we end up where we are today...
When It's broke, It's BROKE
Some radios work better than others on different networks in different places - that has (and always will!) be the case. People though have become complacent in thinking that they are safe running any old bit of radio code from anywhere and are not looking into what effects it can have.
Many flashers don't even know that mismatched radio bootloaders can cause a brick and will have several fun-packed hours sat down trying to turn it into an "unbrick" (or just make it worse turning it into a breezeblock )
The radio rom itself effects how the RIL talks to the OS (windows) and how your signals get transmitted to the base station. Two separate things. Usually, the main bit which radio updates change is the radio stack itself - the bit between the radio hardware and windows - with minor tweaks to the radio hardware itself and how it's driven.
However, it is possible as well for a radio rom to drastically change how the radio hardware (the tiny transmitter in your phone) transmits
its signal onto the network... The tiny transmitter might have a current limit of, say, 50mA but there is nothing except software
to limit the current to 50mA... And software can have bugs or can be tweaked and could accidentally drive 100mA through it and burn the device out if it's in a given situation (like a poor reception area, switching bands etc)
IF (and it's a big if) you find that a poor radio has actually done something like this and caused physical damage to the radio hardware itself (overdriven an output for example) then
unfortunately that's it... It's knackered. No amount of rolling back will fix it to how it was. Like driving an LED with too much
voltage - it will never burn as brightly as it should have done had the specifications been followed in the first place.
Therefore, *IF* a radio like 1.5x turns out to have a bug and has introduced problems with the radio hardware itself - upgrading it or downgrading it will mean the problem will remain - At this point the only cure will be to have the whole radio PGA hardware replaced by a service centre.
Hence the importance of finding out *IF* we are seeing European devices being damaged in this way.
The better news about the RADIO failures (roll-back for warranty)
Most people who have experienced these recent failures find their OS will still boot - in which case it is possible to "roll it back" to how it was if you are under warranty. Don't worry about rolling back the radio - if it's dead it's screwed anyway so doesn't show any trace of what
radio ROM was on it in the first place. Just get the correct OS and bootloaders back on it.
T-MOBILE UK OFFICIAL WM6 ROM WARNING
I've given T-Mobile UK a call about this one... The "official" T-Mobile UK WM6 ROM is in effect a beta and while it is on Tmobiles own site, it IS NOT officially supported by T-Mobile
(according to tech support) and was not meant for general release. Therefore should be treated with caution until more is known and researched - however technically you should be supported and can roll back the device if necessary anyway to the official Tmobile WM5 ROM for warranty (which is, at least at the moment, available on their download site).
This ROM appears to contain radio 1.50 - ONE user (Sbirsen - view post) confirms he had problem introduced with radio 1.50 which was a perfectly working vario II, he upgraded to 1.54 and down but still suffered the problems which 1.50 introduced.
Despite his very kind assurance that there is clearly no problem with radio 1.54 we do not know if his device is dead or alive as he's moved onto trying to brick a TyTN-II due to getting fed up with radio issues apparently not caused by his radio flash
Back to unsarcastic mode - I suspect by T-Mobiles response - he is not the only one and some drilling on the board here may reveal more over the next
few weeks.
This ROM may also be pulled over the next few days due to "feedback issues" - sorry no more info on that one.
IN the mean time please just be careful when selecting your radios, fault find FIRST before thinking a flash will magic up a solution, do your research *properly* and look out for warning signs.
Further update - possible resolution to try if you've having intermittent problems and a very long theory posted here
In short - My thinking is if there is a bug in this radio it will be something to do with the PIC16LF72 chip with the D/A and A/D stuff that drives and measures outputs from the phyiscal hardware radio chips (the Qualcomm ones and the Anadigics amplifiers) on the main mobo.
A small firmware bug affecting values returned from D/A and A/D measurements
This bug or whatever causes either false return values or bad data
This causes radio to work harder
This then either causes wear or heat based issues on the PIC effecting the storage area and causing bad blocks (death) or causes damage to the rest of the radio chipset (qualcomm and anadigics amps).
PS. If any tech support desk needs a bum on seat in either North-West or the South East of the UK - I am now OFFICIALLY AVAILABLE FOR HIRE as I'm officially unemployed from tomorrow morning! I don't have a degree so never get through the paper sift (hence unemployed) but do have the experience and skills and plenty of developers certificates..I-thank-you.
Mike,
Heres another UK Tmobile Herm 300 thats Died
For the record this phone was brand new on 17th December 2007; only been flashed once to the official T-Mobile WM6.
timbouk said:
Mike,
Heres another UK Tmobile Herm 300 thats Died
For the record this phone was brand new on 17th December 2007; only been flashed once to the official T-Mobile WM6.
Click to expand...
Click to collapse
God they're dropping like flies! Sorry to hear about that
Bit concerning though as IIRC the TMUK rom is radio 1.50 but that's the 3rd report of someone having problems introduced by it. (will have to pull the .nhb apart and check). Cheers for the tipoff.
I fear the Hermes will soon be an endangered species - must be a marketing plan by HTC to flog the kieser
Edit :: durr - of course it's radio 1.50 - even your sig says that - I'm rebooting my braincell as I type
Yes, its the 1.50 (My signiture has correct details)
Not sure if this is worthy info; but at work one side of my building has a very low signal strength, so the radio works very hard to keep up the connection. I can tell it is as my battery can be virtually flat after, say, 6 hours!
Maybe its poor signal areas accelerating the radio deterioration?
I got 1.50, and I still have occasional issues, such as hardware buttons that stop functioning.
What other radio could possibly be safer? Maybe 1.43 or 1.47. I kind of remember they used to serve me well.
Mikeapollo said:
PS. If any tech support desk needs a bum on seat in either North-West or the South East of the UK - I am now OFFICIALLY AVAILABLE FOR HIRE as I'm officially unemployed from tomorrow morning! I don't have a degree so never get through the paper sift (hence unemployed) but do have the experience and skills and plenty of developers certificates..I-thank-you.
Click to expand...
Click to collapse
Would be glad to propose you such offer if I could... In the mean time, you definitely should post the same in the main section, given most viewers here are in the tech industry.
im using the 1.54.30.10 for last 2 months and its workg absolutely fine!!!!!!!!!!!!!!!!!!
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)
So I've done a lot of searching and haven't really found anything definitive. I've found that with some roms I'll lose GPS signal after a certain amount of time (say 10-30 minutes) and have to turn GPS off and back on or reboot the phone. I saw something about flashing a different radio may make a difference. Kinda just wanted to see other peoples thoughts on the issue or if maybe there is something else I can do before I go flashing a different radio.
Currently running CELB 4.1 and baseband 2.42.01.04.27 and I have the issue.. I've had it with most of Tazz's roms as well. KaosFroyo is the only one Ive used that I've never seen the issue with, but I'm really diggin CELB right now and this is the ONLY issue I've got with it.
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Bayhill Jacket said:
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Click to expand...
Click to collapse
I have now.. I did the reset and download options in the program. Too bad this isn't something I can quickly test. I'll report back with the results. Thanks!
I have noticed this as well. Last time it happened to me it was 4:30 in the morning, and the "GPS lost" message came up about 180 seconds before I had to make two freeway changes in an area I'd never been before. (CELB 3.9 and same radio as your case). Fortunately for me I had reviewed the route, so I more or less knew what to do.
If I recall correctly, it has always happened after the Nav app had been running for a fair bit of time - at least 30 minutes or more.
However, I don't know if it is something about the root ROMs or not - I started using rooted ROMs back in March or so, so I really don't have a tremendous operating baseline on stock 2.1 ROMs to compare it to. Maybe it is a problem there, too!
If I recall correctly, the last time it happened, I just pulled up GPS Status and asked it reload the aGPS state (without exiting the Nav app), and the Nav app seemed to gracefully recover.
Annoying? Yeah. I don't know what can be done about it, though - like the "undead calls" problem, it happens so infrequently that it is hard to know whether or not a ROM change actually fixes the problem.
bftb0
I had the same problem with every 2.2 rom I used GPS with. I decided to go back to 2.1 because I have been needing GPS alot more often lately but I havent tested it out since I made the switch. I'll try it out today and report the results tonight.
This same thing seemed to happen on the 2.1, CyanogenMod 5 based ELB by Conap as well. If it is happening with all of the 2.2 ROMs, I wonder if it's just a CyanogenMod issue?
See http://forum.xda-developers.com/showthread.php?p=6812308#post6812308 (this was not the only person reporting it, if you search that thread.)
I really don't think it's ALL 2.2 CM roms though. I've gone on 7 hour car trips with Kaos Froyo without a single drop.. to and from. I've seen another theory somewhere around here about it being certain hardware revisions that act this way with certain software builds. At lease we've got a thread dedicated to this issue now.. maybe we can get something figured out.
Still don't know if the GPS status program helps.. I left navigation turned on for a bit sitting in my house and it stayed connected for the half an hour I left it, just don't think that's gonna be an accurate test with not moving around and all. If it doesn't work I will try a different radio.. I saw somewhere one guy had good luck with a specific older version radio. If that's what it comes down to I'll try.
I have been having issues with the GPS working on both of my phones while using 2.2 roms. I switched to 2.1 a few days ago and I used the GPS on my way to work this morning and didnt have any issues. I also had to flash Senseable a couple of months ago while on a road trip because I was tired of loosing the GPS signal every half hour. It may be a CM thing.
Im having the same issues as well. Haven't found a fix yet..
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
deadbot1 said:
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
Click to expand...
Click to collapse
give us another update. is the gps problem still fixed for you? Thanks!
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Jrocker23 said:
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Click to expand...
Click to collapse
I've seen it on several ROM's as well. From what i've messed with, it doesn't seem to be dependent on the autokiller memory preset, radio firmware, or amount of overclocking i'm doing. It doesn't seem to be dependent on how many programs are running either. I usually have nav and pandora running while i'm in the car, and sooner or later, the gps poops out.
I feel like it seems to happen less, now that i'm back to using the on-demand governor. but that could just be in my head.
I've had to go back to a 2.1 rom because of it. Its very annoying when the goa signal gets lost right before the exit ramp.
Sent from my Eris using XDA App
Im thinking of going back to a 2.1 rom as well...
I have also seen the same results on any 2.2 or higher rom. I have since returned to XTRRom 5.0 and have not had a single problem with GPS on any of my jogging runs. I definitely think it is a CM thing. At least on my phone.
Using kaosfroyo v39 and I flashed that sprint phone radio on my eris and haven't had any gps issues. In fact, just the opposite. Mine would lock up before the v39 and the radio flash
I flashed that radio as well and today not one issue at all. Will test more tomorrow
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
haganme said:
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
Click to expand...
Click to collapse
Today I even flashed back to the July 2010 version (2.42.01.04.27). the gps dropped out almost every 5 minutes while i was driving around. that's the worst i've seen. So i flashed back to the 2.42.02.10.29 sprint radio again. I haven't seen very good navigation performance on the v1.1 gingershedbread overall, actually. my position on the gps nav doesn't update very often, although it seemed like the voice instructions were still pretty well timed as usual.
I "flashed" the stock ICS leak 3.11.605.22 and it worked awesome for like 2 weeks. Today I restarted the phone and it never came back on, it never booted up no matter what I did. I now have the replacement rezound and want ICS again, was this just a freak accident or did the RUU mess up?
Did you try a different battery? Id say the ruu had zero to do with it.
I certainly will not flash the leak on my phone. Its working too perfect to risk messing with uncertainties.
Personally, with all the reports of bad devices I would just wait a week or so to make sure your new phone doesn't have any issues before flashing anything.
I really wonder how many people blame the leak for bad phones. Seems like HTC had bad quality control when it came to the rezound. I feel lucky to have had no problems with my phone after reading all the reports of returns and heating issues.
I have had the ICS leaked RUU on my phone since the day it came out and have not had the first problem with it. The RUU didn't mess your phone up, a dead or faulty battery probably did.
It wasn't the battery, the Verizon rep tried a new one and he also tried both batterys in the new phone and they worked fine in the new phone.
The phone that messed up, I had for about 3 weeks or so with no problems. Then I used the RUU and it worked flawlessly for about 2 weeks, then BAM! now I have a brick.
since flashing the RUU i have radio issues galore. data just stops working. sometimes on wifi, sometimes on 3g, whatever.
tspderek said:
since flashing the RUU i have radio issues galore. data just stops working. sometimes on wifi, sometimes on 3g, whatever.
Click to expand...
Click to collapse
See I never had problems with the RUU itself. The radio worked tons better than it did before the RUU.
Now my new rezound won't read my sd card. I tried reformatting still doesn't read it.
For those of you who have flashed the RUU and are having problems, try flashing it a second time.
I paid particularly close attention during the flashing process and hand verified the versions of subsystem I could after the update. It turned out that the first flash only applied the hboot, kernel/boot, and a few minor systems successfully. After a second flash, everything applied correctly.
For instance, a number of people reported that the radio versions didn't change from the update, when in fact the radio changed significantly (currently running @ 1.22.10.0310r, 1.22.10.0308r).
After the update, I've found my battery life is significantly better than the GB kernels (I used BAMFs modified, Incredikernel and the Stock OTA). My reception is noticeably better, but I can't give a qualitative judgement other than that. And, most importantly, the phone is easily 100% more responsive. I used the stock OTA and BAMF 1.0.2 on and off for a while and unless I repeatedly killed background tasks my home screen (ADW Launcher EX) would stutter and lag, games would periodically slow down, web browsing would periodically freeze, etc. Now, my phone consistently has 300MB of RAM free (before it was usually less than 100MB). The leaked RUU is the best thing to have happened to the Rezound so far.
Note: despite my complaints above, my phone was always more usable than my OG Droid and my wife's dinc2, I'm just giving a comparative description.