See attached image. Why is it doing this and can i do something about it? Should i even care?
I wouldn't worry about it unless you're having some real-world performance issues. Cpu0 is the core that's used by default I believe. The others scale up needed.
Sent from my VS980 4G using Tapatalk
Related
Is it bad? Or just personal reference? I have mine on 1200 MHz all the time.
Sent from my NookColor using Tapatalk
I do the same thing, and don't notice a change in battery usage when in standby.
The way I figure it (and someone correct me if I'm wrong), these chips were designed to run at 1Ghz anyway, so pushing them 200Mhz over isn't a huge deal.
I don't set it to be on at boot just in case something is goofy in a nightly. I don't mind turning it on after a boot.
Hey all,
So here is my issue. My clock frequency is doing some crazy stuff. For Cm based Roms, under performance the min frequency stays locked at 1026. I can move it down to 384 but it doesn't stick at all after I go back into the performance section its back up at 1026.
When I first get into the performance section the frequency is always at 1026 then quickly drops to 384. This is what happens in SetCpu as well.
Is this just a bug with the Nexus 4 or is something messed up? This happens on any Rom and Kernel (I've tried a good amount) and I've wiped everything every time. Does anyone know whats going on? This isn't my first unlocked and rooted phone.
Any help very much so appreciated.
That's normal. Mpdecison is active in that kernel, whenever you touch the screen the min is raised to 1ghz. Google added this for project butter, it's suppose to improve responsiveness and fluidity of the ui. Its unnecessary because the s4 is extremely fast and doesn't need some a boost, if this was an a8 then I would understand.
Sent from my Nexus 4 using xda app-developers app
I know many will probably just ignore this bug, but I can't because just knowing it's there is pestering. Anyway the GPU is not functioning properly ever since 4.2.2 . Its frequency isn't dynamic.
I would like if some volunteers with faux clock or another GPU reading app could confirm if they have the same issue on 4.2.2 .
Sent from my Nexus 4 using xda app-developers app
Default governor for GPU is ondemand, it's behaving properly.
meangreenie said:
Default governor for GPU is ondemand, it's behaving properly.
Click to expand...
Click to collapse
On demand doesn't entail a static frequency. Previously it would drop to 128 or 200 but now it sticks to 400... That is definitely not normal behavior for this governor. I only had faux clock open and I doubt that app would be GPU intensive.
And this is a problem for me because the the back is noticeably warmer than before despite me having a max of 1ghz and eco mode.
Sent from my Nexus 4 using xda app-developers app
Ah ok sorry, thought you meant it wasn't scaling through the frequencies on light loads.
Dunno may be it's using some kind of low power state instead, I'm using faux stock enhanced kernel and mine is cool at the back with just normal use, also getting great battery life.
Mine only gets hot with heavy gaming or by just browsing with 3g on.
meangreenie said:
Ah ok sorry, thought you meant it wasn't scaling through the frequencies on light loads.
Dunno may be it's using some kind of low power state instead, I'm using faux stock enhanced kernel and mine is cool at the back with just normal use, also getting great battery life.
Mine only gets hot with heavy gaming or by just browsing with 3g on.
Click to expand...
Click to collapse
My issue is that it sticks to 400 which is high state. The only time it changes is when I set it to 487, it'll switch between 487-->400 constantly. Something is triggering a load but these tests are on fresh installs. It's generating heat which isn't good for batteries, especially non removable.
All these issues with my nexus are seriously making me reconsider my purchase -_-
Sent from my Nexus 4 using xda app-developers app
So I just wanted to see how normal this is, didn't see anybody else really mention anything about this. But my phone only really seems to want to use the 1566 MHz frequency range. It almost never uses any other frequency. Any body ever really notice this or is it not really that big of a deal?
https://www.dropbox.com/s/moqxq1agsriin54/2013-07-14 14.38.13.png
Edit: And for what its worth, I'm stock rooted. Left the governor on ondemand, had the I/O scheduler set to deadline for a while but set it back to CFQ with no changes(as expected). And my max frequency is set to 1890MHz, so it should go all the way up there, but there is almost no usage of those other frequencies, especially the higher ones which was weird since there was a while when I was trying to load it up to get to the higher frequencies.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Awizzle said:
So I just wanted to see how normal this is, didn't see anybody else really mention anything about this. But my phone only really seems to want to use the 1566 MHz frequency range. It almost never uses any other frequency. Any body ever really notice this or is it not really that big of a deal?
https://www.dropbox.com/s/moqxq1agsriin54/2013-07-14 14.38.13.png
Edit: And for what its worth, I'm stock rooted. Left the governor on ondemand, had the I/O scheduler set to deadline for a while but set it back to CFQ with no changes(as expected). And my max frequency is set to 1890MHz, so it should go all the way up there, but there is almost no usage of those other frequencies, especially the higher ones which was weird since there was a while when I was trying to load it up to get to the higher frequencies.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm new to android, so my answer may not worth be much.. but what i've noticed in between switching roms and kernels and cpu apps, clean /dirty/whatever.. is that if you have been messing with cpu settings or voltages in any way then they will always have a small possibility of sticking even after you've deactivated or changed them back to default. the only way to get rid of these little bugs, at least for me, was to restore a stock/rooted/cwm nandroid backup or full wipe and full format under Mounts and Storage in recovery.. then flash back to the same rom i'm currently using.
basically.. the cpu can stick and you may need to reformat the system. seems to bethe case to me anyways.. hope it helps. if you can find a way to clear this issue without wiping data, please post the fix.
Stock min CPU freq is 384 MHz.
Is there a benefit of changing this to a lower frequency?
Better battery?
nadastry said:
Stock min CPU freq is 384 MHz.
Is there a benefit of changing this to a lower frequency?
Better battery?
Click to expand...
Click to collapse
I believe after a certain frequency the voltages become the same. Meaning it takes as much power to run a processor at 384MhZ than it does at per say 126MhZ
Sent from my SM-G900T using XDA Free mobile app
Yeah, I believe the above poster is correct, but even if there is a slight variation in voltages, the battery savings are negligent and not worth the possible instabilities or slow downs that result from running the device at a frequency that low. However, if you wish to give it a shot, flashing the hellscore kernel will allow you to drop the minimum frequency to 81 MHz. Please use with caution and make a backup if you choose to proceed.