Hello,
I dont know if it is normal, but when i check with cpu spy, it shows me that i use for 3 hours with the cpu at 1400 Mhz, and i dont remember playing games for the day. Only internet and listening to radio
I thought with the power saver, it would limit the CPU .
Is It normal ?
I think its normal. CPU is stockly clocked at 1400 mhz.
And every app uses cpu, whether low or high, calculations are required by every app and most of these are performed by cpu, so cpu is used.
correct me if i am wrong though.
That is certainly not right, something is keeping cpu at max frequency, so you need to find out what
slaphead20 said:
That is certainly not right, something is keeping cpu at max frequency, so you need to find out what
Click to expand...
Click to collapse
Yeah i think about the same thing
Even when i reset the cpu spy stat, immediatly, it shows me that something is using it at full power for 20s, even when i close down all the apps and clean my memory
DO you know an app who shows which app use how much Mhz ?
Related
Just downloaded Quandrant to run a test, a little bit confused why it says the current clock freq is 800mhz? but says the max is 1200mhz. Is this normal, should it not be running 1200mhz all the time ?
Also I can run the tests, but it won't connect to the server for results or download the results browser yet I can access the interent no problem everywhere else as connected to my home wireless ?
Cheers Guys.
I presume the CPU runs at 800MHz most of the time, but automatically boosts power when it's necessary. No point in having the phone run at 1200MHz when it's idle, just a waste of battery power.
DVC1985 said:
I presume the CPU runs at 800MHz most of the time, but automatically boosts power when it's necessary. No point in having the phone run at 1200MHz when it's idle, just a waste of battery power.
Click to expand...
Click to collapse
IMO the default frequency is 200Mhz, it will be boosted to 1200 for intensive tasks.
Excellent Cheers Guys,
So I take it if I update to the 1500mhz firmware I can set it a little higher and it will go to the 1500mhz as and when it needs it ?
I find that setting setCPU to 450 mhz (900 mhz because of the dual core) the phone works perfectly for my day to day use.
Would underclocking to 450 mhz from 1000 mhz save a lot of battery, or the process of underclocking would take battery to make it equivalent to leaving regular clock.
Not really sure. I've had it set so it goes to 400mhz when the screens off since I had it. I'm sure it helps a little but i doubt it's going to make you get as extra day of battery or anything
Sent from my MB860 using Tapatalk
primeboss said:
I find that setting setCPU to 450 mhz (900 mhz because of the dual core) the phone works perfectly for my day to day use.
Would underclocking to 450 mhz from 1000 mhz save a lot of battery, or the process of underclocking would take battery to make it equivalent to leaving regular clock.
Click to expand...
Click to collapse
I have to intervene here. When you set it to 450 its not 900 because of the dual core. the cores dont add up speeds.
The Atrix doesnt have a 2ghz processor because its 1ghz but two cores.
But to answer your question - yes you would save battery, but the phone would be very slow because you would be at 450 (not 900 or 1ghz)
i have mine set at 600mhz and its fine through the day though i dont do it for battery but to keep it nice and cool(that 1ghz makes it 60C+ easy) but i guess it helps
You have to consider that a lower clock speed means that the CPU must process things for a longer period of time. Sure at a lower speed it will process using less power but the longer period of time it needs to process may mean that the total power consumption is still the same or even higher since the CPU still consumes power simply by being turned on.
palmboy5 said:
You have to consider that a lower clock speed means that the CPU must process things for a longer period of time. Sure at a lower speed it will process using less power but the longer period of time it needs to process may mean that the total power consumption is still the same or even higher since the CPU still consumes power simply by being turned on.
Click to expand...
Click to collapse
+ 1. I'm starting to believe that even the screen-off profile (I have it set on the lowest) has a negative effect on the battery if you use your phone a lot and keep turning the screen back on all the time! Am turning it off now to try..
Sent from my Motorola Olympus using XDA Premium App.
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
Just finally got around to rooting my USA SGP 5.0 yesterday and download SetCPU 2.24. I set the max clock to 400MHz but noticed that it would periodically jump up to 800MHz. Am I to conclude that it is not properly setting the max speed? ie. not doing anything at all?
thanks!
No, this is normal for this device. When you touch the screen, the driver or the kernel increase the speed to 800MHz, but when you let it go, it will jump back to whatever you set in SetCPU. The driver or kernel overwrites the settings, this is done by Samsung to increase the responsiveness of the device. There's nothing you can do about it.
Interesting... So I want to be able to set a profile so that when the screen is off, the max speed is 200MHz. I am assuming that listening to music does not require the CPU to be clocked at max speed. That said, do we know if the CPU automatically clocks down when not needed? If it does, then does that mean that SetCPU is doing nothing to help with battery life?
I don't know how well the CPU clocks down when not needed. Run some tests with and without caping the CPU and see what SetCPU shows you in terms of clock speed. I have SetCPU on my device because i like to set exact limits to my CPU and not rely on some algorithms to figure it out.
It seems to work whenever I switch the governer to ondemand. Conservative, not so often.
Sent from my YP-G70 using xda app-developers app
If you can buy tegrac overclock..you can undervolt any FQ and overclock how many you want.
Sent from my Nexus 7 using xda app-developers app
Nevermind... I just uninstalled SetCPU. I had set it to max out at 400MHz. I surfed the web for a while and then watched youtube for 1.5 hours and noticed that I dropped from 70% to 45% battery life. I've never seen my battery drain so fast, even when watching full movies. I might give Tegrak a try but I think I'm done with SetCPU for now...
There's something odd with Snapdragon 625 on RN4 (according to me).
I have noticed that the maximum clock is half of the times coming down to 1.6GHz or less instead of 2.0GHz, especially when charging when the phone is warm (but temperature isn't high enough to trigger down clocking-- around 30-40 degree Celsius).
This also happens when the phone is not charging and I am doing some task like using apps or playing games when the phone's hardly heating up (afterall, SD 625 is known for its no heating issues).
It looks like whenever I am doing some task that doesn't involve much processing, the max clock comes down (but when I am performing some CPU intensive task such as installing an app, the max clock stays at 2GHz).
I am using interactive governor. PLEASE NOTE THAT I AM TALKING ABOUT THE MAXIMUM CPU CLOCK WHICH IS AFFECTED IN MY CASE. Using Kernel Adiutor to reset max freq. to 2GHz hardly works. It seems like the system ignores my clock settings. Even if i set the governor to performance, the max clock still keeps coming down and going up.
What's the deal with this processor?
Also, all the 8 cores are ALWAYS ON. There's no option for CPU hotplug in Kernel Adiutor.
Please someone shed some light over this.
CPU is thermal throttling not only when CPU is hot, but also when battery is hot. Also it is using a frequency which it needs, if it's using 1.6ghz it means it doesnt need more for whatever you have been doing.
k3lcior said:
CPU is thermal throttling not only when CPU is hot, but also when battery is hot. Also it is using a frequency which it needs, if it's using 1.6ghz it means it doesnt need more for whatever you have been doing.
Click to expand...
Click to collapse
It also happens when the phone is not warm/hot.
Please note that I'm not talking about the current frequency that is being used, I AM TALKING ABOUT THE MAX FREQ that is pulled down and up when I am working (even when just simply using the phone for little tasks which doesn't really heat the phone up).
While using any governor, the max freq should stick to what it is set to and the current freq varies. But here, the max freq is varying along with the current freq. Is this some feature or what?
If this is actually due to heating, is the management so bad that even 35-40 degree celsius makes the CPU throttle? Generally throttling happens at much higher temperatures.
This is 14nm SoC, it has much lower temperatures but also much lower max temp. (throttling start on lower temps)
You can't heat up this CPU to 60C or more like Snapdragon 8xx for example, because it will shut down.
k3lcior said:
This is 14nm SoC, it has much lower temperatures but also much lower max temp. (throttling start on lower temps)
You can't heat up this CPU to 60C or more like Snapdragon 8xx for example, because it will shut down.
Click to expand...
Click to collapse
LOL means I can't make good use of the 2GHz 8 core CPU for long because it'll heat up and simply throttle down. That's too stupid to have a powerful processor.
i am having heating issue. I found no thread discussing.. I am in Miui9 global beta version. Rooted withMagisk using redwolf twrp. My top part of screen heats in normal usage for 5 minute in wifi/data.I have checked the cpu temp( maximum 42) and battery tem( 36 to 38)..But the screen become hot..any work around? Is it a software or hardware issue? how to resolve it