Is anyone else having issues with the screen not turning on (at all) sometimes? It seems to happen after the device has been in deep sleep for a while. The only solution is to hold the power button until the device reboots.
It used to happen on 4.4.2 as well, but I was using franco kernel and ART then, so I thought it might have been related to that.
Now I'm using everything stock on 4.4.3 and I'm still experiencing this issue at least 2-3 times a week. I even did a factory reset, but the issue persist.
Could this be a hardware issue with my device?
Anyone got a clue? I should also mention that this never happens while the device is charging.
Related
This problem it's becoming more and more frequent - it was once a month, then once a week - now almost daily
The mt3gs starts to vibrate very fast for 5 seconds, black screen with no interaction possibility, and then reboots.
Ever happened to anyone?
I'm running CM 7.2
Tipika said:
This problem it's becoming more and more frequent - it was once a month, then once a week - now almost daily
The mt3gs starts to vibrate very fast for 5 seconds, black screen with no interaction possibility, and then reboots.
Ever happened to anyone?
I'm running CM 7.2
Click to expand...
Click to collapse
Cant say Ive had the exact same issue, but have had similar. Could be a number of things. Some ROMs have problems with phones rebooting when WiFi is turned on. Not sure about CM7 though. I would recommend making a nandroid backup, and reflash your ROM. If it stops happening, it is likely an app or something corrupted causing it. If it continues, go back to a stock ROM and see how it acts. If it stops now, then it was probably something wrong with the ROM. If it continues, it may be a hardware problem that cant really be fixed. (try a different SD card too.)
Yes, sometimes when i turn on wifi, the phone reboots, but it is a different behaviour - the "wifi reboot" it's a system crash, so the screen suddenly turns in the mt3gs boot logo.
When this happen, it is starts to vibrate a lot (for example, it happened at 4am, it woke me up, even if it was far from my ear), then "dies" for a few seconds (doesn't respond to any button press), and then reboots
very strange...
Hello guys,
I tried to search for a similar issues but I couldn't find anything similar so please bear with me.
My KF sometimes shuts down overnight. In the morning then I have troubles to switching it on again (clicking the power button, holding it for longer periods of time...). It usually helps for the tablet being connected to the charger, but it takes a few tries to turn it on. After I managed to turn it on again, for example yesterday, it had 80% of battery left.
I am using CM nighties and this is happening already for some time.
I am also using juice defender, I am not sure if that is relevant.
Do you have any suggestion, what could be the cause of this? Maybe a suggested alternative rom? Or some logs I can check? I think the powering on troubles bother me more than the shutting off overnight since I always think it won't come back on anymore.
Also, not sure if relevant. If I try to turn it on and it doesn't, sometimes the button flashes orange. After a few tries it turns green and powers on. Not sure if I am now not only confusing times, when it was simply out of juice.
P.S. On a different note, just curious, does anyone know how if there is a rom with working mic already?
Thanks in advance.
jkb
Yes, I sometimes have the same issue with the power button - in fact it happened to me this morning where I went from about 60% charge to 16% with a sudden power drop.
Not sure why this happens. I thought it was a bad battery so I changed it but am still getting the problem every now and then.
Sent from my Nexus 7 using xda premium
the only thing that i can think of is that during the middle of the night a soft-reboot happens and it cant boot back up into the system. this would cause it to sit there and continually try to boot up. this would use a lot of cpu and a lot of power. as for why that drains battery while being plugged in, well i cant help you on that.
Thanks for the input. I've wiped dalvik, cache and the system and installed hashcodes AOSP Jelly Bean (http://forum.xda-developers.com/showthread.php?t=2041694) and at least it survived this night without shutting down so maybe this helped. If I come across the same issue, I will update this thread with new info.
Thanks again,
jkb
Check this out:
amazon.com/gp/help/customer/forums/kindleqna/ref=cm_cd_pg_pg139?ie=UTF8&cdForum=Fx1GLDPZMNR1X53&cdPage=139&cdThread=Tx2JSJNEOWHGOIT
Sounds like a hardware issue, and Amazon has been replacing those of customers who buy new from them.
Mine has this issue too. I KNOW it has battery power, and is still on, but the screen won't turn on. Only solution is to plug in power, then hold down the power button until it shuts down hard. Then turn back on.
I'm returning mine because of it.
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
jokob.sk said:
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
Click to expand...
Click to collapse
Try going to the WiFi settings and selecting 'never' for keeping WiFi on during sleep. This seemed to work for me.... So far it hasn't happened again.
Sent from my Nexus 7 using xda premium
I think this is the bug I am experiencing:
Shutdown bug stalls out the shutdown. Looks like the device is off, but it's still powered draining battery. Currently requires long power button press to fully shutdown after the screen is black (about 15-20 seconds).
from the 3.4 kernel thread (http://forum.xda-developers.com/showthread.php?t=2264563). I am not sure if cm 10.1 nighties contain this kernel, but the description is pretty much spot on.I couldn't test the fix (holding the button for 15-20 seconds), since I already changed roms, but if someone experiences the issue again, he can post if this works and which rom and kernel they are using.
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
pwrdbykimchi said:
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
Click to expand...
Click to collapse
Yes, it happened again to me with the same ROM, but it happens less often. I will try the updated kernel once it is finished.
On May 27, 2013, Hashcode listed the known issues of the current kernel on his website:
Sound / MIC debugging
Deep sleep issues with “omapdss_dpi” device
SmartReflex shutdown loop fix.
Charging driver / OTG improvrments
Click to expand...
Click to collapse
Looks like they've been identified and are being resolved. :good:
I have installed CM 10.1. Occasionally the screen will not turn on when I press the power button. I have to hold down the button for 10-20 seconds to reset the device to get it to power on. Happens at least 3-4 times a day. Anyone else have this issue or ideas on how to fix it? Thanks.
Stuke00 said:
I have installed CM 10.1. Occasionally the screen will not turn on when I press the power button. I have to hold down the button for 10-20 seconds to reset the device to get it to power on. Happens at least 3-4 times a day. Anyone else have this issue or ideas on how to fix it? Thanks.
Click to expand...
Click to collapse
No one else has seen this issue?
Many ROMs have their little quirks here and there, this could be one. I use hashcode's ROMs so this is just speculation though.
I had this issue with twa_priv's rom. If I keep at the button, pushing it multiple times at different intervals, it would eventually come on. Interestingly, if I went into the developer options and put the CPU at the full 1200MHz, it didn't happen.
Not having this issue with CM (though I'm running 10.2) so not sure there.
This was a common occurrence in cm10.1 with TWA_priv's build I believe. This is called a Sleep of Death or SoD. I thought that was cleared up, but maybe not. If there is a newer version of the ROM that you are on, I recommend trying that. There is no way to recover from an SoD except to force power off like you did, and start back up.
Sent from my Nexus 7 using Tapatalk
Hi,
I have:
Sony Xperia Z1 Compact
Rooted
CyanogenMod version 11-20141112-SNAPSHOT-M12-amami
Android version 4.4.4
Kernel version 3.4.0cyanogenmod-g1b20e398 [email protected] #1
Build number cm_amami-userdebug 4.4.4 KTU84Q a265284510 test-keys
My phone's screen has the annoying problem of sometimes not waking when I press the power button (while the phone is turned on). The phone is still on, but doesn't respond to input. I can call it, but nothing happens. I can connect the charger, but it doesn't respond.
I did not experience the issue before rooting. After rooting and installing CyanogenMod, the problem occurred perhaps 1-2 a week.
Recently I encrypted my phone. After that the problem has become much more frequent. The screen is now unwakable roughly 2-3 times a day, some times even more!
The only solution I have found, it to either turn the phone off via the red off button next to the SIM card, or by rebooting it by holding the power button in for so long.
The issue is extremely annoying, especially after it started occurring 2-3 times a day.
I have tried searching for similar issues, but haven't found any solutions.
I have tried changing the brightness levels so the max level is 99% instead of 100%, as someone had suggested, but that hasn't made any difference. Unscrewing the phone and cleaning the proximity sensor, as someone else had suggested, is something I haven't tried yet, as I don't feel competent enough to unscrew the phone.
The phone used to have the protection plastic provided from the fabric, but I tore that off not too long ago. No change in behaviour.
I have not managed to find one special event that triggers this behaviour or reproduce the issue on demand.
Hopefully someone will have some tips as to what I can do to solve this issue. Thanks in advance.
Any modifications on the kernel? Like special governors or under/overclocking?
As you are using a custom ROM the clear advise here is: try out with stock ROM and see if the problem is still there.
If not, it is a problem with the ROM.
I'm having the exact same problem. I flashed cm11 snapshot two days ago, and today my screen wouldn't wake no matter what.not even a restart would solve the issue, cause the moment the phone goes to sleep after a boot, that was the last time the screen was on. I'm following this thread in case somebody comes up with a solution.
hi there, my phone is acting the same way as yours described. Mine is rooted on stock lolipop and it never happened before although i had a replacement unit and the one before that acting the same way. Pressed the power button and nothing happend regardless screen on or off. Had to do hard reset and it worked for like 1 or 2 days. I went to sony talk forum and ppl seems to say it a bug since the phone released. If anyone got anything would be great help. Thanks
I'm using my dad's Note 10.1 (2014) and I've been experiencing some problems. The screen would randomly just turn off (but it doesn't shut down) when I looked away. I thought it was the smart eye detection feature thingy but when I checked, it was already turned off. Another problem is that the home button and/or the capacitive just randomly stops working. Had to reboot the device in order to get it working again. At first I thought it was some hardware problem but I'm pretty sure it isn't. So yeah. Does anyone face the same problems? I've heard this device have some software issues that causes this but after some searching I got no answers.
Hi
I have your problem too. i have thiss issue on Stock rom. i use for one day Resurrection Remix ROM. i havn't see this issue.