Hi,
is there any app that display the real time cpu usage per-app?
I used "System tuner", but the cpu % per-app is just a percentage of the time the app stayed in the cpu since the app started, not real time (say last 2-3 secs).
Bump
Related
My phone's been running for 16 hours and 20 minutes on one charge, and the battery is at 59%. Not entirely sure if this is impressive or not, but I figured I'd share my settings. I'm on CM7 Nightly from the 13th.
JuiceDefender v3.4 Beta
Controls
Mobile Data - Enabled
Options - Prefer Wifi
WiFi - Enabled
3G - Off
Options - disable on wifi
Disable timeout - 5m
AutoSynch - ping
GPS - disabled
Everything else is left offSchedules
Schedule - Enabled
Frequency - 1hr
Duration - 30s
Controls - Default
Night - Enabled
Start 12am - End 6am
Options - Silent
Schedule (weekend) - Enabled
Frequency - 30m
Duration - 1m
Night Weekend
Start 2am - End 8amTriggers
Battery - Enabled
Battery Threshold - 35%
Charger AC
Screen - Enabled
Options - After Unlock
Controls - Default
Traffic - Enabled
Traffic Threshold - low
Apps - Enabled
Controls - Default
Location - Enabled
SetCPU
Main
Max: 1017600 Min:245760Profiles
Screen Off: 245 Max 245 Min Priority 100 Ondemand
Charging: 1017 Max 245 Min Priority 99 Performance
Battery <5% Max 368 Min 245 Min Priority 52 Conservative
Battery <50% Max 768 Min 245 Priority 50 Ondemand
Tasker
Profile to manage Turning Bluetooth off from 8:30-16:30 M-F, Exit Case turns bluetooth back on
Profile to manage Turning Bluetooth off from 17:30-7:30 M-F Exit Case turns bluetooth back on.
Profile to manage brightness: Level 0, Auto Brightness off from 00:00 to 08:00 Exit Case restores Auto Brightness
Very good info. I been holding off for to battery life. I might have to go visit the store tomorrow.
Sent from my Nexus One using XDA App
I like the SetCPU settings, I have never messed with the profiles before but that looks like a good idea.
I will see how this goes first then maybe try JD.
Over night my phone finally got down to 1%. Topped out at 31 hours 20 minutes or so.
Jeffsmashkot said:
Over night my phone finally got down to 1%. Topped out at 31 hours 20 minutes or so.
Click to expand...
Click to collapse
I'm monitoring with Current Widget and i'm noticing that my phone is deep sleeping and pulling down to as low as 1mA sometimes! I usually get about 24hrs or so, but I just applied some different setcpu profiles.
I also use Tasker to shut off mobile data in the middle of the night, then turn back on in the morning. I think it's pointless to leave it on and waste battery life while I'm sleeping.
Im going to try out Juice Defender. I had itw ith my Aria and it does work very well at saving battery life BUT on that phone it would cause some lag when switching networks on/off etc. On this phone hopefully it's fast enough to not notice the lagginess when switching networks.
I just did some major testing of the inspire power draw, and you guys are lucky. Compared to my nexus one, it is super efficient. The highest with screen on and pushing the phone hard, current would max at 400mA at max brightness. At 50% brightness current was steady at 230mA no matter what.
In comparison, my nexus one spikes to 700mA when showing white web pages, and around 180mA showing black. These spikes aren't good and no wonder nexus gets crap battery life.
I can see why they under spec the inspire battery, but I wish they didn't.
I'm going to try out your settings for a few days and see how it goes. Thanks.
Would you mind sharing the link for the juice defender. I've downloaded the newest beta and it says it cannot disable the cellular radio because it is not fully supported. Note I did flash it using the kernel with the battery fix posted on the forums. Do you think that could be the problem?
I just use SetCPU profiles and JuiceDefender in default mode. Immediate difference in battery life.
For testing purposes of CM7, I would leave my phone off the charger to see if the battery fix was working. Normally it would drop 15-20 percent sometimes more. With the SetCPU and Juice Defender, Just dropped 8 percent. WOOT!
hack2009 said:
Would you mind sharing the link for the juice defender. I've downloaded the newest beta and it says it cannot disable the cellular radio because it is not fully supported. Note I did flash it using the kernel with the battery fix posted on the forums. Do you think that could be the problem?
Click to expand...
Click to collapse
In order to get the latest beta, you have to register on the forum to be part of the beta group.
I'm on Revolution 3.3. The current widget doesn't work. It doens't show anything. Any ideas?
I've seen this a couple of times now on my Thunderbolt. FYI I am running completely stock non-rooted with the OTA update.
I use an app called "Watchdog" which I have set to checks every ten minutes and warn me if any process is using over 50% of the CPU. Every once and a while I get repeated notifications about "Android System" using >90% of the CPU. This persists over long durations of time.
I got a bit more detail from an app called "Process Monitor" about this "Android System" process:
Process Details:
Identification 1555
Type Process
Sub-Type Forground
Source /system/framework/framework-res.apk
CPU Usage:
Time Since Start 11h 55m 43s
CPU Usage 11h 34m 28.04s
CPU Consumption 97%
Obviously this is a system process, so I wonder if there is either a bug, or if there is some non-system app calling something repeatedly that causes this system package to do a lot of work. Anyone have any idea what this apk actually does so I might get a clue for what to look for?
Strangely the process is listed as "Forground" but the vast majority of the ~12h since boot was with the screen off connected to my charger overnight. I do have Settings - Applications - Development - Stay awake - Screen will never sleep while charging checked. However, I have seen this issue before I knew about that setting.
Even after rebooting and when this "Android System" is not "misbehaving", I notice that it is still my top total CPU user, but at least only uses a single digit percent of CPU.
Anyone else notice this kind of behavoir? What about those of you with custom ROMs? Does this go away or is it inherent to the Android platform?
Apps like watchdog and task killers are pretty counter intuitive with consideration as to how android works. So long as your phone is behaving properly and you aren't noticing significant battery draw, I'd say don't worry. If you are, try a factory reset.
Sent from my CM7 ThunderBolt using XDA Premium App
I had a problem for awhile where Android System was eating all my CPU and killing the battery. I never did figure out what it was. I did a factory reset and that fixed it. I guess maybe it was an app or something I had on the phone. Who knows.
crazed_z06 said:
I had a problem for awhile where Android System was eating all my CPU and killing the battery. I never did figure out what it was. I did a factory reset and that fixed it. I guess maybe it was an app or something I had on the phone. Who knows.
Click to expand...
Click to collapse
It's too bad the froyo battery stats aren't as complete as the gb ones for stuff like individual apps.
Sent from my CM7 ThunderBolt using XDA Premium App
Did some more testing this morning and thought I'd post my data so far.
I still think Android System process is running away, but it isn't as quite as bad as I thought because it only spins while CPU is awake anyway.
Conclusions from below testing data:
* Seems Process Monitor "Time Since Start" only counts time while CPU is awake, not real wallclock time
* "runaway" "Android System" process does not seem to be keeping phone awake (still sleeping 75%-80% of the time)
* "runaway" "Android System" process does seem to keep CPU pegged at fastest 1024 MHz speed (this should negatively affect battery life)
* Setting Applications/Development/Stay Awake seems to prevent CPU from sleeping while charging even when manually turning off screen (normal sleep w/o this setting checked) -> this makes it a lot more obvious that "Android System" keeps running
========
Test Log
* phone not on charger
* CPU Spy -> reset timers
* screen off (8:58am)
* wait for data collection
* screen on (9:24am)
* check CPU Spy stats:
26% 6m52s 1024 MHz
0% 2s 768 MHz
74% 19m18s sleep
26m12s total
* reboot
* check "Android System" in Process Monitor
Start 5m20s
CPU 2m00s (27%)
* CPU Spy -> reset timers
* screen off (9:33am)
* wait for data collection
* screen on (10:21am)
* check CPU Spy stats
1024 MHz 9m57s 20%
768 MHz 5s 0%
Sleep 38m39s 79%
* check "Android System" in Process Monitor
Start 16m13s
CPU 12m12s
* calculations
Sec Description
2921 CPU Spy - Total Time
2880 Aproximate wallclock time (9:33am to 10:21am)
2319 CPU Spy - Sleeping
602 CPU Spy - Awake
653 Process Monitor - Time Since Start
612 Process Monitor - CPU Usage (94%)
* Settings -> Turn off Applications/Development/Stay Awake (Screen will never sleep while charging)
* CPU Spy -> reset timers
* screen off (10:52am)
* wait for data collection
* screen on (10:57am)
* CPU Spy -> stats:
1024 MHz 1m06s 21%
Sleep 4m02s 78%
* Settings -> Turn on Stay Awake
* CPU Spy -> reset timers
* screen off (11:12am)
* wait for data collection
* screen on (11:24)
* CPU Spy -> stats
1024 MHz 12m26s 100%
Any ideas on managing the wakelocks on Android and specifically on the Infinity?
I've checked the option of switching off WiFi with screen-off, but in my battery usage stats I still see that over 10% of battery is consumed by Google Services with 672 wake locks & device waked 77 times (WiFi drain itself is 13,5%, so quite OK). This is what GSam Battery Monitor shows. Android stock battery management (in Settings) shows 51% drain by Google Services and 26% by WiFi (but I believe these stats are wrong most of the time or just measure a different thing, as they show tablet inactive with 2% bar and it has been inactive most of the time actually).
I have google auto-sync on and I need it, but I still think this is too high a number. I don't get 672 e-mails daily, so these shouldn't be PUSH notifications etc.
I'm not sure if I'm the only one seeing these high numbers there?
Have you tried CPUspy for finding out how much time in deep sleep you have?
Better Battery Stats is also a needed tool to find more about wakelocks
Sent from my GT-N7000 using xda app-developers app
Yes, I'm looking at it from time to time, but thanks for this. I had some issues when I started this thread, after wipe and re-flashing new firmware it seems OK in the stats: Deep Sleep 44%, 102MHZ 16%, 1500MHz 24% (running on balanced mode, interactive governor).
I'm still curious to get to know how to manage wakelocks under Android from (low) system level however.
iBestWin 10,000mAh (10A) Battery , AccuBattery &the Samsung Galaxy Note 4 n910f - RRm
Hello, Several days ago I purchased (courtesy of Amazon) an extended battery for the N910f & as many have mentioned knowing when to charge the Battery isn't easy for the casual user
(I'm more experienced than the average , have a fairly good knowledge of electrics - I'm mm electrician by trade - & computers / tech etc , but far from an expert compared to many on XDA)
Via the playstore I eventually (tried many) found this app called AccuBattery (Accubattery.zendesk.com) Which allows for the manual implementation of your batteries Basic specs
Here is a link to their manual :
https://accubattery.zendesk.com/hc/en-us/articles/210226065-Tab-1-charging-screen
Encompassing this I have disabled my battery icon & enabled the notification from the app to provide my battery reading & after several calibrations it appears to be reading accurately
I've accumulated serval screenshots for others to analyse ; being a forum all commentary is welcome
I'm easily able to get more than the 18hrs specified using it with my hot spot (for the note 3) , 4G / LTE , bright screen , Nightmare Cpu &Simple OnDemand governers (just straight performance) although I have underclocked the CPU as i have all 4 cores on (This works best for me less processing power but all cores working - very very smooth)
AccuBattery calculates the per app battery usage a bit differently than Android and many other apps (which can only accurately determine the phone's total battery consumption and then uses fixed profiles to estimate the distribution to each app). Instead, we have opted to calculate the phone's realized total battery drain whenever an app is in the foreground and assign all of it to that foreground app.
A benefit of this is that some apps have related background services running that the Android usage screen doesn't capture while we do. However, with our foreground method, we'll also capture background processes from other apps and end up assigning this to your foreground app (For example if you turn on an overlay and then stare at the clock app for an hour then all of that gets assigned to the clock app). We think it's a reasonable assumption though as the majority of the battery drain comes from the screen and many of the unrelated background services run regardless of which app is in the foreground. Furthermore, when the screen is off the background services don't get added up to the foreground app usage as nothing is considered to be in the foreground when the screen is turned off.
The average battery usage section shows you how we calculate our time remaining estimates and is based on the last 7 days of usage.
The fully battery time estimates give you an indication of expected performance on a 100% charge and might be a bit different to some other apps. You can read more about our time remaining estimates here: https://accubattery.zendesk.com/hc/en-us/articles/211277789
I am playing some games in emulation, they are sometimes not running full speed, but only the middle cores seem to go up when needed (i use CPU float to monitor the CPU usage), while the big one always remains at ~ 800 mhz.
I am not rooted, is there a way to make the big one wake up and improve the performance of the games?
Thanks!
I found a solution (a workaround).
For anyone interested to have (much) better performance in CPU heavy games (emulators) here's how you can force the phone to mostly use the middle (2.4 ghz) cores instead of only/mostly the small ones.
Run "CPU throttling test" apk, LOCK the application and let it run in the background. In the background, the application will ONLY use the 4 small cores, and it'll constantly throttle to ~ 20%.
Now start you game/emulator (in my case Retroarch, with some HEAVY on CPU games), and if you use CPU float monitoring tool, you will notice that the small cores will be kept busy at 1.7 ghz by the CPU throttling test apk, while the medium ones will be used as needed by the game (the big one will still be left unused, or just used for a split second in some cases).
For me, the performance is 'easily' 25% better, if not more, and the battery consumption went from 1% every 4 minutes, to 1% every 3 minutes and 20 seconds.