Related
Hi all,
First time poster here, so hello! I've searched the forums and google but could not find an answer to this question.
Is anyone running a Nexus S on 4.0.4 ICS seeing lots of CPU usage at the 1000MHz frequency?
My phone is a Nexus S (i9020)
Operator: 02 UK
OS: Ice Cream Sandwich 4.0.4
Not rooted.
My phone goes into a deep sleep fine and battery usage seems to be little in this state. However, the moment I turn on the screen and start 'using' the phone, I see a battery drop of at least 1% every 5 mins or so. I'm not doing anything taxing, either scrolling through the home screens, or opening browser to read a web page for a few mins.
Higest three battery users are reported as:
Screen 37%
Android System 15%
Browser 7%
CPU Spy reports the following:
1000 MHz - 25.11 (30%)
800 MHz - 7.35 (9%)
400 MHz -3.34 (4%)
200 MHz - 6.26 (7%)
100 MHz - 6.56 (8%)
Deep Sleep - 33.29 (40%)
Total time: 1h23m13s
From what I've read cpu usage shouldn't max out unless you're running something intensive i.e. it shouldn't be at the 1000MHz frequency, when just reading an already loaded page.
I'm able to go from 100% to 50% in about 2 hours, just using the browser (on wifi) to read webpages and nothing more.
When I first got the phone, a year ago, on Gingerbread, I'd be able to watch 1 hour of video, send calls and texts and make it from 8.30am to 5pm using around 40% battery. These days, I don't get close to that at all.
Noted to moderators: if this is posted in the wrong place or would be better suited in an existing thread, I'm sorry please let me know and I'll edit as required!
Thanks in advance for your time and assistance!
Screen drains most the battery. If there is drain while it's off there would be some kind of wake lock preventing sleep. You likely don't have this since it seems your phone sleeps nicely, assuming you had the screen on for moat the time in that screenshot.
The frequencies you show seem a little skewed to 1000mhz for web browsing. What cpu governor are you using, and what settings? I usually get around 40-40 between highest and lowest frequency with ondemand, 20% or less for the intermediate frequencies. This is while web browsing most of the time.
Harbb said:
Screen drains most the battery. If there is drain while it's off there would be some kind of wake lock preventing sleep. You likely don't have this since it seems your phone sleeps nicely, assuming you had the screen on for moat the time in that screenshot.
The frequencies you show seem a little skewed to 1000mhz for web browsing. What cpu governor are you using, and what settings? I usually get around 40-40 between highest and lowest frequency with ondemand, 20% or less for the intermediate frequencies. This is while web browsing most of the time.
Click to expand...
Click to collapse
I understand the screen drains the most battery, but I feel there is an underlying issue since light usage (like reading) can drain 50% in 2 hours, whereas before I could watch 1 hour video and lose about 10%.
I'm not sure what you mean by CPU governor and settings. I'm running the stock ICS 4.0.4 (got the OTA only a few days ago). I agree it seems skewed. It seems to use the 1000MHz frequency pretty much all the time the screen is on.
chillerz said:
I understand the screen drains the most battery, but I feel there is an underlying issue since light usage (like reading) can drain 50% in 2 hours, whereas before I could watch 1 hour video and lose about 10%.
I'm not sure what you mean by CPU governor and settings. I'm running the stock ICS 4.0.4 (got the OTA only a few days ago). I agree it seems skewed. It seems to use the 1000MHz frequency pretty much all the time the screen is on.
Click to expand...
Click to collapse
First off, welcome to XDA!
The fact that you're not rooted + stock could only mean that there is probably a background app running while your actively using your phone. Have you checked into Settings > Apps > Running and noticed anything peculiar? For a fact, based on everything I'm reading here there is no way your phone should be at 1000 MHz for 30% of the time. At most for my usage, my phone is in the 1000 MHz state < 10% of the time.
If all else fails, you could always try doing a factory reset and seeing if the problem persists. If not then you can install your important apps one by one to find a culprit.
You could also try out this nify tool: BetterBatteryStats to give you more statistics as to what is eating your battery.
http://forum.xda-developers.com/showthread.php?t=1179809
10 percent drain while watching a video is hard to believe.
That would equal 10hrs to drain the battery with screen on watching a video. Which is not happening.
Your battery drain now sounds normal. Maybe in the past it was not reporting it correctly or you're simply mistaken somehow.
The average battery should last along the lines of 4 - 5 hours worth of screen on time. Whether this is playing a game or browsing around hasn't made more than that much difference for me. 1% every 5 minutes would give you ~8 hours of screen on time, a feat very few (aLNG, looking at you) have been able to do without an extended battery. Anything more than this is not going to happen while maintaining a cell signal and watching videos. You may have been exaggerating the time on battery in the past.
Go to Settings --> Developer options --> Show CPU usage and tick it. Leave the phone sitting there with the screen on for a bit and let me know what the top CPU users are.
Which settings are the best for battery lfe? I have stock everything.
Harbb said:
The average battery should last along the lines of 4 - 5 hours worth of screen on time. Whether this is playing a game or browsing around hasn't made more than that much difference for me. 1% every 5 minutes would give you ~8 hours of screen on time, a feat very few (aLNG, looking at you) have been able to do without an extended battery. Anything more than this is not going to happen while maintaining a cell signal and watching videos. You may have been exaggerating the time on battery in the past.
Go to Settings --> Developer options --> Show CPU usage and tick it. Leave the phone sitting there with the screen on for a bit and let me know what the top CPU users are.
Click to expand...
Click to collapse
The list of things using the CPU changes quite often, here's the list of the ones that are at the top of the list for a while (I've also attached a screenshot):
system_server
com.android.systemui
surfaceflinger
com.jim2
kworker/u:1
kworker/0:0
dhd_dpc
wpa_supplicant
UPDATE:
7h 48m 34s on battery
Voice calls: 1h 39m (screen is off for most of the call duration)
Screen on: 1h 23m
Used browser and xda app for less than 5 mins each.
Haven't done much else with the phone and I'm on 44% battery (from full charge).
CPU Spy (measuring whilst phone was charging overnight, so deep sleep is high):
Total CPU time = 13h26m
1000 MHz = 40 mins (5%)
800 MHz = 17 mins (2%)
400 MHz = 12 mins (1%)
200 MHz = 26 mins (3%)
100 MHz = 56 mins (7%)
Deep Sleep = 10h52m (80%)
hi,
I can confirm chillerz's notice. My experience's similar. Last week I upgraded my (non routed) i9023 from GB via OTA (before the update I did a hardreset). My phone became a cityphone I always have to keep a charger in my pocket and looking for power connectors.. with GB I could use my phone at least 2 days but now I'm happy if I can survive my workday.. my best was 13h - in that case Android OS battery usage was 61%.. I still haven't try to use the music player.. but I don't see any sense to it.. I'm also interested in a thread which could help me out and I've found my self here.. what do you recommend? what to do? replacing my 7 months old phone?? I've jus loved my nexus and here I'm.. It won't be a good business strategy in long term..
I know about the issues of released ICS in December.. I was hopping the 4.0.4 will solve them.. now it's April.. I don't want to wait 4 more months again..
thanks in advanced for your helping!
I had horrible battery life after the 4.0.4 update, but it's been much improved after fully discharging the battery and then charging it to 100% with the phone powered off.
great news, I will try tonight and share the result!
thx
The latest usage results seem good and processes also seem standard. Phone calls tend to use a fair bit of battery, keeping and transmitting a constant signal, powering speakers, keeping the entire phone awake and so on. I wouldn't put it above the screen being on, so you should be able to squeeze another ~30 minutes before 44% in normal use but this depends on too many factors to list anyway and bad reception can make it all the more difficult to figure out.
Also, while making calls don't be surprised if the CPU does decide it needs to ramp up to a higher frequency (ondemand likes 1000mhz) but i havn't put this to the test. This could skew the results as in the OP.
hello futangclan,
since your solution the battery usage "normalized" 26h/17%. This workaround would be a great tip on a welcome srceen at the first boot of ICS
before the fully discharging battery I noticed the battery usage of Android OS decreased from 60 to 19%.. I'm thinking about whether the ICS does something "maintenance" in the background after the OTA upgrade the first days or not..
Once upon a time, I too was one of the sullied - one those unfortunates souls, plagued with poor battery life on a Nexus S (stock FTW), brought on by an innocent (and joyful) upgrade to ICS 4.0.4 from 2.3.6.
When I first discovered the trouble, with great gusto, I ran to the interwebs and dutifully followed suggestions of restarting the phone or draining the battery, but alas - it was all to no avail. There is, however, a happy ending to this story. With effort and perseverance, I've since significantly improved performance. Here is my brief tale of success.
After the upgrade, Android (praise be its name!) decided to start, in the background, every single application on the phone. Verily Snake '97 was indeed running all the time. The horror!!! The game is entertaining certainly, but hardly worth keeping alive at the cost of other, more critical apps.
I was not deterred and took matters into my own hands. Using Manage Apps -> All (not Manage Apps -> Running, mind you), I went about Force Stopping each application (including some Android core apps). It was tedious and frightening. I was very careful and hesitant, as you should be if you are affected by a similar malady.
By the next day, I saw much improved battery life (hooray!), yet I wasn't free and clear. The hold of evil had not been loosened completely.
I found within, a strange and dangerous lock (wakelock - was that its name?) keeping the Gallery in the list of active applications, even when I had not used it for some time. It refused to move to the cached apps list. Puzzled, I scratched my empty head. The interwebs were of no use this time - I was on my own.
(cue ominous music)
Peering within, in the Sync section I found the system was trying to sync photos on an account where the checkbox for syncing was not selected.
A quick off-on-off stopped the syncing. The app slinked off the Running apps list. Soon, I was overjoyed, for I was experiencing improved battery life!
I've now returned to performance much closer to that from days of 2.3.6. My Nexus S' battery now reaches 40%-30% in ~16 hours, with always-on 3G, Wifi and GPS, oft use of phone, contacts, messaging, whatsapp, twitter, foursquare and browser, and infrequent use of music, market, maps, camera and rarer usage of games like Angry Birds (which consumes vast amounts of battery) and gallery.
All is well with the universe.
Certainly, this tale may or may not be a mirror to your own. Should you be experiencing similar problems, I hope my tale brings you solace, and provides a means to the end of your troubles.
demarcolister said:
Once upon a time, I too was one of the sullied - one those unfortunates souls, plagued with poor battery life on a Nexus S (stock FTW), brought on by an innocent (and joyful) upgrade to ICS 4.0.4 from 2.3.6.
When I first discovered the trouble, with great gusto, I ran to the interwebs and dutifully followed suggestions of restarting the phone or draining the battery, but alas - it was all to no avail. There is, however, a happy ending to this story. With effort and perseverance, I've since significantly improved performance. Here is my brief tale of success.
After the upgrade, Android (praise be its name!) decided to start, in the background, every single application on the phone. Verily Snake '97 was indeed running all the time. The horror!!! The game is entertaining certainly, but hardly worth keeping alive at the cost of other, more critical apps.
I was not deterred and took matters into my own hands. Using Manage Apps -> All (not Manage Apps -> Running, mind you), I went about Force Stopping each application (including some Android core apps). It was tedious and frightening. I was very careful and hesitant, as you should be if you are affected by a similar malady.
By the next day, I saw much improved battery life (hooray!), yet I wasn't free and clear. The hold of evil had not been loosened completely.
I found within, a strange and dangerous lock (wakelock - was that its name?) keeping the Gallery in the list of active applications, even when I had not used it for some time. It refused to move to the cached apps list. Puzzled, I scratched my empty head. The interwebs were of no use this time - I was on my own.
(cue ominous music)
Peering within, in the Sync section I found the system was trying to sync photos on an account where the checkbox for syncing was not selected.
A quick off-on-off stopped the syncing. The app slinked off the Running apps list. Soon, I was overjoyed, for I was experiencing improved battery life!
I've now returned to performance much closer to that from days of 2.3.6. My Nexus S' battery now reaches 40%-30% in ~16 hours, with always-on 3G, Wifi and GPS, oft use of phone, contacts, messaging, whatsapp, twitter, foursquare and browser, and infrequent use of music, market, maps, camera and rarer usage of games like Angry Birds (which consumes vast amounts of battery) and gallery.
All is well with the universe.
Certainly, this tale may or may not be a mirror to your own. Should you be experiencing similar problems, I hope my tale brings you solace, and provides a means to the end of your troubles.
Click to expand...
Click to collapse
You, my friend, deserve a cookie for such good writing.
@demarcolister Awesome first post here on XDA.
Great story too. Most will blame battery drain on the custom ROM/kernel they flash and fail to realize their battery drain is usually caused by a rogue app running in the background ...
I've never had good luck with the stock gallery app. I always freeze it via adb when I flash a new ROM. It seems much worse in ICS. It would always start back up.
Stock GB gallery was an absolute joke. Slow, missing thumbnails, weird background and hard to see what you're scrolling through. The stock ICS gallery i actually prefer over alternatives. Though i don't use picasa so that is disabled. Never an issue with it (besides always showing my damned album covers).
Harbb said:
You, my friend, deserve a cookie for such good writing.
Click to expand...
Click to collapse
nom nom nom!!
AeroEchelon said:
@demarcolister Awesome first post here on XDA.
Great story too. Most will blame battery drain on the custom ROM/kernel they flash and fail to realize their battery drain is usually caused by a rogue app running in the background ...
Click to expand...
Click to collapse
I was quick to (negative) judgement too, but I figured that Google would not (certainly!) release an update that completely cripples a modern and high-selling device.
Harbb said:
Stock GB gallery was an absolute joke. Slow, missing thumbnails, weird background and hard to see what you're scrolling through. The stock ICS gallery i actually prefer over alternatives. Though i don't use picasa so that is disabled. Never an issue with it (besides always showing my damned album covers).
Click to expand...
Click to collapse
Agreed! In fact, I'd accept, grudgingly, if album covers show up in the gallery (although, truly they should not), but I do not, under any circumstance, want to see the icons (tick for yes, cross for no, i for icons, etc.) used by an application in my Gallery. Idiocy!
What is the solution? I wish to remain Stock, so rooting and editing the equivalent of plist or config files is not an option. At least 'Camera' is the first option, always! That makes it usable, but as soon as I use picplz or camera360 or instagram their folders get shuffled in position. Is Google hinting at something!? *sigh*
Hey guys...
Sent from my Nexus S
I don't want to compromise any features to gain a bit of battery. Is there any power settings which get keep things running the way most android phone run?
Also i heard that by default apps will not run with the screen off and that you need to allow apps to do this on a per app basis? Is this correct? how do i get to these options?
For your first question if you set battery to Intelligent, it will use smaller cores for normal usage like web, social media, youtube and such and bigger cores mainly to performance stuff like playing games. Honor got this pretty balanced (got 6hours SoT while watching Twitch for and hour and playing GTA:SA for about half hour)
For your second question. You can disable this feature completely - go to Battery settings in Phone Manager > Protected apps and from there you can select Protect All. This will let all your apps run in background so you wont miss any notifications (also I believe that Marshmallow Doze is somewhat implemented in EMUI too)
Here's what I've found related to slow scrolling jitter and the touchscreen. When you first open an app, the very first couple slow scrolling swipes produce very smooth screen animation. It will then get jittery but if you exit the app, then reopen, the smoothness will return. Do this experiment in Contacts app to see what I mean.
Now I found this app called "Touch MultiTest" which reads out the touchscreen sample rate as you move your finger on the screen. When you first open it and do a swipe, you see smooth tracking and a solid sample rate reported greater than 120 Hz. However after a couple swipes the dot response becomes jittery and sample rate drops to something around 100 Hz. Closing and reopening the app gets you back to 120 Hz.
So I think this proves the hardware and software touch loop can produce smooth motion, and it's really sampling at 120 Hz. The big question is what exactly degrades after a couple swipes. In the best case it's some driver or software buffer / interrupt handling that degrades. In the worst case it's related to low level hardware issues. I'm hopeful it's software related. By the way somehow Chrome browser always scrolls smoothly with slow swipes. What is Chrome doing differently than all other apps? Just filtering?
Scrappy1 said:
Here's what I've found related to slow scrolling jitter and the touchscreen. When you first open an app, the very first couple slow scrolling swipes produce very smooth screen animation. It will then get jittery but if you exit the app, then reopen, the smoothness will return. Do this experiment in Contacts app to see what I mean.
Now I found this app called "Touch MultiTest" which reads out the touchscreen sample rate as you move your finger on the screen. When you first open it and do a swipe, you see smooth tracking and a solid sample rate reported greater than 120 Hz. However after a couple swipes the dot response becomes jittery and sample rate drops to something around 100 Hz. Closing and reopening the app gets you back to 120 Hz.
So I think this proves the hardware and software touch loop can produce smooth motion, and it's really sampling at 120 Hz. The big question is what exactly degrades after a couple swipes. In the best case it's some driver or software buffer / interrupt handling that degrades. In the worst case it's related to low level hardware issues. I'm hopeful it's software related. By the way somehow Chrome browser always scrolls smoothly with slow swipes. What is Chrome doing differently than all other apps? Just filtering?
Click to expand...
Click to collapse
Have you tried contacting Essential or possibly using their beta feedback form to tell them about your theory/findings?
Our screens sample at 60Hz. We already know this from the AMA's on Reddit. The test app you're using is inaccurate if it reads 120Hz or even 100Hz.
60Hz sampling in of itself shouldn't be a problem either since iPhones (except for the newest ones) sample at 60Hz and everyone knows how smooth they are.
Hopefully there's not some other hardware flaw and it's just Essential's software.
ChronoReverse said:
Our screens sample at 60Hz. We already know this from the AMA's on Reddit. The test app you're using is inaccurate if it reads 120Hz or even 100Hz.
60Hz sampling in of itself shouldn't be a problem either since iPhones (except for the newest ones) sample at 60Hz and everyone knows how smooth they are.
Hopefully there's not some other hardware flaw and it's just Essential's software.
Click to expand...
Click to collapse
I don't put much stock in the AMA response since its so vague and nonspecific and could be referring to screen refresh rate (60 Hz) either intentionally or accidentally.
If new iPads and iPhones sample at 120 Hz, it's entirely possible essential panel is sampling at 120 Hz.
Try using Touchscreen Benchmark to test and you'll be able to verify the actual samples per second. As a point of comparison, the Galaxy S4 samples at 90Hz and the Shield tablet does a whopping 180Hz!
In any case, it's easy to see that it's not refreshing at 100Hz or 120Hz simply by looking at the number of touch samples that actually appear on the screen. Try it on a faster phone and you can see the higher density of touch responses.
Furthermore, you can't reliably discern the sample rate in the first second so trusting the app saying it's 120Hz and dips to 100Hz is even less reliable than the AMA.
ChronoReverse said:
Try using Touchscreen Benchmark to test and you'll be able to verify the actual samples per second. As a point of comparison, the Galaxy S4 samples at 90Hz and the Shield tablet does a whopping 180Hz!
In any case, it's easy to see that it's not refreshing at 100Hz or 120Hz simply by looking at the number of touch samples that actually appear on the screen. Try it on a faster phone and you can see the higher density of touch responses.
Furthermore, you can't reliably discern the sample rate in the first second so trusting the app saying it's 120Hz and dips to 100Hz is even less reliable than the AMA.
Click to expand...
Click to collapse
I invite anyone to do my test and decide for themselves or measure and produce new data. That's what I'm going for here. Not regurgitation of bland statements.
Scrappy1 said:
I invite anyone to do my test and decide for themselves or measure and produce new data. That's what I'm going for here. Not regurgitation of bland statements.
Click to expand...
Click to collapse
I just invited you to use a different test instead of relying on one that doesn't spit out reasonable numbers.
Does it make more sense that the Essential potentially is using a 120Hz touchscreen which Essential won't confirm despite it being a feather in their caps (since even iPhones only got 120Hz recently) or does it make more sense that Essential is using a slower than average (for Android) panel which their software isn't filtering out as well as Apple's software does? Which is more likely to cause jitter and touch latency?
ChronoReverse said:
I just invited you to use a different test instead of relying on one that doesn't spit out reasonable numbers.
Does it make more sense that the Essential potentially is using a 120Hz touchscreen which Essential won't confirm despite it being a feather in their caps (since even iPhones only got 120Hz recently) or does it make more sense that Essential is using a slower than average (for Android) panel which their software isn't filtering out as well as Apple's software does? Which is more likely to cause jitter and touch latency?
Click to expand...
Click to collapse
It's actually that your misunderstanding terminology...
Your mistaking sample rate and refresh rate...
Refresh rate is how many times per second? the screen is redrawn...
Sample rate is how many times per second? the screen reads touches...
No way you can tell the difference between 120hz vs 100hz.
Sent from my PH-1 using Tapatalk
rignfool said:
It's actually that your misunderstanding terminology...
Your mistaking sample rate and refresh rate...
Refresh rate is how many times per second? the screen is redrawn...
Sample rate is how many times per second? the screen reads touches...
Click to expand...
Click to collapse
No, I'm referring to the touchscreen. Obviously the Essential LCD only refreshes at 60Hz (only the Razer and iPad Pro refreshes at 120Hz) but the touchscreen also samples at 60Hz which is common for lower end Androids (90Hz and 120Hz are the other common sampling rates found in Android devices).
The new iPhone X's OLED still refreshes at 60Hz but has a 120Hz sampling touchscreen which is higher than the 60Hz it used to be in other iOS devices (except for the iPad Pro). I also mentioned the Shield tablet sampling at 180Hz and there's no mobile device with a screen refresh that fast either.
LNJ said:
No way you can tell the difference between 120hz vs 100hz.
Click to expand...
Click to collapse
The drop to 100 Hz after a couple of seconds is "indicative of the problem", not that a 100 Hz rate would not be smooth in a properly designed device. Something comes unhinged at the point we see the drop to 100 Hz. Could be touch buffer / event que is not being serviced fast enough due to low level driver or hardware. Also could be some piece of software in critical path starts consuming more time than allowed, leading to non uniform response. Could be actual stuttering of hardware.
When you exit and then restart an app, the touch event pipleline is flushed, so things are fixed again for a couple of seconds.
YouTube app
Scrappy1 said:
Here's what I've found related to slow scrolling jitter and the touchscreen. When you first open an app, the very first couple slow scrolling swipes produce very smooth screen animation. It will then get jittery but if you exit the app, then reopen, the smoothness will return. Do this experiment in Contacts app to see what I mean.
Now I found this app called "Touch MultiTest" which reads out the touchscreen sample rate as you move your finger on the screen. When you first open it and do a swipe, you see smooth tracking and a solid sample rate reported greater than 120 Hz. However after a couple swipes the dot response becomes jittery and sample rate drops to something around 100 Hz. Closing and reopening the app gets you back to 120 Hz.
So I think this proves the hardware and software touch loop can produce smooth motion, and it's really sampling at 120 Hz. The big question is what exactly degrades after a couple swipes. In the best case it's some driver or software buffer / interrupt handling that degrades. In the worst case it's related to low level hardware issues. I'm hopeful it's software related. By the way somehow Chrome browser always scrolls smoothly with slow swipes. What is Chrome doing differently than all other apps? Just filtering?
Click to expand...
Click to collapse
I have noticed that if you launch the camera and then open the YouTube app or whatever you're using where you can see the touch scrolling jitters, the touch scrolling is nice and smooth. Then after some time it comes back. The touch scrolling in Chrome is perfect and I wish it was the same everywhere. For some reason the YouTube app performs the worst for me. Chrome must have received an update a while back since I used to get bad touch scrolling on that too. The thing that worries me is some claim touch scrolling is perfectly smooth on their device. Hopefully that's a case of them not noticing it and not a case of actual hardware differences.
mhajii210 said:
I have noticed that if you launch the camera and then open the YouTube app or whatever you're using where you can see the touch scrolling jitters, the touch scrolling is nice and smooth. Then after some time it comes back. The touch scrolling in Chrome is perfect and I wish it was the same everywhere. For some reason the YouTube app performs the worst for me. Chrome must have received an update a while back since I used to get bad touch scrolling on that too. The thing that worries me is some claim touch scrolling is perfectly smooth on their device. Hopefully that's a case of them not noticing it and not a case of actual hardware differences.
Click to expand...
Click to collapse
Cool tip! I hadn't noticed that. Opening camera then switching to contacts had me scrolling smooth for many minutes. However after a few rounds of tests it lost the magic. I could no longer use camera open first to produce the smooth scrolling. So there are several factors at play here and this could use more investigation. Most of all though this gives me hope the issue can be totally fixed in software.
I'm starting to think the thing that goes bad and causes choppiness is the rendering pipeline. I enabled "Profile GPU Rendering" and then did a screen capture after scrolling my battery stats in settings for both 1) good condition just after launching settings when scrolling is smooth and 2) bad condition that kicks in after a few seconds when things get choppy. The bad condition shows vastly inflated rendering time which blows the 60 FPS (green line) budget. The largest increase is in red (command issue), but EVERYTHING is inflated in the bad condition. What could cause this?
The captures of the good and bad conditions are attached.
Turns out the reason the rendering pipeline starts taking so long is due to the application thread moving from high performance CPU cluster to the low performance CPU cluster. Using the paid version of System Monitor I opened a floating window of CPU load and freq. I then again opened battery settings and scrolled around in the good and bad state. I can see the CPU load is on the high performance cluster right away (5-8) and those guys are running at 2.4 GHz. Hence everything is smooth. When the jitters set in, the load has moved to low performance cluster (1-4) and they are running much lower clock rate < 1 GHz. I do believe this is probably fairly normal android behavior, but it's obviously tied to the slow scrolling jitters for us. It could be a subtle governor or big.LITTLE thread scheduling issue somehow playing into touch screen weirdness I suppose.
The two captures attached show the issue. One was captured right after launching battery settings when things are smooth and CPUs 5-8 are screaming. Other was captured after things went jittery, and here you can see CPU load that was on 5-8 has moved to 1-4, and clock frequency is much lower. (Hovers between 300 - 1000 Mhz)
Scrappy1 said:
Turns out the reason the rendering pipeline starts taking so long is due to the application thread moving from high performance CPU cluster to the low performance CPU cluster. Using the paid version of System Monitor I opened a floating window of CPU load and freq. I then again opened battery settings and scrolled around in the good and bad state. I can see the CPU load is on the high performance cluster right away (5-8) and those guys are running at 2.4 GHz. Hence everything is smooth. When the jitters set in, the load has moved to low performance cluster (1-4) and they are running much lower clock rate < 1 GHz. I do believe this is probably fairly normal android behavior, but it's obviously tied to the slow scrolling jitters for us. It could be a subtle governor or big.LITTLE thread scheduling issue somehow playing into touch screen weirdness I suppose.
The two captures attached show the issue. One was captured right after launching battery settings when things are smooth and CPUs 5-8 are screaming. Other was captured after things went jittery, and here you can see CPU load that was on 5-8 has moved to 1-4, and clock frequency is much lower. (Hovers between 300 - 1000 Mhz)
Click to expand...
Click to collapse
Let's try this
@DespairFactor
GPU governor
rignfool said:
Let's try this
@DespairFactor
Click to expand...
Click to collapse
Well I can tell you it's not all because of the CPU performance since setting GPU governor to performance on Oreo beta 2 completely gets rid of the touch screen jitters for me. I'm running Oreo beta 2, Rey.R3 Kernel and Magisk 15.2. Using EX Kernel Manager to set GPU governor to performance, I have eliminated the touch scrolling microstutters. Try it out for yourself and see! I also set CPU governor to conservative to compensate for the slightly increased battery usage. Phone is blazing now. https://forum.xda-developers.com/essential-phone/development/kernel-rey-kernel-t3723601 is the link to the kernel.
mhajii210 said:
Well I can tell you it's not all because of the CPU performance since setting GPU governor to performance on Oreo beta 2 completely gets rid of the touch screen jitters for me. I'm running Oreo beta 2, Rey.R3 Kernel and Magisk 15.2. Using EX Kernel Manager to set GPU governor to performance, I have eliminated the touch scrolling microstutters. Try it out for yourself and see! I also set CPU governor to conservative to compensate for the slightly increased battery usage. Phone is blazing now. https://forum.xda-developers.com/essential-phone/development/kernel-rey-kernel-t3723601 is the link to the kernel.
Click to expand...
Click to collapse
Thanks for your input! I would go down the root and tweaks path if I didn't have to use my phone for work with the Google device policy and all. Hoping for some jitter improvement in next official stock update.
rignfool said:
Let's try this
@DespairFactor
Click to expand...
Click to collapse
I think we can move the touchscreen to it's own workqueue, but not sure if it'll handle this.
mhajii210 said:
Well I can tell you it's not all because of the CPU performance since setting GPU governor to performance on Oreo beta 2 completely gets rid of the touch screen jitters for me. I'm running Oreo beta 2, Rey.R3 Kernel and Magisk 15.2. Using EX Kernel Manager to set GPU governor to performance, I have eliminated the touch scrolling microstutters. Try it out for yourself and see! I also set CPU governor to conservative to compensate for the slightly increased battery usage. Phone is blazing now. https://forum.xda-developers.com/essential-phone/development/kernel-rey-kernel-t3723601 is the link to the kernel.
Click to expand...
Click to collapse
Post a video. In all likelihood, it's just placebo effect. I've heard time and time again people claiming that that the slow-scrolling stutter is gone. It's never once been proven. Here's a side-by-side comparison vs the Pixel XL.
I don't understand this feature at all. After reading this article http://www.xperiablog.net/2020/06/01/xperia-1-iis-hs-power-control-feature-bypasses-battery-charging-to-maximise-gaming-performance/ I thought it will allow me to play games for as long as I want without depleting the battery. I've tried charging with this feature turned on 2 times now, and both times the battery level was dropping., so where's that battery degradation reduction they write about?
Furthermore, H.S. power control supposedly prevents the battery from charging, but during both tests, Franko Kernel Manager was showing that the battery was charging, not in a usual way though. Speed was going back and forth between charging rapidly (as fast as 6000 mA) and charging slowly (as slow as 12 mA).
"Limits performance reduction and battery degradation caused by device overheating during charging. The battery doesn't get charged when this feature is on. Turn off this feature when charging". So you launch a game, go through the game enhancer's features, and see this confusing AF wording, which tells you the feature prevents overheating while charging and gaming, but at the same time tells you not to turn it on while charging and gaming.
I use this feature when navigating. I was happy that it's not only available for games. Worked well. At least battery level didn't changed after some hour drive. Didn't checked it with Franco kernel Manager.
You selected the App and the colored bar appeared when App was in use?
Undead_Son said:
I don't understand this feature at all. After reading this article http://www.xperiablog.net/2020/06/01/xperia-1-iis-hs-power-control-feature-bypasses-battery-charging-to-maximise-gaming-performance/ I thought it will allow me to play games for as long as I want without depleting the battery. I've tried charging with this feature turned on 2 times now, and both times the battery level was dropping., so where's that battery degradation reduction they write about?
Furthermore, H.S. power control supposedly prevents the battery from charging, but during both tests, Franko Kernel Manager was showing that the battery was charging, not in a usual way though. Speed was going back and forth between charging rapidly (as fast as 6000 mA) and charging slowly (as slow as 12 mA).
"Limits performance reduction and battery degradation caused by device overheating during charging. The battery doesn't get charged when this feature is on. Turn off this feature when charging". So you launch a game, go through the game enhancer's features, and see this confusing AF wording, which tells you the feature prevents overheating while charging and gaming, but at the same time tells you not to turn it on while charging and gaming.
Click to expand...
Click to collapse
Must be a bug, works fine on my phone though....try resetting the phone perhaps?
Phoost said:
I use this feature when navigating. I was happy that it's not only available for games. Worked well. At least battery level didn't changed after some hour drive. Didn't checked it with Franco kernel Manager.
You selected the App and the colored bar appeared when App was in use?
Click to expand...
Click to collapse
Yes, the enhancer works, just not exactly as advertised.
yekollu said:
Must be a bug, works fine on my phone though....try resetting the phone perhaps?
Click to expand...
Click to collapse
I've spent quite some time on customizing the phone, installing apps etc. so I'd rather not start all over again. Unless there won't be any custom ROMs for a very long time...
it is a bug. if you still have problem. or other people have a problem there a way to fix it without factory reset. if your phone running android 12 or android 11. BUT not lasted firmware(of the android version.). try to download lasted version of Game enhancer(i recommended version 7.x.x instead version 8.x.x, because it more stable on 7, but if you rooted or can install subsystem apk, you can go with lasted version and i more recommended to do so to get more feature), subsystem and monitor apk from apkmirror, dont worry all app have same Game enhancer logo. if you have android lasted android 11 or android 12 firmware, only download Game enhancer and monitor app, as subsystem has been set to persistent app. and cannot be updated. if you are rooted download all app i mention and install as system app then reset your phone. im using xperia 1 ii with version 7.0.A.1.20 game enchaner as my original version came with my firmware have bug and H.S does not work as intended. whoever updated it does fix the problem(you can see with most battery monitor app that charging switch from -x/+x to null or 0) whoever not installing subsystem and lasted monitoring app from cause :
1.powersaver or balance does not effect anymore(but switch to Power save allow phone to use 600-700mah more often, and performance while have same usage sometimes spike to 1000mah sadly the display stay at 60hz, this is not intended as using original app power are limitied to 400-650 while average around 480mah with 40hz display)
2.while congrats you can streaming from you phone now, unless subsystem installed you may only have 1 chance to screenshot thumbnail until you reset user data. as importing image or re screenshot not working without newer subsystem. but at least all stream function working fine as i test it for 1 hours nonstop(just make use you have atleast 20-30mbps UPLOAD as lower than that cause stuttering on youtube even on 480p stream)
3.it may or may not disable/bypass thermal throttling while gaming(cant confirm but on my phone using original apk will give me around 280gips max then down to around 160 or 180gips under 5 minutes while using update version will stay more than 300gips, on CPU Thrttling, same as 3d mark, while normal benchmark average, extended test will have better result than most xperia on same model with 99.5% stability and score around 1108 to 1106 from loop 1 to loop 4 with identical performance range from loop 1 to loop 20)
4.recording no longer work on sdcard as they change folder name and older subsystem still using older name, it just keep asking permission
5.on stream and record menu. there option for capture card. it does nothing, even installing another backend app. like audio app from G.E and other app, it still wont work, unless you are rooted and install all backend app as system app, whoever fearnot, you stil can stream your content via type c to hdmi like normal, but dont except you can get audio bypass or settings like xperia 1 IV have,
*again point 3 is unclear as for me performance from older bencmark are deference than now, but it is from era android 11, i can be sony fix thermal issue and performance from firmware and not this trick, but it does effect mine since i can just remove update and see instantly the deference and it may can on your xperia too
*i said both monitoring/monitor app and subsystem app. because it called that but apk file name uploaded as sony multitasking function and GE subsystem
here a proof for point number 3, and not it not with any mod(no fan cooler but no case either with H.S enabled)
Hello,
You can add custom apps to H.S. Power Control right?
Only supported apps or ALL apps installed?
Does that also work if you turn the screen off? or does the phone start charging as soon you you turn the screen off?
To all those who claim to get over 7 hours screen on time, especially by using debloat scripts, using adb to uninstall/ disable pre-installed apps and services, other tweaks, etc.:
Please do us a favour when posting your battery stats:
1. Use your phone in manual brightness mode with brightness set at 50% (if you want, you can increase but not decrease).
2. Do NOT watch videos (local or streaming) for more than 30 minutes during the day.
3. Do not use any app (like browser) for more than 2 hours during the day.
4. If you're having dual SIM, leave both ON.
Now post your battery stats.
In cases where I see people claiming great battery life, I see that much of the battery savings happen because the user was mostly watching videos at very low brightness or just using one or two apps for more than 50% of the time.
These are NOT typical usage. We need to evaluate the effectiveness of changes done by using the phone normally.
For a smartphone, normal usage means leaving all the smart features ON, including but not limited to, WiFi, Mobile Data, Bluetooth, Location, Auto-Brightness, etc. Also keep display resolution at maximum and screen refresh rate at Adaptive (or auto managed by system).
Thanks.
Screen on time without using apps or streaming video? That doesn't make sense. You're basically saying don't use the phone and just leave the screen on. Sounds like a recipe for burn in.
No one is going to leave their screen on without using their phone. Whether it's gaming, social media, streaming media, or web browsing, "screen on time" infers that the user is actually using the phone. Battery age also plays a huge part - my Pixel 5 when new could easily manage 8+ hours of YouTube, but 3 years later it would probably only manage 5 or so....I'm not sure because I keep it plugged in.
"Normal usage" is subjective. My normal usage involves social media and streaming media. Others might do a lot of gaming, which is particularly power intensive. Others might simply use their device as a phone/PDA.
V0latyle said:
Screen on time without using apps or streaming video?
Click to expand...
Click to collapse
That's not what I said (obviously). Please read the post again.
TheMystic said:
That's not what I said (obviously). Please read the post again.
Click to expand...
Click to collapse
That's exactly what you said:
TheMystic said:
1. Use your phone in manual brightness mode with brightness set at 50% (if you want, you can increase but not decrease).
2. Do NOT watch videos (local or streaming) for more than 30 minutes during the day.
3. Do not use any app (like browser) for more than 2 hours during the day.
Click to expand...
Click to collapse
You're saying to limit usage to 2 hours 30 minutes or less, but why would someone's screen be on if they aren't using their device?
V0latyle said:
That's exactly what you said:
You're saying to limit usage to 2 hours 30 minutes or less, but why would someone's screen be on if they aren't using their device?
Click to expand...
Click to collapse
I was referring specifically to just video watching or using just one or two apps for an extended amount of time. Normal usage would involve a lot more like phone calls, video calls, chat, social media, etc.
In most battery stats that show a high SOT, I see that videos pretty much are the main usage (like 4 to 5 hours), browser for a couple of hours, and rarely or minimal use of other apps.
I too can get 7 hours or more of SOT on my S22U if I only watch YouTube at night (minimum brightness). But that isn't typical usage. On an average, I get only about 5 hours of SOT and a standby of about 12 hours (17 hours since last charge) when the battery is around 15%.
Just to prove my point, I'm attaching battery stats from two different devices that demonstrate phenomenal battery life.
In both cases, I used the phones primarily for video streaming over Bluetooth and browsing the internet. Although the Motorola phone has only the most essential apps, the iQOO phone is pretty much a full setup.
I did NOT use any debloat scripts or uninstall apps using ADB. I simply disabled unnecessary apps and services wherever the system settings allowed me to.
CONCLUSION
The battery life is largely a function of the quality of apps installed, network reception and screen brightness. Debloat scripts and other battery saving tips often only provide a placebo effect.