Related
Well I loaded in the new sprint rom last night, and now my phone is completely useless. The radio has major problems, my signal goes from nothing to 4 bars, back and fourth, and the phone goes into permanent sleep mode when I let it sit. I found this out when I woke up this morning and missed 10 calls from a client havign an emergency overnight... wonderful. I have it sitting here on the desk, and it will go to sleep and require a reset every hour or so.
I haven't had any of those problems.
WM6 lag is basically gone now and the keyboard lag is gone.
Everything is WAY more responsive and the memory leaks seem better so far.
The memory "leak" / Cacheing is more managable, and the device isn't as laggy.
I've had no problems at all. I'm loving it.
cbunting said:
Well I loaded in the new sprint rom last night, and now my phone is completely useless. The radio has major problems, my signal goes from nothing to 4 bars, back and fourth, and the phone goes into permanent sleep mode when I let it sit. I found this out when I woke up this morning and missed 10 calls from a client havign an emergency overnight... wonderful. I have it sitting here on the desk, and it will go to sleep and require a reset every hour or so.
Click to expand...
Click to collapse
my MOGUL also goes into Perminant sleep if I let it sit.
i've had to take out the battery about 4 times just today.
anyone know why this could be?
Me too
Got the same problem installed last night. Woke up got into the car and checked phone sleeping had to soft start. Then same thing at least 3 times today. Also watched a short video in MP and it was show a few sec then sleep. Soft start and then you could watch it. Seems like after being on for a couple of hrs phone runs out of memory or something a freezes up?
claude9039u said:
Got the same problem installed last night. Woke up got into the car and checked phone sleeping had to soft start. Then same thing at least 3 times today. Also watched a short video in MP and it was show a few sec then sleep. Soft start and then you could watch it. Seems like after being on for a couple of hrs phone runs out of memory or something a freezes up?
Click to expand...
Click to collapse
Check your power setting setup, maybe it's set to turn the device completely off after 1min etc... For some reason my phone never shut off even if I let it set idle for more than 30 mins like it was set to do. Perhaps with the ROM update it actually does what it's supposed to now. Just an idea.
it's not supposed to TURN OFF as in shut down, it's just supposed to sleep. and it never comes out of sleeping mode. i've had numerous other problems, with bluetooth, etc... going back to Colonels rom, which was much more dependable.
cbunting said:
Well I loaded in the new sprint rom last night, and now my phone is completely useless. The radio has major problems, my signal goes from nothing to 4 bars, back and fourth, and the phone goes into permanent sleep mode when I let it sit. I found this out when I woke up this morning and missed 10 calls from a client havign an emergency overnight... wonderful. I have it sitting here on the desk, and it will go to sleep and require a reset every hour or so.
Click to expand...
Click to collapse
i too loaded it yesterday as well, but i want to wonder if you did a hard reset before you installed the rom. i did it, and it gave me no problems at all with radio version 1.47.00... oh, and the phone automatically cuts off when the alarm goes off while you charge it overnight (a big no-no, but you probably know this as well, but i ain't mad at ya). if you got anything, feel free to PM me. thanks in advance.
Thesian said:
The memory "leak" / Cacheing is more managable, and the device isn't as laggy.
I've had no problems at all. I'm loving it.
Click to expand...
Click to collapse
Mine's still leaking, badly too.
Any of you try to use BT on this new rom?
If you did you'd know that this rom is worthless
-mark
The culprit appears to be the 1.47 radio. The 1.47 radio coupled with any rom version will experiance sleeping, bt and other problems.... so I am rolling back to 1.40 radio to see how it acts
As a tech in a corporate sprint store, i'd be interested in the details behind this "sleep mode" issue. What are ppl running? How can I, in the store, reproduce the problem? Is it reproducable on command or guaranteed, or is it hit or miss?
As I've said, I have the new Rom and Radio, and have no new issues, and the memory "leak" / cache issue isn't gone, but its definetly not as bad, the OS even seems to have a SLIGHTLY smaller ram foot print... maybe just a few megs smaller, but smaller on my device.
cbunting said:
The culprit appears to be the 1.47 radio. The 1.47 radio coupled with any rom version will experiance sleeping, bt and other problems.... so I am rolling back to 1.40 radio to see how it acts
Click to expand...
Click to collapse
I tried that. The 1.40 radio with the new ROM still had all the new bugs.
D-pad cutting in and out...
I have found that if I push the power button to put the phone to sleep when it stops working, then turn back on, the d-pad works again. This seems to get it back to working. I wish that they could just get it right...
Jim
How do you get the new ROM?
I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
What programs are installed that could cause problems?
What registry hacks have been done that may cause problems?
What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron
Sorry, it's not anybody's installed programs. The bugs show up with nothing else but the bare ROM.
It's a train wreck.
There are more details on ppcgeeks and pdaphonehome -
http://forum.ppcgeeks.com/showthread.php?t=10366
Basically, on a stock ppc-6800 phone with nothing else installed, the BT keeps shutting off.. For me whenever a call comes in or after using my headset for a few minutes on an outgoing call...
-mark
Clean rom, nothign changed at all, it sucks, clearly. We are the beta testers obviously, as usual, with most products today
I installed the new ROM after backing up with SPB Backup, then installed my backup file back on and I haven't noticed any issues. I don't use bluetooth however, so I can comment on that. But, I haven't had the sleep issue others are describing either.
There have been multiple cases of Radios suddenly stopping to work lately. This is not related to NO GSM error as these occur while phone is in use and not while flashing.
Symptoms are as follows:
- Radio suddenly ceases to work (no signal with any SIM), or its condition deteriorates over the time.
- While trying to flash a different Radio ROM, the upgrade stops at 0% and bricks the device
- Devices can be recovered to operating state, however only OS is intact and GSM radio does not work.
- MTTY gives no feedback
- Information about device resembles these symptoms:
Radio Version : Nothing
Protocol Version: Nothing
IMEI : Nothing
Possible causes of this problem:
- Hardware fault
- Radio ROM corruption
- Bad blocks in NAND
This phenomena seems to be the new source of bricked Hermes devices and the number of occurences is growing.
Threads of people with this kind of bricks:
http://forum.xda-developers.com/showthread.php?t=346315
http://forum.xda-developers.com/showthread.php?t=345230
http://forum.xda-developers.com/showthread.php?t=347145
http://forum.xda-developers.com/showthread.php?t=346894
http://forum.xda-developers.com/showthread.php?t=338413
http://forum.xda-developers.com/showthread.php?t=322587
http://forum.xda-developers.com/showthread.php?t=325018
http://forum.xda-developers.com/showthread.php?t=343260
There also were some threads with this issue in the Hermes WM6 forum.
What we do not know is:
- What was the last radio version those people used?
- Did they use custom ROMs or did it happen with official ROMs too?
- What do these cases have in common?
- Is it really a hardware fault (no results from the service centers so far)?
- Can something be done to prevent this kind of bricking?
- Anything that might help those people recover the phone capability of their devices.
Please share your knowledge about this problem so we can know what kills our device's radio.
Common symptoms:
ROM with radio (both official and unofficial) - flash stops at 12% (magic number?)
Radio ROM stops at 0%
After reading a lot about flashing - upgrading the Tytn, i think the first question to be answered is:
Has anyone with an official untouched device had the radio death situation??
(i.e never had any cooked-baked-boiled rom or radio other than the official flashed on the device)
On every incident i have read, there was at least one mentioning of "Unlock, SuperCID, HardSpl, cooked XXXX-WM6 rom, and so on.
Is it a coincidence?
Dont get me wrong, i my self love this forum and have used tools and roms many times (previously on my MDA Pro and now on my Tytn).
my unit started the NO GSM syndrome just 3 days after i upgrade to 1.54.00 radio..
ROM without radio - flashes 100% working
ROM with radio (both official and unofficial) - flash stops at 12% (magic number?)
everyone else has thier rom + radio flash stop at 12%
I would add: http://forum.xda-developers.com/showthread.php?t=343260
First post updated with your comments&link.
I opened mine this week, cleaned the inside and also taken the metal covers inside off. One very small chip looks like it has a little brown spot on it, like it has gotten too hot.
Don't know if this is the problem or not, but i think it has to do with the radio and that it's fried
my radio rom was 1.54 something i believe.
and before it broke my phone started to hang short times for a few weeks and when it got back the radio signal was also lost,so i guess it was starting to break down
now it is just a pda, i connect it to internet through my old phone, but it takes 5 minutes after turning on before it will use bluetooth, some programms also refuse to start in the first 5 minutes.
I have been seeing what I think is the beging of this issue. It started about a week or so ago, my phone locked up on a call so I soft reset it. IT cam back and I was able to use the phone again. About ten minutes later it locked again and this time when it came up my passcode would not work. After trying to log in 8 time it hard reset itself. I let it reset and then I upgraded my radio from 1.48 to 1.54.07.00 as I thought the radio was hanging the phone. A few days went by and everything was fine. Then I started to notice the radio was completely loosing signal and seeminlgy locking the phone. The only fix seemed to be a soft rest (at the time) This went on for a few days and eventually my password died again after a soft reset. and it hard reset me. At this point I upgraded from vp3G 3.0 to schapps 4.20 and 1.54.30.10 for the radio. Again it helped for a day or two maybe but it has not started to loose radio signal completely (no service and modem disconted error etc were I always have signal) I have tryed a few diffrent rom and radios in additon to all of these and still get the issues. Last night I got some more clues after installing the new google maps with the my location "soft gps". I was playing with it on my ride home folling my trip etc and about 25 min in my radio started acting up. This time the only thing that fixed the issue was to remove the battery and sim card and put them back in. I am startign to think this is a heat issue in one of the radio components. I also have a ruberized cover which could contrinute to a heat issue. Also for the record I have IPL-1.04 and SPL-2.10-0lipro.
Can anyone comment on ROM botloader etc AT&T would want to see on the phone if I got them to replace it? It is only like 3 months old.
Ma
Great idea to open this post. Here's my experience of 2 issues I had this week:
First, I changed the ROM to HC Lite, and the Radio to 1.54.30 last week-end.Before that I never had an issue with GSM.
3 days later I operated a clean-up, using Oxios Close-Apps and Hybernate.1 or 2 hours later, the GSM signal disappeared, and the green button stopped responding. I also noticed I was unable to open "Contacts". Nothing would make it come back, not even a soft reset.
What I did is a Sprite backup, in case, then a hard reset. Everything was then back to normal, so I restored the backup, and it kept working! Now the sad part is that the exact very same event occurred today.
I'm a bit confused whether the issue is hardware related, or is it to do with the radio, the rom..? Anyway, I will right now change the Radio so as to see if any improvement. Your comments will surely be appreciated.
It seems to be related to the newer radio versions. I am running the 1.47 that came with the official Dutch WM6 Rom and have had no problems what so ever with Schaps Rom. So my guess is that it is related to the 1.54 versions of the Radio.
Anyone had these problems with the older radio versions?
Just thought I'd add some info to this topic. I have been running Radio 1.54.00.10 for about 1.5 months with Schaps 4.20 and vp3G's 3.62.3 and have not had any problems with reception, phone use, etc, but I ran 1.54.07.00 radio for 2 days and it was terrible.
It would hunt forever for a signal. If I went into a building and lost reception, I would have to soft reset to get a signal (after I left the building). I figured something was gonna get damaged(too much heat).
I don't know if anybody's experience with that version was as bad as mine, but I hope this problem can be narrowed down to a particular radio rom.
sbrown138 said:
I have been seeing what I think is the beging of this issue. It started about a week or so ago, my phone locked up on a call so I soft reset it. IT cam back and I was able to use the phone again. About ten minutes later it locked again and this time when it came up my passcode would not work. After trying to log in 8 time it hard reset itself. I let it reset and then I upgraded my radio from 1.48 to 1.54.07.00 as I thought the radio was hanging the phone. A few days went by and everything was fine. Then I started to notice the radio was completely loosing signal and seeminlgy locking the phone. The only fix seemed to be a soft rest (at the time) This went on for a few days and eventually my password died again after a soft reset. and it hard reset me. At this point I upgraded from vp3G 3.0 to schapps 4.20 and 1.54.30.10 for the radio. Again it helped for a day or two maybe but it has not started to loose radio signal completely (no service and modem disconted error etc were I always have signal) I have tryed a few diffrent rom and radios in additon to all of these and still get the issues. Last night I got some more clues after installing the new google maps with the my location "soft gps". I was playing with it on my ride home folling my trip etc and about 25 min in my radio started acting up. This time the only thing that fixed the issue was to remove the battery and sim card and put them back in. I am startign to think this is a heat issue in one of the radio components. I also have a ruberized cover which could contrinute to a heat issue. Also for the record I have IPL-1.04 and SPL-2.10-0lipro.
Can anyone comment on ROM botloader etc AT&T would want to see on the phone if I got them to replace it? It is only like 3 months old.
Click to expand...
Click to collapse
I had the same kind of behavior with mine. Radio was 1.47
After a few days of similar misbehavior... the radio died
sdemon said:
It seems to be related to the newer radio versions. I am running the 1.47 that came with the official Dutch WM6 Rom and have had no problems what so ever with Schaps Rom. So my guess is that it is related to the 1.54 versions of the Radio.
Anyone had these problems with the older radio versions?
Click to expand...
Click to collapse
Nope, I had it with 1.47 back 6 months ago...
By the way
To me it is obviously hardware related: if I try to flash the radio 5 or 10 times I end up managing in flashing it (I have to try, retry, etc...) with another radio. However... I still have the No GSM issue, even after the new radio has been flashed
It's the best proof soemthing is broken inside, not just the radio
Alcibiade said:
I had the same kind of behavior with mine. Radio was 1.47
After a few days of similar misbehavior... the radio died
Click to expand...
Click to collapse
I've had this issue with every radio after 1.47, and multiple cooked ROMS, I've tried every radio newer than 1.47 with a bunch of different ROMS. My phone hasn't died....yet but I wouldn't count on it in an emergency or any urgent situation.
I haven't even had this phone 1 year, no way I'm going to spend 300+ AGAIN because of a ****ty HTC product.
What error messages are you guys getting?
I get (not verbatim) the following very often:
phone not ready, wait 15 seconds
answering modem has disconnected
(not a message) searching for signal
(not a message) no signal, just a ! in the signal meter
call not completed
(not a message) phone hangs when dialing a call
(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.
I have noticed lately that I have less problems in 3G areas.
eagercrow said:
I've had this issue with every radio after 1.47, and multiple cooked ROMS, I've tried every radio newer than 1.47 with a bunch of different ROMS. My phone hasn't died....yet but I wouldn't count on it in an emergency or any urgent situation.
I haven't even had this phone 1 year, no way I'm going to spend 300+ AGAIN because of a ****ty HTC product.
What error messages are you guys getting?
I get (not verbatim) the following very often:
phone not ready, wait 15 seconds
answering modem has disconnected
(not a message) searching for signal
(not a message) no signal, just a ! in the signal meter
call not completed
(not a message) phone hangs when dialing a call
(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.
I have noticed lately that I have less problems in 3G areas.
Click to expand...
Click to collapse
I have the EXACT same problem as eagercrow. The only difference is that I HAVE NOT *repeat* HAVE NOT mod, or use any cooked ROMs. When i'm using WM5 and radio 1.04, the problem did happen very often. Then when the official WM6 witn radio 1.47 release by HTC, i flash it straight away. It clears all the problem for a few month but some of the problem start to appear since last month:
answering modem has disconnected
call not completed
(not a message) phone hangs when dialing a call
(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.
It happen in any area with weak network (less than 4 bar/full), either 2G, 3G or 3.5G.
For answering modem disconneted, i have to shut down the phone and remove the battery to solve he problem. I must say that the problem may be due to heat. Since when i using it as a modem, the phone gets pretty hot.
I wonder why since i'm using the official ROM only (i've never use any cooked ROM). Even HTC servrice center can't really solve the problem. (my phone board controller was faulty and HTC changed it for me. After that all those problem just vanish for a few month). HTC says its normal!. I paid almost USD600 for the phone. I'm thinking of getting O2 but my friend says he had almost similar problem.
Wonder why......
I forgot to add one more problem to the list, phone sometimes will not disconnect from a call, I have to soft reset
eagercrow said:
What error messages are you guys getting?
I get (not verbatim) the following very often:
phone not ready, wait 15 seconds
answering modem has disconnected
(not a message) searching for signal
(not a message) no signal, just a ! in the signal meter
call not completed
(not a message) phone hangs when dialing a call
(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.
Click to expand...
Click to collapse
I get most if not all of these 'errors'.
eagercrow said:
I forgot to add one more problem to the list, phone sometimes will not disconnect from a call, I have to soft reset
Click to expand...
Click to collapse
I get this one alot! But first it drops the actual call then just hangs the dialer.
two more to the list:
- long error message about the number not being right or something
- call not completed
sbrown138 said:
I get this one alot! But first it drops the actual call then just hangs the dialer.
Click to expand...
Click to collapse
Yeah that is what is happening with mine, the phone call is ended but you wouldn't know it by looking at the phone.
Well i didn't do my searching right, so i posted my issue in a new thread...
My issue is almost the same...It all started with BT getting disconnected from headset, and only soft reset will connect again...and then, radio started to act up. Phone went to sleep one night, and the next stay when i tried to wake it up, it wont wake up. Had to reset it to wake it up...it came back up, but when i plugged it to the puter, the puter wont recognize it. Here is what has happened so far...
1. GSM works after soft reset, and when on phone the phone freezes. Soft reset is the only option...(call is continued until soft reset)
2. BT will disconnect and will take forever to start up
3. Phone will not be recognized by PC (USB device not recognized error)
3. Can flash OS, Splash screens, ext ROM using SD flash method, but will not flash OS with GSM...hangs about as soon as it starts GSM (about 12%)
4. GSM, protocol numbers are still intact
My phone is less than 2 months old and i didn't get my phone through AT&T, so no warranty...kinda screwed eh I think this is a hardware problem...
Occasionally I will try to make a call and will connect, but will not get any audio either way, this is also happening on incoming calls.
The only way to fix this is to reboot the phone, I haven't tracked down what causes it to start doing this, but has anyone else had this problem?
I never had this problem with 3.2.3.
This started to happen to me recently too. Can you end the call, I couldn't. Also, is your phone running dog slow too? I ended up having to hard reset my phone. Works great now.
vbundi said:
Occasionally I will try to make a call and will connect, but will not get any audio either way, this is also happening on incoming calls.
The only way to fix this is to reboot the phone, I haven't tracked down what causes it to start doing this, but has anyone else had this problem?
I never had this problem with 3.2.3.
Click to expand...
Click to collapse
try reinstalling your radio.
Same problem here
I warranty-replaced my first Titan because of these exact symptoms with both the stock Verizon ROM and dcd 3.1.6. I got my new phone (this time with 3.2.6 and 3.42.50) and still the same problem, although less frequently now.
I haven't found a solution yet, but I'll let you know if I do.
We've got 5 phones running 3.2.6 in my office. I was having quite a bit of problems running 3.2.6 and the 3.42.30 radio, it's happened once in a week with the 3.42.50 radio.
Phone runs really good otherwise, but having the actual phone part of the Titan not working 100% is very frustrating...
I was also having the problem and sent back the phone and got a new one then updated to 3.4.4 and it has continues to happen any ideas why
Recently my phone has been suspending the screen and not bringing it back when I press the power button. I was running 3.2.6 before, reverted to 3.2.3. Tried hard-resets, taken out the battery, tried running with just the rom and nothing else installed after flashing, still doesn't work.. I've also tried taking out my memory card and running without that.
The power button still works because it will still turn the phone on, and bring the phone out of sleep sometimes, but if it doesn't work on bringing it out of sleep it seems that I have to soft-reset or the phone just doesn't work...
Any suggestions? Also.. I this is a bell phone, they have stock roms available on their site, but am I able to get the stock bootloader back on in case I have to warranty this thing?
You've tried most things that people could suggest, however have you tried a different ROM?
I know this used to be a very common problem when the Tilt came out, but once everybody started changing ROMs, it slowly disappeared.
My suggestion in short: Try relocking the bootloader
My Two Cents:
This is actually the most evil bug ever for this phone. I got this bug on my Sprint Mogul and couldn't get rid of it. Some people say it's because Java is running and then causes the phone to hang, but I never found that to be the issue. I got a Verizon XV6800 and experienced this problem only when I was flashing from stock to dcd 3.2.6. It occurred after I unlocked the bootloader, but after I flashed to dcd it went away. It was between having the stock and dcd roms that I found that most people experienced this problem when the loaded they new bootloader.
If I had to guess, based on my knowledge of operating systems, that some process is taking up a lot of resources, mostly CPU time, and is not allowing the phone to come out of standby. I guess this because sometimes I have had this happen and the screen would come on after a LONG delay.
Over the past week or so my phone has decided just to cut off while in my pocket, it turns back on right away. I can't seem to pinpoint any particular time that it turns off because I don't know it's off until I look at, although oddly it seems to happen only when I am at home. It is rooted and running BAMF with new radio and the default BAMF kernal. Also there was a full cell phone coverage outage in my area recently if it has anything to do with the new radio.
Possibly overclocked your kernel too much? Or maybe with the new BAMF feature of waking your phone on the volume keys you are waking and rebooting your phone without realizing it?
Thanks for the reply, I will try changing kernal settings and see if I notice any change.
fireminion said:
new radio
Click to expand...
Click to collapse
There's your problem, I'll bet.
I was fine with the "old" (original) radio revision, but I upgraded to the rooted, but otherwise stock "leaked" version, which included the new radio stuff. It seemed to be fine at home, but I was travelling out of town today, and it rebooted at least 5 times this morning. 3 of those times, without having really done anything with the phone. After a reboot, I'd connect to the WiFi at that site, then just let the phone sit on the table - it would reboot again within an hour. I did try with cell set to both LTE+CDMA and CDMA (auto), didn't seem to make a difference. Maybe it depends on what brand of local BSS/BTS (Nortel, Lucent, Motorola).
So, I flashed the old radio back on (didn't change anything else). It went the rest of the day without rebooting.
I realize this is just one anecdotal bit of data, but it sure points to the new radio, in my case. If you look around, others have blamed reboots on the new radio release, too.