Database Info

Battery with System Panel

I went to sleep around 11:30 last night. Before I went to bed I turned off mobile completely and had 94%. When I woke up at 7:45 I had 64%. Take a look at these screenshots and tell me how I can improve my battery. As you can see in the second screenshot I didn't use my phone at all but look at the drastic decrease.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ADR6400L using XDA App

That's odd for sure. Did you check the system's battery stats? Just seems like the app you're using isn't telling the whole story.
BTW, what app is that?
Sent from my ADR6400L using Tapatalk

System Panel
Sent from my ADR6400L using XDA App

Anyone know what I could do to fix this?
Sent from my ADR6400L using XDA App

First thing I'd target is system panel itself...an app that polls your phone for system statistics...yeah...

Was this a one time thing, or does it happen every night? Did you check the system's battery info, as suggested above? Are you running a custom kernel/ROM? Did you see CPU spikes in System Panel during that period? Was wifi on?
I frankly have no idea what your problem could be, but a little more info might help.

Carnage9270 said:
First thing I'd target is system panel itself...an app that polls your phone for system statistics...yeah...
Click to expand...
Click to collapse
system panel is superb, it uses barely any cpu at all.
anyway to the OP, i do the same test every night, i leave my phone idle, then check system panel in the morning. i drop 6% in 7 hours, but yours definitely dropped a lot. obviously no app or process is showing up, so i would just reboot and try another test tonight. perhaps some glitch happened, radio was wacky, i dont know. but that's not normal.
however we do know that the stock ROM has a high current draw at idle, around 34mA, when other phones get 4mA during idle. so who knows maybe it's normal.
i wish i had some screen shots of my system panel figures to show you.

I've noticed abnormal battery usage with low phone signal as well. Think the phones (Inc and Thunderbolt) ramp up voltage trying to amplify a low signal.
But i notice that you have a graph for 8 hours but the usage report is showing you only 2 mins. Dont think it's giving you an accurate usage report while charging. Depending on what you having it charging on it's possible to drain more charge than your receiving. Especially with USB computer charging.

Carnage9270 said:
First thing I'd target is system panel itself...an app that polls your phone for system statistics...yeah...
Click to expand...
Click to collapse
Linux is actually keeping the statistics, the app just scans /proc and other directories at intervals to log it over time. Intervals are 15 minutes-ish on battery, our target spec is <1 min of CPU consumption per day to perform this service. (Am the author)
Unfortunately SystemPanel also isn't finding the specific culprit in this case, i.e., it's only showing that app CPU usage isn't the problem. Best guess in such scenarios is either some app that is running in the background preventing the phone from going into its best low power state or is using a bunch of power running one of the radios. I'd next try doing the same thing in airplane mode.
Will be adding more data logging for additional such as network bandwidth in future versions.

Carnage9270 said:
I've noticed abnormal battery usage with low phone signal as well. Think the phones (Inc and Thunderbolt) ramp up voltage trying to amplify a low signal.
But i notice that you have a graph for 8 hours but the usage report is showing you only 2 mins. Dont think it's giving you an accurate usage report while charging. Depending on what you having it charging on it's possible to drain more charge than your receiving. Especially with USB computer charging.
Click to expand...
Click to collapse
What the usage report is saying is that in those 8 hours his System Processes only used the CPU for about 2 minutes. That would lead me to believe that there is something running in the back ground that System Monitor is not picking up. I would suggest doing what the Dev above me said and see if that might help figure out what process that is.

ska.t73 said:
What the usage report is saying is that in those 8 hours his System Processes only used the CPU for about 2 minutes. That would lead me to believe that there is something running in the back ground that System Monitor is not picking up. I would suggest doing what the Dev above me said and see if that might help figure out what process that is.
Click to expand...
Click to collapse
i believe system panel uses linux commands such as "top" which picks up everything that hits the CPU. so the offending battery drainer is something else, such as the radio for example going wacky, etc. i admit the OP's usage seems strange as i do the same test every night with system panel, but when something weird does happen, the ofending app clearly shows up in system panel.
the next step is taking logs with the current widget and seeing how high idle current draw is. i get around 5mA to 10mA idle current draw.

[HELP] Battery Use App has gone mad!?!

Hi folks!
I tried to search the topic before starting a new thread but I couldn't find any.
So, here's my problem. I noticed that since I flashed the stock JQ1 Gingerbread from chainfire's thread apart from everything else being fantastic, the battery use statistics in Settings -> Status -> Battery Use I can see are stranger and stranger.
First I have noticed that my the battery usage of Display had frozen to 2%. It is completely impossible, comparing it to the Froyo before, where it often went beyond 50 or even 60% of total battery usage.
Then, I saw that the Android System was taking about 90% of the stats. At first I thought it may be the infamous Gingerbread battery drain. It is not that, however, because I do not feel the battery draining any faster than before.
Then came the realization that no matter what application I am running, it does not get reflected in the Battery Use - only Android System percentage grows bigger. The funny part is that from time to time the total of all percentage goes beyond 100%
And, finally, today I unchecked the background update of the PULSE application, because I do not really use it and checking the Battery Use again what did I see. See attachment:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not only the display category had gone away totally, but half of the battery usage is now transferred to PULSE, which I don't use.
Please, do you have any ideas how to repair that?
I am on a European Galaxy Tab, JQ1 2.3.3 Android + CF-Root v3.3 for JQ1

Not anyone experiencing the same problem? Just a little update from me. I read half the cloud already, strange but it is the first time that I cannot really find my topic in Google.
I tried what not - no result. I wiped battery stats, which only helped to the extent that the PULSE has gone from battery use stats, and display is back but the readings are stuck at 2% no matter how much I am actually using the display.
I read somewhere that it could be the kernel, where some thing may have not been allowed or switched on??? But if that was the case I would not be the only one with the same problem, but all the people that have flashed the ROM + CF Root 3.3 from chainfire's thread????
Still no ideas?

Hey guy,
Once ago I had the same problem. I don't think that pulse realy eats your battery. But we all know that the battery statistics is incorrect. So don't worry. Do use "AntTek App Manager ☆ root" (its free) to remove the puls app and wipe the cach. Or just install the overcome rom. It's much better then the Sock Rom. Trust me Because after removing of puls, there are other false statuses. I don't remember but i think it will show you that the battery is eaten by the core apps for more then 70%.
Sorry guy... I know about my terrible english

Hey odysseus84,
don't worry about your English. I am glad that you tried to be helpful. It is not that bad. After all I understood what you mean. You are right, even without Pulse in battery stats, I am still missing statistics for practically everything.
It is interesting that the Battery Use fails to record third party apps. As you can see below, the usage for all main system processes like Idle, Standby, Bluetooth, Wi-fi, Voice Calls are there. The statistics for display usage is stuck at 2% as already mentioned, which is the most annoying part.
Another interesting thing is that everything seems to be put into Android System usage, because normally it wouldn't get more than 10% of the overall battery usage share.
May I ask for other people running Gingerbread 2.3.3 to post their battery stats here?

Look. It's just a Bug. There is "Android System"written but it means the % of the Display. There is "Display" written but it means something else. As you can see on the attached pic we have almost the same "Display" usage.
And the other thing is that the statistics nothing shows with less then 2% usage.
Finally you can just accept it or flash something else.

odysseus84 said:
Finally you can just accept it or flash something else.
Click to expand...
Click to collapse
I really liked that last sentence. It really seems that I am going to just accept things or flash the OVERCOME. From what I read the dev team have done a great job! Thanks.

Testing voltage control with benchmark apps?

I'll start by saying this isn't about posting highest bm results. I'm just trying to find best results in statistical form for my daily driver. But i'm not sure if this is a good practice or not. I'm running Basic with a twist, kg4 modem, and Antonx barebone. I go into voltage control, change a setting(io scheduler, and overclock) then run a bm test, take a screenshot. I did this 8 times, and picked the setting with the best results(which I found to be noop, smartassv2, 200/1300, -25} Other than battery life, would you say this is a good way of doing it? Or am I completely off base? Phone feels great, and battery lasts all day BTW, but just looking for some insight. Thanks!
Sent from my SGH-T959V using xda app-developers app

I think you're on the right track.
There are sort of two things to consider, as I see it, past "the phone is responsive enough for my needs"
Deep sleep time when not "in use"
Drain when in use and screen on
The first of those is probably best examined by using Better Battery Stats religiously. Probably half the nights of the week I charge my phone fully before going to bed, pull the charger, and turn off the screen. Then just leave it there. No checking your stock prices at 4 A.M. When I wake up, I immediately open Better Battery Stats and save a report (make sure you have configured it ahead of time to include everything on the list). If you're seeing more than 5-10% of time time that your phone isn't in deep sleep on CM9 or AOKP, your drain "problems" are more likely your apps or settings than the ROM.
Given that I am seeing on the order of 1% per hour average battery drain (~20 mA average over an hour) and that it comes in spurts (my email wakes the phone for 5 seconds, it goes back to sleep, my Twitter app wakes the phone for 5 seconds,...) I think you would be hard pressed to measure the current with a meter that most had access to.
Wake time, in my opinion, is dominated by screen current (hence why I wracked my brain on the auto-brightness issue and agonize over adding another step in the brightness curve that would consume more current, even if it is easier to read) and, for some users, CPU/GPU. The Android screen that shows battery usage by app is probably pretty good for this to a first order, but as far as app by app, I don't believe it (there is nothing in the device that actually measures current draw other than total from the charger cord), and certainly not for app-by-app decisions.
I think the idea of a "benchmark" of your everyday apps the way you use your phone is a good one. When I was tuning Hefe kernel I tried to use my phone the way I generally did everyday, then collected data over several days at each setting change. You're on the right track about taking several data points to try to smooth out "normal" variation.
There have been other attempts to measure power consumption, but I have some serious doubts about the methodology. For example dBm is a power measurement and requires a known impedance, which the phone certainly is not. The mentions of "logarithmic scale" support that the wrong measurement was made (mA is a linear scale on an analog meter). As a result, I find the results "interesting," but I wouldn't bank on any of them to guide decisions.
Edit -- For example, the post referenced in the previous paragraph suggests that undervolting can only have a 2% effect. However, power required to charge a capacitor goes like the square of voltage (IC "gates" look a lot like capacitors when they are working), and this quadratic behavior can be easily confirmed elsewhere. Undervolting by 5% (60 mV on 1200 mV) would then be roughly a 10% gain; undervolting by 10%, if your phone could take it, roughly a 20% gain.

Talking with Raver on irc a while back he said overclocking past 1.2 will end up hurting battery life. Im not sure if that applies to gb roms or just the ics flavors tho. But it is something to consider when using oc/uv settings. I never go past 1.2 and my voltages are -50 from top to bottom. I average 12-14 hours depending on how many phone calls I have to make.

eollie said:
Talking with Raver on irc a while back he said overclocking past 1.2 will end up hurting battery life. Im not sure if that applies to gb roms or just the ics flavors tho. But it is something to consider when using oc/uv settings. I never go past 1.2 and my voltages are -50 from top to bottom. I average 12-14 hours depending on how many phone calls I have to make.
Click to expand...
Click to collapse
This is specific to the DVFS based cpufreq.
The aries kernel and the blastoff v3 (to be released... soon) use standard (non-DVFS) cpufreq.
We will see different OC/UV results with these kernels.

I'd also add that no matter how it is done, overclocking any amount will pretty likely increase CPU power consumption.

(make sure you have configured it ahead of time to include everything on the list).
Ok,
This is extremely helpful and very interesting. Thanks Jeffsf! (and Eollie and Bhundven)
I just downloaded BBS off of Play store. I'm attempting to set up and include everything on the list, but it's only letting me select one at a time ( Other, kernel wakelock, partial wakelock,alarms etc. etc.) Is this what you're referring to? I was reading through BBS devs O.P., maybe I'm missing the first time setup instructions. But I see the "getting started", and "how to" but nothing on how to select all. However "Other=Group of different indicators about what is consuming the battery. This statistic should always be checked first as it gives a good idea about the draining profile". <This quote makes me think each has to ran seperately.... True?
Thanks

They all "run" even if you don't have them selected. I looked and the current settings for what goes into the dump file are from the ICS-style settings icon near the top right, then scroll down to Dumpfile and click it. Select everything on the next screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One of the great things about BBS is that it primarily uses stats the kernel already collects, so it doesn't interfere much, much, if any, with what the phone would otherwise do.
Posted from my SGS4G, thanks to Team Acid development

I started my first step last night. The results are not terrible, but there is certainly some room for improvement. I was surprised to find the top culprit under wakelock is *backup* Android system= 6min. 44s ( second entry is only 11s., huge jump). Seems the consensus online is go to Settings>Privacy>Backup data, and uncheck. I started to do this, but when I unchecked the backup, I got a message saying something like "are you sure you want to do this? You're gonna F up your phone" So I am holding off for a minute. 2nd highest wakelock is Alarm manager (which I'm stil looking into) at 11s., and 3rd is GTALK_ASYNC_Conn at 7sec. Which I believe I may have fixed by Super Manager>APK startup>Google framework g-talk>disable startup..... we'll see at next run.
The how to guide on BBS says if Power Manager is not the top entry under Kernel Wakelocks, then check Network stats. I actually have 4 entries above that. Starting with SVnet at 5min 58s. I'm thinking this may be email check frequency, but there is nothing listed under Network on my dump file.
Radio interface 3min 54s
mmc_delayed_work 2min 32s
Anyways, I'm still looking into all of this, and going to attack little by little each day. But I figured I'd share, and maybe get some insight.
Thanks all!

Sounds like you're on your way to at least understanding your phone a lot better than most. It's well worth the time, at least in my personal experience. I went from not being able to make it through the day on GB, to getting a day's run time without a sweat in ICS.
I believe you're right that svnet is the radio (the "phone" one, as compared to the "WiFi" one).
mmc_delayed_work, from staring at kernel code, appears to be part of the "normal" in the process of writing to disk. I haven't gone much further than that, but I am guessing it is a periodic "flush" of queued write requests.

Z3 D6603 - Battery life is not good

Hello,
So recently i've noticed the Battery performance on my Sony Xperia Z3 has become poor, I mainly use my device for socialising etc, I don't game alot. I'm currently Running Android 4.4 Kitkat (UK)
(I'm usually at home and connected to Wi-Fi)
See the results for yourself:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hussain_Salam said:
Hello,
So recently i've noticed the Battery performance on my Sony Xperia Z3 has become poor, I mainly use my device for socialising etc, I don't game alot. I'm currently Running Android 4.4 Kitkat (UK)
(I'm usually at home and connected to Wi-Fi)
See the results for yourself:
Click to expand...
Click to collapse
Check if the device is constantly awake at the detailed battery information if you click on the graph.
If that's the case, search xda for "wakelock" and how to get rid of it.
An easier attempt is, to think if it's a certain app you installed recently or a change you made to your system.

Aronuser said:
Check if the device is constantly awake at the detailed battery information if you click on the graph.
If that's the case, search xda for "wakelock" and how to get rid of it.
An easier attempt is, to think if it's a certain app you installed recently or a change you made to your system.
Click to expand...
Click to collapse
Thank you for your response,
I'll Go ahead and download a Wakelock Detector By someone who works here at XDA, and i'll see if it finds anything; But as of now my battery died again; So i left it dead for 15 minutes, and now i'm charging it back to 100% with no interruptions

Hussain_Salam said:
Thank you for your response,
I'll Go ahead and download a Wakelock Detector By someone who works here at XDA, and i'll see if it finds anything; But as of now my battery died again; So i left it dead for 15 minutes, and now i'm charging it back to 100% with no interruptions
Click to expand...
Click to collapse
You could also install the ota update for lollipop and see if that automatically solves your issue. (new versions are being created to be better)
Another option is to flash the lollipop stock rom and try if that solves it. (but that's a bit more advance)

I suddenly got a similar issue - not as bad as yours but a drop in battery life. I turned off scanning even when wifi is off and turned on location based wifi and my battery life went back to normal. I'd just had a Google Play Services update and have had this issue with various play services updates in the past on other devices which is why that was one of the first solutions I tried.
Might be worth a shot if you haven't already tried it :good:

There's always Greenify.

Repair it or flash another ftf file.

Same thing here. Since I've had this when I purchased it new I've not had any good battery life. My old z2 had way better battery life and stamina mode works.
Sent from my D6603 using Tapatalk 2

Was there any update to this matter, OP?
What brightness options are you using? (% and adaptive or not?)
Also, did you actually update it to Lollipop? Was there any problem with wakelock?
Best regards.

Network & Wake Lock
The last screenshot you posted clearly shows that the battery drain is because of your Mobile Network and a Wake Lock.
Network Signal:
As signal strength decreases, the device requires additional power resulting in battery drain.
The cost of 1 hour’s worth of calls is 150mA, assuming a strong signal
So, on a 2000mA battery, it takes 8% of total capacity (8% =150 / 2000)
This means the same 1 hour of calls could cost as much as 23% of battery life (23% = 450 / 2000)
Wake Lock:
WakeLocks are a Power Manager system Service feature, available to your applications to control the power state of the host device.
Wake Locks can be used to keep the CPU running, prevent the screen from dimming, prevent the screen from turning off, and prevent the keyboard backlight from turning off.

Where can I see battery usage since last charge (the total time)?

So I am new to both the S10e and Android 10 (or 9) and I can't find where the total battery usage since the last charge is displayed. On the battery usage page there is only 2 charts which show percentages, and not time, individual times per app, not total time, and even if I were to manually add the individual times together, for each separate day, I'm still missing standby time. Googling I found that there is supposed to be a 3-dot menu button to enable full usage statistics but I can't find that either. Am I just being a noob or did Samsung decide we don't need to now the usage time since last charge?

I use GSam Battery Monitor. You can find it in the Play Store.

riggerman0421 said:
I use GSam Battery Monitor. You can find it in the Play Store.
Click to expand...
Click to collapse
I will check it that app out but did Samsung really remove this basic information or Google did? I don't really like adding yet another app for something that should be there by default.

So I've been googling for the past few days and found little to no information on this issue. What makes it worse is that I don't even know if this is standard in Android 10, it's only on Samsung phones, or only on this specific model. Installing a third party app is something I am trying to avoid, but after all the useless information on the net (when you google android and battery, the results you get are either people complaining about battery life or people providing the same old useless tips for improving battery life, none of which answer my question) I've actually answered my own question. It seems the information I seek was there all along, hidden in plain sight (though not exactly what I was looking for but it's better than nothing). Check the shot below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The second chart has the time. 0 - 4 - 8 - 12 - 16 - 20. Why it's in sections of 4, I dont know, why it's missing the key number, 24, I don't know, why they didnt bother adding just a small "h" to the scale so people can see those numbers are actually hours, I don't know. Now, this still doesn't give me the total usage since last full charge (the charge was on dec 19th) because I have yet to find a way to select multiple days, if I select the individual days, 19,20 and 21 and approximately add up the charts, I get the total time. So, 21st has about 12h (as you can see above), 20th has 24h, and 19th has about 20-30 mins there, I'd say 36-37 hours of usage since last charge. Now, why exactly they removed this tiny bit of useful information is beyond me (it's been there all the way up till Android 8, I don't about 9, and it's gone in 10, or just removed by Samsung, again still don't know if it's been removed by Google or specific to Samsung only, I don't have another non-Samsung Android 10 phone just lying around for me to check).
Maybe someone can shed some light on this issue, maybe there is a way to select multiple days in the chart so it's automatically added up, maybe it will be added back in a future patch (yeah, right).

I've seen Android 10 on Pixel 4, it shows battery usage and screen on time since last full charge, so it's just OneUI 2.0 that doesn't.
Not only they removed this, they also removed idle time and its battery usage.
This would be my last Samsung phone.

themohd said:
I've seen Android 10 on Pixel 4, it shows battery usage and screen on time since last full charge, so it's just OneUI 2.0 that doesn't.
Not only they removed this, they also removed idle time and its battery usage.
This would be my last Samsung phone.
Click to expand...
Click to collapse
I appreciate the confirmation. At least we know it's on Samsung, not Google.

Anyone know of an app that adds the battery settings back to the quick settings? It's REALLY inconvenient to get the battery stats for this. I can't understand why Samsung removed that from quick settings.

I noticed the same issue with my S10e. This OS seems to be full of bugs and issues [emoji35]
Sent from my SM-G970F using Tapatalk

I think that android 10 features... Digital well being... Even on xiaomi it's like that... No screen on time since last full charge....

I use Gsam battery monitor.