What App is everyone using to set their cpu governor along with voltage control? Tegrak? SetCPU?
Also, if you can run 100 mhz on your rom.. Is it even worth using?
Sent from my SCH-I500 using XDA App
Crap wrong section. Move please.
Sent from my SCH-I500 using XDA App
What kernel are you using? If on an OTB kernel, you can use voltage Control. Actually the newest version of voltage control can change governor for any kernel i think, though you can't change voltage settings.
elarson006 said:
What kernel are you using? If on an OTB kernel, you can use voltage Control. Actually the newest version of voltage control can change governor for any kernel i think, though you can't change voltage settings.
Click to expand...
Click to collapse
Otb
Sent from my SCH-I500 using XDA App
Looks like you can change voltages as well on this new version, thanks . Any ideas about the 100 mhz step?
Sent from my SCH-I500 using XDA App
Increasing the voltage for the most part increases the amount of power the CPU consumes (and amount of heat generated!). Higher clock speeds require more power, and therefore a higher voltage. As clock speeds decrease, it's safer to decrease the voltages.
The idea of the having all this control is to allow the user to customize how their phone operates. You can overclock it and go for performance all the way, or keep the clock speeds low so you can decrease voltage and save battery. If you want, you can create a mix between them by decreasing the voltage different amounts on each of the clock speed steps.
Voltage control does the clock voltage and governor for me. I can use 100mhz with CM7 but I wouldn't be too worried about not having it.
Keithn said:
Voltage control does the clock voltage and governor for me. I can use 100mhz with CM7 but I wouldn't be too worried about not having it.
Click to expand...
Click to collapse
Well the thing is i read that it's essentially worthless, as it draws the same voltage as the 200 mhz step... Hence why it's disabled by default
Sent from my SCH-I500 using XDA App
Putting the CPU all the way down to 100 MHz can cause some problems anyway, particularly if you use your phone to play music. A lot of software isn't designed to operate on clock speeds that low. I only go down to 200 MHz.
kallell said:
Well the thing is i read that it's essentially worthless, as it draws the same voltage as the 200 mhz step... Hence why it's disabled by default
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Although you wouldn't notice the difference because it's so little, you will save more battery if you use 100mhz. Because it's on 100mhz you will be able to put it a lot lower than 200mhz. Many people including me is putting -150 with 100mhz.
deaffob said:
Although you wouldn't notice the difference because it's so little, you will save more battery if you use 100mhz. Because it's on 100mhz you will be able to put it a lot lower than 200mhz. Many people including me is putting -150 with 100mhz.
Click to expand...
Click to collapse
Problem for most undervolting that low at 100mhz would be running any music app while the screen is off then upon waking up your phone it would freeze up.
Related
What's the purpose of overclocking and undervolting. What's the reason for the undervolting?
Sent from my ADR6400L using XDA App
It reduces CPU temperature and the amount of battery needed. It is especially useful when you overclock your CPU as both benefits are seen then.
Undervolting typically increases instability, unless it is also in conjunction with underclocking.
If you overclock, you might add voltage to keep the processor running higher than its rated speed. Similarly, if you drop the clock cycles, you may be able to drop voltage and run a cooler, more power-friendly processor.
I am currently underclocking to 768MHz on stock voltage.
Is that why with the speedtweak on 1.92 with the under volting makes the phone lock up.
Sent from my HTC ThunderBolt using XDA App
Likely. The only time I experienced frequent locks was when I was undervolted extremely. If you're running an overclocked and undervolted simultaneously you increase the odds that the cpu won't have enough juice to run properly.
Virtually every device will tolerate speedtweak's extreme undervolt/overclock to 1.41GHz with complete stability. Most will also remain stable running within stock voltage up to 1.222GHz. I've never been a fan of running with a hard cap on speed. Adjusting governor settings makes more sense. I'm also thinking underclocking and using HTC stock voltage scaling is a waste since the CPU will definitely remain more stable at more extreme undervolting at those speeds. Some kernels will run well with a minimum voltage of 650.
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
I use SMARTASS as my CPU speed governor and I set my CPU to 480-748 MHz, seems pretty stable for me.
Sent from my LG-VM670 using xda premium
thaunknownartist said:
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
Click to expand...
Click to collapse
Overclocking values differ from phone to phone. Test it out with different values and use the one which is stable for you.
This was just discussed in the IHO technical-discussion thread, as a matter of fact.
My phone is stable for most stuff at 806 MHz, but sometimes the camera will cause a freeze/reboot. So I run at a 786 MHz max. Your phone will be different; this has to do with minute physical differences between individual chips.
The thing to keep in mind when overclocking is that the processor in our phone (unlike those of many other phones) does not make use of dynamic voltage scaling. There are only two voltage levels: a lower one if the phone is running at or below (or is it just below? correct me if I'm wrong, guys) 480 MHz, and a higher one if the phone is running above. So below 480 MHz, the system will give the processor a certain amount of voltage (period), and above, the processor will get a certain higher amount of voltage (period).
Because of that, the tests that have been done indicate that 806 MHz is the sweet spot for battery efficiency when the phone is in use--and the closer you get to 806, the better. Thus, I've had the following settings for quite some time:
786 MHz min
786 MHz max
Performance governor
which has treated me pretty well. On a day of light to moderate use, I'd end up with 65-75% battery left (occasionally more like 80%), depending on cell signal where I am et al. And it gives me probably the best performance I'm gonna get out of this phone.
However, I very recently decided to change the minimum to below that 480 MHz threshold and see what a lower voltage when idling would do for my battery life. My current settings are:
320 MHz min (may change to 480)
786 MHz max
Smart*** governor
There is actually a noticeable performance decrease when I first wake the phone up, so I may switch governors as well. In any case, I've had those settings for only one full day now, but for that one day the battery life was noticeably better. I'll post an update when I've had a few more days to test.
As always, it's difficult to quantify battery life in a reliable/rigorous manner (much less a universally applicable one), so YMMV.
Thanks to CPU spy, I've recently discovered that the CPU is only running at about 400 mhz while running some pretty demanding games, leading to poor performance. Changing the CPU governor from conservative to smart ass v2 seemed to work at first, but it still only kicks up to the full 1000 mhz every third attempt or so. Any suggestions for reliable CPU in demanding situations apart from setting it manually with 'set cpu' every time I want to play something?
Using cm7 7.1 a streamline kernel.
Sent from my SGH-T959 using XDA App
Use on demand. Conservative will only use your minimum setting
Sent from my SGH-T959 using XDA App
Is ondemand better than smartassv2 for this sort of thing?
Sent from my SGH-T959 using XDA App
Smartass would be better from what I understand smartass is the same as the interactive governor but it just keeps the phone at its lowest frequency when its asleep. With interactive( or smartass) the CPU scales to the highest frequency then it analyzes the load and scales down appropriately which gives a better user experience and I think it would be better for games. Ondemand starts off at a lower frequency then scales up very quickly depending on the load. Conservative tries to stay at lower frequencies as much as possible to save battery it scales up as slowly as possible.
Sent from my GT-I9000 using xda premium
Siyah kernel + Checkrom...
Tried Voltage control, setcpu....
So, for specific frequency under performance governor, i can set any voltage...
Under all other governors it work ok...
Please help.
Sent from my GT-I9100 using XDA
mad_max911 said:
Siyah kernel + Checkrom...
Tried Voltage control, setcpu....
So, for specific frequency under performance governor, i can set any voltage...
Under all other governors it work ok...
Please help.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Performance governor uses only one single frequency (min freq = max freq) and is only useful for testing (benchmarks).
Do not use this governor for daily usage.
Select another governor, such as Ondemand.
You can still set min freq = max freq, if you want your phone to run on only one single frequency.
Thank you. Very good point to use, let say ondemand and min/max at same frequency... why didnt i think of that??... About performance governor, it does feel "snapier" in day to day usage, deep sleep still works and battery is not much worse as screen still uses 60% of battery.... only time when performance governor uses much more battery is if u are using gps or some background task that is preventing phone from going to sleep while screen is off...
Sent from my GT-I9100 using XDA
UPDATE: After some more research i conclude: problem is NOT due performance governor or kernel... Same think happens on any kernel and governor if you set min and max frequencies same(custom voltage set in any program will not apply). Solution is to have minimun 2 steps( for example 1200 min and 1400 max mhz in my case). Further, you can use setcpu profiles for "screen off" etc., and battery loss due this performance governor imitation gets minimal....
Sent from my GT-I9100 using XDA
Just finally got around to rooting my USA SGP 5.0 yesterday and download SetCPU 2.24. I set the max clock to 400MHz but noticed that it would periodically jump up to 800MHz. Am I to conclude that it is not properly setting the max speed? ie. not doing anything at all?
thanks!
No, this is normal for this device. When you touch the screen, the driver or the kernel increase the speed to 800MHz, but when you let it go, it will jump back to whatever you set in SetCPU. The driver or kernel overwrites the settings, this is done by Samsung to increase the responsiveness of the device. There's nothing you can do about it.
Interesting... So I want to be able to set a profile so that when the screen is off, the max speed is 200MHz. I am assuming that listening to music does not require the CPU to be clocked at max speed. That said, do we know if the CPU automatically clocks down when not needed? If it does, then does that mean that SetCPU is doing nothing to help with battery life?
I don't know how well the CPU clocks down when not needed. Run some tests with and without caping the CPU and see what SetCPU shows you in terms of clock speed. I have SetCPU on my device because i like to set exact limits to my CPU and not rely on some algorithms to figure it out.
It seems to work whenever I switch the governer to ondemand. Conservative, not so often.
Sent from my YP-G70 using xda app-developers app
If you can buy tegrac overclock..you can undervolt any FQ and overclock how many you want.
Sent from my Nexus 7 using xda app-developers app
Nevermind... I just uninstalled SetCPU. I had set it to max out at 400MHz. I surfed the web for a while and then watched youtube for 1.5 hours and noticed that I dropped from 70% to 45% battery life. I've never seen my battery drain so fast, even when watching full movies. I might give Tegrak a try but I think I'm done with SetCPU for now...