I do not know whether it is coincidence, but I updated couple of days ago and all of sudden, starting this morning, the Android system is draining battery at alarming rate. It does appear that this happens only when I am on cellular network and not on wifi.
I have been off the charger about 2 hours and my battery is down to about 50% already.
The phone is running very hot. (I took it out of the case) It does not appear that turning off cellular data affects this at all.
Rebooted the phone couple of times to no avail, at this point, I am considering factory reset of the phone, but would like to get some opinions on what may be the cause.
I saw the thread on the "android system battery drain", but this does not appear to be related to what majority of people are reporting as this slows down the phone significantly enough that the phone is almost unusable at this point.
Cleared cache but don't think is helping. That said, when I was trying to get to the recovery, the system said "Installing update" and then "No command", before getting me to the cache, I am wondering whether the "update" did not clean up itself...
Thanks.
EDIT: Looks like the system cache clearing did help after all.... System appear to be working normally now. Will have to see..
Ok, well, back to the drawing board. The phone behaved ok all day long. Came home, I did 2 things, turn on wifi, and then turned on bluetooth to test out a headphone and then shut off the bluetooth. High battery drain again. Phone got hot and everything is VERY sluggish.
Shut down, cleared the cache again. Will see what happened.
Is there a way to go BACK to previous stock ROM WITHOUT factory reset?
Found out the issue, it was Oculus update which caused the issue. Looks like the bug caused the "Oculus Room" to install it self over and over again. I manually ran the Oculus home app, and it prompted me to update, which I did and it appear to have fixed the issue.
Flash your decice with version from sammobile.com
I have this exact same problem, posted about it yesterday but had no help.
I don't have Oculus on my phone though. But phone behaves for a most of the day, then does as the OP describes, still cant see why, but its only since the update.
Steve
Related
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Are you using apps2sd?
No, I'm not using the apps2sd feature.
The lockscreen text showed "No service" and the notification bar icon showed the same. The "phone" application was the only one that would attempt to restart after being forced closed. After a second fc though, it would apparently give up.
Oh, and just remembered one other oddity.. Once booted and all force close messages removed, attempting to turn on the mobile network resulted in a hard reboot. I really didn't expect anything since there was no service link, but I was just clicking various shortcuts to see what did or didn't work.
Good part is that a Nandroid restore saved the day, so it's more of a curiosity at this point to what the root cause might have been.
I wouldn't have thought that a battery drain could have corrupted the apps or prevented the root filesystem from mounting.
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
mkhopper said:
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Click to expand...
Click to collapse
oddly enough I've had a similar experience. it was 2 days before christmas and i was doing all my last minute shopping. heavy use of the phone caused the battery to die, so i just threw it on my car charger. it booted, but REFUSED to get any data at all (i didn't run into any fc's, however). I rebooted it 3 times and each time the issue persisted.
I was running the AOSP 2.0 build at the time, so i flashed my backup of 2.1 and everything was fine from there...
patches11 said:
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
Click to expand...
Click to collapse
Hmm, good possibility there. Just did a count and I do have 85 apps installed.
(whoof, I had no idea the number had gotten that high. just too many useful apps for this phone.
Today my GS5 started freaking out. I cannot install or update any apps from the Google Play store - they all get stuck at a certain percentage of the way through the download. Each app has a different sticking point (22%, 39%, 75%, etc.), but each app sticks at precisely the same percentage every time. At the same time, my wifi has gone completely bonkers. If I turn on wifi, it will connect to my home network like normal, then drop off without warning, then get back on, then drop back off, etc. every few seconds. If I go into the wifi settings and observe while this happens, I see the message that the phone will connect when the signal is stronger...but if I look at the details, my wifi signal shows as Excellent strength and 100+Mbps speed! The phone is warmer than usual (though not hot) and battery is draining faster than usual, but that's probably to be expected given what else is going on. The wifi network itself isn't having any noticeable issues with any of my other devices or laptops.
Both of these things began happening at the same time, but I'm not sure what triggered it. Everything was working correctly this morning, but sometime this evening everything blew up. I uninstalled all apps that have been installed in the past few days anyway, but the behavior persists. I am not rooted, and I have not yet upgraded to Lollipop. I have rebooted and cleaned the app cache several times, and there is at least 3GB of free space on the internal partition (and far more on the SD card).
I don't even know how to trouble shoot this! I would be most grateful if someone could give me some guidance on how to resolve this. Thanks!
Just a few questions. What OS build is your S5 running? Is it rooted? If it is rooted are you running any Xposed modules or have any apps that might have caused this?
mrjiggywiggy said:
Just a few questions. What OS build is your S5 running? Is it rooted? If it is rooted are you running any Xposed modules or have any apps that might have caused this?
Click to expand...
Click to collapse
I'm running 4.4.4 (see screenshot), not rooted. I have not (to my knowledge) touched any Xposed modules. Any apps that might have caused the problem have been uninstalled (unless I accidentally missed something).
Just FYI for anyone else who might be having these issues...I think we have some answers. After some testing and other suggestions, it looks like I have the 5.0 firmware but am still on 4.4.4, and that discrepancy appears to be causing the freakout. I assume Verizon pushed the new firmware during a reboot over the past couple days because I certainly didn't do it intentionally (and I have no plans to upgrade to 5.0 Lollipop anytime soon, either). However, by unselecting the Smart Network Switch functionality, it appears the wifi is behaving itself again and all is back to normal. Thanks, Big Red.
This morning I noticed my phone getting very hot in my pocket. A quick check of gSam showed the phone temp at 105°. Battery had dropped from 100% to 60% in under two hours with no use. When I checked app usage mm-camera-daemon was running at 89% usage. I booted to recovery and wiped cache and that stopped it. Did a Google search and found that this was a bug with 4.4.2 and was fixed with 4.4.4. Now there are lots of posts on various forums about people having this problem with 5.0. It is the process that runs the camera and it apparently gets stuck running after using the camera or if any camera related apps are used. Clearing the cache fixes it, but I'm reading in different places that it may start again within a few hours. Just wondering if anyone else here has experienced this yet.
newmanx4 said:
This morning I noticed my phone getting very hot in my pocket. A quick check of gSam showed the phone temp at 105°. Battery had dropped from 100% to 60% in under two hours with no use. When I checked app usage mm-camera-daemon was running at 89% usage. I booted to recovery and wiped cache and that stopped it. Did a Google search and found that this was a bug with 4.4.2 and was fixed with 4.4.4. Now there are lots of posts on various forums about people having this problem with 5.0. It is the process that runs the camera and it apparently gets stuck running after using the camera or if any camera related apps are used. Clearing the cache fixes it, but I'm reading in different places that it may start again within a few hours. Just wondering if anyone else here has experienced this yet.
Click to expand...
Click to collapse
I would suggest checking to make sure you have Smart Stay turned off; it's not a complete solution but it eliminates a way the camera can turn on without you having directly initiated it. Since Smart Stay uses the camera to check if you are still looking at the phone before turning the screen off, it can cause the daemon to start even without a person realizing it leading to the overheating and power drain.
The morning this happened I booted to recovery and wiped the cache partition then left the phone off until it cooled down. I have not had this happen again since.
This is now happening 9 out of 10 times I open the camera or the gallery. With the original Lollipop update it was sporadic, but since OC4 it has become a regular problem for me. Is anyone else experiencing this?
newmanx4 said:
This is now happening 9 out of 10 times I open the camera or the gallery. With the original Lollipop update it was sporadic, but since OC4 it has become a regular problem for me. Is anyone else experiencing this?
Click to expand...
Click to collapse
It isn't just a lollipop problem. I'm on 4.4.4 NI2 and it happened to me. I deleted apps and still couldn't get it fixed. I had to go back to an earlier backup to get rid of it. Never figured it out.
Strange I never experienced this on KK. A cache wipe always fixes it but it's very annoying.
Probable Solution!
I had same problem on towelrooted 4.4.2 NE9 stock ROM. You can try this. I removed skype, rebooted and re-installed it again. And I never had this battery drain issue because of this again.
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
ks-man said:
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
Click to expand...
Click to collapse
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
jbkmin said:
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
Click to expand...
Click to collapse
Did your issues first start after you upgraded to lollipop?
ks-man said:
Did your issues first start after you upgraded to lollipop?
Click to expand...
Click to collapse
Definitely after the upgrade.
While on KitKat, it never happened (1 month ownership). But after upgrading to lollipop, it has happened 4 times (6 nights since lollipop).
Have you figured anything out with your situation? Woke up this morning to my backup alarm and the Yellow Sprint screen on my phone.
I guess I'll have to try another factory reset and if it still happens try and get a replacement. It just doesn't seem widespread enough of an issue to be a software bug with 5.0.1.
Very frustrated. I did another factory reset but the issue still plagues my device. It still only occurs once or twice a week but when I hear my old clock radio alarm in the morning I know when I look over I'll see the yellow frozen Sprint Spark screen. I am completely out of ideas and guess I will need to have it replaced under warranty. I'm hoping Sprint won't give me a hard time as this will be very hard to demonstrate.
It definitely appears to be a software issue as it never happened before I upgraded to Lollipop but there must be more to it or others would be complaining.
If anybody has ideas please let me know. Thanks.
Response to Note 4 Freeezing while charging
I have found that after turning the quick charge feature off the problem is not happening. Hopefully this is fixed in 5.1
I'm having the same issue even after turning quick charge off..def a lollipop bug, never experienced this on kk.
I know its not the BEST option, but after taking the update to lollipop, sometimes left over kitkat files can make the system poop out. Sometimes a factory reset will take care of the leftovers. But of course, then you have to set your phone up again
If you've tried this or plan to to, let us know the results.
(When i first took the update, my heartrate monitor sensor was always on, so i did a factory reset and it fixed my problem).
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
same problem here
Ive tried turning off fast charging option on the powersaving mode
And also tried the option on developer mode, the "keep device awake while charging"
And even flashing dofferent firmwares from sammobile through ODIN and installed custom roms. These options doesnt resolve the issues on freezing while charging..
I think turnong off your device while charging is the only option..
Im using note4 N910C..
Clasimodo said:
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
Click to expand...
Click to collapse
Thanks a lot, Mate. I'm trying your workaround now. Will report later if it works on my phone. BTW, so, are you sure it is a just a system issue? Definitely, isn't a hardware problem? Did you fix it, after your post -a month ago-, installing, for example, lollipop 5.1.1 or Cyanogenmod 12.1? I'm on 5.0.1, SimpleRom V4. Of course, mi device, N910C, is rooted.
Thanks again.
With lollipop 5.1.1 the problem is solved for me, even without this workaround.
Sent from my SM-N910F using XDA Forums PRO
I'm having similar issues as you guys. I found out that my phone will only perform normally when I charge it with my laptop USB port which I think is around 0.5amps. Anything above that, even a 1amp charger would cause the phone to freeze, reboot and turn off and not turn back on. The phone has been in repair 4 times and the problem is still there. Now every night I'm forced to charge my phone with my laptop which takes an age instead of the fast charger that came out of the box.
Currently my phone is still freezing and rebooting when I'm out and about and the only way I can get it to perform normally is when I plug it into my laptop. This normal functioning would only last whilst the phone is plugged in.
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
waqar747 said:
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
Click to expand...
Click to collapse
Sounds like a bad flash. The new flash removed the issues, so you're good to go.
Guess what guys, the problem returned after about 3-4 weeks. Appeared randomly while using FB. Phone went into bootloop and overheating again, and even when it restarted properly, it would go into the same cycle when I started using apps like messaging, whatsapp and facebook.
I booted in recovery and cleared the cache after about 25 reboots. One thing I noted was that recovery initially showed an update running, which got stuck first, and then completed after another reboot and entering into recovery. Has been stable for the past 24 hours now, like it never happened. I can't figure out what the issue could be, since now I can do whatever I want and it won't overheat like before or reboot.
Feels like a software issue since it disappears like it was never there. Hardware rarely does that. Is there a possibility that storage of some sort is bad at some point, and when data is written over that point, the problem appears. I'm shooting in the dark but can't figure it out otherwise.
Yup.
Seems you have memory issues.
Go to Samsung service and replace memory chip.