governor differences, Reborn 2.2.2

Axe

Well-known member
May 19, 2010
200
3
0
Can someone explain the governor differences as they relate to phone behavior in general, and specifically to Reborn 2.2.2?

No-frills CPU Control shows ondemand, performance and smartass. I guess on v2, the default was ondemand. With 2.2.2, smartass is default, but causes unclean reboots when I drop the max to 600mhz. A drop to 600 required ondemand instead of smartass, at least for me.
 
I'm not really sure how this relates to RebornRom, but from what I googled just seconds ago it appears that things can still vary bewteen developers and kernels. Here is a basic breakdown of some governors (from xda). Do a search on google for android kernel governors and you will get more information.

Performance: Keeps CPU at max all of the time
Powersave:Keeps the CPU at min at all times
Conservative: Keeps CPU at lowest clockspeed possible while trying to perform well
Smartass: works like conservative most of the time but locks the CPU at a low clock speed with screen off (depends on the kernel on exacts)

My google search resulted in many resources for kernel governors.
 
I got another question to add to this thread what do you set the min/max cpu for screen off? i set mine to 126/545 just wondering what other people set theirs too.
 
I got another question to add to this thread what do you set the min/max cpu for screen off? i set mine to 126/545 just wondering what other people set theirs too.
It all depend on the user! I have mine set at 122/480 when screen off.:cool:
 
I got another question to add to this thread what do you set the min/max cpu for screen off? i set mine to 126/545 just wondering what other people set theirs too.

Because I don't much care about battery life I run at 825/825

Sent from my LS670 using Tapatalk
 
Sure, the governor concept isn't exclusive to Reborn Rom, but it's my first overclock situation. No Frills CPU Control just surprised me when it caused repeat reboots.
 
Sure, the governor concept isn't exclusive to Reborn Rom, but it's my first overclock situation. No Frills CPU Control just surprised me when it caused repeat reboots.

Reboots like that are usually because you are clocked too high. Even though we all have the same phone, not all of them can clock to top speed and still be stable. Some have no issues clocking to 844, others cannot clock past 768 without random reboots. You will just have to play around with it and find out which speed gives you the most stability.
 
Reboots like that are usually because you are clocked too high. Even though we all have the same phone, not all of them can clock to top speed and still be stable. Some have no issues clocking to 844, others cannot clock past 768 without random reboots. You will just have to play around with it and find out which speed gives you the most stability.
Hmm. The current Reborn default is 748 with smartass governor. Wouldn't let me drop the speed without reboots. Changed to ondemand governor and it went to 600 just fine. Just didn't seem like a reboot scenario. Reborn v2 was ondemand and underclocked to 600 without a flinch.
 
If it seems to be doing it with only Reborn you may want to browse the Reborn thread and see if anyone else has had the same issue. I know it can be a long process going through all those posts, but you can use the search funtionality of the forums to help narrow down your reading in the thread.
 
Hmm. The current Reborn default is 748 with smartass governor. Wouldn't let me drop the speed without reboots. Changed to ondemand governor and it went to 600 just fine. Just didn't seem like a reboot scenario. Reborn v2 was ondemand and underclocked to 600 without a flinch.

I'm on reborn 2.2.2 with smartass governor clocked to 600, no issues. Just to add to the difference of phones ;)
 
I'm on reborn 2.2.2 with smartass governor clocked to 600, no issues. Just to add to the difference of phones ;)

ditto, though I'm using cpu master, not no-frills cpu. maybe try a different cpu app? I don't know why one would cause problems and another wouldn't, though.
 
ditto, though I'm using cpu master, not no-frills cpu. maybe try a different cpu app? I don't know why one would cause problems and another wouldn't, though.

I just changed from setcpu to cpu master for root users. Setcpu after last update was not working right, the widget would not update with the correct speed (mhz). It would always stay at the highest setting.
 
I got another question to add to this thread what do you set the min/max cpu for screen off? i set mine to 126/545 just wondering what other people set theirs too.

Depends on the governor you use: not required with smartass, in my understanding, as it handles that on its own. I never noticed much difference in battery life by limiting the screen off governor with on demand.
 

Trending Posts

Members online

Forum statistics

Threads
957,948
Messages
6,975,052
Members
3,163,947
Latest member
lefler