Related
Hey guys!
So I run off of the stock stuff sprint gave me, too lazy and totally happy with stock stuff.
So I updated to 4.3 the other day and my battery drains super fast. Before the update I could go through my whole school day and get home and my battery was at 40% ish every day but it would vary on the day no lower than 25% though.
Today my phone died 2 hours before I even got home which I have never had with any phone that I have owned.
What is causing this and what can I do to fix this issue?
Probably a wakelock issue. Go to the play store and download a wakelock detector app.
I downloaded a wakelock detector app, I will keep an eye on what is says and report back here if any other problems exist.
So I downloaded a Wakedetector app as suggested... the problem still persists. Today after an hour off my charger I am at 80%.
What could it be? I close my apps, I have the brightness turned down, I barely watch videos. GPS is off, connected to my home wifi all the time when i'm home. Never searching for stuff in the settings.
If this can't be fixed can I go back to what I was running before the update?
So I was having the same problem and my husband was having it worse.
I'm on Barebones 4.3 rom and I did the following:
Installed Greenify and hibernated apps I do not use all the time,
Using the built in app manager I turned off the 3 print services apps that I don't use,
then drain my phone all the way, set it charge, once full, unplugged and set it to recharge.
My phone was saying it was 100% but it wasn't really. Did one of those charge to 100% unplug recharge till the time from charging to charged was about 1 minute.
My husband on the other hand is stock ota 4.3 w/ knox. So I did used the built in app manager and started one by one turning off what bloatware I could (kies, print services, other samsung stuff he doesn't use), cleared cache on everything, and some data on sprint apps hoping it would stop them from running. Finally did the same battery charge thing I did with my phone and now it's behaving like it was stock 4.1.2.
Before I begin, let me state that I have already factory reset countless times and reflashed my firmware at least 3 times in the past week. Neither of these have helped me at all, so PLEASE do not suggest this. I've been trying to solve this problem for a week or two and everyone has suggested this to me and of course I've already done it, so it hasn't helped me at all.
PHONE: E980
FIRMWARE: Stock 4.4.2 E98020g
BASEBAND: APQ8064/MDM9x15M
SYMPTOMS:
-Battery draining ridiculously fast (appx 10%/hr, but before my last reflash, it was draining 50%/2hrs!)
-Phone only lasts about 5hours.
-Android OS is consuming about 80-90% of battery, followed by Screen at around 10%
-Phone is constantly warm
-Phone rarely enters Deep Sleep (it stays awake 95% of the time).
TESTS DONE:
-As I said, I factory reset numerous times with the same exact problem
-I reflashed my firmware 3x, with same problems
-I usually keep auto-sync on, but the issue occurs whether it is on or not.
-There is supposably a Kitkat 4.4.2 (in general) issue where the camera will consume a ton of CPU resources and get stuck that way. I haven't used my camera much, but do use Smart Stay, so I disabled this. No positive result.
-Disabled the Google Now "OK Google" hotword detection. This helped reduce the drain, but didn't solve it. Drain went from like 15%/hr to 10%/hr.
-Took battery out of phone for 10 minutes and placed back in. Seemed to help at first, but after about an hour or so, it returned.
-"Recalibrated" the battery numerous times. This was done by draining the battery until the phone shut itself off. Then I charged the phone to 100% while the phone was still off. Once the phone read as having 100% charge, I let it charge for another 1 hour. Then I unplugged the phone and booted it up. Again, this appeared to help at first, but after a while, the phone began to drain rapidly again.
NARROWING THE ROOT PROBLEM:
-Both WakeLock Detector and BetterBatteryStats show "wlan_wake" and "wlan_wd_wake" as being the largest wakelocks.
-As previously mentioned, "Android OS" is consuming a huge amount of battery
-Problem only seems to happen when wifi is on, whether it is connected to an SSID or not.
OTHER:
I have narrowed the issue down to wifi but I can't seem to figure it out any more than this.
Both of the "wlan_" wakelocks are caused by wifi being on and I need wifi on whenever possible because I can't afford a huge data plan. My current one is 2GB/mo and it is shared between 3 people.
I noticed today that my phone drained 10% within 1 hour after taking the phone off the charger, and I was connected to my home wifi. I then went to work, but still had wifi turned on on my phone. At work, I was only connected to mobile data (but the phone was just sitting in my pocket). The battery drained another 15% within an 1hr 30min, and the phone was warm in my pocket (very uncomfortable!). I then turned wifi off completely, and the battery drain completely disappeared!!! The battery life was amazing in fact!
PICTURES:
I've provided some screenshots with notes. Please take a look at them.
I'm going to manually make the problem happen again and will upload new pictures afterwards. They will be of WLD and BBS. Any current info I have is tainted since I turned wifi off and the problem temporarily turned off too. I want to get only screenshots of what is going on when the problem is happening.
EDIT: BTW, the problem occurs whether my mods are installed or not (the mods used to remove the icons in statusbar, AdAway, etc)..
The issue seems to be pureply related to wifi and nothing else.
IDEAS:
Could adding a wifi supplement scan interval to the build.prop solve this problem?
Is Wifi bugged in this firmware? (This never happened on Jelly Bean!!!!)
Is maybe the "Battery Saving for Wifi" feature bugged?
Would maybe flashing the Jelly bean modem (e98010p) solve this issue (since it didn't happen on Jelly Bean)? If so, does anyone have a flashable version of this? <- I just did some research and it seems that the baseband (AKA modem) is the same in Kitkat as it was in Jelly Bean. Weird....
These pictures were taken shortly after making my first post. I already had wifi turned off, so I turned it back on and after a few minutes, the battery began to plummet. I went from roughly 77% to 66% in just an hour!!!!
Just to make sure that it is clear, I have both BBS and WLD set to start recording data after the phone has been unplugged from the charger. So to restart the data collection, I simply plugged the phone into my charger for a few seconds and then removed it. THEN I turned wifi on. The data seen in the pictures should only have occurred between the time when I unplugged the phone and the time I took the pictures.
EDIT: Also just to make sure it's clear: All the data shown in the System picture is actually since I unplugged the phone this morning. I only posted these pictures to show any changes from the similar ones posted earlier.
PLEASE! Can anyone help me solve this!?
Or is this a major Kitkat bug!? (or ATT bug, or modem bug, etc etc).
After a full week of this problem, I think I just made another breakthrough. Unfortunately, I think it IS one of my Xposed modules, which is weird because I didn't think any of them would have a need to constantly connect to the internet.
All I know is that I just completely uninstalled the Xposed Framework and the phone started to sleep like a baby... with wifi on!
Now I just need to pinpoint the module, which I can do myself.
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
spexwood said:
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
Click to expand...
Click to collapse
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Toledo_JAB said:
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Click to expand...
Click to collapse
In this case, I need to be more specific about my solution then.
The problem seems to be caused by the module, Xposed Torch. It's still usable, but you need to tap the overflow (3-dot) icon and disable ads (it's free to do this). The module requires internet access permissions, which I was not aware of, and it constantly connects to the internet to stream the ads. This in turn causes the wifi to constantly receive data (thus the wlan_wd_wake and wlan_wake). When wifi is on, but not connected to a network, I think it forces wifi to constantly scan in order to find a connection so that it can get that ad data. I'm not sure why it doesn't just use mobile data though... unless it does and it's just more power efficient.
So far, I have disabled the ads via module settings and the phone is now sleeping like it should.
So if anyone else is having wlan_wake wakelocks of any kind, especially followed by wlan_wd_wake or wlan_rx_wake, then this means that something on your phone is constantly accessing the internet via wifi. FIrst turn off auto-sync, and if this doesn't help, then you need to uninstall apps until the problem ceases.
My phone is currently icy cold in my hand and I've never been so happy to feel it like this!
Problem came back today. I've basically uninstalled every app now and the battery is still draining whenever wifi is turned on.
Under Better Battery Stats, there is a process (?) called dhc_dpc that's been running the entire time my phone has had wifi on. There are also the wlan_wakes too. (NOTE: IIm backing up my phone right now, so these names are coming from memory).
According to this thread (different phone and unknown Android version, but similar problem), the wifi driver may be bugged. They recommend doing a reinstall, but I've done this many times now and it doesn't seem to help:
http://forum.xda-developers.com/galaxy-s2/help/dhddpc-t1246190
EDIT: I think I've found the culprit and while it is definitely wifi-related, it's NOT an app. It's the actual Android system constantly pinging the internet. According to my research, it's constantly collecting location data by using either mobile data or wifi and will do this whether you have location services (gps) or Location Reporting enabled. This has been described as a "bug." It was introduced by Google as a cool new feature, but it's implementation was buggy.
I am currently testing a fix to resolve this issue, but want to be certain that it's fully working first.
Just an an FYI, this fix SHOULD help anyone running Android 4.4.2 and experiencing high battery drain caused by Android OS. Even better, the fix does not require root, so anyone can do it!
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
3617 said:
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
Click to expand...
Click to collapse
Not to be rude, but the first sentence of my first post says I did this several times.
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
zamajalo said:
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
Click to expand...
Click to collapse
It's definitely Xposed related I think.
I've disabled Xposed during some testing a day or two ago and yeah, battery definitely improved.
The only modules I have installed are:
App Settings
Enable BatteryStats Permission (just to allow me to track this issue. I installed this after problems had already begun)
Greenify (all Xposed settings checked)
YouTube AdAway
I have also been using G2 TweaksBox up until last night. I only used it to declutter my status bar and to enable the advanced reboot menu. (I hate all the icons in the status bar!!!). Last night I disabled G2 TB and battery life improved dramatically!
I can't explain why G2 TB would cause battery drain, but I did notice it doing something odd yesterday. I have the lockscreen off sound enabled in the system settings, so I hear the sound whenever I lock the screen. Well, I turned my phone on yesterday for some reason when in my car. I then turned the screen off, heard the lock sound, and started driving. 15 minutes (NOT seconds!) into my drive, I randomly heard my phone make the locking sound, but the screen was not turned on!! I wonder if G2 TB delays my lock somehow.
I switched to GravityBox[KK] today since so many people claim that it works perfectly on their OGP, and so far, battery drain is MUUUUUCH better than with G2 TB activated, but it still may not be as good as pure stock. I need more time to figure it out though. This morning, my battery dropped 5% in 40 minutes while connected to my home wifi. I then left my house for a few hours, but left wifi turned on on my phone (it's hard for me to remember to switch it off and on all the time!). The battery seemed to be pretty stable after that, but I can't explain the weird 5% drop, but I did receive 2 missed calls and a text during that time too. Should I lose 5% just from getting a text and having my phone ring?
It's now night time and I'm at 75% battery. This past week, I would be at about 10% by now or even DEAD, so I'm happy as heck right now.
I would LOVE to be able to keep using GB, but I now just need to figure out if it too is draining battery, or if everything is stable. I'm going to continue comparing stock VS GB tonight and tomorrow. I'll live with stock if needed, but I'm just very OCD about the statusbar clutter.
In GB, I only disabled some icons, centered the clock, enabled advanced reboot menu, and enabled the lockscreen torch.
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
zamajalo said:
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
Click to expand...
Click to collapse
OK, so I just got home from work and today I not only had GravityBox disabled, but I also had the ENTIRE Xposed Framework uninstalled.
My battery is now at 30% and I was only gone for 7 hours!!!!!!!!!!!!!!!!!! This is ridiculous!!!!!!!!!
*sigh* <- frustrated with this whole situation
Yes, the wakelocks are still active.
The top two Kernel Wakelocks are "wlan_wd_wake" (46.3%) and "wlan_wake" (46.2%) in that order. The next in line is "PowerManagerService.Wakelocks" (8.0%) and then "msm_hsic_host" (6.1%). This was since my last reboot, which was about 2 hours ago (I had to rebooted after removing an app that I thought was the culprit... apparently it wasn't).
Again, I keep Auto Sync on, but disablign it seems to not help in this matter at all.
I also keep wifi on. When at work, it isn't connected to a network, but I often forget to disable wifi when I leave the house, or I come home and forget to enable it and end up sucking my data plan dry. Nonetheless, I also did this while on Jelly Bean and had no issues whatsoever.
My phone is only staying in deep sleep less than 10% of the time and the time when it is awake, the CPU is running at full 1.7GHz! This is causing the phone to get warm in my pocket. It doesn't hurt, but it's enough to make things uncomfortable.
According to the battery stats (in system settings), Android OS is consuming 83% of the battery.
The biggest network drainers are "Google Play Services" (33.3%), something simply called "0" (14.8%), and a weather app. I had the weather app open manually not too long ago though, so that explains that one, but the other two I can't. I have no clue what "0" is and I have not opened Play at all today.
It's something to do with wifi itself I think, and maybe not a specific app accessing wifi. (?)
I turned wifi completely off about an hour ago and the battery drain has been stable. It's been like this for days too. If I turn off wifi, the drain is "normal." If wifi is on and connected, drain is higher than with wifi off, but barely. If wifi is on and not connected, the battery level plummets like a rock in a pond.
OH! One thing I just thought about and should mention:
Before I discovered that G2 TweaksBox was causing serious drain, I was on another battery-related thread in the OGP forum. Someone told me to delete the "libiq_client.so" file from System/lib. He assured me this would give me excellent battery life (which apparently it did not). So I did. Normally, I just rename system files so I can restore them if needed, but I guess I accidentally deleted this one.
Could this be causing the drain, and if so, can someone upload a copy of libiq_client.so so I can try it on my phone (after setting it's permissions correctly)?
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
zamajalo said:
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
Click to expand...
Click to collapse
"Scanning always available" has been disabled since day 1
The only nand backup I have is after I already deleted the file :/
I did try clearing Google Service's cahce/data at one point and I think it helped for a few hours. It may have been a placebo effect though. I also di the recovery cache wipe and dalvik wipe with same results.
I don't keep location on at all since I don't use it. It's always off, but at one point, I did enable it to select the battery mode and then turned it off again. I did this mainly so that if and when I do use location, it would always use Battery and not High Precision.
I'm currently backing up my rom, so all partial wakelocks were cleared for now. Sorry.
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
spexwood said:
"Scanning always available" has been disabled since day 1
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
Click to expand...
Click to collapse
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
zamajalo said:
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
Click to expand...
Click to collapse
It's OK, I'll get the file from the flashing. I know it'll be a pain, but this may be safer just in case there is some sort of difference between the E988 and E980 versions. I doubt there would be, but better safe than sorry I guess.
I did add those settings to my build.prop as a test, but I was smart there and backed up my stock build.prop first and ended up restoring it a few hours later. It was causing my screen to not always turn on when I pressed the power button.
I have not tried any other ROMs. I prefer to stick to stock ROMs (or modified versions of stock... basically anything stock-based and not CyanogenMod or AOSP). I had bad experiences with AOSP-based ROMs on my old phone.
If I tried a stock-based ROM though, it must have everything working though. I mean everything: calls, texts, LTE, bluetooth, speaker phone, etc etc.
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
spexwood said:
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
Click to expand...
Click to collapse
Better to misplace than to delete it, trust me
Post results.
zamajalo said:
Better to misplace than to delete it, trust me
Post results.
Click to expand...
Click to collapse
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
spexwood said:
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
Click to expand...
Click to collapse
Libiq.so enables carrier IQ, its removal should only help battery drain, not cause it.
Just to ask, have you tried adjuating wifi scan interval? You can try as well the xposed module, "wifi deep sleep". Helped minimize my wifi related drain
Me and my partner both have HTC ONE x's, Endeavouru, round a similar age, but her phone recently started draining battery.
Both running ARHD, with the same kernels. First I checked if apps were responsible, wiped and reflashed the ROM and kernel both.
This did not work, so then checked battery health with *#*#4636#*#* - showing the battery was in good health, but then replaced the battery anyway to eliminate any possibility of this being the culprit.
Now it's still giving massive drain - a charge up to 100% will last up to 5 hours of standby, with only mobile network activity turned on, all other radios off.
Been throughout the forums and other websites looking for any solutions to this problem but not striking any luck. Tried resetting the radio, changing it to LTE (Not even available where we are), and back etc, as one thread suggested, turned radio completely off and back on. Tried super cleaning the system before reflashing the ROM, tried a different kernel, an AOSP ROM, and still no luck.
It just all of a sudden started to do it, similar conditions to my phone, which makes it harder to pinpoint.
Any new idea's to bring to the table, open to any.
nb: Posted in wrong forum earlier, my bad.
goentillsundown said:
Me and my partner both have HTC ONE x's, Endeavouru, round a similar age, but her phone recently started draining battery.
Both running ARHD, with the same kernels. First I checked if apps were responsible, wiped and reflashed the ROM and kernel both.
This did not work, so then checked battery health with *#*#4636#*#* - showing the battery was in good health, but then replaced the battery anyway to eliminate any possibility of this being the culprit.
Now it's still giving massive drain - a charge up to 100% will last up to 5 hours of standby, with only mobile network activity turned on, all other radios off.
Been throughout the forums and other websites looking for any solutions to this problem but not striking any luck. Tried resetting the radio, changing it to LTE (Not even available where we are), and back etc, as one thread suggested, turned radio completely off and back on. Tried super cleaning the system before reflashing the ROM, tried a different kernel, an AOSP ROM, and still no luck.
It just all of a sudden started to do it, similar conditions to my phone, which makes it harder to pinpoint.
Any new idea's to bring to the table, open to any.
nb: Posted in wrong forum earlier, my bad.
Click to expand...
Click to collapse
try downloading wakelock detector and seeing what keeps the phone awake and then uninstalling/reducing its privileges
the privileges part can be done with xposed and a module called appops
suljo94 said:
try downloading wakelock detector and seeing what keeps the phone awake and then uninstalling/reducing its privileges
the privileges part can be done with xposed and a module called appops
Click to expand...
Click to collapse
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
goentillsundown said:
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
Click to expand...
Click to collapse
Looks like faulty battery, try change the battery with new one and see what will happend
goentillsundown said:
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
Click to expand...
Click to collapse
check if your cpu is stuck at 100% or 1.5 ghz in trickstermod and could you post a screenshot of wakelock detector?
Thant said:
Looks like faulty battery, try change the battery with new one and see what will happend
Click to expand...
Click to collapse
in the OP he said that he did that already
suljo94 said:
check if your cpu is stuck at 100% or 1.5 ghz in trickstermod and could you post a screenshot of wakelock detector?
in the OP he said that he did that already
Click to expand...
Click to collapse
Sorry I didn't see that. Then I am 80% sure the light sensor not working or working wrong. Must to check this. I am sure it is some of the sensors
Thant said:
Sorry I didn't see that. Then I am 80% sure the light sensor not working or working wrong. Must to check this. I am sure it is some of the sensors
Click to expand...
Click to collapse
Surely if it's the light sensor it would be irrelevant if it was turned off or on though, same with the CPU. I'm going to spend some time getting power into it today, charge, then put in freezer to cool it, and repeat.
Once some power is into it I'll start with suggestions, one at a time, and get some screen shots up, and logs of the current drain.
Thanks for the help so far, would be good to get it going again, instead of having a $350 paper weight.
An update:
Changed the recovery from Philz recovery to an older CWM recovery program, and now possibly just through coincidence the battery isn't super heating to the point it needs to live in the freezer to charge.
I have restored to stock ROM, and have a couple of pictures of the battery history, which are neither here nor there, apologies as I wiped a lot of things off, including my WLD pictures from the ARHD ROM.
I purchased trickstermod and had a look into the CPU settings, and nothing seemed out of the ordinary. Also turned on the dev options of graphic CPU usage on the homescreen - not really showing unusual signs of anything. About to flash the original recovery on and email HTC to see if they might feel sorry enough to accept it as a straight manufacturing defect, without evidence of where we purchased it (as it was a second hand phone off the net).
subscribing to this thread - I have the exact same issue. I have installed CM11 and ParanoidAndroid. Torched and Bubba kernel... turned off lots of stuff.
I have whatsapp, soundcloud and facebook as the only background running apps. not sure what's the issue
sensors drain battery
Hello!
I also have a similiar issue.
I noticed, after a while, that my phone keeps dying under 16-18 hrs on idle from full charge.
I thought it1s the battery, since my HOX is 2 years old. Someone suggested, to try some battery monitoring, so i got the battery monitoring widget, after for like 3rd time, the phone turned off overnight.
The problem, is the Light, and the acceleration sensors... they won1t let the phone go to sleep.
I tried turning off locations, and such, also auto rotation, and my back light was never on auto. it is set around 30%
Still, these sensors run, and consume battery like crazy. This started about 2 weeks ago.
I have a stock rom. not the original, since i thought flashing a custom rom might solve this, so i tried ViperX 4.1.1, the problem was still there.
After that, i reflashed an untouched original HTC JB rom.got the latest OTA update, and the problem is still there...
I don't have any apps running in the background, that should require these sensors to run. i always clear multitasking also.
Have Wifi on, but that barely consumes anything.
Any idea, i know this started on Gingerbread, and was supposedly fixed in ICS, but it's still happening to some ppl.
Any help would be appreciated!
Laccee said:
Hello!
I also have a similiar issue.
I noticed, after a while, that my phone keeps dying under 16-18 hrs on idle from full charge.
I thought it1s the battery, since my HOX is 2 years old. Someone suggested, to try some battery monitoring, so i got the battery monitoring widget, after for like 3rd time, the phone turned off overnight.
The problem, is the Light, and the acceleration sensors... they won1t let the phone go to sleep.
I tried turning off locations, and such, also auto rotation, and my back light was never on auto. it is set around 30%
Still, these sensors run, and consume battery like crazy. This started about 2 weeks ago.
I have a stock rom. not the original, since i thought flashing a custom rom might solve this, so i tried ViperX 4.1.1, the problem was still there.
After that, i reflashed an untouched original HTC JB rom.got the latest OTA update, and the problem is still there...
I don't have any apps running in the background, that should require these sensors to run. i always clear multitasking also.
Have Wifi on, but that barely consumes anything.
Any idea, i know this started on Gingerbread, and was supposedly fixed in ICS, but it's still happening to some ppl.
Any help would be appreciated!
Click to expand...
Click to collapse
I have checked all the sensors in the testing menu by dialing *#*#3424#*#* and they all turn off and on as required properly. I noticed yesterday that I've actually burnt out the charging system as it has got too hot at one point, so no use pursuing anymore. I will stick with my HOX until it too breaks in some way. Received an email back from HTC saying "Not under warranty, not our problem" after asking if they had had any phones with similar issues pass through.
Hello! I've been lurking around trying to solve my battery drain issue for two days without success. I have a d2att with severe battery drain, where battery would last for around 2 hrs MAX before shutting down at 40%. This was apparently an issue before (my brother was using it) when it was on stock unrooted 4.3. I installed Carbon 4.4.4 to look for improvements.
Symptoms:
Rapid battery decrease during use
Shutoff at 40% (when rebooting it would show 0%, when charging it will start at 40%)
Constant wake (I believe from the systemupdate wakelock that is unstoppable)
Feels warm during short times of use, cool when standby
Attempts to fix:
Using GSAM to monitor battery drain (just installed Betterbatterystats, will update with that info later)
Installed MyAndroid Tools and Disable service to stop systemupdate and checkin services
Autoruns to stop all systemupdateservice receivers
Dalvik cache wipe to try to fix the 40% shutoff
Privacy guard to turn off keep awake for Google play services and Android system
Privacy guard to turn off location for GNow
Have not done:
Replace battery (just ordered one that's coming in two days)
Clearing batt stats, as apparently that doesn't help
Factory reset, as it's a pain to setup again (Should this be next?)
Greenify
Xposed
I am just generally confused at this point at whether systemupdate service is turned on or off, or how to solve that, or if that is even the main problem, and what my next steps should be. I'm not an expert and can only understand half of what's going on, so any advice is greatly appreciated!
*Update: It seems that the phone is able to go to deep sleep (~50% of the time). When I use it just 5 minutes for texting, the battery can drop 5%. After reading from another thread, I re-enabled systemupdate services from Disable Services/My Android tools to see if that would solve the problem, and it looks like it is not hogging wakelock anymore; however it does revert on boot, similar to this: forum.cyanogenmod(.)org/topic/96459-systemupdateservice-wakelock-on-cm11-m7-massive-battery-drain/
Update 2: I flashed Liquidsmooth 3.1 stable instead. This time I used autoruns manager and wakelock blocker (included in liquidsmooth settings) to disable the services, but systemupdate service still manages to run, so I have to disable the block to somehow make it stop with every boot. Once that is fixed, deep sleep functions normally, but now the new problem is that Chrome browser app seems to be stuck in an AudioMix wakelock. I uninstalled Chrome updates and this seems to have fixed that issue, however battery drain is still severe (5%/2min) during active phone use. No application stands out in constant wakelock anymore, so I'm suspecting it may be the battery itself? I will switch to a new battery tomorrow to verify.
Update 3: Well since no one bothered to help, I will just post this for future reference as a log, since I solved the last part by the battery switch to an Anker battery. The phone still gets hot, and I still have to manually deactivate systemupdate service on every reboot, but now it runs for "normal" times 5-6hrs (heavy use).
To be honest, it sounds like you had a failing battery. It happens.
obfuscated said:
Hello! I've been lurking around trying to solve my battery drain issue for two days without success. I have a d2att with severe battery drain, where battery would last for around 2 hrs MAX before shutting down at 40%. This was apparently an issue before (my brother was using it) when it was on stock unrooted 4.3. I installed Carbon 4.4.4 to look for improvements.
Symptoms:
Rapid battery decrease during use
Shutoff at 40% (when rebooting it would show 0%, when charging it will start at 40%)
Constant wake (I believe from the systemupdate wakelock that is unstoppable)
Feels warm during short times of use, cool when standby
Attempts to fix:
Using GSAM to monitor battery drain (just installed Betterbatterystats, will update with that info later)
Installed MyAndroid Tools and Disable service to stop systemupdate and checkin services
Autoruns to stop all systemupdateservice receivers
Dalvik cache wipe to try to fix the 40% shutoff
Privacy guard to turn off keep awake for Google play services and Android system
Privacy guard to turn off location for GNow
Have not done:
Replace battery (just ordered one that's coming in two days)
Clearing batt stats, as apparently that doesn't help
Factory reset, as it's a pain to setup again (Should this be next?)
Greenify
Xposed
I am just generally confused at this point at whether systemupdate service is turned on or off, or how to solve that, or if that is even the main problem, and what my next steps should be. I'm not an expert and can only understand half of what's going on, so any advice is greatly appreciated!
*Update: It seems that the phone is able to go to deep sleep (~50% of the time). When I use it just 5 minutes for texting, the battery can drop 5%. After reading from another thread, I re-enabled systemupdate services from Disable Services/My Android tools to see if that would solve the problem, and it looks like it is not hogging wakelock anymore; however it does revert on boot, similar to this: forum.cyanogenmod(.)org/topic/96459-systemupdateservice-wakelock-on-cm11-m7-massive-battery-drain/
Update 2: I flashed Liquidsmooth 3.1 stable instead. This time I used autoruns manager and wakelock blocker (included in liquidsmooth settings) to disable the services, but systemupdate service still manages to run, so I have to disable the block to somehow make it stop with every boot. Once that is fixed, deep sleep functions normally, but now the new problem is that Chrome browser app seems to be stuck in an AudioMix wakelock. I uninstalled Chrome updates and this seems to have fixed that issue, however battery drain is still severe (5%/2min) during active phone use. No application stands out in constant wakelock anymore, so I'm suspecting it may be the battery itself? I will switch to a new battery tomorrow to verify.
Update 3: Well since no one bothered to help, I will just post this for future reference as a log, since I solved the last part by the battery switch to an Anker battery. The phone still gets hot, and I still have to manually deactivate systemupdate service on every reboot, but now it runs for "normal" times 5-6hrs (heavy use).
Click to expand...
Click to collapse
theres an xposed app called amplify that helps to block some wakelocks , startups and alarms. it might help.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Background:
So last night I went to bed and left my phone on my dresser with 30% battery. The phone normally drains a few % overnight. WiFi on, Location on (high accuracy), Mobile Data On, etc. I wake up this morning to find that my phone is completely dead. I thought it was pretty strange so I connected the phone to the charger for an hour or so and charged to about 96%. I disconnected my N5X from the charger and put it on my computer desk and sat down to play The Division for a little while. After about an hour, I noticed that my phone was still very warm and that my battery had sank down to 88%... I've never had this problem before, even on my current ROM and kernel setup, which I've been running for about a week now.
Problem: Insane battery drain. CPU is Awake 100% of the time, even when the screen is off. No Deep Sleep and No Doze.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did notice, however, that the phone reported WiFi being on for a large portion of the day where I actually had turned the WiFi off. The gym I go to every day has horrible WiFi and I prefer to use LTE. I usually forget to turn WiFi back on after leaving to go back home and shower. So there's at least a 2-3 hour segment there where WiFi was absolutely not enabled, and yet the battery graph shows that it was....
Culprit:
This mother****er right here. com.google.android.gms. Specifically two alarms: ALARM_WAKEUP_LOCATOR and ALARM_WAKEUP_ACTIVITY_DETECTION. I'm not so sure about the latter, but the Alarm_wakeup_locator is actually waking the phone up at least twice a minute, which is insane. It's massacring my battery life as well.
Solution?
I've never had a battery drain problem like this before. In fact, I haven't had a drain problem like this in at least a year or two. I have no idea what to do to fix this. I've Googled this issue and there doesn't really seem to be a straight answer.
I think it has something to do with Google Now or Google Play Services, perhaps a location setting, but I've tried disabling Location for 2 hours now and it has not fixed this issue. I have considered perhaps disabling a service but I can't identify which service exactly is causing the issue.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update! - March 22nd, 2016
After a second clean wipe and a switch to Pico Gapps, the problem was resolved. This gave me a barebones operating system in which the CPU was sleeping just fine when the screen was off. No wild wakelocks or alarms to report. One by one I reinstalled my favorite apps, avoiding almost anything by Google -- No drain / keep awake issue reoccurred. My phone is now back to normal with only one thing missing. Google Now. The Google app and Google Now Launcher are both NOT on my device and my phone is achieving some seriously sick battery life and SOT. I am confident that if anyone else is facing these issues that the culprit is Google Now and the Google Search app. Those experiencing this issue should try removing these apps if possible or clean wipe and install with a very minimal Gapps package, just as I did.
I get similar Google alarms too, but it shouldn't cause any drastic drain.
I recently had a massive battery drain but couldn't work out the cause. Was going down 30%+ overnight and nothing had really changed on the system (few new apps which I removed).
The only thing showing any high battery drain was Google play services but even that was only at 4-5% (104 ish mah in the battery stats from memory) which didn't tally with the massive drain I was showing.
Ended up having to do a full reset to sort it out and all fine now.
This was pre the March update and fixes, I did flash the fixes while I had the issue and nothing improved.
roofrider said:
I get similar Google alarms too, but it shouldn't cause any drastic drain.
Click to expand...
Click to collapse
Yes but does your phone enter deep sleep? The only reason why I'm even looking at the alarms is because something is keeping this phone awake constantly.
Alcolawl said:
Yes but does your phone enter deep sleep? The only reason why I'm even looking at the alarms is because something is keeping this phone awake constantly.
Click to expand...
Click to collapse
Yes mine does go to sleep. Attaching some of my battery (mediocre) screenshots.
I would suggest turning off wifi and bluetooth scanning in location settings. I found it kept my wifi always active (even if wifi was turned off) when GPS was set to high accuracy. Sometime even if you change from high accuracy to battery saving, the wifi continued running til the phone is rebooted (at least in my case). Bad network will also cause drain, but none of these should keep the CPU firing always. Have you checked the CPU states? Is Google Service keeping you mobile radio active? How about Android OS?
roofrider said:
Yes mine does go to sleep. Attaching some of my battery (mediocre) screenshots.
I would suggest turning off wifi and bluetooth scanning in location settings. I found it kept my wifi always active (even if wifi was turned off) when GPS was set to high accuracy. Sometime even if you change from high accuracy to battery saving, the wifi continued running til the phone is rebooted (at least in my case). Bad network will also cause drain, but none of these should keep the CPU firing always. Have you checked the CPU states? Is Google Service keeping you mobile radio active? How about Android OS?
Click to expand...
Click to collapse
Mobile signal is excellent. Full bars of LTE at work (which is where I am now). The top battery users (besides the screen) are Android System and Google Play Services. Attached are some screenshots of the keep awake times.. Something very strange is happening here. Bluetooth and WiFi scanning are both off I. Location settings.
Just factory wipes for the second time but went with a Pico Gapps package and the drain is gone. The cpu sleeps now whwn the screen is off. I haven't logged into Google yet, so I'm not sure of the cause yet.
Alcolawl said:
Just factory wipes for the second time but went with a Pico Gapps package and the drain is gone. The cpu sleeps now whwn the screen is off. I haven't logged into Google yet, so I'm not sure of the cause yet.
Click to expand...
Click to collapse
i got the exact same problem with you.
Phone was idle overnight, WiFi on, Location set on High.
Forgot to install BBS so i cannot see what's causing it but i think it is the same thing that causes your battery to die.
mflow said:
i got the exact same problem with you.
Phone was idle overnight, WiFi on, Location set on High.
Forgot to install BBS so i cannot see what's causing it but i think it is the same thing that causes your battery to die.
Click to expand...
Click to collapse
Factory resetting and reinstalling my ROM with the smallest gapps package possible (Pico Gapps) fixed the issue for me. I'm starting to think it was Google Now. Shame, I really liked Google Now too, but I've signed in and installed some of my favorite apps already and there's no drain and the CPU is sleeping like a baby with the screen off.
Alcolawl said:
Factory resetting and reinstalling my ROM with the smallest gapps package possible (Pico Gapps) fixed the issue for me. I'm starting to think it was Google Now. Shame, I really liked Google Now too, but I've signed in and installed some of my favorite apps already and there's no drain and the CPU is sleeping like a baby with the screen off.
Click to expand...
Click to collapse
is Pico Gapps refers to Open Gapps Pico Package? or something else?
ps. i don't use Google Now..
==
update :
clean flashed Latest pure nexus, using latest Open Gapps Pico Package.
*fingers crossed* hope that the problem is gone..
mflow said:
is Pico Gapps refers to Open Gapps Pico Package? or something else?
ps. i don't use Google Now..
==
update :
clean flashed Latest pure nexus, using latest Open Gapps Pico Package.
*fingers crossed* hope that the problem is gone..
Click to expand...
Click to collapse
Yep. That's exactly what I did. Just keep an eye on the battery graph and reset the stats. I put the phone down, walked away and then came back 5 minutes later. I checked the graph and the phone went to sleep after a minute or two so I knew it was fixed. Just remember to let the ROM settle for a little while before doing this. After flashing a ROM lots of stuff needs to settle in the background.
Alcolawl said:
Yep. That's exactly what I did. Just keep an eye on the battery graph and reset the stats. I put the phone down, walked away and then came back 5 minutes later. I checked the graph and the phone went to sleep after a minute or two so I knew it was fixed. Just remember to let the ROM settle for a little while before doing this. After flashing a ROM lots of stuff needs to settle in the background.
Click to expand...
Click to collapse
Okay, done the exact same steps *fingers crossed*
By any chance, do you use any battery saving apps such as Amplify or Greenify?
mflow said:
Okay, done the exact same steps *fingers crossed*
By any chance, do you use any battery saving apps such as Amplify or Greenify?
Click to expand...
Click to collapse
Nice, the screenshots look promising.
Also, no, I prefer not to use apps like that and let the Operating System do its thing. I did almost consider using one of those if I couldn't figure out how to fix this problem but you can get into trouble pretty fast with those apps if you disable/slowdown/restrict/greenify the wrong thing.
Alcolawl said:
Nice, the screenshots look promising.
Also, no, I prefer not to use apps like that and let the Operating System do its thing. I did almost consider using one of those if I couldn't figure out how to fix this problem but you can get into trouble pretty fast with those apps if you disable/slowdown/restrict/greenify the wrong thing.
Click to expand...
Click to collapse
yeah Right, almost installed Xposed only to use Amplify to reduce the Play Service wakelock.
will fully charge this device tonight, and leave it on idle till morning.
I do have Amplify installed to tame play services, but now I'm being tempted to do a clean flash (maybe this is all that is required? Not everyone using the same GApps package seems to be reporting such issues) and try a different GApps packages. Currently on PN GApps. Lets see how long the thought of wiping the data and reinstalling all the apps continue to put me off.
Made the mistake of firing up Google Opinion Rewards today and it asked me if I wanted to use my Location History. I declined and it somehow started destroying my battery life anyways. CPU is being held awake again. Can Google design a single ****ing app correctly?
Alcolawl said:
Made the mistake of firing up Google Opinion Rewards today and it asked me if I wanted to use my Location History. I declined and it somehow started destroying my battery life anyways. CPU is being held awake again. Can Google design a single ****ing app correctly?
Click to expand...
Click to collapse
Are you sure it doesn't have anything to do with any custom software you're using? I'm on a stock device (no root) and have no such issues, I've got just about every Google app installed and use Google now regularly.
bblzd said:
Are you sure it doesn't have anything to do with any custom software you're using? I'm on a stock device (no root) and have no such issues, I've got just about every Google app installed and use Google now regularly.
Click to expand...
Click to collapse
I actually wiped the phone and reinstalled apps one by one until the issue came back and it stemmed from ElementalX's Kernel Management app somehow. I haven't contacted Flar2 about it yet because I'm not sure if it's from a setting that I touched or just the app itself.
Alcolawl said:
I actually wiped the phone and reinstalled apps one by one until the issue came back and it stemmed from ElementalX's Kernel Management app somehow. I haven't contacted Flar2 about it yet because I'm not sure if it's from a setting that I touched or just the app itself.
Click to expand...
Click to collapse
What is EXKM causing? I thought previously Google Services was the problem.
How did you narrow it down to that app? I have it too, maybe i can test.
roofrider said:
What is EXKM causing? I thought previously Google Services was the problem.
How did you narrow it down to that app? I have it too, maybe i can test.
Click to expand...
Click to collapse
I installed the apps I like one by one and recorded them on a list on my computer. After each app install I wiped the battery graph and let it sit with the screen off for a minute or two and checked to see if the CPU was being held awake. I installed like 15 apps before I got to Google Keyboard and EXKM. I installed both at the same time and repeated the procedure. When I looked at my phone, it was being held awake so I knew the culprit was either Google Keyboard or EXKM. I uninstalled Google Keyboard and did a reboot. Phone was still being held awake. I uninstalled EXKM and did a reboot, phone went into deep sleep. I reinstalled Google Keyboard, CPU still wasn't being held awake. I installed EXKM again after a few minutes and the awake issue came back. I uninstalled EXKM and proceeded to install more apps and the phone functions completely normally. I have no idea how EXKM can hold the phone awake like that but I'm guessing its a setting in there that is broken? I installed Kernel Adiutor and applied the same settings and tweaks that I normally would with EXKM and there was still no CPU awake issue so it's gotta be that app.