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
Related
I'm looking at the sys info on quadrant and it shows my current freq: 800mhz.
any one know why it would be showing 800mhz and not 1ghz?
Yep, because it fluctuates.
ahhh... saver modes then... thanks for the info..
now if there's a way to make it static at 1ghz
Why do you want it to run at full power constantly? Why do you want it to suck more power then it needs to?
Believe it or not, your computer CPU does the same thing. It's frequency fluctuates depending on the task at hand. Take this for example: my Core 2 Duo isn't going to always run at it's 2.5Ghz. Intel has something called CPU stepping in it's instruction set and it's meant to decrease power usage, wear and tear, and energy drain when at idle or near idle. Same thing with your phone.
I read the overclocking guide by shaolin95 here
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
In the post it reads to go with the lowest possible UV settings at 1.2ghz.
The post shows -100 on all the clock speeds.
I managed to overclock to 1.2ghz with those settings and being stable. From what I know, undervolting can save battery.
Since the voltage control can go all the way down to -200, has anyone tried having a stable device with some voltages of less than -100 at least on some of the lower clock speeds?
Also, if I was to lower the voltages further on the lower clock speeds, how can i test the lower clock speeds are stable with the low voltages? It seems the stability test will put the CPU to run at the maximum, and Neocore is a CPU intensive application
likiud said:
I read the overclocking guide by shaolin95 here
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
In the post it reads to go with the lowest possible UV settings at 1.2ghz.
The post shows -100 on all the clock speeds.
I managed to overclock to 1.2ghz with those settings and being stable. From what I know, undervolting can save battery.
Since the voltage control can go all the way down to -200, has anyone tried having a stable device with some voltages of less than -100 at least on some of the lower clock speeds?
Also, if I was to lower the voltages further on the lower clock speeds, how can i test the lower clock speeds are stable with the low voltages? It seems the stability test will put the CPU to run at the maximum, and Neocore is a CPU intensive application
Click to expand...
Click to collapse
The lowest Ive gotten is -150 mV. -200mV isnt stable at all. If you want to test it, play some music, surf the web, play some games, and if it doesnt crash, then its stable. Keep adjusting until you cant go long without crashing or until you are happy.
Sent from my SAMSUNG-SGH-I897 using XDA App
Setcpu determines that 1704mhz can be achieved, would it be safe running the GNote at that constantly does anyone know?
Hmm...
I would say, this is depending on more than only the frequency,
if you set the voltages for 1704mhz on e.g. 1650mV u'll get a very hot phone and a hot accu... this will not be good for ur phone, if you're doing this constantly.
But if u find a good compromise between voltage and frequncy, u can do this constantly.
Also you could make profiles in SetCPU so that for example if you're gaming it will set voltage and frequency to 1704mhz and if your screen is off, it setz frequency to 800mhz.
So you have to decide if u'll want to take the risk...
I hope i could help u and sorry for my bad english,
Schnizel.
Aside from benchmarks theres no real benefit from running at 1.7ghz. Most of the time thebphone stays at 200 to 1200mhz
safe?
thought overclocking is always a risk. think nobody here will tell go do it its safe is there ?
and why would you overclock a 1,4ghz dual core in a mobile ?
Thanks, i've seen in a different thread that the voltage would need to be lowered so overheating isnt too bad.
SetCPU gives information on what frequencies are used by percentage and mine is either minimum or max so it suggested its topping out while doing stuff....
1.7ghz is too much for a constant setting.
I had my phone at 1.7 and while watching Netflix on 3G, it would get TOO HOT. and i mean TOO HOT.
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
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.