Hi!
I have a D802 with cyanogenmod 10.2 .Everything is perfect except the cpu controlling. My problem is that when i set a maximum cpu frequency it wont stay there. After a couple of minute the phone override it and change it self.. I have tried setCPU , cpu adjuster and the system default settings. Do you have any suggestion. I would like to underclock my cpu because it generates lot of heat while on heavy load.
Thanks for your aswers!
Sincery,
Moqs
I am having the same issue. Have you found the solution?
Related
If I set the min cpu speed to the minimum (245MHz) using SetCPU and then refresh the CPU monitor, it's always at Max (998MHz).
However if I set the min to 384MHz and refresh, it's at 384 (unless something else is going on in the background in which case it might increase a bit).
This is all with the CPU governor set to on-demand
If I set MAX cpu to 245 then the monitor says it's 254, btw, so it seems it can run at that speed fine and the monitor is working ok apparently. It's just with min speed set to 254, it seem to stick at 998Mhz.
Does anyone else see this behaviour?
It this just a problem with SetCPU, or an underlying issue?
well, having played around with it some more, it seems it's actually the cpu speeding itself up so rapidly when monitoring it that it registers max MHz!
If I increase the up threshold, or the sampling rate, so that it doesn't step up a gear so quickly, then the monitor reads 245MHz.
This does raise the question though that if simply pressing the refresh button is enough to up the cpu to max when it's at the default settings, maybe there are better settings for battery life?
Maybe a slightly higher minimum speed is better, so that it doesn't step up all the time (because when it does, it seems to go straight to max).....
Hey guys. i'm using Solarflare rom and it uses snowleopard kernel. What's the right settings to undervolt it? I want to extend my battery life more. I tried to change the values in the undervolt settings but the phone always hangs.
actually i want to know those settings too, my battery seems to be running out so quickly.
Actually SetCPU UV settings are different from phone to phone, you have to find your own good settings. Just start running a day with -25mV on the different speeds and see if it's stable and if so lower it another -25mV the next day etc...
And if you are running out of battery too quickly try to set a screen off profile 200-500MHz with a conservative governor. Also try to recalibrate your battery if you have not done that, that may work wonders on your phones. What kind of battery times are you getting ? Screentime ?
Like Reidar said it's different for every device. Right now I'm using Ninphetamine v2.05 and I'm UC @ 800mHz. With UV I have it at -125mV for 800mHz, 500mHz, and 200mHz with a conservative screen off profile. Been running this for a while now and it has been stable.
A quick tip, if you want to see if a new voltage is stable quickly is to set the voltage and run a stress test in setCPU. And always remember to uncheck the Set on Boot box when testing voltages or even CPU speeds.
Sent from my Galaxy S II using MIUI
With my GS2 i use screen off profile on demand 200Mhz with undervolt of 800mV and work very nice, only thing is a 0,5 sec lag when i unlock my phone
http://forum.xda-developers.com/showthread.php?t=1158102&highlight=SetCPU
Right, so I'm going mad trying to undervolt my CPU.
Sometimes I drop voltages by -50mv, and the phone crashes. Alright I know that the voltage settings have been applied, and it's too low.
On other occasions, I can drop the voltage by ridiculous amounts and have 2.2Ghz running at 600mv (which is obviously impossible), and the phone doesn't crash for two or three days. Obviously the settings aren't being applied.
So my question is, when is the best time to apply voltage settings such that I know they are actually in effect? And is there a way to verify that the voltage settings are actually in effect?
I have been doing a bit more testing.
It seems to me that voltage settings are applied if you apply the setting to all frequency levels (for example some apps like Kernel Tweaker have a -25mv button). Hitting that button twice (for a total of -50mv) causes the phone to crash. However if I were to adjust just the voltage for one frequency at a time, the phone doesn't crash.
Should this be reported to kernel devs? Just want to make sure I'm not doing stuff wrongly.
First of all voltage regulator has some minimum and maximum values, if you go above or bellow those, they will not be applied. If you change voltage just for one frequency, do you force CPU into that particular frequency? Otherwise CPU could be skipping that frequency, for example if you change 600MHz, CPU could be going from 300MHz idle to 0.9GHz skipping some in between values and never actually stay on your changed 600MHz.
I am currently using CloudyFlex 2.6, clean install, but it started with several different ROMs, kernels and configurations...
The thing is: Unless I use conservative governor (tried with interactive/ondemand/intelliactive/alucard), the CPU frequency for the first core stays higher than it should while idling.
Even with less than 10% CPU usage, I find CPU_0 sticking with +1ghz frequency, some time ago the same governors with similar loads slowed down to 300mhz while idling (the expected), now none but conservative seems to respect the established thresholds for slowing down.
For interactive CPU_0 ramps to max_speed, then goes down to defined highspeed_freq parameter and stays there for no good reason or load (3% CPU usage, 6% for several seconds and it still stays at highspeed_freq).
It should go down to 300mhz until new heavy load (80/90% or whatever threshold defined) , but it does not, and I cannot find the reason for it (even played with governor controls without being able to deactivate this battery wasting behavior).
I think something changed recently, but the worst at all is that all kernels seems to be affected (cloudykernel, dorimanx, simple kernel) I already tried disabling all init.d scripts (just in case), disabled xposed framework, uninstalled tweakers, and I cannot find the culprit, clean install, same issue. Different ROMs, same issue... Only conservative slow down as it should.
Any clue on recent cpu handling changes that might produce this behavior? Other users that might try if you see the same behavior?
Thanks in advance
I have been facing this issue that at times, my Mi9t cpu run at max frequency and causes my phone to heat up.
I am still clueless on what causes it. Is there any method to find out which process causes it without having to root/flash my phone as I don't want to void its warranty?
In aida64 what is the cpu governor? Mine is schedutil and cpu downclocks whenever needed. My device is k20
rounakr94 said:
In aida64 what is the cpu governor? Mine is schedutil and cpu downclocks whenever needed. My device is k20
Click to expand...
Click to collapse
I just reset my phone. Downloaded aida64 and the scaling governor is schedutil too.
I am suspecting the notification fixer I used that cause the cpu to go haywire at times but more tests need to be done.
Anyway, do you have any tips on how to get notification all the time without resorting to third party app?
I did off miui optimization, set the background limit to standard, and disable any battery optimization on the apps I need for notification.