Can you experienced doods, help out a noob? I have recently rooted my phone (after MUCH research and reading) and just installed Set CPU app. I have been reading about the different settings for Set CPU, and it appears to be device specific, so I wanted to know if any can suggest some stable and useful settings and profiles I can use.
My goal would be to extend battery life and increase erformance while the phone is being used. I kinda guess this is most peoples reason for using this app. Slow the CPU down while the screen is off, and increase it a bit when the screen is on. I am not totally sure why you adjust it while it is charging. And wold this fi into the screen is off profile.
Ok enough rambling, and thanks for any assistance!
Forget SETCPU. Voltage Control is the way to go. For battery life, I would underclock to 100-800mhz and have -100mv all through the range. For performance, 100-1400 mhz (1.5 & 1.6 ghz are heavily overvolted) and have -100mv from 100-1000 mhz and -75 for 1100-1400. Leave the governers and io schedulers where they are.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Forget SETCPU. Voltage Control is the way to go. For battery life, I would underclock to 100-800mhz and have -100mv all through the range. For performance, 100-1400 mhz (1.5 & 1.6 ghz are heavily overvolted) and have -100mv from 100-1000 mhz and -75 for 1100-1400. Leave the governers and io schedulers where they are.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Using the voltage control within SetCPU or a voltage control app?
Thanks
Edit: after installing set CPU my phone seems to be running slower than usual. So, I ran a quadrant benchmark and it is coming up with much lower scores than it did before. Is there any way to set it back to the original cpu speeds with out deleting the app?
Delete setcpu and get voltage control from the market.
Sent from my SCH-I510 using Tapatalk
sneakysolidbake said:
Delete setcpu and get voltage control from the market.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
Thanks, can I use this with imnuts OTB kernal?
gdubya34 said:
Thanks, can I use this with imnuts OTB kernal?
Click to expand...
Click to collapse
you should be able to yeah.. try a different set of settings every day to find whats the most fast and stable on your phone, what works on mine may not necessarily work on yours or someone elses
blazing through on my VZ Droid Charge 4G
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
Tried those settings and my phone froze a few times so I upped the voltage to get it to work for me. This is my first time overclocking a phone. Do any of these settings look strange using voltage control?
100-400mhz uv-75
800-1000mhz uv-50
1200-1300mhz uv-25
I haven't froze yet, although I noticed my battery drains a little faster then normal (that was expected).
hmmm.... The GummyCharged GBE 1.9RC1 8/13/11 kernel is not incompatible with the Voltage control free app.
Error message "Unsupported kernel detected. The kernel your device is running is incompatible with Voltage control."
praveen1789 said:
hmmm.... The GummyCharged GBE 1.9RC1 8/13/11 kernel is not incompatible with the Voltage control free app.
Error message "Unsupported kernel detected. The kernel your device is running is incompatible with Voltage control."
Click to expand...
Click to collapse
GummyCharge GBE is gingerbread which means stock kernel, no voodoo and therefore no changing of voltage settings
blazing through on my VZ Droid Charge 4G
Gotcha! Thanks to that.
Now I have a crazy question below. (trust me there are even more questions all over my mind now)
When they say "ROM", I'm assuming that its collective of Kernel, all the apps and the radio.... Can't we just downgrade the kernel of "GummyCharge GBE" Rom?
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
These gave me a reboot watching netflix on wifi. Will try -25 @ 1300 and see what happens. Thanks for the post though. Its a great starting place for me.
running humble 1.51
Khanusma said:
These gave me a reboot watching netflix on wifi. Will try -25 @ 1300 and see what happens. Thanks for the post though. Its a great starting place for me.
running humble 1.51
Click to expand...
Click to collapse
Yeah those are kinda high 'performance' settings, not all phones like being overclocked or undervolted much less both lol.. Start with it just overclocked for a day or two and see how it runs, however there's gonna be some serious battery drain obviously. Then move on to undervolting slowly like maybe -25 across the board and leave 1400 alone for another day or two... just experiment like this until you have the right balance of speed, stability and battery life. As a matter of fact I toned mine down a bit afterwards and it worked nice:
Overclocked to 1.2ghz (1200mhz),
took out 600mhz frequency and set 100 to -75, then 200-800 at -50, 1000 and 1200 at -25
or if you want battery life and don't mind sacrificing a little performance you can underclock to 800mhz and set all to maybe -75... its a lot of testing to find what works for your phone, if it reboots freezes or lags too much its either overclocked too much or undervolted too much
edit: I also use the free voltage control app from the market, it lets you set min. and max. clock speeds as well as voltage so thats all I need lol
blazing through on my VZ Droid Charge 4G
praveen1789 said:
Gotcha! Thanks to that.
Now I have a crazy question below. (trust me there are even more questions all over my mind now)
When they say "ROM", I'm assuming that its collective of Kernel, all the apps and the radio.... Can't we just downgrade the kernel of "GummyCharge GBE" Rom?
Click to expand...
Click to collapse
Roms are not always all inclusive with a kernel and whatnot.. Most are custom apps, themes, and build/framework remakes to operate on top of the stock roms and will use stock radio and kernel to operate unless a custom radio/kernel is flashed. While most radios and apps will work well with different roms, kernels (being basically the 'engine' for the android OS i believe) are dependant on baseband and will not work by switching them around or flashing one over the other. This is the way I understand it to be anyway, I just know kernels are not compatible between 2.2 and 2.3
blazing through on my VZ Droid Charge 4G
anoninja118 said:
Roms are not always all inclusive with a kernel and whatnot.. Most are custom apps, themes, and build/framework remakes to operate on top of the stock roms and will use stock radio and kernel to operate unless a custom radio/kernel is flashed. While most radios and apps will work well with different roms, kernels (being basically the 'engine' for the android OS i believe) are dependant on baseband and will not work by switching them around or flashing one over the other. This is the way I understand it to be anyway, I just know kernels are not compatible between 2.2 and 2.3
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
Makes sense. I'm sure the apps and radio are dependent on the kernel as it is the core. (like an Operating system that provides the platform for applications to work.)
I'm sure the developers thoroughly test these combinations before releasing any ROM, .
However I want to have some fun updating the kernel on the GC GBE 1.9 that I currently have on my charge with couple other kernels out there....
Will see if I create some magic
praveen1789 said:
Makes sense. I'm sure the apps and radio are dependent on the kernel as it is the core. (like an Operating system that provides the platform for applications to work.)
I'm sure the developers thoroughly test these combinations before releasing any ROM, .
However I want to have some fun updating the kernel on the GC GBE 1.9 that I currently have on my charge with couple other kernels out there....
Will see if I create some magic
Click to expand...
Click to collapse
don't use froyo kernels with GB (as of right now there's only one custom GB kernel, navenedrobs nameless ext4 one), it will just lead to a soft bricked phone... i could be wrong but i think imnuts and imoseyon from team gummy are working on some GB kernel awesomeness
blazing through on my VZ Droid Charge 4G
What about the noop, fifo, bfq, vr options? What do these mean?
Sent from my gummycharged SCH-I510 using XDA Premium App
gdubya34 said:
What about the noop, fifo, bfq, vr options? What do these mean?
Sent from my gummycharged SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Don't touch them. They will either make your phone crawl or have FCs. It hasn't been implemented in the kernel yet.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Don't touch them. They will either make your phone crawl or have FCs. It hasn't been implemented in the kernel yet.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Oh crap, I am not sure what one it was on when I installed it. I think I changed it by accident. right now it is on the vr setting.
Are there any setting s to avoid when messing with the voltage control, and if I delete the app does go back to the default settings?
gdubya34 said:
Oh crap, I am not sure what one it was on when I installed it. I think I changed it by accident. right now it is on the vr setting.
Are there any setting s to avoid when messing with the voltage control, and if I delete the app does go back to the default settings?
Click to expand...
Click to collapse
To avoid: IO schedulers, overvolting (only done in Extreme), and going above 1400 mhz, as 1500 & 1600 are HEAVILY overvolted. Toasted processors=bad magic.
However, you can switch the governers from conservative to performance, but its kind of useless.
If you delete the app it will NOT go back to default...I think. The default io scheduler for imoseyon's kernel is deadline, I forgot what PBJ's is. If you switched it and its still working, don't worry about it.
Sent from my Droid Charge running GummyFroyo 1.9.1
I was looking to see if anyone has the stock unmodified using a stock kernel (or say a modified kernel with no overclock or anything) voltage table. Im already modified and rooted and cant seem to get the stock UCLA3 kernel to load using ones I found in the development thread so I cant check myself.
I just wanted to get an idea of the stock VDD table to see where Im at on my undervolting. Im currently using faux123's kernel which seems to work great.
I know many on here mention they are able to get -100 using fauxclock, but Ive used System Tuner Pro and Ive got it even below that. Then I cut the clock speed down to 1.29ghz and I seem to what I think is almost -200 from where I started and beeing using the phone all day and no reboots. Also ran a few stress tests using this app called StabilityTest v2.3.
So just looking to see out of curiosity what the vdd table looks like stock (if this is even possible).
Thanks
Dixit
-200? unlikely. I was using system tuner with 009m and it was telling me that at 192 I could run at 700 mV, but I know the PPL is actually capable of this. Using fauxclock set at the same -100mV I could see significant battery improvements over system tuner. I deduced that it wasn't actually dropping the voltage that low, and I was correct
for stock vdd check the values in Gideon stock return script in second post of faux kernel thread in dev section
Well attached is the original vdd table from faux kernel. Then the other screen shot is where my system tuner shows its running -200 less. Which I verified by looking at the vdd table itself. Also my system tuner does not allow the voltage to go lower than 800 so my first 8 lower frequencies are all at 800. I'm using the 010 beta.
Remember I'm sitting at a 1.29ghz underclock as I mentioned.
Dixit
Good evening all,
I am currently running vb with the latest above kernel and xda-edition of setcpu...
My question, has anyone found voltages that are stable?
I have always/only used tegrak, when adjusting the voltages I am able to adjust "internal" as well as "core" voltages, as you may know setcpu only allows the adjustment of one voltage. So, I set all levels to the "internal" voltages that worked for me on tegrak(scaling set to smartass), everything was working fine until I rebooted the phone... At that point the phone would boot then freeze after the third media scan, I had to flash back to the b1 kernel to get back up and running.
Any advise would be greatly appreciated.
Thank you in advance!
Sent from my SGH-T959V using xda premium
You're trying to undervolt? Anton's b5 in undervolted. I'd stick with his recommended values.
How do you actually implement these voltages? I've only used Tegrak so this is new
Sent from my SGH-T959V using xda premium
QUIETLYloud , I dont't have paid Tegrak so I cannot make a thorough test.
I tried using very old Ultimate version available someplace on the web, and it does in fact seem to mess the phone up. I didn't need to reflash, but had to uninstall Tegrak, reboot, clear caches, and rescan SD for errors. Google says that there were issues with Tegrak module and custom kernels, but they were supposedly fixed around version 1.4.
I tied the new free version 1.6.7 from Market. It doesn't let me do much (like setting on boot), but at least it seems to work correctly with frequencies.
The setup with OC kernel is a little different. Before, if you wanted to OC, you would go and enable CPU Max Frequency, which would replace 1 GHz. Do not go there! The kernel already has all overclocking frequencies available. Instead set the Scaling to the highest frequency you want to use (let's say 1.2 Ghz, which is CPU Level 2). Then go to Optimization and set desired voltages for the frequencies you chose. No need to change anything for frequencies above you max scaling, the CPU will not go there anyway. Maybe it's a good idea to completely clear Tegrak data and start setting it up form scratch.
Let me know if you succeed.
Btw common Google knowledge doesn't seem to recommend lowering internal voltages. You will not gain much, there is just not a lot of current draw there. It's the core that draws a lot of current.
EDIT: Hmm... Tegrak seems to have a problem with smartassV2 governor. If the scaling in Tegrak is set to use anything but all frequencies, including 1.4 Ghz, the governor will never lower the frequency from the highest selected. The kernel itself (with SetCPU or without) doesn't have this problem, it's only when proprietary Tegrak module is loaded.
AntonX...
I decided to scrap tegrak for the time being and use what you recommended with setcpu and left voltages alone until I have a better understanding, since doing so haven't had any problems
Sent from my SGH-T959V using xda premium
Btw I said before I set the default voltages kind of safe, even if they are slightly undervolted. I'm running the kernel UV-ed a little more with SetCPU for second day without any issues. Here are my numbers right now:
1.4 - 1350
1.3 - 1300
1.2 - 1275
1.0 - 1250
800 - 1175
400 - 1025
200 - 925
100 - 900
Hi guys
I apologize for some noobness coming this way, but I don't understand. Kernel beta5 is oc/uv - what does it mean if I don't use setcpu/tegrak?
Will kernel behave other than prior versions?
And if I decide to do use setcpu? What good does it make if uv makes no change (according to Antonx) and oc will only drain the battery even more, I mean, phone is pretty much fast, so why bother oc it?
Thanks!
Sent from my SGH-T959V
I have two stock Verizon Samsung Galaxy S3's. Both are running System Tuner. Neither CPU is running at speeds above 1GHz, despite the fact that each should be capable of 1.5GHz. I've tried increasing clock speed using ST and am unsuccessful. I've rooted one using the procedure at http://forum.xda-developers.com/showthread.php?t=2046439, and am still unable to get the CPU to run at anything above 1GHz. I've installed SetCPU, and still no success. I select 1500Hz, but SetCPU max remains at 1026Hz, even with "set at boot" selected and after restarts.
Questions:
- is this a limitation imposed by VZW or the kernel running on the phone?
- is it considered "overclocking" just to get the CPU to run at speeds higher than what it currently does (i.e. 1GHz) even if those higher speeds (up to 1.5GHz) are within the advertized specs of the CPU?
- what is needed to get past this? Is it even possible to increase clock speeds using the stock kernel/ROM, or is another kernel or ROM needed?
Thanks.
cesniff said:
I have two stock Verizon Samsung Galaxy S3's. Both are running System Tuner. Neither CPU is running at speeds above 1GHz, despite the fact that each should be capable of 1.5GHz. I've tried increasing clock speed using ST and am unsuccessful. I've rooted one using the procedure at http://forum.xda-developers.com/showthread.php?t=2046439, and am still unable to get the CPU to run at anything above 1GHz. I've installed SetCPU, and still no success. I select 1500Hz, but SetCPU max remains at 1026Hz, even with "set at boot" selected and after restarts.
Questions:
- is this a limitation imposed by VZW or the kernel running on the phone?
- is it considered "overclocking" just to get the CPU to run at speeds higher than what it currently does (i.e. 1GHz) even if those higher speeds (up to 1.5GHz) are within the advertized specs of the CPU?
- what is needed to get past this? Is it even possible to increase clock speeds using the stock kernel/ROM, or is another kernel or ROM needed?
Thanks.
Click to expand...
Click to collapse
Never tried to OC stock kernel although some say you can if have root. Sure you are not on Power Saver mode. Will clock down to like 1100.
prdog1 said:
Never tried to OC stock kernel although some say you can if have root. Sure you are not on Power Saver mode. Will clock down to like 1100.
Click to expand...
Click to collapse
That's exactly what it was. I was only checking the governor settings with the CPU and never checked or thought about the Android level "Power Saver" mode. Once I unchecked the CPU box under "Power Saver", I was able to get much better speeds out of the CPU.
Thank you very much.