Something is killing the battery, according to battery monitor widget pro, I'm losing around 200 mA. Looking at the partial wakelocks tab doesn't help, there isn't anything running that isn't supposed to be.
Related
Does anyone know what's up with Current Widget? It's constantly reporting very high idle-draw values that I KNOW aren't correct. It's always reporting draws of anywhere from 70-400mah. If those numbers were accurate, my phone would be dead within hours but I'm getting very good battery life so they can't be right.
Every idle drain app I've tried does this, on every rom I've tried. I've read posts where people say they're getting 2-4mah drain, so is it just MY phone that's funky or is there some other way to measure idle drain?
kabuk1 said:
Does anyone know what's up with Current Widget? It's constantly reporting very high idle-draw values that I KNOW aren't correct. It's always reporting draws of anywhere from 70-400mah. If those numbers were accurate, my phone would be dead within hours but I'm getting very good battery life so they can't be right.
Every idle drain app I've tried does this, on every rom I've tried. I've read posts where people say they're getting 2-4mah drain, so is it just MY phone that's funky or is there some other way to measure idle drain?
Click to expand...
Click to collapse
maybe you could try " battery calibration " from market and calibrate your battery... might do the trick..
and it's impossible to get 2 or 4 mah even in sleep mode on the sensation...
i use battery monitor widget and info are correct , on temperature and on Mah.. around 200 - 215 mah in standby mod..
It seems all the current draw apps are not working correctly on the Sensation at the moment.
You could estimate the idle current by noting your current battery capacity, putting the phone into sleep (screen off), and then leaving it that way (nothing waking it) for some amount of time. Then, after you have noted the time in sleep, check to see what the new capacity of the battery is.
Example:
Starting battery capacity: 1900mA/Hr
Sleep time: 1Hr
New battery capacity: 1850mA/Hr
Difference in capacity is 50mA, time is 1 Hr, so you used 50mA/Hr while in sleep. This will work out better for longer sleep times. It cant be 100% accurate since the reported capacity may not be 100% correct at any given time. (The monitor updates every minute or so)
This will, however, let you know whether or not you are seeing a reasonable current draw in sleep. It just wont be useful for knowing the EXACT value. At least you will know whether or not you are seeing low current draw or high.
Matt
I think it's got something to do with dual core. It was designed for single core.
I'm not really sure what most of the followings things are, but they are what shows up when i run betterbatterystats. For some reason my battery stats are always changing. One day I could get over a day on a full charge and others it could be 6-8 hours and mainly the same amount of use. I have noticed on the bad days that the partial wakelocks and kernel wakelocks are much higher. the problem is that I dont know what these services are and whether or not I can kill them, or even how to kill them. But here is my lists.
Phone running on full charge for 4hr39m.
Wifi on 4hr17m
Awake 1hr01m
Screen On 32min25s
Partial Wakelocks, only EmailEngineAPI is more than a min. at 10m47s
Kernel Wakelocks:
PowerManagerService 7m47s
svnet 5m27s
DPRAM 2m42s
radio-interface 2m33s
max8998-charger 1m43s
Ive read that PowerManagerService is the collection of all wakelocks so I guess that doesnt really count. I assume emailengine is just the push email (kinda sucks that its either push or never and you cant just have it auto refresh every hour or so). As for vbus, i read that that is when your phone is on the charger which makes no sense because my phone is never on a charger or connected through usb. I have a seperate wall charger that charges the batteries on its own so I never plug my phone in, when the battery dies, I just put in a fresh fully charged battery. The other wakelocks I couldnt find when I searched for them.
BTW I dropped down to 77% battery and as you can tell by my screen on time, I was only on the phone for 32m. So these damn wakelocks are stopping my phone from deep sleep (which btw is at 66% according to cpu spy) On good battery days the deep sleep is between 80-90%
If anyone knows anything about this stuff and can pass on some words of wisdom I'd appreciate it. Thanks.
Could be wifi causing the wakelock, this is a known issue with most roms, I'd try killing the wifi when you don't need it.
Either use a toggle widget or use something like juice defender.
Personally, I've got power control plus to manually kill GPS and wifi and then juice defender ultimate to automate data every couple of hours to synch apps. I've never had any wakelock issues using this setup.
CPU Spy:
1267 MHz: 8%
1075 MHz: 1%
384 MHz: 1%
245 MHz: 11%
Deep Sleep: 75%
Seems strange that you have such a large drain on some days and not others, anything stand out when the battery is draining faster (away from home for example, meaning your data will be on rather than wifi ?)
Does anyone know where I can find better battery stats apk or link for it. I've obviously been looking in the wrong threads.
http://forum.xda-developers.com/showthread.php?t=1179809
I have had quite bad battery drain issues for a while, and searched BBS dump files and forums for an answer, but the logs appear normal with no unusual wakelocks. In short, the battery consumption profile is OK but it just goes too fast. So I concluded I needed a new battery and was too cheap to buy Samsung original battery and instead got a noname type (same capacity, 1500 mAh).
But it didn't help. Still 12-16 hr standby with low use (<1 hr screen time at lowest brightness).
So I tested the health of the two batteries by draining them as fast as possible. I used the app "Battery Drain" (https://play.google.com/store/apps/details?id=com.fuzzyoneapps.BatteryDrain) and drained using full screen brigtness, wifi, bluetooth, gps, CPU but NOT the vibrate function.
The results are attached to this post. As observed, there's no big difference between the two batteries. And I don't know what to expect.
So now I'd like someone else to do the same test so that we can compare the results
Basically, just 1) Run the app with all the settings turned on except vibrate, 2) make note of battery percentage, 3) leave it for exactly one hour, and 4) check percentage again. Is ~45% per hour normal for the nexus s?
Thanks in advance
Recently my phone discharges extremely quick. It can go from 100% to 0% in less then 6 hours without any heavy usage. It is LG G5 with stock ROM (just rooted) and I have a spare battery. Both discharge so fast, so I don't think the battery is responsible for it.
Sometimes I notice that while wearing the phone in my pocket, it gets quite hot and battery went down by 20% in just a few minutes. If I look at the battery stats in system settings, it show the battery was mainly used by Android and phone stand-by.
How can I find out what was the real case of the problem? I guess because the phone is so hot, some app (or process) was causing that the CPU to work at high frequency a caused the drain. How could I identify what really is the problem? I even tried Greenify or Force Doze to eliminate the problem but with no success. How can I identify, what's wrong and what is causing the overheating and battery drain?
Thank you.
Hi Guys,
I purchased my Note 10 a month ago. Since I purchased, I am experiencing heavy battery drain at night. Almost 40-50% juice is consumed. I am keeping wifi, mobile network, blutooth and sync off.
Is there any problem with my mobile?
Thanks in advance.
Shaggy
40% standby drain is definitely abnormal, most likely due to a rogue app consuming battery in the background. Install GSam Battery Monitor, run the following adb command to enable a detailed list of battery usage:
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and see what is consuming battery in the background.
sublimaze said:
40% standby drain is definitely abnormal, most likely due to a rogue app consuming battery in the background. Install GSam Battery Monitor, run the following adb command to enable a detailed list of battery usage:
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and see what is consuming battery in the background.
Click to expand...
Click to collapse
Hi,
Thanks for help. I did found one app which was consuming battery. After disabling it, the power consumption reduced to nearly 25%. Is this normal now? I got 22 hours of battery life yesterday. Attached is the screen shot of battery drain pattern.
25% drain overnight is still way too much, and even though Google Play Services was active for 7.5 hours, it doesn't drain a lot of battery. My overnight drain is ~3%. You still have something consuming a lot of battery in the background. I don't use WhatsApp, so I don't know how much battery it typically uses. But something is definitely not right. If you can't pinpoint what is using so much battery, then do a factory reset and install GSam Battery Monitor but nothing else. Use the phone stock (without any additional apps) for a couple of days and see what your baseline battery drain is. Then install your regular apps one at a time and see how each one affects battery drain. You'll be able to identify which app is causing the problem.
sublimaze said:
25% drain overnight is still way too much, and even though Google Play Services was active for 7.5 hours, it doesn't drain a lot of battery. My overnight drain is ~3%. You still have something consuming a lot of battery in the background. I don't use WhatsApp, so I don't know how much battery it typically uses. But something is definitely not right. If you can't pinpoint what is using so much battery, then do a factory reset and install GSam Battery Monitor but nothing else. Use the phone stock (without any additional apps) for a couple of days and see what your baseline battery drain is. Then install your regular apps one at a time and see how each one affects battery drain. You'll be able to identify which app is causing the problem.
Click to expand...
Click to collapse
Hi Sublimaze,
I found some more apps which were running in background for no reason. Now the battery drain at night is near to 5% only. I can blame fluctuating network signal in my area for this.
Thanks,
Shaggy