For the past several days I have been having this issue with my phone that is happening at least once or twice a day. There are times when I press the power button to turn the screen on, nothing happens. I thought at first that it wouldn't come out of sleep mode. When I looked at the battery stats, it shows that the phone has been awake. The phone will ring and email and sms notifications work. I can also answer the phone using a bluetooth. The screen won't come back on until I either pull the battery or hold the power button until it does a hard shutdown. Is there a anything I can do that might fix this or am I going to have to take it to sprint? I am hoping I don't have to get it replaced because that means I have to leave it with them the whole day in order for them to see it happen.
ElAguila said:
For the past several days I have been having this issue with my phone that is happening at least once or twice a day. There are times when I press the power button to turn the screen on, nothing happens. I thought at first that it wouldn't come out of sleep mode. When I looked at the battery stats, it shows that the phone has been awake. The phone will ring and email and sms notifications work. I can also answer the phone using a bluetooth. The screen won't come back on until I either pull the battery or hold the power button until it does a hard shutdown. Is there a anything I can do that might fix this or am I going to have to take it to sprint? I am hoping I don't have to get it replaced because that means I have to leave it with them the whole day in order for them to see it happen.
Click to expand...
Click to collapse
Have you tried switching roms, returning back to stock to see if it still does it? If you have tried all those options I would flash back to stock and take it to sprint.
As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?
maybe someone using another kernel/rom can try to reproduce this?
I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)
But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)
Check my posts:
http://forum.xda-developers.com/showthread.php?p=35205418#post35205418
http://forum.xda-developers.com/showthread.php?p=35496824#post35496824
Check my post here:
[URL="http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638"]http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638[/URL]
whre I answered to that phenomen. I was on RBJ + franco r348 that time
I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.
Just wanted to post my results, maybe it's too early to tell as r360 is too young.
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
Maybe because OMAP is abandoned at 3.0.
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Jessie-James said:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
if your device wakes, even after a few presses, its not sod.
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
pressing and holding the power button for 10-20 seconds will force reboot those devices.
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
MondoMor said:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
Click to expand...
Click to collapse
wouldnt it be easier to just pull the battery? thank you for your observations btw.
simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.
simms22 said:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
Click to expand...
Click to collapse
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:
Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.
Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.
We are flooding here.. lets discusse this other place and leave the devs alone here
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
andQlimax said:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
Click to expand...
Click to collapse
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.
I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.
I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
Sent from my Galaxy Nexus using xda app-developers app
Hey guys... so I've noticed my phone acting a bit funky after the latest KitKat update. Just a bit of freezing and lagging, but my 32GB of space was also full. So I did a complete wipe and factory reset and started from scratch. At first everything was great (about a week or two). Then the past day or two I've noticed the below issues...
1. While at work, I keep the phone plugged into my computer via USB with Internet Pass-Through and WiFi turned on. I have it setup this way so I can use the computers internet and trickle charge the phone at the same time. But when I leave my desk I simply unplug my phone and it connects to my works WiFi while I'm walking around the office. I get back to my desk I plug it back in.
Problem: I've noticed lately that I'll pick up my phone and it's HOT to the touch. As well as the battery percentage is actually dropping even though it's plugged in.
2. At night when I go to sleep, using the HTC Charger and Cable that came with the phone I'll plug it in next to my bedside and let it charge.
Problem: I'll wake up in the morning, hit the power button to light up the screen and nothing happens. The Home Key and the Back Arrow (are these what everyone refers to as the "soft keys"?) are lit up but the screen will not turn on. To get the screen on, I have to HOLD the power button down, the screen then lights up with the Restart menu showing (and yes I've restarted it many times in hopes of fixing this issue) and I have to tap outside that box (on my wallpaper or wherever) and the menu will go away and my screen is back up like normal. However as soon as I tap the power button to turn off the screen (not the phone) and tap the power button again, nothing happens except the bottom keys being lit up. It's an ugly circle.
I have noticed a few times when holding the power button to bring up the screen/reset menu, sometimes the screen/reset menu will not turn on, but the home and back arrow keys on the bottom will flash a few times.
Any ideas guys? Loved this phone up until now
So after 200+ views and no comments I'd just like to add that I think I found the fix for this. I spoke with a few different HTC techs and tried multiple things before having to ship it out to them and right before doing so they had me reset what they termed the "Charging Logic"
To reset the Charging Logic
1. Power phone completely off
2. Once powered off, hold the Volume UP, Volume Down, and Power buttons for 2 minutes (my fingertips were sore afterwards LOL)
3. You should get a white background with the green HTC logo turn on/off multiple times. Almost as if it's trying to reboot...
4. After 2 minutes, let go of the buttons and let it reboot.
DONE!
Since I've done this, I've noticed my battery life extremely improved. My phone is no longer getting crazy hot, and the screen now turns on after an over-night charge!
Hope this helps others!
Does it matter what kind of charge you have on the battery when you do this? This is the first I've ever heard of resetting Charging Logic.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Does it matter what kind of charge you have on the battery when you do this? This is the first I've ever heard of resetting Charging Logic.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I'm not sure what you are asking by "what kind of charge". Could you clarify?
Soul TKR said:
I'm not sure what you are asking by "what kind of charge". Could you clarify?
Click to expand...
Click to collapse
Does it matter what percentage your battery is at and does it work for rooted phones? Do I need to be on the stock Rom/recovery for it to work?
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Does it matter what percentage your battery is at and does it work for rooted phones? Do I need to be on the stock Rom/recovery for it to work?
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Sorry I'm not familiar enough with the developer side of things to tell you "it's ok" or "not".
What I can say is, the HTC tech never did ask me if my phone was fully charged or what percentage it was at. Which at the time was like 97% if I recall correctly. I am completely stock...
I would imagine this would work for rooted phones and it wouldn't matter what battery percentage but can't guarantee you...
I just wanted to come back in here and update this again. The above fix did not actually fix the phone as the problem came back again eventually. I am now on my third HTC ONE M7 and looks like I'll have to send this one back as well for the same issue.
I have a theory that it's either a problem with the OS or Light Sensor causing the screen not to turn on.
Can a mod take this thread off "fixed"
The model of my phone is SGH-T999. It is not rooted (I'm going to root it soon though), its running Android 4.3 and I do admit I've dropped it a few times but it has a cover. It shuts off at the most random moment and restarts itself, and sometimes it won't go past the Galaxy SIII logo before restarting itself once more. Theres a possibility the lock button has something to do because when it stays in that startup loop I play around with the lock button till it finally finishes the startup succesfully, but I don't know how the lock button can make it shut down on its own while its turned on without me touching the "power off" option in the window that comes up.
Let's assume for a minute that the Power Button is not the culprit of the reboot. Its certainly possible that the button causes reboots during Boot. Several people have discovered, this button can get stuck.
So given that, let examine your Reboot. You may have to try a factory reset to see if that helps. Typically if there are a lot of background apps running, the phone may get warm and reboot.
Speaking of temperature, you may want to use some Battery Temp monitor like TempMonitor. Stock firmware tends to have low tolerance for temperature and may force Reboot.
Holdin the power button will force a hard reset btw. So if itz sticking that'll do it.
Sent from my SGH-T999 using Tapatalk