Recently i have noticed that if i charge my phone all night it won't wake up in the morning and i have to pull out the battery and have it reset. Any idea what could be causing these hard lock ups? I have also had a few hard lockups randomly but the morning thing seems to be EVERY morning. I was using the omap program to overclock it but i disabled and deleted it. Any ideas?
Check to make sure that your phone still sleep when on external power (e.g. charging) from your Power property of your phone Setting page. Just to see if having it on for the entire night causes the problem.
If not, use any software (capable ones) to look through your notification queues, and see if there are any items that starts every morning to locate the culprit that may have been causing the problem.
Related
Got a weird problem with my AT&T stock non-rooted S4. About 4 or 5 times since I got it on release day when I charge my phone and I get the notification that it's fully charged the screen won't turn back off. I use a Belkin Conserve socket that is set to shut off after 3 hours and I've woken up after charging to find the phone dead. I've managed to catch this happen once and when the fully charged notification comes on the screen won't go to sleep, it just stays on and flickers a little bit. For all but one of these instances I had blocking mode on so I'm not disturbed by email or text notifications in the middle of the night. It did happen one time when I didn't have blocking mode on. I use a pin lock for my lockscreen and usually have BeyondPod playing overnight (only one hour long podcast while it's still charging) if that makes a difference. Is the function that enables the screen to stay on when you're looking at it malfunctioning? Any help? I've attached two screenshots of battery life when this happens.
Tryptonite said:
Got a weird problem with my AT&T stock non-rooted S4. About 4 or 5 times since I got it on release day when I charge my phone and I get the notification that it's fully charged the screen won't turn back off. I use a Belkin Conserve socket that is set to shut off after 3 hours and I've woken up after charging to find the phone dead. I've managed to catch this happen once and when the fully charged notification comes on the screen won't go to sleep, it just stays on and flickers a little bit. For all but one of these instances I had blocking mode on so I'm not disturbed by email or text notifications in the middle of the night. It did happen one time when I didn't have blocking mode on. I use a pin lock for my lockscreen and usually have BeyondPod playing overnight (only one hour long podcast while it's still charging) if that makes a difference. Is the function that enables the screen to stay on when you're looking at it malfunctioning? Any help? I've attached two screenshots of battery life when this happens.
Click to expand...
Click to collapse
So in settings under the Developer Options, there is a setting "Stay awake" if checked screen will never sleep while charging. Now I see that your Belkin shuts off the power but your phones still detects the usb plugged into a power source.
I think things happen in this order: you hookup your phone to charge and shut off your screen, phone charges to 100% and screen lights up saying fully charged, it stays on because of that setting, Belkin kills the power, it is still hooked up to USB so ... you get the rest.
I would find that setting and disable it.
if your next question is "I don't see developers option" it is hidden by default in android 4.2.2 so to make it available, go to Settings > About phone and tap tap tap Build number seven times. Return to the previous screen to find Developer options. Or Indiana Jones might pop up and give you the cup to get eternal life !!!
Thanks for the reply Commodore64 but I already checked that setting when it happened the first time and it's not checked.
No one else has had this problem?
Tryptonite said:
No one else has had this problem?
Click to expand...
Click to collapse
I have this problem as well as my wife's S4. around 3am, I notice our room is bright with our two phones' screens on. It will stay on until the morning.
In the developer's section of the settings, the stay on when plugged in is NOT checked.
Also, on our phones, we notice the phones overheating because the screen is on for hours at a time at night.
I've just spent an hour looking through the internet, and while many report this, they are simply being dismissed by others as in having "checked" the setting in developer section.
Also, when the batttery does get fully charged, the "Battery if full, unplug the power" notification also rings the default notification ringtone. I've installed phoneweaver to set my phone to no sound overnight, but it only stops the sound, the screen still stays on and phone gets really hot.
This is turning out to be a huge problem for us.
pyrophilus said:
I have this problem as well as my wife's S4. around 3am, I notice our room is bright with our two phones' screens on. It will stay on until the morning.
In the developer's section of the settings, the stay on when plugged in is NOT checked.
Also, on our phones, we notice the phones overheating because the screen is on for hours at a time at night.
I've just spent an hour looking through the internet, and while many report this, they are simply being dismissed by others as in having "checked" the setting in developer section.
Also, when the batttery does get fully charged, the "Battery if full, unplug the power" notification also rings the default notification ringtone. I've installed phoneweaver to set my phone to no sound overnight, but it only stops the sound, the screen still stays on and phone gets really hot.
This is turning out to be a huge problem for us.
Click to expand...
Click to collapse
Do you use a PIN (number) lock? I did but switched to the pattern unlock and it hasn't happened since. Also, I've been trying to charge only during the day or evening, not overnight. Maybe, since I charge during the day and I use it periodically while it charges it doesn't go into a "deep sleep" like it would if it charges while sleeping and the full charge notification would keep it awake. I don't know exactly why but it hasn't happened since. Hope this helps.
Power Button Not Working SGS4 Not Sleeping SOLVED
For whatever it's worth, see http://forum.xda-developers.com/showthread.php?p=48871706#post48871706 - maybe that will be helpful.
I am charging it using the provided USB cable and adapter, but the phone is almost too hot to touch when I wake up some mornings. It quits charging because of it, but it still remains very hot. It happens irregularly and I cannot pinpoint the problem.
I am running completely stock AT&T.
Can someone help me figure this out?
Edit: some more info: The cell radio has turned off with this issue at least twice. It turned back on after a restart. Airplane mode was not enabled, so I am not sure why this would happen. When charging at night, I run the Sleep As Android sleep tracker, and it's on my bed, but I run it every night and I am not sure why it would only give me problems occasionally (every ~10 days or so). It's possible I bump it in my sleep, but would that cause this issue? When I wake up it is fully plugged in and too hot to continue charging.
toastthemost said:
I am charging it using the provided USB cable and adapter, but the phone is almost too hot to touch when I wake up some mornings. It quits charging because of it, but it still remains very hot. It happens irregularly and I cannot pinpoint the problem.
I am running completely stock AT&T.
Can someone help me figure this out?
Edit: some more info: The cell radio has turned off with this issue at least twice. It turned back on after a restart. Airplane mode was not enabled, so I am not sure why this would happen. When charging at night, I run the Sleep As Android sleep tracker, and it's on my bed, but I run it every night and I am not sure why it would only give me problems occasionally (every ~10 days or so). It's possible I bump it in my sleep, but would that cause this issue? When I wake up it is fully plugged in and too hot to continue charging.
Click to expand...
Click to collapse
Is there any wakelocks keeping your device running? Look into it. Something could be keeping your device running in the background. Or perhaps something is turning on your device.
Worst case scenario is that you have a defective device in which I suggest you go see an att repair center or call att so they can exchange it due to defective issues. The replacement will be free.
Sent from my GT-I9505G using Tapatalk 2
Febby said:
Is there any wakelocks keeping your device running? Look into it. Something could be keeping your device running in the background. Or perhaps something is turning on your device.
Worst case scenario is that you have a defective device in which I suggest you go see an att repair center or call att so they can exchange it due to defective issues. The replacement will be free.
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Well put, reminds me of a scenario I had on my SG3. When I had first gotten my SG3 awhile back it would give me temperature warnings every so often (2-3) days. I found the problem to be that a couple of my applications were running background processes that were very cpu extensive and keeping my device awake. This caused the CPU to ran at nearly max frequency throughout the entire night, thus over heating my phone. I wiped every application I had and reinstalled and set background permissions to not allowed for a majority of them; this resolved the problem.
I haven't experienced this at all on my SG4, but I still disallow a lot of my apps to use background processes unless necessary. I did read online that some of the SG4 devices did have a defective heat sync though, however I'd try removing all your applications until you're down to bare minimal stock and reinstalling and keeping an eye on what could possibly be running your CPU up when your phones locked.
- Br4nd3n
I'm guessing that it has a spike in temperature, it turns off the charging, but it still is plugged in so the temperature keeps going up. Hottest I saw on it was around 65 deg. Celsius.
I attached a few graphs of this happening on different occasions (one portrait is the same day as the landscape). The fast drop-off is where I unplug it and let it cool and reinsert the charging cable, and it surprisingly does not get hot again. No restart is necessary, so I doubt there is much to do with the phone's CPU but I could be wrong.
I have the SM-G901F version, 805 processor.
I finished charging my device last night at 100% and took it off before sleep, all was well. I woke up this morning, and it was dead at 0%.
Something similar has happened twice in the past and that is the screen refusing to turn on, and when it does it jitters a lot and says a certain app has crashed. The first time THIS happened, it said nova launcher crashed. The second time, same day, I locked the device while still in whatsapp and the same thing above happened but this time it said WhatsApp crashed, this leads me to believe it's not Nova launcher causing it but you never know. During the time of these crashes when the screen was off, I had rapid battery drain.
This is why I think overnight something like this happened, and since I didn't try and wake it up like the other two times the battery continued to drain. However, I have attached an image of the battery info suggesting that the phone app caused this.
*I close all apps before sleeping, all the time.
*Data off, blocking mode on.
*Never leave it on charge over night
*UK device, only had it for about 1 month.
...
android doesn't need apps to be closed manually.
sometimes its better to backup all your data and start fresh mate. that's will isolate the problem a bit more.
For those of you using Air Wakeup, I've noticed a potential problem.
My phone has frequently been kept "awake" for no apparent reason for longer periods of time, according to the power history. I began to notice this because of sudden increased battery drain.
It always starts after the phone has been unplugged for at least a day since last charge. The solution has up until now just been to reboot the phone, and it has gone back to deep sleep as normal. However, since this happens so often, I tried to dig a bit deeper and see what was actually keeping it awake.
It turns out that it was the Air Wakeup that kept the phone awake. The first day after charge is always fine, but the drain (in all cases I can remember) has started after a day - and it keeps it from deep sleeping until force stopping air wakeup, or rebooting as mentioned eariler.
For now, I've just disabled air wakeup, but if you have problems that your phone stays active when you are not using it, and you have air wakeup enabled, it might be worth looking into.
Yeh i have the same problem... i thought it was the s-view cover that was at fault.
Where is the air wakeup option?
krifos said:
For those of you using Air Wakeup, I've noticed a potential problem.
My phone has frequently been kept "awake" for no apparent reason for longer periods of time, according to the power history. I began to notice this because of sudden increased battery drain.
It always starts after the phone has been unplugged for at least a day since last charge. The solution has up until now just been to reboot the phone, and it has gone back to deep sleep as normal. However, since this happens so often, I tried to dig a bit deeper and see what was actually keeping it awake.
It turns out that it was the Air Wakeup that kept the phone awake. The first day after charge is always fine, but the drain (in all cases I can remember) has started after a day - and it keeps it from deep sleeping until force stopping air wakeup, or rebooting as mentioned eariler.
For now, I've just disabled air wakeup, but if you have problems that your phone stays active when you are not using it, and you have air wakeup enabled, it might be worth looking into.
Click to expand...
Click to collapse
I encountered this problem too yesterday, is this a firmware bug? Cause before updating to the latest firmware I didn't have this problem.
I have this and i have not received the update yet.
So i am not sure if this is a nougat issue or something else but recently i have noticed that when i plug my phone in to charge for the night i wake up and see that sometime probably during the night the charing stopped because the phone is at like 60ish % or so and not charging. When i unplug and plug it back in then it charges again normally. This dosen't always happen but from time to time.
Another issue i have been experincing also lately from time to time that my weekday alarm suddenly dosen't sound in the morning. When i go into the clock (google btw) then the alarm is set to on but the little alarm icon is not showing in the statusbar. Turning it off and on again it goes back to normal. But this is highly annoying if my alarm suddenly decides not to go off in the morning despite in the app it showing to be set to on.
Not sure if these issue are related to the nougat update but i have been experiencing these issues only recently (last couple of weeks).
Anyone else have similar issues?
Freakadude said:
So i am not sure if this is a nougat issue or something else but recently i have noticed that when i plug my phone in to charge for the night i wake up and see that sometime probably during the night the charing stopped because the phone is at like 60ish % or so and not charging. When i unplug and plug it back in then it charges again normally. This dosen't always happen but from time to time.
Another issue i have been experincing also lately from time to time that my weekday alarm suddenly dosen't sound in the morning. When i go into the clock (google btw) then the alarm is set to on but the little alarm icon is not showing in the statusbar. Turning it off and on again it goes back to normal. But this is highly annoying if my alarm suddenly decides not to go off in the morning despite in the app it showing to be set to on.
Not sure if these issue are related to the nougat update but i have been experiencing these issues only recently (last couple of weeks).
Anyone else have similar issues?
Click to expand...
Click to collapse
Try different charger and especially cable. For the 2nd question - google alarm clock? Most likely the OS put it to sleep. Go in apps/power management and put the google clock into the exceptions, i.e. never to be put to sleep.
I got today some sort of call stuck, so no notification sound no alarm. I was late to work... Rebooted and sound appeared again. Nougat BTU.