I'm using arconium 8.0 with doomkernel v19, and recently install setCPU. In setCPU I can choose min/max cpu freq. and different governor. I just wonder what is the original governor of arconium? (or should it be decided by the kernel??) before I adjust anything in setCPU. And if I uninstall setCPU, will everything go back to original?
It's not in Acronium 8, but in the kernel used that the gouvernor and the frequencies are fixed on the init.d script. You can change both the frequencies and the gouvernor on set cpu. When ininstalled, they come back to the original values in the kernel.
If you use stock kernel, there is no settings for the gouvernor and the scaled frequencies.
mekayzer said:
.....When ininstalled, they come back to the original values in the kernel.
Click to expand...
Click to collapse
Are you sure about this?They remain on last setting value if i remember right.
Related
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock so I have no choice to but to stay on stock kernel. I have no ext3/ext4 partition on my SD card in case you ask.
Current ROM: TB Fusion 1.1.2
Radio: 12.54.60.25U_26.09.04.11_M2
Any idea what should I do to solve this issue?
golokipok said:
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock
Click to expand...
Click to collapse
uoooo this is sooo dangerous for your handset... u can "smoke" it...
Any idea what should I do to solve this issue?
Click to expand...
Click to collapse
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
SERGI.3210 said:
uoooo this is sooo dangerous for your handset... u can "smoke" it...
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
Click to expand...
Click to collapse
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ). Is there any effect if I'm using smartass profile on those kernels I've mentioned?
golokipok said:
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ).
i hope that the processor works or not works (don´t crashes a little bit...)
but the reason of your freezes maybe (almost sure) because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
golokipok said:
there any effect if I'm using smartass profile on those kernels I've mentioned?
Click to expand...
Click to collapse
it´s possible, take this explanation, read and judge by yourself what´s the better cpu governor...
smartass (Best explanation i've found paraphrases to: based on interactive, but better.)
----
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
Click to expand...
Click to collapse
Thanks for the info
SERGI.3210 said:
because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
Click to expand...
Click to collapse
You have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Anyway, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
golokipok said:
have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Click to expand...
Click to collapse
you only should do a good over/underclock & set the correct cpu governor for your daily use....
well, you know ho is @MDeeJaay? the developer of MDJ kernels and roms...
he explained smartass with this words:
SMARTASS GOVERNOR - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245.
golokipok said:
, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
Click to expand...
Click to collapse
no, no buddy... i only show the max speed nothing more... i set my cpu concretly like this;
CPU GOVERNOR:interactive
MAX SPEED:1113 MHZ
MIN SPEED:245 MHZ
PROFILE: screen off; 245 MHZ max.
245 MHZ min.
in adition i´m going to modify my syg LOL
haha..thanks again. I'm gonna try playing with the frequencies to see which will suit me
i hope someone can make a stable 1.8ghz kernel without the freeze
IT´S POSSIBLE but i don´t want to try it LOL
i love a lot my DHD
Hi, I am kinda confused by one thing. What is the difference between using SetCPU or similar apps (CPU Master, etc.) vs just setting the Max/Min and governors in Settings -> Advanced Settings -> Performance -> CPU Settings?
If it matters, I am using deck's gingerbread ROM and Tiamat 3.3.7 sbc.
Not much difference really. SetCPU and similar apps are mainly designed to be used on roms that don't have the feature that you're talking about.
peterpunn said:
Hi, I am kinda confused by one thing. What is the difference between using SetCPU or similar apps (CPU Master, etc.) vs just setting the Max/Min and governors in Settings -> Advanced Settings -> Performance -> CPU Settings?
If it matters, I am using deck's gingerbread ROM and Tiamat 3.3.7 sbc.
Click to expand...
Click to collapse
It depends on what type of governor that you want to use. If you plan on using a smartass governor, you should not use SetCPU, but if you are going to use some of the other ones, you may want profiles for screen off, charging, etc. You need Set CPU to do the profiles.
well i dnt think cyanogen has a profile ft like setcpu
djnarcotics said:
well i dnt think cyanogen has a profile ft like setcpu
Click to expand...
Click to collapse
I don't think it does with the default kernel, but if you flash something like SavagedZen kernel with Cyanogen, you will see access to those governors like interactive, ondemand, etc.
I am using the Tiamat 3.3.7-sbc kernel and the available governors are: interactive, conservative, userspace, powersave, performance, smartass.
Any idea on why the settings don't stick? Sometimes I will set the Max CPU at 691MHz, but when I check after a while its back at 998MHz.
Running MikG3.11 along with underworld0.8 kernel nohavs noUv:
SetCPU v3.0.7
Frequency and govenor will not stick after setting. Defaults back to smartassV2 or conservative DEADLINE after screen on/off or after a reboot. Any ideas?
lostsoul77 said:
Running MikG3.11 along with underworld0.8 kernel nohavs noUv:
SetCPU v3.0.7
Frequency and govenor will not stick after setting. Defaults back to smartassV2 or conservative DEADLINE after screen on/off or after a reboot. Any ideas?
Click to expand...
Click to collapse
Do you have another app, like system tuner, or rom toolbox, that has the settings for frequency and sheduler set for "set at boot"?
i.e...perhaps another app is changing it back
MIKESTONY said:
Do you have another app, like system tuner, or rom toolbox, that has the settings for frequency and sheduler set for "set at boot"?
i.e...perhaps another app is changing it back
Click to expand...
Click to collapse
Unless MIK placed something in the system/etc or in the init.d file. It only began doing this when I upgraded to the latest version of SetCPU. Not running system tuner; only running Gemini App which is a task manager and I have SetCPU marked as a Favorite so that it never gets killed. Only other thing I can think of is something in MikTweaks but I havent found any settings related to the frequency/schedulers, only memory settings and i'm using defaults.
Yeah, setCPU doesn't like to keep the CPU settings upon reboot. Just use NoFrills from the Play Store, it's free!
I agree with MBQ,No-Frills CPU is the best one out,its never givin me any problems mate.
6ANONAMUS9 said:
I agree with MBQ,No-Frills CPU is the best one out,its never givin me any problems mate.
Click to expand...
Click to collapse
Yep. It is the best IMO.
AND it's free
Hi guys. I'm using DoomKernel v14, so far so good.
I install setCPU and set a couple of profiles, but when I went to undervolt there was no undervolt tab on set CPU. To handle this, I install SetXperia but when I activate setCPU profiles on boot my Xperia PLAY crashed and reboot soon after boot. So, I guess I should NOT use setCPU and SetXperia at same time, problem is I need to undervolt my PLAY so I can squeeze more power from battery.
I read the documentation (well, sort of...) in SetCPU webpage and it states "The Voltages tab is only available with some custom kernels and devices. If the Voltages tab is available, it will automatically show up between the Governor and Profiles tabs. Otherwise, the Voltages tab is unavailable.".
Now my question is: Why SetCPU is not allowing me undervolt when is obvious that DoomKernel v14 allows this (SetXperia allow me to undervolt after all)?, more important, how do I fix it?, if I change to Lupus kernel will I be able to undervolt with SetCPU (will the undervolt tab be enable in SetCPU)?
Thanks.
Ok, I just install Lupus kernel and still there is no undervolt options in SetCPU.
I'm open to suggestions.
SetXperia can modify your voltages: https://play.google.com/store/apps/details?id=com.SetXperia.Inteks.org
It works with both Doomkernel and Lupus.
jcarbox said:
SetXperia can modify your voltages: https://play.google.com/store/apps/details?id=com.SetXperia.Inteks.org
It works with both Doomkernel and Lupus.
Click to expand...
Click to collapse
Yeah, problem is, with SetXperia I can't set dynamic profiles like in SetCPU...
I have a rooted Mi A2 lite with updated stock Oreo (5 sept). I tried to change cpu governor with an terminal app but only performance seems to work. For example when I changed to powersave governor, actually the cpu is scalled to other frequencies too.
The kernel may override external CPU governor settings, you could try to fine-tune settings with tools like Kernel Adiutor.
thorin0815 said:
The kernel may override external CPU governor settings, you could try to fine-tune settings with tools like Kernel Adiutor.
Click to expand...
Click to collapse
Exactly this app I have installed to check total time spent to different frequencies. Before installing this app I configured through Terminal app powersave governor. After that, Kernel auditor show me that maximum fequency that one core can reach is 652800 mhz, which is correct because I have configured powersave cpu governor. Than I reset time history in Kernel Auditor and after few minutes when I checked time spent on different frequencies I have noticed that other frequencies where used too (in special the last one, 2 ghz). Even if the phone have very little load the last frequency is used a lot. I think this issue have nothing to do whith fingerprint sensor because I have this with and without fingerprint checking active. Maybe cpufreq scalling driver msm have something to do.