Anyone who is running Setiron's kernel, what undervolt settings work best for you? I can't seem to find any that are stable
Some phones can't be undervolted.
Start low.
I have: 125,125,100,75,50,25 (Top to bottom in the program). Set scheduler to noop.
don't 'Set on Boot', that way if it screws up, you can recover. Once you think it is good to go, then set on boot.
If it locks up, go with less. Just keep experimenting to find your threshold.
Thanks your uv settings work great for me!
Sent from my GT-I9000
I ran -125 on all of them without issue. Just play with it until find the sweet spot.
Sent from my SAMSUNG-GT-I9000 using XDA App
Related
So I found a kernel on the Fascinate forums that was built off of our EC10 froyo source that was from nemesis2all and I saw that he had added the ability to overclock and undervolt from within the ROM so I installed it just trying (backed up of course) and found that it does indeed work.
I then got the Voltage control app from the market and started playing around doing Quadrant scores throughout after each change. I found that at 1200 mhz I was getting 1600s instead of 1400s and the phone ran great. But when I tried 1400 mhz the phone froze up and restarted while doing the CPU section of the Quadrant test so I reverted back.
My question is, what would be safe to stay at for general use?
Second question, how do you use the voltage app to undervolt I see the settings but I don't know what to set them too.
Here is the link to the kernel
1200 has proven to be the most stable overclock, any higher and it will freeze up eventually.
With voltage control, the way it works is that you set the max clock and then it will give you increments that the phone will automatically clock to within the guidelines you give it. Then for each increment you can set the voltage it will use. Just look around and experiment with voltages, see how low you can go without having issues and never set it to apply at boot unless you know that's what you want, other than that go crazy and a reboot will fix it if you have a problem.
I recommend keeping setCPU installed along with it, that way you can still force it to underclock or overclock or whatever. It all depends on how much you use the phone and what for.
Sent from my MIUI SCH-i500
Thanks sage I'm glad someone who knows what their talking about replied lol.
Swyped using USCC Mesmerize
I've been running overclocked at 1.3 and undervolted at least 50 for a couple days now. Only one issue and I'm not even sure it was related as it janet happened again. I posted my settings in the otb thread if you're curious.
Sent from my SCH-I500 using XDA App
akellar said:
I've been running overclocked at 1.3 and undervolted at least 50 for a couple days now. Only one issue and I'm not even sure it was related as it janet happened again. I posted my settings in the otb thread if you're curious.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
H'm, I tried going up to 1.3 and it would freeze up after 5 or 10 minutes every time.
Like I said, 1.2 is the only one that has proven to be safe for everybody... not each phone is exactly the same and if akellars CPU has a soldering that is done a little bit different than mine, it might allow him to clock a little higher. who knows
Sent from my MIUI SCH-i500
I've been running it for a week @ 1400 -25 undervolted and haven't had any issues. The new 1.6 gives me trouble. I don't think there's enough overvolting in that one to make it stable for pretty much anyone. I use the 1400, 800, 400, 200 steps all undervolted @50 except 1400 which as mentioned is -25. Battery life is good because during sleep it doesnt really hit the high end and by not having the other steps its snappy when in use. Fastest this phone has been by far. I don't use setcpu because I think it and the voltage app conflict. That was nemisis's instruction to install it.
Sent from my SCH-I500 using XDA App
sageDieu said:
H'm, I tried going up to 1.3 and it would freeze up after 5 or 10 minutes every time.
Like I said, 1.2 is the only one that has proven to be safe for everybody... not each phone is exactly the same and if akellars CPU has a soldering that is done a little bit different than mine, it might allow him to clock a little higher. who knows
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Yup I'm just lucky 1.4 worked for me too but I didn't see much of a performance difference so I didn't see the need to stress the cpu out anymore than I already was. battery life had been awesome for me with my setup as well.
Sent from my SCH-I500 using XDA App
My Undervolt settings i been running see attachment. Also power-save Screen off Profile doesn't play nicely with setting try interactive. Turn off background data if you don't absolutely need it at all times
Set cpu 1000 - 100 Conservative
Screen off 200-100 Interactive
Rom: Cyanogenmod nightlies
Kernel: Netarchy 1.3.6 BFS
Is that UV setting stable?
Sent from my Nexus S c",)
Yup for my device atleast, if your device freeze then reboots try adding 25mv until stable
Sent from my Nexus S 4G using XDA App
My phones not real friendly with UV. I can only do -40 across the board. This sucks. Lol.
Btw, i have the gsm not 4g.
Sent from my Nexus S c",)
I tried your settings with no success. Time for some trial and error tweaking.
using Tapatalk.
Yea i literally had to let my phone freeze and reboot until i found the right UV for each frequency, every device respond differently to certain UV settings, also the latest update 2.3.5 Radios may also help battery life with reception fix just test and find out
Running the infused v1 rom... and it constantly kills setCPU...
when i reload it, the values in the "advanced" tab are always back to -1 and they SHOULD be
80000
70
30
0
5
Thats on the Conservative governor...
how can i keep setCPU from being killed?
You don't need to have SetCPU running, you just need to save your values.
One way to make sure its running when you think it's not is to set up a profile for "charging" set the values to something other that stock (obviously) select the setcpu widget then plug your phone into the charger, if values change (may take a second or 2) than your all set.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Ph0z3 said:
Running the infused v1 rom... and it constantly kills setCPU...
when i reload it, the values in the "advanced" tab are always back to -1 and they SHOULD be
80000
70
30
0
5
Thats on the Conservative governor...
how can i keep setCPU from being killed?
Click to expand...
Click to collapse
Which kernel? I don't know about the default kernel with Infused v1, but with bedwa's Infusion kernels there's some code in the kernel that consistently overrides the up_threshold and down_threshold values in the Advanced tab.
SetCPU isn't dying - it's just the kernel and the Advanced tab don't get along. All other functions (Voltage on Infusion kernels, min/max/governor changing profiles on all kernels) should function fine.
Edit: nash2000 has a good suggestion. As a test set a "charging" profile with a clock limit - if this profile gets activated when you plug the charger in, setCPU is working fine.
nash2000 said:
One way to make sure its running when you think it's not is to set up a profile for "charging" set the values to something other that stock (obviously) select the setcpu widget then plug your phone into the charger, if values change (may take a second or 2) than your all set.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
Alright... did that... seems to be working fine now.
i guess the v1 kernel is just crappy battery life and the kernel is janky...
seems everyone else is having issues with v1. Guess i need to load v2
My setcpu has been activing funny as well, only since gingerbread install. Ill keep my profiles the same (low values with screen off and when charging) now when I turn my screen off I can't open my phone back up, I have to pull battery. My values are real low but worked fine on froyo. Now I'm playing with juice defender and a few others.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
+1
I gave up on it....
nash2000 said:
My setcpu has been activing funny as well, only since gingerbread install. Ill keep my profiles the same (low values with screen off and when charging) now when I turn my screen off I can't open my phone back up, I have to pull battery. My values are real low but worked fine on froyo. Now I'm playing with juice defender and a few others.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
There's a known Sleep of Death issue with screen-off profiles that limit the phone to below 800 MHz. It was fixed in Froyo but I'm not sure if gtg has pulled netarchy's fix into his Gingerbread kernels yet.
Entropy512 said:
There's a known Sleep of Death issue with screen-off profiles that limit the phone to below 800 MHz. It was fixed in Froyo but I'm not sure if gtg has pulled netarchy's fix into his Gingerbread kernels yet.
Click to expand...
Click to collapse
hhhmmm... guess ill find out when i load GB
wanted to report that i am using setCPU to OC to 1600, UV every frequency, as well as set sleep/charging profiles on GTG's GB ROM.
the sleep profile is set at 400, and so far no SOD issues. i'm even UVing that frequency minimally.
so far (a few hours, since bedwa's new kernel dropped), completely stable.
UVing with setCPU on froyo was a certain SOD, as soon as i set the values - so far, so good on GB!
I'm sorry for the noob question but I really don't understand voltage terms and what's it for and how it work I was wandering if anyone could explain it to me?
In the past I would use set CPU and create a few profiles and would be done with it but I been reading on the forums about setting voltages higher and lower for better performance.
Currently i'm on eagles blood 2.3.5 ROM, trinity t15 (fun) kernel.
Any help would be much appreciated.
Sent from my LG-P999 using XDA App
Don't know what it does don't use it
Sent from my LG-P999 using XDA App
ritthyhang said:
I'm sorry for the noob question but I really don't understand voltage terms and what's it for and how it work I was wandering if anyone could explain it to me?
Click to expand...
Click to collapse
It's to save power and get better battery life. You lower the amount of power the chip gets at various clockspeeds until it starts not working correctly, then back up to a voltage at which the chip is stable at that clockspeed. Some chips can handle lower voltages than others while still working correctly.
Overclocking = get better performance
Undervolting = get better battery life
Both can lead to phone instability if you set the values to extremes.
Thank you for the info
Sent from my LG-P999 using XDA App
lannister80 said:
It's to save power and get better battery life. You lower the amount of power the chip gets at various clockspeeds until it starts not working correctly, then back up to a voltage at which the chip is stable at that clockspeed. Some chips can handle lower voltages than others while still working correctly.
Overclocking = get better performance
Undervolting = get better battery life
Both can lead to phone instability if you set the values to extremes.
Click to expand...
Click to collapse
So lemme ask this how do I undervolt and what voltage is safe to undervolt?
Sent from my LG-P999 using XDA App
ritthyhang said:
So lemme ask this how do I undervolt and what voltage is safe to undervolt?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It all depends on the kernel your using and if it supports UV, it should say if it does in the name of the kernel tho(just look for uv ) Setcpu 2.2.4 will allow you to change voltages only if your kernel/rom support it.
you can safely undervolt -50 -75 at most all the way up to 1.0ghz-1.1ghz i wouldn't undervolt past that.
d12unk13astard said:
It all depends on the kernel your using and if it supports UV, it should say if it does in the name of the kernel tho(just look for uv ) Setcpu 2.2.4 will allow you to change voltages only if your kernel/rom support it.
you can safely undervolt -50 -75 at most all the way up to 1.0ghz-1.1ghz i wouldn't undervolt past that.
Click to expand...
Click to collapse
So what your saying is I can use setcpu to change the voltage?I just recently changed kernels I saw that option available but I didn't understand how to use it.under voltages it shows all the GHz underneath it it shows 0.From here what do I do?, do I go too each GHz profile and -50 from all of it?
Sent from my LG-P999 using XDA App
I've looked and searched everywhere but I can't find anything like this. On all of the JB roms, all of a sudden, my CPU frequency sits at the highest speed and won't move no matter what governor I use. Is there any way to solve this, I'm really at a loss. I installed CPU spy and it's showing that deep sleep is not used and that only 1200 MHz(the highest CPU setting I'm using) is being used. Help please. Thanks in advance.
if a reboot doesn't fix it, you need to wipe and reflash
qkster said:
if a reboot doesn't fix it, you need to wipe and reflash
Click to expand...
Click to collapse
Yeah, tried that already, a few times. I think it has something to do with my sd card. I'm gonna format it and see what happens.
So..I went all the way back to stock, and came back to JB and still experiencing the same problem. When I flash a JB rom, the CPU frequency gets stuck at the highest frequency until I select a different governor and reselect the one I want to use. Any help would be appreciated.
which roms have you tested? and are you using nstool to adjust your governors and schedulers?
-illest- said:
which roms have you tested? and are you using nstool to adjust your governors and schedulers?
Click to expand...
Click to collapse
I've tested avatar, Beanstalk(my daily driver), Cyber...
Nd yes, I am using the built in performance menu, but it has the same settings as nstools
Sent from my SGH-I997 using xda app-developers app
Are you using NSTools along with the built in performance menu? I had the same problem on Beanstalk with the SmartassV2 governor where my cpu would stick at 1200 mHz, but once i removed NSTools, smartass worked fine. perhaps try disabling or removing nstools?
Oh okay, I see what you are saying. I really like BLN, so you just don't use bln anymore?
Sent from my SGH-I997 using xda app-developers app
well try and see if it works. if your using beanstalk, then you can just use the BLN control - free app that scott has included as an addon. this app will enable BLN with timeout. you just can't change the blink speed with this app.
Well I disabled nstools and everything seems to be back in order. I'll report back if I see something else.
Sent from my SGH-I997 using xda app-developers app