It's been three days since I have a small bug sometimes.
Sometimes when I press the button to turn on my device the phone wake up (the buttons light up) but the screen sty off... The only thing I can do is a softreset and then everything is all right...
Does someone have the same problem and is ther a fix?
Thanks for the answer
Happens to me sometimes too
I guess the ROM is not 100% stable yet... Let's pary 6.5 will be out soon ! (With TF3D 2.5 or even better with the new sense interface !)
same problem here, if he stays off you can hear de volume butons if you press them so it is only the screen or something.
also when i slide out the keyboard, the screen is rotating realy slow and bit by bit. hope for a soon spl and custom (nrg) rom
paulaafjes said:
same problem here, if he stays off you can hear de volume butons if you press them so it is only the screen or something.
also when i slide out the keyboard, the screen is rotating realy slow and bit by bit. hope for a soon spl and custom (nrg) rom
Click to expand...
Click to collapse
Have this too, sometimes. I thought it was due to WAD which sometimes uses way too much CPU.
But the screen not comming off is really annoying! And I don't know why this happens.
I removed SPB Pocket Plus and did not experience this problem again - I think it's just coincidence, but still... You could try!
UPDATE
It seems to happens very very more often if I use the camera apps.
Sebacestmoi_666 said:
It's been three days since I have a small bug sometimes.
Sometimes when I press the button to turn on my device the phone wake up (the buttons light up) but the screen sty off... The only thing I can do is a softreset and then everything is all right...
Does someone have the same problem and is ther a fix?
Thanks for the answer
Click to expand...
Click to collapse
1 More here..
got the same problem .... but then I just keep trying to turn the screen on with the on/off button .... that always works after a few tries
Text msg wont wake up phone
Is this normal? when I receive a text msg, the phone doesnt wake up. My TyTN II woke up when a text msg came through
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
I have cm11 and if i power on the tablet and let it a couple of minutes it is freezed at the lock screen. I cant unlock it by swiping the screen and i cant press on the clock widget. If i press the power button it turns on or off the lock screen but i can still do nothing. Only way to restore it is to keep pressed the power button to hard reset the tab. It boots normally then if i unlock the screen and dont let it auto lock. Is anybody else experiencing this issue? It gets really annoying. Could it be the nova launcher because i cant remember this happening before installing it.
katsika said:
Could it be the nova launcher because i cant remember this happening before installing it.
Click to expand...
Click to collapse
Your guess seems to be on the money. Stay away from all those launchers.
mackeev said:
Your guess seems to be on the money. Stay away from all those launchers.
Click to expand...
Click to collapse
yep, i disabled the option from nova settings to autolock the desktop and that seemed to fix it. This option prevents any changes to desktop and it looks like that it conflicted with cm11
Hi all,
I have some trouble with my Z1 compact. Very often when screen is off and pressing powerbutton (to get to unlock screen) the screen goes on but in the same sec goes it off. The same thing can also happen if screen is on and I want to turn it off -> it goes off and again on and I'm back at unlock screen. This issue appears kind of randomly and I have no idea if this is a software bug or a hardware problem.
Using CM11 M12 stable. Any ideas? Thank you
Milltach said:
Hi all,
I have some trouble with my Z1 compact. Very often when screen is off and pressing powerbutton (to get to unlock screen) the screen goes on but in the same sec goes it off. The same thing can also happen if screen is on and I want to turn it off -> it goes off and again on and I'm back at unlock screen. This issue appears kind of randomly and I have no idea if this is a software bug or a hardware problem.
Using CM11 M12 stable. Any ideas? Thank you
Click to expand...
Click to collapse
I have the same phone and OS, and have seen the same issue, but until I saw your post I have dismissed it as something I was doing when pressing the power button. I believe it must be a software bug, since I did not have the problem when running the stock OS. Perhaps it is worth a bug report.
Milltach said:
Hi all,
I have some trouble with my Z1 compact. Very often when screen is off and pressing powerbutton (to get to unlock screen) the screen goes on but in the same sec goes it off. The same thing can also happen if screen is on and I want to turn it off -> it goes off and again on and I'm back at unlock screen. This issue appears kind of randomly and I have no idea if this is a software bug or a hardware problem.
Using CM11 M12 stable. Any ideas? Thank you
Click to expand...
Click to collapse
I use Xposed and GEM Xperia Xposed module, that has 'wake up with volume keys'
Not really a solution, more of a workaround
Occasionally I get a 10-20 second delay before the phone comes on when using either the fingerprint or pressing the power button. Has anyone else had this issue? It may be something I installed, not sure.
steelersmb said:
Occasionally I get a 10-20 second delay before the phone comes on when using either the fingerprint or pressing the power button. Has anyone else had this issue? It may be something I installed, not sure.
Click to expand...
Click to collapse
Are you hiding the top and/or bottom bars using immersive mode? It seems to happen then. This thread fixed it for me on 8.0 https://forum.xda-developers.com/pixel-xl/help/android-oreo-immersioln-mode-problems-t3666479 but I'm having the issue on 8.1