Quick question to anyone out there: Is battery life the only benefit of having all 100Mhz frequencies hit as you progress up to a max clock frequency? I know it's part of the determination of what the system needs, but if you trimmed down some of the options wouldn't it result in a more "snappy" experience?

It seems to me that running CPU cycles on those relatively useless, in-betweener clock speeds is a waste. All they usually do is have a cycle to determine that you need to move up to the next one.

Wouldn't a decent compromise be limiting the available CPU clocks to something like:
100Mhz
200Mhz - (maybe not even necessary)
400Mhz
800Mhz
<MAX> - This is whatever you set the ceiling to be.

I'm just curious on the rationale as I've been messing around with various kernels and their respective Governors recently. Smartass on DMz Nightly #3 sort of did this with only the 500Mhz and <MAX>, but having a lower one than 500Mhz could be more efficient while the phone is on the charger or whatever passive services are running, right? And I think Immortality does something similar to what I stated above when using ondemand, but I had a couple of sleep of deaths when running Immortality (even when not using smartass) to keep it just shy of a daily driver for me. Not to mention I really like the SIO scheduler in the new DragonMOD kernel Very nice SD read/writes and DB scores.

Or at least an option to disable certain frequencies.

Not sure if this is possible, but if it is, I would love to have the option!

Originally Posted by kaiser_bun

Quick question to anyone out there: Is battery life the only benefit of having all 100Mhz frequencies hit as you progress up to a max clock frequency? I know it's part of the determination of what the system needs, but if you trimmed down some of the options wouldn't it result in a more "snappy" experience?

It seems to me that running CPU cycles on those relatively useless, in-betweener clock speeds is a waste. All they usually do is have a cycle to determine that you need to move up to the next one.

Wouldn't a decent compromise be limiting the available CPU clocks to something like:
100Mhz
200Mhz - (maybe not even necessary)
400Mhz
800Mhz
<MAX> - This is whatever you set the ceiling to be.

I'm just curious on the rationale as I've been messing around with various kernels and their respective Governors recently. Smartass on DMz Nightly #3 sort of did this with only the 500Mhz and <MAX>, but having a lower one than 500Mhz could be more efficient while the phone is on the charger or whatever passive services are running, right? And I think Immortality does something similar to what I stated above when using ondemand, but I had a couple of sleep of deaths when running Immortality (even when not using smartass) to keep it just shy of a daily driver for me. Not to mention I really like the SIO scheduler in the new DragonMOD kernel Very nice SD read/writes and DB scores.

You can have a snappy experience even with the 100mhz steps depending on how you have the governor tuned. Also with the way I currently have it tuned it stays towards the lower frequencies more aggressively. To be honest I agree that I wanna get rid of most of the steps but the 100mhz was asked for specifically. The stepping I want is

100,200,400,600,800,1000,1100,1200,1300

I tend to tune my governors to aggressively down clock when not in use just so u guys know

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by creeve4

Or at least an option to disable certain frequencies.

Not sure if this is possible, but if it is, I would love to have the option!

It is possible but the system will select a frequency based on load and isn't necessarily going to use each of the frequencies in the table or even touch on em when clocking up and down

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by creeve4

Trying Beta 2 with Project-V, my phone reboots every time the screen turns off when using Smartass, SmartassV2, or Scary.

While I was running CM7, I used SmartassV2 exclusively. Any idea why these governors are not playing nice with my phone when running Froyo?

I'm using Voltage Control to set the governor, scheduler, and frequencies (which I also did on CM7).

Not getting the reboots, just added the new govs. If people can get me logcats and the/proc/ last_kmsg that would help alot

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by ECOTOX

You can have a snappy experience even with the 100mhz steps depending on how you have the governor tuned. Also with the way I currently have it tuned it stays towards the lower frequencies more aggressively. To be honest I agree that I wanna get rid of most of the steps but the 100mhz was asked for specifically. The stepping I want is

100,200,400,600,800,1000,1100,1200,1300

I tend to tune my governors to aggressively down clock when not in use just so u guys know

Sent from my Galaxy Nexus using Tapatalk 2

Those are the steps I like too, except for 600 MHz.

I made an init.d script to modify the governor settings, but none of the values are sticking. I ran the script through Script Manager and everything wrote just fine, but none of the values stuck. What do you suggest for tuning the governor?

Originally Posted by creeve4

Those are the steps I like too, except for 600 MHz.

I made an init.d script to modify the governor settings, but none of the values are sticking. I ran the script through Script Manager and everything wrote just fine, but none of the values stuck. What do you suggest for tuning the governor?

Depends on what ur goin for...performance? Balanced? Battery? Also why not on 600?

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by ECOTOX

Depends on what ur goin for...performance? Balanced? Battery? Also why not on 600?

Sent from my Galaxy Nexus using Tapatalk 2

My phone seems to mostly use 100, 200, 800, 1200. 600 doesn't seem necessary.

I'm trying to configure lulzactive for performance, but can't get any of the values to stick.

Originally Posted by ECOTOX

You can have a snappy experience even with the 100mhz steps depending on how you have the governor tuned. Also with the way I currently have it tuned it stays towards the lower frequencies more aggressively. To be honest I agree that I wanna get rid of most of the steps but the 100mhz was asked for specifically. The stepping I want is

100,200,400,600,800,1000,1100,1200,1300

I tend to tune my governors to aggressively down clock when not in use just so u guys know

Sent from my Galaxy Nexus using Tapatalk 2

Yea, I get what you're saying. It'd be interesting to see stepping you proposed. I was thinking of the 100, 400, 800, MAX only because it's close to what your Nighly #3 was with Smartass. Just having 500 and MAX on that one kept the phone very responsive, but I think the battery could see a minor improvement (if the governor plays nice) with the extra 2 steps to work off of.

I'm getting a feast or famine kind of experience with what I've been trying out recently. Scary seems to work as a better middle ground with your new kernel (Beta 1) in that some of those middle clocks actually get some usage. Smartass takes a little to long to get to the top clocks for my tastes, but I'm willing to take some hits on the battery life for the sake of speed so that's just my take.

Either way I'm a big fan of your kernels. Even though I keep a copy of Overstock on the ready as a just in case DMz Nightly #3 is my new goto when I have to fall back.

I've been using scary with 100 to 1300 and screen off profile to 100 and 500 smartass. Been working pretty good.

Sent from my SGH-T959 using xda premium