Related
I have recently encountered a problem with my hox, where, if I press the power button, the screen doesn't awake. It's a little weird, because the back home app switcher buttons do light up if it is dark enough around me and, after pushing them a few times, the volume buttons respond as well.
I haven't fully tested it, but it seems like when I wait like a minute or so, maybe more, the screen does finally wake up. I have also held the power button several times to restart it while it was like this and then the screen doesn't light up until the sim unlock screen pops up.
I have yet to factory reset the phone etc., but I was wondering if anyone else had run into this problem. I have looked around the internet, but was unsure what to search for.
CAPSGUY said:
I have recently encountered a problem with my hox, where, if I press the power button, the screen doesn't awake. It's a little weird, because the back home app switcher buttons do light up if it is dark enough around me and, after pushing them a few times, the volume buttons respond as well.
I haven't fully tested it, but it seems like when I wait like a minute or so, maybe more, the screen does finally wake up. I have also held the power button several times to restart it while it was like this and then the screen doesn't light up until the sim unlock screen pops up.
I have yet to factory reset the phone etc., but I was wondering if anyone else had run into this problem. I have looked around the internet, but was unsure what to search for.
Click to expand...
Click to collapse
Are u using sweep to wake?, that sometimes causes this problem
Sent from my HTC One X using Tapatalk 2
Nope, I do not have sweep to wake.
Well, after a while of being okay, the issue is showing up again. If I press the power button it does wake the phone somehow (back, home, tasks lights light up, volume can be altered), but the screen wont come on. And when it's one of those rare moments that it does turn on the UI flies everywhere, making it literary uncontrolable, until at some point the screen just turns itself off.
I am not running any custom things, everything is stock. I tried a factory reset without erasing the SD storage. I also have just sent an email to HTC, but it being weekend and all I still have to wait a day or two.
Any other things I could try?
Never had this problem with the HOX.
Only with Xperia Arc and X10 when a heavy task ran in the background
Sent from my HTC One X using xda app-developers app
i have same issue taking ti back to vodafone today
CAPSGUY said:
I have recently encountered a problem with my hox, where, if I press the power button, the screen doesn't awake. It's a little weird, because the back home app switcher buttons do light up if it is dark enough around me and, after pushing them a few times, the volume buttons respond as well.
I haven't fully tested it, but it seems like when I wait like a minute or so, maybe more, the screen does finally wake up. I have also held the power button several times to restart it while it was like this and then the screen doesn't light up until the sim unlock screen pops up.
I have yet to factory reset the phone etc., but I was wondering if anyone else had run into this problem. I have looked around the internet, but was unsure what to search for.
Click to expand...
Click to collapse
I've not had black screen but sometimes the slide to unlock does not respond until I press power then unlock again
Sent from my HTC One X using xda premium
Same Issue
CAPSGUY said:
Well, after a while of being okay, the issue is showing up again. If I press the power button it does wake the phone somehow (back, home, tasks lights light up, volume can be altered), but the screen wont come on. And when it's one of those rare moments that it does turn on the UI flies everywhere, making it literary uncontrolable, until at some point the screen just turns itself off.
I am not running any custom things, everything is stock. I tried a factory reset without erasing the SD storage. I also have just sent an email to HTC, but it being weekend and all I still have to wait a day or two.
Any other things I could try?
Click to expand...
Click to collapse
Hi, I was wondering what did you do regarding the lockscreen problem. I'm having exactly the same problem here. I've already done a factory reset but it did not solve the issue. From time to time I'm not able to unlock the phone.
Please HELP!!!
It sometimes happens to me, recently after clearing the clock and weather apps and widgets. I don't know what it is.
I've been having this issue and its been happening to me on stock, CM10 and ktoons rom as well.
Just randomly when i want to wake my phone up using the home button, it does nothing, or the buttons for menu and back lit up but the screen is black.
Sometimes if i hold home long enough it will show the lock screen or if i use the power button its fine.
Ive just switched over to the S3 from an iPhone so im really used to pressing home to unlock the phone.
Anyone else having this issue? Ive searched around alot of people have lag issues but i haven't seen one like mine yet.
Danielk91 said:
I've been having this issue and its been happening to me on stock, CM10 and ktoons rom as well.
Just randomly when i want to wake my phone up using the home button, it does nothing, or the buttons for menu and back lit up but the screen is black.
Sometimes if i hold home long enough it will show the lock screen or if i use the power button its fine.
Ive just switched over to the S3 from an iPhone so im really used to pressing home to unlock the phone.
Anyone else having this issue? Ive searched around alot of people have lag issues but i haven't seen one like mine yet.
Click to expand...
Click to collapse
On CM10 / AOKP, yes. Known issue.
On stock, never.
radeon_x said:
On CM10 / AOKP, yes. Known issue.
On stock, never.
Click to expand...
Click to collapse
Ok i thought so, sorry for creating a topic on it. on stock it happened it to me a few times as well though.
i just wanted to make sure it wasn't faulty.
I used to be able to just hit the home button twice and it would work but lately it's just a black screen no matter how many times. Using tasks ROM. I'm getting used to using the power button
Sent from my SGH-I747 using Tapatalk 2
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
In Android 4.1--pretty much every iteration of it, including CM10--when I hit my power button to sleep the phone, the phone would go to sleep immediately. In 4.2 and beyond, there is a half-second delay when I push the power button and when the screen actually turns off.
This issue is present in 4.2 stock, 4.2.1 stock, 4.2.2 stock, 4.3 stock and every single version and nightly of both CM10.1 and CM10.2 that I've flashed. Disabling the CRT animation or changing the animation scale does not fix the issue; the device still hangs for a half second or so before turning off the screen.
This persists no matter what I do. The usual suggestions do not work; the problem persists. It's going to drive me nuts eventually, because I keep thinking it didn't take, mashing the power button a second time, only to turn my screen back on again.
synaesthetic said:
In Android 4.1--pretty much every iteration of it, including CM10--when I hit my power button to sleep the phone, the phone would go to sleep immediately. In 4.2 and beyond, there is a half-second delay when I push the power button and when the screen actually turns off.
This issue is present in 4.2 stock, 4.2.1 stock, 4.2.2 stock, 4.3 stock and every single version and nightly of both CM10.1 and CM10.2 that I've flashed. Disabling the CRT animation or changing the animation scale does not fix the issue; the device still hangs for a half second or so before turning off the screen.
This persists no matter what I do. The usual suggestions do not work; the problem persists. It's going to drive me nuts eventually, because I keep thinking it didn't take, mashing the power button a second time, only to turn my screen back on again.
Click to expand...
Click to collapse
Hello.
Add the "go to sleep" control on the notification drawer's power widget (Settings->Interface->Notification Drawer) and try it. If works, problem solved. If not, we can discar hardware (power button) issue.
I've never encountered the issue in everyday use. It has happened to me a handful of times, but only when the phone is heavily bogged down. Never under normal use. I assume you would know if your phone was being bogged down though?
Sent from my Galaxy Nexus using xda app-developers app
In general I've been happy with 5.0 but every now and then the lockscreen doesn't respond to touches. the power button turns the screen on but when i swipe to unlock my tablet, nothing happens. Now matter how I swipe, nothing happens. The screen eventually just times out and goes off. This also means that I can't turn it off to reboot it. Sometimes plugging it in to the charger fixes this, but I usually just have to wait a while for it to start working again.
Anyone else have this happening to them??
nvillamob said:
In general I've been happy with 5.0 but every now and then the lockscreen doesn't respond to touches. the power button turns the screen on but when i swipe to unlock my tablet, nothing happens. Now matter how I swipe, nothing happens. The screen eventually just times out and goes off. This also means that I can't turn it off to reboot it. Sometimes plugging it in to the charger fixes this, but I usually just have to wait a while for it to start working again.
Anyone else have this happening to them??
Click to expand...
Click to collapse
If you press the power button and wait for the menu to pop up, does it respond when you press the screen? Having this issue as well and only a reset seems to fix it. I'm running 5.0.2
noahvt said:
If you press the power button and wait for the menu to pop up, does it respond when you press the screen? Having this issue as well and only a reset seems to fix it. I'm running 5.0.2
Click to expand...
Click to collapse
No, I can get the power menu to pop up just fine, but nothing happens when i tap it. I finally figured out that it would turn off after holding down the power button for a long time. But when I tried to boot it back up, it just got stuck on the "android" screen. I let it sit overnight and this morning was able to get it to boot up normally.
my 2012 Nexus 7 died after 13 months (1 month after the warranty ran out). This is my 2013 Nexus....guess how old it is (hint: 1 month out of warranty).
nvillamob said:
No, I can get the power menu to pop up just fine, but nothing happens when i tap it. I finally figured out that it would turn off after holding down the power button for a long time. But when I tried to boot it back up, it just got stuck on the "android" screen. I let it sit overnight and this morning was able to get it to boot up normally.
my 2012 Nexus 7 died after 13 months (1 month after the warranty ran out). This is my 2013 Nexus....guess how old it is (hint: 1 month out of warranty).
Click to expand...
Click to collapse
My nexus 7 is just 1 month old lol. But I assume that this is a software problem on lollipop since I do not experience this on kitkat
Yeah i think it's got to be software. Never had this on 4.4. This happens on my N7 and I get random reboots on my N4 ever since L came out.
N7 is completely stock an unrooted by the way.
+1 same issue, I encounter it once in 5 days
Sent from my Nexus 5