I've had my G2X close to a month now and the battery life hasn't been very good. After using the LG update tool to go to 2.3.3 I noticed Tasker was using 25% of the battery, about the same as cell standby and phone idle. I installed CM7, nightly 99 and noticed the same behavior. I never noticed Tasker using much on my Nexus One, so I started looking through the battery history and noticed the sensor usage stat being really high for Tasker. I turned off the one profile I had that would have been causing sensor usage and didn't notice a drop until I rebooted.
I noticed the same behavior out of the Camera app and Dialer. Today I saw the same behavior out of the Kindle app. Anyway I tried to do a little more scientific experiment and opened Google Sky Map and let it load used it a few seconds and got out of it. I put the phone to sleep and let it sit for 30 minutes, I came back and checked and the sensor usage of Sky Map was 15 minutes. I then opened a task killer and stopped Sky Map and put the phone to sleep for another 10 minutes and saw the sensor usage was now at 20 minutes. Anyway it seems after any app uses the sensors, it continues to use them until I reboot. Has anyone else noticed this behavior? Is there a known way to fix it?
Update: I noticed this only happens when auto rotate is turned on in display properties. I just did a quick test where I had auto rotate turned on, I started the Kindle app. When I exited, I noticed the sensor usage was still climbing. I turned auto rotate off, then started Google Sky Map, when I exited it, the sensor usage stopped climbing. However, the sensor usage kept climbing for Kindle. If I turn auto rotate completely off, the sensor usage doesn't increase after the app exits. Very strange, but I have a work around.
Update 2: The same behavior happens on my nexus one, I just never noticed because I keep auto rotate off most of the time. I guess its an android issue rather than something with the G2X
Hi all, after updating to Android L (5.0 and 5.0.1) I've noticed that the ambient and proximity sensor will stop working after a certain amount of time. The time appears to be random at the moment. It started off with the adaptive brightness not working correctly, it would always be near max brightness in the dark and minimum in bright light, and at some points it would just stop changing altogether. So I decided to get lux autobrightness, it works better than adaptive brightness in L, but it would also stop adjusting itself after awhile.
Then I noticed that sometimes during a phone call, the phone's screen will not turn off so at the moment I decided to check the sensor's value with an app when the auto brightness/proximity wasn't working anymore. Turns out that the sensors are all registering 0 values or not changing it's readings despite being in different light conditions.
A reboot fixes this but, it's really annoying having to reboot the phone once a day.
Anyone else experiencing this?
EDIT: nvm, found out that other people are experiencing this as well. Haven't been on xda for awhile and forgot how to use the search button
I've searched all day for this, but haven't found anything.
Frequently, I have the camera zoomed and tweaked the way I want, just waiting for some action shots...and two minutes later, the camera app returns to the home screen. If I'm actively using the camera it will stay on, but after two minutes of inactivity, it returns to the home screen. Then I have to re-open the camera app and reset all my settings, focus, and zoom. It's a giant pain.
Changing the Settings > Screen Timeout option doesn't do anything, as the screen isn't actually timing out - it's just closing the camera app and bringing me home.
Does anyone know of a mod, hack, or some edit I can make to increase the length of time before the camera timeout? I know extending keeping the camera active longer will put a bigger dent in my battery life, but that isn't a concern when I'm trying to take great pics.
I have a Verizon Galaxy S6 Edge, rooted, stock, running Android 5.0.2
Thank you in advance
*bump*
bump
hi
i have a new (3 months old) unrooted nexus 5 update to latest OS version which is showing some very odd stats wrt battery consumption.
first i had heavy battery drain but then i disabled the scanning options in the location menu which helped. but still even with brightness at only 18%, battery saver on 95% of the time, location & mobile data off all the time & wifi only used for short bursts it still seems to drain quite quickly.
app usage stats as reported by the inbuilt battery stats option differs quite a bit from other battery management apps (du battery saver, battery doctor, gsam battery monitor)
for eg. inbuilt battery stats doesnt even show wifi consumption in the stats even if i use it for few hours (then suddenly one time it showed up with some excessive consumption stats - 1500mah for 2 hours usage; photos attached). very often it shows gravity screen app as the biggest consumer of battery while other apps show gravity screen as consuming very little power. otoh gsam shows battery doctor as consuming the most of all the apps.
what could be the issue?
gsam shows average battery life with screen on as 3h 42m. is that ok?
was also wondering if the optimization options of the battery management apps work or are they gimmicks? for eg both du battery saver & battery doctor show 'x' number of apps consuming power in background & when you press the optimise/close apps button it shows some cool effects of shutting down those apps but you come back after a few hours & the same apps show up in the running in background.
also, the front camera is very grainy. cant believe its that bad in what was a flagship phone. is it just my phone or is that the how it is for other users?
anyone with any inputs?
You got nearly 5 days on a single charge??? Yes, your battery consumption is fine. Nearly 4 hours of SOT is fantastic.
The graininess of the camera will depend a lot on the lighting. Unless you have a light shining directly on your face, the picture is probably pretty dark. That said, it's "only" like a 3MP camera. It's well known as a sub-standard front camera (I'm not a selfie machine so I don't really care). When you think about how microscopic the light sensor is on the front camera, it's no wonder the picture is grainy.
exninja said:
You got nearly 5 days on a single charge??? Yes, your battery consumption is fine. Nearly 4 hours of SOT is fantastic.
The graininess of the camera will depend a lot on the lighting. Unless you have a light shining directly on your face, the picture is probably pretty dark. That said, it's "only" like a 3MP camera. It's well known as a sub-standard front camera (I'm not a selfie machine so I don't really care). When you think about how microscopic the light sensor is on the front camera, it's no wonder the picture is grainy.
Click to expand...
Click to collapse
thanks for your reply exninja
that 5 days was a one time thing where i barely touched the phone & then only to test it. i wish it were that good LOL. normally i get about 2 days with very conservative usage (brightness at only 18%, battery saver on 95% of the time, location & mobile data off all the time & wifi only used for short bursts, 0 talktime)
is 4 hrs SOT that good? i see a lot of people getting 5 to 6 hours + & that too without those conservative usage patterns.
the thing that got me worried is the strange battery usage stats reported in the stock settings.
Honestly I wouldn't worry that much about what each app says is using energy. They're each consuming very little anyways. I'm not familiar with gravity screen so I wouldn't know about it.
I haven't heard of many people getting 5-6 hours of sot, especially since lollipop. I got 4 hours on KitKat, then dropped to 3 or less on lollipop. Now it's usually around 2 hours.
@fguy76
First of all, just to let you know, recently Google Play Services have been acting up. Sometimes I get normal battery drain overnight when I sleep, and sometimes it drains like crazy. For now, there is nothing we can do about Google Play Services.
However, if u noticed that WiFi has been turned on the whole time via the battery history chart, despite the fact that you did not even turn on WiFi at all during that period, then this can only mean one thing. You must have enabled WiFi Scanning (the famous Scanning always available bug in Lollipop & KitKat).
To disable WiFi Scanning, go to Settings first. Then on the top of settings, there is a search bar. Type in "Scanning".
Then u will see the following options. Make sure u disable WiFi Scanning.
Having said this, there is another annoying bug. This bug is when you have left a WiFi hotspot and forgotten to turn of WiFi. So after awhile u realised it and u proceed to turn off WiFi. But hours later, u check your battery stat, and it still shows your WiFi have been active the whole time despite turning it off. For this, the only workaround is to reboot the phone. To avoid this bug, always turn off WiFi b4 u leave the WiFi hotspot area.
@pcphobic i have wifi scanning off & i always remember to turn wifi off when not using it so that second scenario is not an issue with me
fguy76 said:
@pcphobic i have wifi scanning off & i always remember to turn wifi off when not using it so that second scenario is not an issue with me
Click to expand...
Click to collapse
@fguy76
The other solution that I can offer is under Location settings, go to Google Location History and make sure it is turned off.
You can still use GPS based apps with Google Location History turned off.
I suspect that if u find intermittent wifi showing up in your battery history, it could only mean that Google Location History is periodically waking up and using wifi to get an approximate location. I used to get this until I turned off Google Location History.
With all power saving modes disabled brightness reduces when you open browser and several other apps. Unless brightness is very low or very high. Really annoying when you're outdoors and suddenly can't see anything
If you use power saving mode, it reduces brightness all the time but when you restart phone brightness is normal again
Only happened after enabling power save mode for first time so 100 percent a bug. Still present in latest Chinese developer Rom so not going to be fixed any time soon.
How can such an obvious bug exist in the first place let alone be around for over 6 months