Performance governor @ 500mhz - AT&T Samsung Galaxy S II SGH-I777

With talk of late about smooth scrolling and step time between frequencies I got to thinking. What draw backs are there to running at 500mhz with the performance governor?
I know that means it's forcing 500mhz when it could be 200mhz. And while ideally the processor should be as low as possible, 500mhz is pretty low.
But the phone has really felt so smooth! Scrolling is near jitter free and things seem to open much quicker, average smaller things, not intense games obviously.
With screen off deep sleep should be no problem. And how many times does the phone drop down to 200mhz while in use? If I'm not using my phone the screen is off. Seems the the extra battery spent would be made back up by it not going over 500mhz.
So I guess my questions are: Has anybody tried this for am extended period of time? And/or is there really that much processor strain by forcing 500mhz during use?
Sent from my páhhōniē

---

Huh? Performance governor fundamentally fixes the clock at maximum stock speed (1.2 GHz).
Do you mean setting the minimum for ondemand/conservative to 500 MHz when the screen is on? I do this on my device. When the screen is on, the power consumption difference between 200 MHz and 500 MHz is very small, especially thanks to cpuidle, which gates the clock when the CPU is not loaded, eliminating most of the usual linear contribution of clock frequency to power consumption.

---

Processor is set to 500mhz max 200mhz min with screen on.
The governor set to performance to keep it at 500mhz while screen is on.
If power difference between 200 and 500 is not that big, then that's how I'm going to leave it for now. Everything has been very stable. No slow downs on normal phone operations, no force closes, no sod's, or soft reboots.
Sent from my páhhōniē

---

Performance governor fixes the CPU at 1.2 GHz... Not sure what you're talking about.
Not sure why you would want to downclock your device so much.

---

If you move the max slider in setcpu to 500mhz and set the governor to performance, it pins the CPU at 500mhz, not 1.2ghz
Sent from my GT-P7510 using Tapatalk

---

K Rich said:
If you move the max slider in setcpu to 500mhz and set the governor to performance, it pins the CPU at 500mhz, not 1.2ghz
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Yahtzee!...er, correct
And so far everything had been great. Stable, no freezes. I did undervolt it pretty low @ 500mhz (dropped it 75mv) and it got choppy. But upped the voltage 25mv and been silky smooth ever since. Battery life hasn't seemed to be effected much. I was hoping for more but aiming to break even. I'm ok with same battery life.
Turkbey rom / latest entropy512's dd
Sent from my páhhōniē

---

I'm running miui, at 500max on performance I see skyrocket class jittery performance. Maybe its miui vs stock based that's giving that difference. My phone spends most of its time at 500 when not charging or deep sleep, according to CPU spy. So the difference in battery should be minimal, but to me the difference in performance is very noticible. YMMV.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy S II (i777)

---

Hehe, you're doing the exact opposite of me - I have things set to conservative with 500 MHz minimum when screen is on.
(Why? Because the diff. betwen 200 and 500 in terms of power consumption is far less than the baseline power consumption of the screen.)

---

Entropy512 said:
Hehe, you're doing the exact opposite of me - I have things set to conservative with 500 MHz minimum when screen is on.
(Why? Because the diff. betwen 200 and 500 in terms of power consumption is far less than the baseline power consumption of the screen.)
Click to expand...
Click to collapse
Same set up here.
Sent from Wernicke's Area

---

500mhz starting giving me issues. Switched to 800mhz.
Had the phone heat up pretty hot one time. I'm guessing the cpu limit somehow didn't kick in. So instead of performance governor keeping the phone at 800mhz, I set the high cpu limit to 800mhz and the low cpu limit to 800mhz. Since that is now keeping it at the speed I want, the governor can be set to conservative, or whatever you want other than performance, and I don't have to worry about overheating or excessive battery drainage if something goes wrong again.
So far it's been working great. Haven't noticed a change in battery life.
Sent from my páhhōniē