I'm on 6:24 SoT with 25% battery remaining.
Sent from my LG-H870 using Tapatalk
Sent from my LG-H870 using Tapatalk
Standby drain
- Thread starter XDA_RealLifeReview
- Start date
But Android Nougat has already got Doze so what is the need from a third party app?
Sent from my LG-H870DS using XDA-Developers Legacy app
Sent from my LG-H870DS using XDA-Developers Legacy app
Right, but it's called "aggressive doze" it kicks in once the screen is off rather than after 30 minutes of inactivity
Sent from my LG-H872 using Tapatalk
How much do you estimate it gained you battery over a day please?
Sent from my LG-H870DS using XDA-Developers Legacy app
Sent from my LG-H870DS using XDA-Developers Legacy app
Depends on your usage. If you look every 15 Minutes on your Display you will never go into deep doze.
Aggressive Mode makes sense for me.
If i remember right, it doesn't work when you move or hold it in your hands.
For those having issues with battery drain, are you on the stock launcher? I went from 3-4% (or even more) per hour down to less than 1 when I switched to Nova.
I still have issues with the phone sometimes randomly sucks up 5% in 10 minutes though... I think it's whenever I wake the phone up, so it might be some doze/wakelock thing.
I still have issues with the phone sometimes randomly sucks up 5% in 10 minutes though... I think it's whenever I wake the phone up, so it might be some doze/wakelock thing.
on Nova, debloated a bunch of non-essential LG apps, and stuff by Google that i'll never use (Slides). accidentally tested drain last night when i left my G6 in the car from 6pm to noon. about 18hrs. went from 75% when i left it to 50% when i picked it up, with AOD, BT, WiFi, data, etc. off.
G6 lost 25% charge over 18 hours while doing nothing -- i dunno, i think that's BRUTAL, esp coming from an Xperia Z3c and Sony's Stamina Mode.
There is a problem.
Check for location settings and other things. Should be between 0 to 3%.
Sent from my LG-H870DS using XDA-Developers Legacy app
Used to use greenify or forcedoze, but deleted both of them and achieving pretty good standby time. With force doze i would usually get around 0.7 or 1.0/hr. Now im getting 0.3/hr without them
Attachments
i think the massive drop might have been because the phone was in my car, which was parked on level two of an underground parkade, so maybe the phone was struggling to find the network. last night in my loft (5th floor), only drained 2% ... thank goodness
My SoT is currently at 6:18 which is great, with 10% left in the tank and 62 odd hours since last charge. I'm very chuffed with the G6 thus far on many fronts.
Sent from my LG-H870 using Tapatalk
Sent from my LG-H870 using Tapatalk
Good stuffMy SoT is currently at 6:18 which is great, with 10% left in the tank and 62 odd hours since last charge. I'm very chuffed with the G6 thus far on many fronts.
Sent from my LG-H870 using Tapatalk
Sent from my LG-H872 using Tapatalk
After many moons of trying to pinpoint the cause of my painfully quick standby drain (~2h SOT) I've finally found the culprit. I wasn't able to solve the problem yet though, just avoid it... Perhaps someone here can help.
It turns out my phone never really goes into deep sleep while I'm at work which, unfortunately, is most of the day. I study and live on an university campus that has a WPA2-Enterprise network (TTLS, PAP) on both my workplace and the dorm. While I'm at home the phone goes into deep sleep almost immediately (I have Greenify's aggressive doze enabled), whether I'm there overnight or just for a quick snack. However, while I'm at work the phone insists on being active with the screen off. One can actually clearly see when and for how long I was at work just by looking at my battery consumption graph, it looks like a staircase.
I have a rooted US997 so I was able to dig a bit further into this. I found out, thanks to BatterBatteryStats, that the culprit is a kernel wakelock by the name "wlan_rx_wake". I had never heard about it before and so I've been reading a lot about it since finding out it was the reason behind my drain. It appears to be have been a fairly common problem on some android phones for a while now, but I don't think nobody really knows how to solve it. The most common solution is to change routers and/or internet settings, which is not going to happen in my case. Another quite efficient fix seems to be the use of a custom kernel... Yeah, also not going to happen, at least not for a while. Some people partially solved the problem by ditching DHCP for a static IP and disabling IPv6, which I've tried without any effect, as well as connecting to 2.4 GHz networks only, an option which unfortunately has been disabled on android for a while now. Finally, some people found that they had some sort of app running on a different device on their network that was sending packets all over.
This is where it gets tricky, for I know nothing about networking. I installed several packet sniffers and found out that my phone is being bombarded with packets or icmp echo requests (ping) all the time. The only difference is that instead of having like Dropbox running on my desktop sending packets to my devices at home, I have hundreds of unknown devices going crazy shooting packets all over the building. I'm pretty sure this doesn't happen with any of my other android devices, so I assume the G6's kernel should just be ignoring all these requests instead of keeping awake. I've installed a firewall (AFwall+) and tried to run some custom iptables scripts. Keep in mind though, that I know very little about this. First I tried to block a few specific IPs that I saw on the sniffers were sending me packages, but every time I blocked those few I immediately got packets from a few new ones. Also, there's a chance those devices don't even have static IPs, so this method would end up being useless anyway. I then tried to block and/or ignore all incoming icmp echo request with a handful of different scripts, but I just ended up loosing all internet access (probably my bad). Given that at the dorm none of this happens, probably because there aren't that many devices, if any, sending packets, I assumed the problem was with the LAN. I therefore disabled all app's LAN access on AFWall+, but it also din't make any difference... Which makes sense because my phone is not sending packets on it's own, just responding. Also, it's a kernel wakelock, so no specific app is causing it.
All in all, the only "fix" I've found so far is to either connect to a guest-net or use mobile data while I'm at work... Or just skip work altogether, haha. However, if any of you guys are having fast draining exclusively when connected to a specific wireless network you might just have to disconnect your wireless printer or something!
I'm enrolled in LG's developer program so I think I'll drop those guys a line. I was half afraid I'd make a fool of myself for not seeing something obvious though, so I thought I run this through you guys first.
Btw: Long time reader, first time commenter. Go easy on me!
It turns out my phone never really goes into deep sleep while I'm at work which, unfortunately, is most of the day. I study and live on an university campus that has a WPA2-Enterprise network (TTLS, PAP) on both my workplace and the dorm. While I'm at home the phone goes into deep sleep almost immediately (I have Greenify's aggressive doze enabled), whether I'm there overnight or just for a quick snack. However, while I'm at work the phone insists on being active with the screen off. One can actually clearly see when and for how long I was at work just by looking at my battery consumption graph, it looks like a staircase.
I have a rooted US997 so I was able to dig a bit further into this. I found out, thanks to BatterBatteryStats, that the culprit is a kernel wakelock by the name "wlan_rx_wake". I had never heard about it before and so I've been reading a lot about it since finding out it was the reason behind my drain. It appears to be have been a fairly common problem on some android phones for a while now, but I don't think nobody really knows how to solve it. The most common solution is to change routers and/or internet settings, which is not going to happen in my case. Another quite efficient fix seems to be the use of a custom kernel... Yeah, also not going to happen, at least not for a while. Some people partially solved the problem by ditching DHCP for a static IP and disabling IPv6, which I've tried without any effect, as well as connecting to 2.4 GHz networks only, an option which unfortunately has been disabled on android for a while now. Finally, some people found that they had some sort of app running on a different device on their network that was sending packets all over.
This is where it gets tricky, for I know nothing about networking. I installed several packet sniffers and found out that my phone is being bombarded with packets or icmp echo requests (ping) all the time. The only difference is that instead of having like Dropbox running on my desktop sending packets to my devices at home, I have hundreds of unknown devices going crazy shooting packets all over the building. I'm pretty sure this doesn't happen with any of my other android devices, so I assume the G6's kernel should just be ignoring all these requests instead of keeping awake. I've installed a firewall (AFwall+) and tried to run some custom iptables scripts. Keep in mind though, that I know very little about this. First I tried to block a few specific IPs that I saw on the sniffers were sending me packages, but every time I blocked those few I immediately got packets from a few new ones. Also, there's a chance those devices don't even have static IPs, so this method would end up being useless anyway. I then tried to block and/or ignore all incoming icmp echo request with a handful of different scripts, but I just ended up loosing all internet access (probably my bad). Given that at the dorm none of this happens, probably because there aren't that many devices, if any, sending packets, I assumed the problem was with the LAN. I therefore disabled all app's LAN access on AFWall+, but it also din't make any difference... Which makes sense because my phone is not sending packets on it's own, just responding. Also, it's a kernel wakelock, so no specific app is causing it.
All in all, the only "fix" I've found so far is to either connect to a guest-net or use mobile data while I'm at work... Or just skip work altogether, haha. However, if any of you guys are having fast draining exclusively when connected to a specific wireless network you might just have to disconnect your wireless printer or something!
I'm enrolled in LG's developer program so I think I'll drop those guys a line. I was half afraid I'd make a fool of myself for not seeing something obvious though, so I thought I run this through you guys first.
Btw: Long time reader, first time commenter. Go easy on me!
Don't know if this could support your theory but i noticed that under wifi there is always something that downloads data (almost 300 bytes/s) and rarely the number goes to zero as it should.
The problem is that under wifi bettery life is better in standby, when using mobile data there is some problem with switching that force the phone to go 3G/H+ even if LTE/4G has a better signal, in fact if i force LTE Only the battery drain is less, seriously, don't know why, was the same on my G5.
Hope to be of some help, i have a rooted H870 if needed other infos or testing =)
I also had the wakelock problem at my university with my old phone. Also a few friends had the same problem. This is not LG G6 specific. This is an android bug!
I am again at the university in october. Then I can test it with the G6.
I am again at the university in october. Then I can test it with the G6.
I have another problem: com.android.phone alarm wakes up the phone by 12.5 times per minute (4221 times in 5h30m), while I'm in the same place under 4G+ network. I tried in the past disabling fast dormancy but it didn't look as it solved anything.
Thanks! I think my problem is pretty much hopeless for now... At least until someone fixes it with a custom kernel, which is way beyond my skill. But some people here might be able to work around it, if they are in control of the network causing the problem that is.
I'm not sure if the packets I suspect are causing my problem actually have any data in them, they' should be just icmp echo requests... But 300 byte/s does sound reasonable to me. I haven't actually tested using data-only, not at work at least. The phone does display the 4G LTE icon as soon as any of my WiFi networks is not in range, but I guess I'd have to test the speeds to be really sure the phone is not in fact just using 3G. I've checked with BBS and, using data-only, the wakelock is no longer a problem. However, I haven't really compared long term battery life between my problematic network and 4G LTE. I guess there's a chance the latter will be even worse, ugh. I haven't done it because I stream quite a bit of music and really don't want to do it over data. I'll download a few albums over WiFi and test a full day using data only. I have a feeling it'll be better than when connected to this specific network. I appreciate your offer to test! At this point I can't think of a lot though... If you haven't yet, you might want to install tPacketCapture and look at the results in WireShark in a computer, it might tell you what exactly those 300 byte/s are.
I guess this is indeed an old android bug that affects most android running devices. Fortunately though, this bug appears to be fixable with custom kernels and all my previous and current devices have/had one of those. I also guess that I've just inadvertently solved the problem that way without even realizing it. I remember that my Nexus 5 had great battery life at work and I've recently read that Franco Kernel, which it was running, has had a fix for this bug for a while now. What troubles me is that in my dorm I have exactly the same network, with the same security settings and dynamic IP, and my battery life is impressive. I stayed home Friday night and all Saturday and my battery went from 100% to 80-90%, I was at work all day Sunday and it went from the same 80-90% to 0%. I still agree this an android bug, but it appears to be specific to some local networks. I also considered that the phone could just be constantly switching routers at work for some reason, but in the dorm there are also quite a few of them... And this problem also does't happen with the guest-net, which I presume uses the same many routers. Anyway, it'd be really nice if you could update us on this by October.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone