So I installed CPU-Z and noticed that all the 8 cores are stuck at 1689 MHz for some reason. Even if the phone is idle, the average cpu usage is above 80%.
Just to confirm, installed CPU Monitor and got the same results.
Can anyone install these apps and post their results here?
CPU-Z: https://play.google.com/store/apps/details?id=com.cpuid.cpu_z
CPU Monitor: https://play.google.com/store/apps/details?id=com.glgjing.stark
Edit: It seems this happens sometimes after rebooting the device and continues for a few minutes. It can also happen randomly. But this does not effect the working of the phone in anyway and the CPU temperatures stay normal.
The frequencies go back to normal after sometime, so nothing to worry about.
Use Trepn Profiler to view the frequencies of the processor cores while you perform other tasks.
Related
I was thinking about installing SetCPU but I have heard stories of it not working very well on the Captivate. Does anyone use this, and if so what kind of battery life improvement are you seeing? Post config settings too please!
Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave
kenjindomini said:
Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave
Click to expand...
Click to collapse
Thanks for these, I was looking for a some decent settings. Mine were close to that to start, but I had no idea what I was doing, haha
I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.
CPU throttles itself. Any effects of setCPU is placebo effect
Err if you set the clocks yourself, you can produce a difference depending on what it's catered towards. I'm sure if I set the max clock to 200 (assuming the app works) for all situations there will be a difference.
Does the stock ROM have a perflock like the EVO that we need to disable?
Also, does the stock ROM automatically underclock at times, or???
I've now verified after clearing user data, the stock firmware already sets the conservative governor and allows it the full range of frequencies supported by the CPU. Only benefit from SetCPU should be profiles - reduce max clock when hot or low battery, that sort of thing.
Sent from my Samsung Captivate
I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already
Default Profile: 800 MHz
Profiles:
Temp > 46 C -- 400 Max 100 Min Conservative
Battery < 40 -- 400 Max 100 Min Conservative
Screen Off -- 400 Max 100 Min Conservative
This now gives my phone life of about 2 days with moderate use (1 hour calls, 1 hour browsing and another 30-45 mins of using apps that need screen on like games, etc)
brandonb81 said:
I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already
Click to expand...
Click to collapse
One thing u got to keep in mind, CPU scales up when woken from low speeds (like when u set for 200 n this takes a second or two). After some R&D i realized 400 MHz when sleeping is optimal with hardly noticeable lag.
Unhelpful said:
I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.
Click to expand...
Click to collapse
well, i have tried playing heavy games like asphalt 5, dungeon hunter, assasin's creed... these all games seemed to work with no lag even at 400 MHz when my battery was less than 40. Most apps I have or used or saw were very comfortable even at 400 MHz. But with multiple apps open, sometimes there was lag, so i set the max at 800 MHz, instead of 1 GHz.
Also, I set my connection to EDGE from 3G. This helped reduce phone from getting heated up with long calls.
I tried using this app myself but uninstalled it after a week. While I'm sure there was some underlying cause, it made my phone never wake up from sleep mode when it turned off.
Honestly thou, I know several android phone owners with s lot of phones That didn't see any real change in their battery life as s result. And based on my experiences, I'd say stay away from it.
Just my 2 cents thou
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi.
I have used CPU Info and CPU gauge to monitor the CPU usage of.my phone. Both these apps display my processor as having a speed of 681.57 MHz. I hope that is not true. Any idea why they say so ?
Ps: which is the best app to monitor my CPU ?
Sent from my Desire HD using XDA App
That sounds right. Even though the phone has a 1Ghz CPU, by default, it doesn't run at 1Ghz all the time. This is to save battery charge as the CPU throttles the speed depending on load. If you put it under full load it will go to 1Ghz for sure. I think when device is in standby it runs at around 200MHz.
You can change that of course, as in what the minimum and maximum values are with a program called SetCPU, but the phone must be rooted.
Hope this helps
It seems the CPU scaling is not set properly with the kernel that cause the phone runs warm and decrease battery life. Checked with CPU Spy and I noticed it often idles around 1134~1026MHz, instead of all the way down to 384MHz.
What you need:
1. Download any CPU control apps, like AnTuTu CPU Master, No-frills CPU Control, CPU Tuner...etc...
2. ROOT!
3. Set the minimum frequency to 384MHz. Leave all other parameters unchanged.
4. Check Apply on boot.
Now check with CPU Spy again you'll see your CPU idles at 384MHz and your phone is running cooler.
Yeah seems the kernel needs to be tweaked a little. It will most likely be patched by .1
Sent from my Nexus 7 using Tapatalk 2
the phone goes in standby, but the cpu stands over 1000Mhz instead of scaling at the bottom?
Mine already goes down to 384mhz without intervention of any CPU apps. At this very moment my CPU is at 1% and clocked at 384mhz.
I don't think doing this will have any effect on battery life or heat.
OverTheBelow said:
Mine already goes down to 384mhz without intervention of any CPU apps. At this very moment my CPU is at 1% and clocked at 384mhz.
I don't think doing this will have any effect on battery life or heat.
Click to expand...
Click to collapse
Mine aswell. Clocks down to 384 Mhz when doing nothing.
Thermal throttling is NOT supposed to throttle to minimum, its not a rollercoaster. It would lag terribly intermittently. Perhaps the threshold needs to be brought up, but the throttling clocks seems about right. Something else that could be done and help a lot is adjust the voltages.
Edit : sorry I misread your post.
OverTheBelow said:
Mine already goes down to 384mhz without intervention of any CPU apps. At this very moment my CPU is at 1% and clocked at 384mhz.
I don't think doing this will have any effect on battery life or heat.
Click to expand...
Click to collapse
Mine does go down to 384MHz. But my point is the CPU does not go down to 384MHz when it should be.
From CPU Spy it seems like when idling the CPU half time stays on 1134MHz and half time goes down to 384MHz.
After the tweaking the CPU goes down to 384MHz all the time, and does NOT affect smoothness or fluency of the system.
richteralan said:
Mine does go down to 384MHz. But my point is the CPU does not go down to 384MHz when it should be.
From CPU Spy it seems like when idling the CPU half time stays on 1134MHz and half time goes down to 384MHz.
After the tweaking the CPU goes down to 384MHz all the time, and does NOT affect smoothness or fluency of the system.
Click to expand...
Click to collapse
Mine oscillates between 1 and 1.5 Ghz while in use, and goes down to 384 when lightly used or when WifFi is on (Wifi prevents my phone from entering Deep Sleep). The rest of the time, it's in Deep Sleep.
384 is the minimum? Damn, I remember when 384 was the maximum.
Sent from my Nexus 7 using xda app-developers app
Hehe, time goes on and we need more power xD
I see my CPU works on 40-50% in idle mode without turning on applications and stuff. I also noticed that the frequency is varying constantly and onle 2 cores are ON, the others are stopped. I think that all of the cores should work in similar frequencies and the CPU load should be around 10%.
Let's see what is the CPU work of the others......
Just installed the app. All 4 cores are active but they seem to be sitting around 300mhz jumping up to 1400 or 1190 as they cycle.
29% cpu load.
Running BBS tho, 300mhz is where my phone sits most of the time and the cpus have no issue going into deep sleep.
Does any have experience with editing the available CPU frequencies? I want to go to a lower frequency than 1113 GHz. So, the opposite of overclocking. From what I understand, it requires either editing the kernel or getting an entirely different one - which I am not capable of doing myself.
As it bugs me (and probably you) how fast the battery drains on Mi 6x, I looked in the CPU settings.
As it looks:
CPU 0 to 3 run on a minimum frequency of 633 GHz each.
CPU 4 to 7 run on a minimum frequency of a whopping 1113 GHz each.
When I put the phone into standby, it continues to run on 1113 GHz on 4 cores. So, is it surprising that Mi 6x drains battery? No. (In addition to a massive screen that requires extra battery, in addition to a smaller battery... very smart engineering here) Imagine you'd put your laptop into standby and it would continue to work with half its processor speed. Not acceptable.
daokris said:
Does any have experience with editing the available CPU frequencies? I want to go to a lower frequency than 1113 GHz. So, the opposite of overclocking. From what I understand, it requires either editing the kernel or getting an entirely different one - which I am not capable of doing myself.
As it bugs me (and probably you) how fast the battery drains on Mi 6x, I looked in the CPU settings.
As it looks:
CPU 0 to 3 run on a minimum frequency of 633 GHz each.
CPU 4 to 7 run on a minimum frequency of a whopping 1113 GHz each.
When I put the phone into standby, it continues to run on 1113 GHz on 4 cores. So, is it surprising that Mi 6x drains battery? No. (In addition to a massive screen that requires extra battery, in addition to a smaller battery... very smart engineering here) Imagine you'd put your laptop into standby and it would continue to work with half its processor speed. Not acceptable.
Click to expand...
Click to collapse
Hello. It is normal for the processor to operate at its normal frequency while the phone is idle. There are plenty of processes in the background. If you have root rights, then you can download an application like (l speed) through this application, I put my battery my processor and the data in the background that allows me a loss of only 1% over a period from 10 am
If I'm not mistaken, your processor cores should go into deep sleep state when you turn your screen off. If they stay on 633/1113 then something is probably keeping the phone awake and battery is going to suck.
Download Dev Check to see how long the cores stay on certain frequencies. If you leave your screen off for most of the time, then most of the graph should show "Deep Sleep" instead of any other frequency.