Firstly, I know what I'm doing when it comes to flashing. But I'm completely dumbfounded here..
Okay in standby mode, with wifi on i usually get -3 to -7mA.
But suddenly a few days ago, my phone doesn't sound my alarm in the morning because it had turned its self off.
Imagine my surprise when I had to plug it to start it. Turns out it had drained 60% in little over 3 hours.
So I began testing - turns out my phone had started to fluctuate between -90 and -150 mA EVEN IN AIRPLANE MODE.
After trying countless solutions (inc many different ROMs), I had had enough. I full wiped from CWM and installed fresh ARHD 5.1.6, skipped all setup, installed just titanium, and restored just battery calibration and currentwidget. I calibrated and then left it overnight in airplane mode - and STILL it fluctuated just as wildly.
I wouldn't post this if I hadn't tried everything, but I have spent hours reading xda trying to amend this. Changing radios didn't help (am using latest atm), changing ROM didn't help (not GB or froyo or CM7), even restoring my nandroid from when my battery drain was normal didn't help.
Does anyone have ANY ideas as to why this is happening?
The only thing I can conceivably think of is that my battery is giving up.
Is this good enough cause to get a replacement battery/phone from HTC?
Edit: Meant to post this is Q&A tread, sorry
if you changed the ROM and radio, then i'd be near to positive to say that the problem is from the battery!!
Buy another one and give it a long 20-22 hrs charge (although HTC recommends 8hrs - but they talk alot of crap ) before opening your phone.
Or, alternatively, see if anyone (friends/family) can lend you a battery and see if the problem still persists
CodeNameUnknown1 said:
if you changed the ROM and radio, then i'd be near to positive to say that the problem is from the battery!!
Buy another one and give it a long 20-22 hrs charge (although HTC recommends 8hrs - but they talk alot of crap ) before opening your phone.
Or, alternatively, see if anyone (friends/family) can lend you a battery and see if the problem still persists
Click to expand...
Click to collapse
Official batterys are expensive... does HTC do replacements?
not sure, never tried or asked, gotta phone them up!
have you tried turning USB debugging on? that solved it for some people.
i also had this problem, and the USB debug didnt work, but i found that it was something to do with HTC hub repeatedly trying to connect to the internet and using a shed load of CPU in doing so. aeroplane mode didnt help me either, but after turning off everything with HTC in its name it worked again. (specifically HTC sense in accounts and sync)
hope that helps, worth a try.
oh and my battery is fine now, lasts 2 days or so. can last a week though.
still charge it every night though.
Thanks for replying, but USB Debugging was always on for me, and when I tested with fresh install I didn't put ANY accounts in so the HTC thing shouldn't be an issue. i guess I'll just try the replacement battery thing
sometimes the radio signal kept switching also may cause a drain in your battery.
Setting > Mobile networks > Network Mode > Preferred Network Mode
for me i preferred it to be set as 'WCDMA' rather than 'GSM/WCDMA Auto'. The draw back is that i may lost signal if the signal is weak but this setting prevent the radio from being switching.
OKAY GUYS I FIXED IT
How you may ask?
I HAVE NO IDEA
I was just flashing things over trying to fix it and suddenly it went back to normal. I'm currently using a UV kernel, so maybe that's helping too.
apoorvajsh said:
Firstly, I know what I'm doing when it comes to flashing. But I'm completely dumbfounded here..
Okay in standby mode, with wifi on i usually get -3 to -7mA.
Is this good enough cause to get a replacement battery/phone from HTC?
Edit: Meant to post this is Q&A tread, sorry
Click to expand...
Click to collapse
Dont want to go too far OT, but how do you measure the battery current?
I assume you dont physically wire up an ammeter, or do you?
Ian P
Hahahahahaha, that's brilliant. I'm signaturing that
But no, I don't. The phone creates estimates of the present current/voltage loss, much the same way as it makes estimates of the battery % left.
So all you need is an app to log that! Currentwidget is the lightest, but I recommend battery monitor widget
OK its a battery monitoring app, but can you see the current drain whilst actually using other programmes?
Some apps use full screen so even the top status bar is not visible.
Ian P
elanman99 said:
Dont want to go too far OT, but how do you measure the battery current?
Click to expand...
Click to collapse
CurrentWidget, logging to file :
https://market.android.com/details?id=com.manor.currentwidget
Hi all, just visiting from the gnex forums. My wife has a desire running the official gingerbread rom. She has a recurring problem whereby she'll power off the phone and it appears to shut down but will still have a grey tint like the screen is still slightly lit. Last night from a full battery it had permanent screen on in the battery stats and was near empty in the morning showing a constant drain all through the night. Has anyone had this issue?, is it related to the gingerbread update or is it just a rogue app??
I've attached an image of the battery stats with the night period being the steep drop on the right...
Any tips or advise is greatly appreciated....
Probably a rogue app. Search for Better Battery Stats app here on XDA to help you see what's keeping it awake.
Furthermore, try disabling fastboot from settings, don't remember which settings, but it should be in there somewhere.
Thanks for the replies. I've got that better battery stats app and just need to read up a bit on how to use it then I'll give it a go tonight. From my searches I found multiple things suggesting it could be an app but it seemed odd to me that it was preventing the phone from powering off and not just preventing it from sleeping.
Regarding the fast boot option I've just found that and it was turned on - what is this option for and why could it cause this problem then? ....
On Better Battery Stats, I usually check Partial Wakelocks - Since Unplugged. Most processes should be below 1% from what I understand. But it will depend on how long you are using a certain app. If you see a process that's been running for so long but you've just used the app related to it for a relative short period of time, then you check that particular app. Maybe the sync option is too frequent or it's just really poorly coded app.
If it appears that a valid android process is the one eating the battery, then an app is probably keeping it awake and you may need to dig a little deeper to figure out what app is causing that.
Regarding the fast boot option, all I know is that it's a feature to reboot the phone without going through the main HTC logo animation. So it's really like rebooting the phone without actually killing the background processes. (Not sure about it though maybe someone can explain this.)
Basically, with the Fastboot option the phone never REALLY turns off, it's a little bit like it's on hibernate, that's why it can boot a lot quicker, as it skips the bootloader and goes straight to booting the system.
Thanks guys. With the fast boot turned off it didn't do it last night so I'll try with fast boot turned on tonight and see what happens - try to confirm what's happening......
Many thanks for your help!
I turned fast boot on again yesterday and the fault occurred again overnight. Went from 100% battery to 55% overnight. Pictures of the stats for useage during this period are attached.
Anyone know what this alarm manager and sleep broadcast are?
Sometimes the battery works great, lasts a couple days. And sometimes, I get strange spikes where the battery drains extremely quickly (see attached images).
I have tried:
1. New device - I swapped my unit yesterday
2. Hard reset - restore all factory settings (and erase everything) off the phone
3. Battery cycle - i.e. let the battery run out entirely, recharge it from scratch
I have also tried diagnosing the issue via the stock battery app, GO Power Master, and BetterBatteryStats, but I don't see anything out of the ordinary when the battery usage spike occurs. Maybe there is some process running wild, but it doesn't seem to do anything...
Has anyone had similar issues? The only non-Google Play store app I have installed is Visual Voicemail - the apk I downloaded from this board.
You have tried everything I would normally suggest, but might have noticed something. Your sharp drop coincides with that red band on your signal bar. The red part signifying no cell tower signal. The sharp drop seems to start there. Is your phone stuck searching for cell towers when it has already re-established a signal? The earlier dip in the battery also has a red bar under it.
Also battery performance is not linear. If you are at 50% after 24 hours, you will not necessarily get another 24 hours. I am alwaysfinding myself at 50% after 18 hours and think, "Cool, I've found the right kernel" but sure enough I'm still plugging it into charge at 24 hours!
I know you say you normally get two days (which is very good) but this is all I can think of.
I use a powerful automation app called Tasker. With it you can set any phone setting to any phone condition. I've just checked, and it is possible to set a profile based on signal strength. With this you could specify a weak or no signal to do any manner of things, from play a notification sound, to turn off 3G and auto-sync. Set an exit task and it will also turn 3G and auto-sync back on when signal strength is healthy again. Might be worth a try.
Edit: If you have root access, Tasker supports the app 'Quick Boot Plus' as a plugin. With this you could set Tasker to reboot your phone if it is out of signal for more than 'x' seconds. I know it might not be very practical, but it would tell you if you we are looking at the real culprit.
Another edit: Scratch that. You could set Tasker thatif it sees no signal for 'x' seconds, turn on airplane mode, wait 'y' seconds, turn off airplane mode. No need to buy a plugin.
Thanks, wnp_79 - appreciate the thoughtful response!
Yes, that's a good point - there is a drop in battery starting with the red line for the signal. I take the subway to/from work in the morning and evening. But I don't see any problems connecting after I get outside (i.e. it doesn't seem to be searching for signal).
Perhaps next time I can try setting airplane mode on/off when I notice the battery draining quickly - and see if that helps the issue. If it does, clearly it's a signal issue.
I like the Tasker idea, I will give that a try! Thank you for the suggestion.
I wasn't by any means expecting another 24 hrs, but that drain of "50%" occured over a span of like 3 hours... with no screen usage (i.e. the phone was just sitting next to me at the desk, supposedly "idle").
Whatever you do, don't cycle your battery deeply unnecessarily.
Sent from my HTC One X using Tapatalk 2
Thanks tsleng, will keep that in mind.
I guess I am surprised other people haven't seen this issue. Maybe it's something specific to my software...
I've got this issue but it's down to my signal. At home it's fine and battery last's me well but as soon as I get to work my battery starts to dip due to Vodafone having poorer signal. Bad signal is killing my battery too bad we can't change radio's as of yet due to no S-OFF.
what happens when we can s-off? i mean what adv will we encounter regarding with the issues that we are having?
mohaimed said:
what happens when we can s-off? i mean what adv will we encounter regarding with the issues that we are having?
Click to expand...
Click to collapse
Well S-OFF, we can unlock bootloader without having to use HTCDev meaning we can revert back to stock easily and without it tampering the status. We can lock it back to it's original state.
We can flash kernels without having to use fastboot.
We can flash radios. By flashing other radios we can improve our signals if one radio is bad, an improved signal is friendlier on the battery.
I get a weird spike too but mine causes the phone to die. Also mine was done overnight when I was sleeping. (see attachment) I'm not really sure what I can do. I hope this was a one time problem...but i'm not so sure. I'm still under warnty and this is my second HOX
neocryte said:
Sometimes the battery works great, lasts a couple days. And sometimes, I get strange spikes where the battery drains extremely quickly (see attached images).
I have tried:
1. New device - I swapped my unit yesterday
2. Hard reset - restore all factory settings (and erase everything) off the phone
3. Battery cycle - i.e. let the battery run out entirely, recharge it from scratch
I have also tried diagnosing the issue via the stock battery app, GO Power Master, and BetterBatteryStats, but I don't see anything out of the ordinary when the battery usage spike occurs. Maybe there is some process running wild, but it doesn't seem to do anything...
Has anyone had similar issues? The only non-Google Play store app I have installed is Visual Voicemail - the apk I downloaded from this board.
Click to expand...
Click to collapse
You have the LTE version of the one x Maybe they can help you there:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
yap, I have two gnexs both have had this problem.
I can get a screenshot with vol-down + power
but the screen is totally black.
Yeah I've had this screen of death issue too. I've been trying forever to diagnose what is causing the problem. It happens on any kernel including stock. I factory reset, flashed stock images, everything.
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
i not have restaert using apk franco updater and set :good:
The sudden battery drop is normal when you pull out the battery. Basically, the phone loses it's calibration on the battery capacity. And that " auto charge" is your phone slowly trying to get a better estimate of your phone battery capacity.
Sent from my Galaxy Nexus using Tapatalk 2
I believe that SODs are a common problem faced by many on 4.2 i personally havn't faced it yet =] running arhd with ak kernel
I was able to reproduce this using Velis Auto Brightness https://play.google.com/store/apps/...SwxLDEsImNvbS52ZWxpcy5hdXRvLmJyaWdodG5lc3MiXQ
After messing with the brightness it wents black screen.
I'm sure this has to do with the autobrigtness!
Best regards
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
klobkelosh said:
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
Click to expand...
Click to collapse
I think you just helped me pin it on animation off. I have had the black screen happen to me 3 times in the 3 days that I disabled animations (stock rooted ROM, developer options). I kept trying to find an app that caused it but the animation off matches the start of my problem.
EDIT: Well, animation off isn't the cause since I just had another black screen.
simms22 said:
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
Click to expand...
Click to collapse
Totally agree with you!happened to me many times too,especially when crashing after tweaking\benchmarking.
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