I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
had this problem once: I switched on the camera, and then left the device on the table for a long time - so it went to standby.
I could not wake it up by the power button after 20 minutes, but as an incoming call came, it was ringing with a black display, and I could answer the call with my BT headset. screen was still pure black
finally I pushed the reset button and since then everything is fine - I still feel this was connected to the camera.
terta said:
had this problem once: I switched on the camera, and then left the device on the table for a long time - so it went to standby.
I could not wake it up by the power button after 20 minutes, but as an incoming call came, it was ringing with a black display, and I could answer the call with my BT headset. screen was still pure black
finally I pushed the reset button and since then everything is fine - I still feel this was connected to the camera.
Click to expand...
Click to collapse
Yeah if it only happened the once then that was probably the case, if you have the problem on a regular basis and you know its nothing to do with the camera (becuase you never loaded it) then you have the problem I am describing.
I have exactly the same problem has Terta.
I'm 100% sur that it's the camera that make this bug I have tried all my weekend to reproduce the bug a lot of time and it was always the camera...
Hope someone can fix this bug cause now I can't take any photo without soft-reseting my phone. Very, very, very annoying...
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Yes I guess there are many reasons for the Standby of Death, if you have ruled out all software causes such as the camera or installed apps then have a think about the SIM and/or the settings that impact the SIM.
Its the last thing most people will think about. It worked for me and got rid of a random SOD problem 2-3 times a week which coinceded with being in weak 3G areas (where the phone might switch bands automatically) although that never occured to me at the time.
You see I haven't installed other applications nor do I load up the camera and leave it running so I couldn't figure out what was causing it, it just happened randomly not connected with anything particular that I was doing.
i hope there is some kind of magical solution for this because i just got my Sprint TP2 today and I have this issue everytime my phone goes into standby. Pushing the power button wont bring it out but every once in a while opening the keyboard does. I have to continually reset my new phone just to use it
PS; beyond this annoyance, I love it!
coppertop24 said:
i hope there is some kind of magical solution for this because i just got my Sprint TP2 today and I have this issue everytime my phone goes into standby. Pushing the power button wont bring it out but every once in a while opening the keyboard does. I have to continually reset my new phone just to use it
PS; beyond this annoyance, I love it!
Click to expand...
Click to collapse
Try taking out the SIM card and see if it still happens everytime the phone goes into standby...
For the past few days I have been restarting my phone thru the soft reset. I think this is a windows issue...it has happened to me even without having the camera app running, and yes I checked the task manager. Hopefully this will be fixed when windows mobile 6.5 comes out, since Im getting frustrated with this phone...I have the phone for about a month now....grrr Stand by of Death!!!
coykiam said:
For the past few days I have been restarting my phone thru the soft reset. I think this is a windows issue...it has happened to me even without having the camera app running, and yes I checked the task manager. Hopefully this will be fixed when windows mobile 6.5 comes out, since Im getting frustrated with this phone...I have the phone for about a month now....grrr Stand by of Death!!!
Click to expand...
Click to collapse
so its not just mine then? this is ridiculous
Right, i had got seriously fed up with the standby of death happending, so i decided to contact HTC Europe directly.
They went over the usual 'factory reset' and 'update' solutions before coming to the conclusion that either there is a loose connection/faulty screen or there is some confiliction between drivers of the pre-installed software.
Because all HTC phones have 2 years warrenty as standard they have asked me to send if off so they can invistigate the problem and send me a replacement.
So if anybody is in the same boat as me a suggest you contact HTC and arrange a fix/replace.
Hope this helps.
nlel said:
Yeah if it only happened the once then that was probably the case, if you have the problem on a regular basis and you know its nothing to do with the camera (becuase you never loaded it) then you have the problem I am describing.
Click to expand...
Click to collapse
Add me to the list, seems to happen when I am charging my phone and it hits 100%
This phone reminds me of all my previous Sony Ericsson phones....very unstable OS' ... Makes me regret of getting this one and should've gotten an iPhone...but then again I'm pretty sure iPhone's have issues that apple fanboys aren't admitting. The reason that made me not get an iphone is because of ATT's ridiculous plan pricing...Its crazy!!!
if you are on sprints network, take out the sim card. This has fixed the issue for me. Used to get SOD a few times a day but opening the keyboard and then pressing the power button used to get me out of it. This was really annoying, and i read that it may be issues with the sim card. Took that out a week ago and havent had a SOD yet
jabberoo said:
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Click to expand...
Click to collapse
Jabberoo I can verify that this was caused by the SRS WOW HD program on my touch pro 2 as well. AS SOON as I uninstalled this application, restarted, everything was fine again.
I don't know if this will help anybody but if your phone suffers from SOD and you have TMO put it in airplane mode and see if it still does it.
I did that and it never went into SOD so that lead me to believe that the radio was the culprit. before that I tried everything listed. I don't have the 3G Plan so the 3.45.25.14 (T-Mobile) radio is the only one that worked for me.
I have the same problem.. just have installed spb mobile shell with mskip ultimate. I try to unistall all
I have a question: if I choose the 3G only option (WCDMA + UTMS 2100 in Europe) and the signal strength is low there will not be an automatic switch between 3G and 2G am I right? ...and i'm offline then
jabberoo said:
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Click to expand...
Click to collapse
sanjsrik said:
Jabberoo I can verify that this was caused by the SRS WOW HD program on my touch pro 2 as well. AS SOON as I uninstalled this application, restarted, everything was fine again.
Click to expand...
Click to collapse
Confirming this....
I had this issue for a while now...I tried hard resets, ROM flashes etc. It all works fine and was stable until I flash Sps Wow HD (I just realized this). Yesterday I flashed the latest HTC released sense ROM and right now after installing all the softwares I had the SOD again. Fortunately I saw the 2 posts and thought I will give it a try...and guess what?
I uninstalled the Srs Wow HD and phone is back to normal...no issues till now...will report later if I see any.
I am going to tmobile to get the SIM changed anyways hoping that it will fix another issue I am having. Every day I have to turn the airplane mode ON and OFF at least twice to get my data connection back. Mostly after a call and sometimes in random the phone is unable to reconnect to the data, it gives me an error that the epc.tmobile didnt respond or something like that. If any of you know how to fix this issue...plz help
I have been Experiencing this so called "SOD". HTC touch pro 2 sprint. On the 6.5.5 Build 23569 i had MAJOR sod issues. Energyrom , mighty , titanium , you name it. Ive Task 29 and reflashed them all multiple times. Still SOD was there... But i may have found a temp cure for me atleast. This is what i did....
First , i used task29 , next i reflashed the stock 6.1 rom, check for SOD... still had it... i task 29 again. Installed titanium edition , without sense. SOD was cured, phone worked fine, tryed to install sense 2.1, failed, SOD was back. Soo...
Then i task29 again, then repeated task29 a second time at the boot screen.... then i flashed Energyrom GTX themed 21907 build june 27th......Once it was flashed unplugged my USB plug and plugged it into the usb wall plug i have . Installed LUMOS, light sensor still was inactive and no response, could not brighten and still nothing... Installed G-light right after lumos without uninstalling lumos.... Still plugged into the AC wall USB plug....let it sit. Still nothing, couldnt adjust or brighten..... So i task 29 AGAIN... then flashed 21907 build GTX themed again... once flashed, unplugged it & back into wall charger... Installed lumos.... SUDDENLY!!! the sensor worked, and was accepting light AGAIN! ...
So i ran the LUMOS wizard, followed instructions and my phone was SOD FREE!! Let it sit over night, was fine....I wanted to see now if i could overwrite / flash over GTX themed with DiNiK glass cause i liked it better... so i DID NOT USE task29 this time, just reflashed over GTX themed one With DiNiK glass... same build 21907 and followed all my same steps, with wall plug, installed lumos, did the wizard,.... WALAaa.... works still like a charm. Have been using and testing it for 5 days, SOD is gone as far as i know.... ALSO in options, under setting / system / power / batt... i turned off the option to charge it when plugged into PC....Not sure if it helps or not. But Something i did is doing the trick. Seems between the backlight, and something to do with my 2.0 usb cord thats messing it up.
Seems to be cured... Still not sure exactly what fixed my phone. But between all that, IMO i believe installing lumos and glight triggered something also i think not letting it charge thru the PC, and only using a wall plug for charging has something to do with it....Either way . now its back to normal working just great... ONLY running LUMOS cab, and all the games i want. Energyrom Build 21907 DiNiK Glass Themed june 27th.... HOPE this helps!!! Have a wonderful DAY!
OK so this has been an issue for several months now and its gotten worse.
The ear speaker has been working intermittently and will usually not come on at all.
This seems specific to CM7 because flashing back to CM6 it works fine.
Problem is: Speaker works randomly, at first i thought it was hardware issue but every time a loud sound or voice was played through it would come on.
I would use a saved voicemail and play it a couple times and that would usually kick the speaker to work. But as of recently its doesnt come on at all, only when it wants to.
I have no idea if this would help, but using OSMonitor's log, whenever i tried to play a sound through the ear speaker it would always log audio_disable().
Sometimes reboot works, mostly it doesn't. Ive done clean wipes, fresh installs, and reverting back to previous nightlies and stables. it only has gotten worse with newer updates.
I've looked everywhere for an answer. I dont mind uploading a log, just dont no what to exactly copy for the speaker.
it happpened to me too.
Called tmobile.. pretended to run the test they told me to run.. they then agreen that it was broken internally, and sent me a replacement.
Then I un-rooted my phone, sent it to them, and life is good now
lol
do it..
any other ideas on whats causing this??any solutions besides the return?? ha
I dont know if this is a coincidence or not.. but my speaker died as soon as I flashed the Salsa Slide ROM.
I have had no issues previously.... and I am not trying to pin the blame, it just seems coincidental.
I do have a slide that I bought right at launch, so I dont know if that has anything to do with it...
Either way, I will be calling today to get it replaced because when I flashed back to NB-mod I still could not hear from the internal speaker.
Just bought a nexus from Verizon, on my second device now. First device was exchanged after 1 day, battery ran out in 6 hours, never held signal for more than 2 min. Second device is a refurb, phone worked great and had ZERO issues until updating to 4.0.4. Came with 4.0.2 on it, put off the update for several days to see if it worked ok. Everything ran smooth and fast, great battery life and signal. Immediately after the update, phone now hangs and freeze when unlocking, switching home screens, open app menu etc. Phone also seems to randomly think a headset is plugged in and will not make any sounds except ring, and in a call, neither ear speaker or mic work. Speakerphone works, and if a headset is plugged in, sounds works normally through headset. Found this app:Wired Headset Routing Fix which sometimes fixes mic issue. Sounds and mic work normally after a reboot, but will then randomly stop. Found several pages of threads all over about the mic issue, but with no fixes.
Tried flashing Bugless Beast rom to adress some of these issues, all problems remain. Mic/sound issue seems tom be related to something with the software that controls the headphone jack. Should I continue trying different roms? Try a different kernel? Possible to complete reset phone back to stock 4.0.2? It worked FANTASTICALLY before the update, how could I get it back to the way it was when I unboxed it? My 14 day warranty runs out on the 22nd, so I could exchange the phone again, but my Verizon store has been hounding me to switch to another device.
Any help would be greatly appreciated!
After your first device they gave you a refurb? Only After a day? That's strange.
Sent from my Galaxy Nexus using xda app-developers app
They initially gave me a brand new one, case was cracked completely through when they opened the box to activate it. The only other phone they had on hand was a refurb.
Figured I'd cross post this as it seems to be an issue for a few people. ( http://forum.xda-developers.com/showthread.php?t=1951699 )
I've noticed this issue since first getting my S3 in July. So I do know it happened with 4.0.4 and now with 4.1.1. I've never used the "Stay Awake" option in the dev options and it still remains off. I've had the issue with both "Smart Stay" on and off. I've tested it with all screen time out times, as well as going through the trouble of factory resetting the device and nothing changed. The only solution I've found is reboot the phone and it will work again for a day or so until I notice it again. Very annoying and would love to find a solution to this!
I just started having the same issue. I was using Black Jelly's JB ROM for like 2 weeks without the problem then I flashed the LK3 modem and it started happening. I did a full wipe and flashed the ROM from this thread - http://forum.xda-developers.com/showthread.php?t=2034844 last night and I'm still having the problem. My touch key lights stay on all the time too along with the screen not timing out.
My S3 has been stock from day one. I also got mine a few days after it was released, starting to wonder if its a hardware issue?
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
I've noticed it on a replacement S3 I got when it wasn't an issue with the prior one. The new one (as with the old) is stock, updated to JB when I got it. GFs phone does the same.
geiswiz said:
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
Click to expand...
Click to collapse
This is interesting. I've been noticing this issue ever since I updated to 4.1.1 some weeks back, but had not considered any connection with missed calls. Among the dozens of reports I see online (with not a single one resolved), I found another thread that mentions it happening after missing a call (or receiving an SMS).
I completely wiped my phone and flashed a stock 4.1.1 rom two days ago and noticed this happening again while sitting at my desk today. I did miss a call earlier, so I think there is something to that suspicion; I rebooted the phone and sure enough the screen and touch keys timeout as they should. I just received a text and that didn't trigger the issue, but I'll have to wait til I get another call to know for sure, or until I get home and have the time to test it.
Ok, yep, it definitely is somehow triggered by missing a call, but it seems to only happen some time later after the last reboot. I had rebooted my phone yesterday, missed a call not too long after, and the keys and screen would shut off normally. But I just missed a call right now and sure enough it's acting up again...
So.. i have had a weird problem for quite awhile now but have been putting up with it..
When on a voice call when the screen goes off it will mute the mic, leaving the other person asking if i am there.. i have to shake the phone or hit the power button a bunch. It also doesn't wake up instantly when that happens, almost like its in a deep sleep. I don't have any battery saver apps or anything installed....
I am using CM11 right now with FL24 modem, i have tried other modems.. same issue.. This issue also happened on other roms incluing vanir and others...
I did a search and found one other person with the same exact issue.. but no fix posted, was hoping someone might have an idea on how to figure this out.. thanks..
Experiencing Similar Problem
I've been experiencing a similar issue for a bit over a month, too. I'm not quite sure if it was when the screen went off, but certainly within 15 seconds of making or receiving a call my mic cuts off. It sometimes comes back after -- I don't know if that's because I shake the phone around or otherwise get the screen to come on, although the mic turning back on and the screen turning back on do not happen at the same time.
I'm also on CM11 with FL24 modem on a Samsung Epic 4G Touch, which makes me suspect it's the same problem. Do you have a link to the other forum post?
I suspect it's a relatively recent regression with CM, because I installed CM11 on the phone at the end of October and everything was fine. I first started experiencing the issue a few weeks thereafter. I can't recall if it happened after upgrading CM, or if It was after I installed Google Voice (since removed,) or if there was no particular prompt.