- Nov 9, 2014
- 23
- 0
- 0
No, it shows an estimated almost 15 hours on a charge to full discharge (which you should NEVER do - always try to recharge at the 40%-60% point), which isn't bad. It also shows that you used Maps and LG Health a lot, but didn't have the screen on much.
It says that the battery is currently at 41% (which means I'd charge it in about an hour or two), and 3 hours ago it was at about 47%.
What's the problem?
I may be missing something here, but how is it possible to have the screen on, even if it were at its lowest brightness setting, for 2h 25m, and yet consume only 3% of the used charge?
Puzzled, UK.
Posted via Android Central App
I suppose this is still an early build for 5.0. Or the polish version is not fully compatible with his version of the phone? Strange.
I may be missing something here, but how is it possible to have the screen on, even if it were at its lowest brightness setting, for 2h 25m, and yet consume only 3% of the used charge?
Puzzled, UK.
Posted via Android Central App
that's what i'm talking about i'm so confused and cant understand this and btw i set the brightness @ 40%
no this is the final version of android 5 Poland version i downloded from mylgphone
There's nothing final about the first version of Lollipop. I suspect many "bugfix" releases to come in the next few weeks.![]()
I've just lost 34% of my battery charge overnight, most of it to Android OS and Android System, which I hope will cheer you up a bit. What laughs! But those two occasional battery drainers are old friends, whereas your problem seems to be a new type. Do you know any other G3 owners in your area, who might be having the same problem? We need to learn whether it's a general G3 update problem, or one unique to your device.
Posted via the Android Central App
^^^If it's Google Play Services, that app is now contributing substantially to the drain of the other two I mentioned, as I text this. Heh heh. That's in spite of wiping the Cache Partition, clearing the Cached Data in Storage, and turning off Location Reporting altogether. I think that the Play Services drain is likely to be caused by apps using location reporting, or a syncing error. But I don't know that.
Together we will beat this, Hamz.