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
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
ok, I have a rooted Evo 4G running Fresh 4.0 rom, what profile settings should i use in order too make the battery last , or just some other suggestions on maintaining battery life while keeping the phone running smooth.
thanx
frankie253 said:
ok, I have a rooted Evo 4G running Fresh 4.0 rom, what profile settings should i use in order too make the battery last , or just some other suggestions on maintaining battery life while keeping the phone running smooth.
thanx
Click to expand...
Click to collapse
Create a screen off profile & set it to 245/245 max/min with smartass governor or conservative. When I was using SetCPU, I undervolted so that while my screen was on, the max was ~600. For the most part I rarely needed it any higher than that for my usage. However if you want to keep it at 998 or above, you will still benefit from a screen off profile.
I only run AOSP, so Sense may need more juice with the screen on.
plainjane said:
Create a screen off profile & set it to 245/245 max/min with smartass governor or conservative. When I was using SetCPU, I undervolted so that while my screen was on, the max was ~600. For the most part I rarely needed it any higher than that for my usage. However if you want to keep it at 998 or above, you will still benefit from a screen off profile.
I only run AOSP, so Sense may need more juice with the screen on.
Click to expand...
Click to collapse
Awesome, ill give this a shot, thank you much
Sent from my PC36100 using XDA Premium App
Do you overclock or underclock? If so, to what point? If not, why not? What clocking profiles/situations do you have set up? Share your thoughts and experiences.
Sent from my Inspire 4G
EDIT:
Below is the setup that has worked best for me, in terms of performance and battery life. I seem to have found a good balance.
1.2 GHz/245 MHz (Conservative)
Profiles
Screen Off - 768/245 MHz (Conservative)
Charging - 1.2 GHz/245 MHz (On Demand)
In Call - 1 GHz/245 MHz (Conservative)
*Profiles are ordered in terms of priority (e.g., if I am on a phone call and my phone is charging, the charging profile is activated).
*I'm also undervolted.
I keep my phone at ~.7GHz (underclocked) when on battery, 1GHz when on charger, and have profiles for medium (~1.3GHz) and max OC (~1.7GHz), as the kernel will allow, in case I need the extra power for something (like FPSe, chainfire, etc).
I keep mine at 500Mhz...gingerbeast is so beastly it can run decently even at about 200Mhz, I only use maximum...1900Mhz when I am showing off.
Sent from my Inspire 4G using XDA Premium App
ThEiiNoCeNT said:
I keep mine at 500Mhz...gingerbeast is so beastly it can run decently even at about 200Mhz, I only use maximum...1900Mhz when I am showing off.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
Damn if it doesn't. Never tried it but since you said it I figured I'd test it. Typing this this at 245mhz, and it actually functions decently, even scrolling this page. I tried this with my captivate and it wouldn't even swipe screens. I'm kinda amazed right now.
ThEiiNoCeNT said:
I keep mine at 500Mhz...gingerbeast is so beastly it can run decently even at about 200Mhz, I only use maximum...1900Mhz when I am showing off.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
Wow! If that's the case, I may have to give Gingerbeast a shot
Sent from my Inspire 4G
I keep mine at 768 Mhz when on battery. Just to save some power. But i could even go down to 368 Mhz (which i have <50% battery) and it runs decently. I'm using CM7.
what is this overclocking? and how do i check speeds?
2nr808 said:
what is this overclocking? and how do i check speeds?
Click to expand...
Click to collapse
Just make sure you have root and use setcpu from market
Sent from my Inspire 4G using XDA Premium App
i use LeeDroid's GB rom setting smartass setcpu at 245-1036 MHZ
battery can last long time
is there a free version because the only one i see a paid version
Im at 1344mhz daily with absurdly outstanding battery life on leedroid 3.1.1. And I'm using antutu CPU master cause setcpu wouldn't let me adjust the slider. No problems whatsoever.
sent from my Inspire 4g - hacked and slashed - Leedroid_3.1.1 - 1344mhz
Before my phone got jacked "another on the way" i run TPGB with ~1.5ghz top and .232ghz low. Smartass govener, and i use my phone alot. I easily got over a day. Thats with tethering-games-email-calls-messaging,
Sent from my VEGAn-TAB using Tapatalk
I was running at max OC (1.8Ghz with LeeDroid's kernel) for a little bit, but realized I didn't need the speed. Since I'm a PC overclocker as well, I couldn't just let things be at stock, so now I'm at 1.267Mhz max, and .245Mhz min. I'm doing my best not to bump it up more, and going to see how much I get out of my phone. I'm a very light user most of the time, so it's sometimes hard to gauge.
I overclocked for the same reason I OC'd my PC, because I could. That said, I'm running MDJ's kernel on Inspired Ace with the smarta** governor set at 245 min and 1400 max.
Seeing several people using smartass governor. I've been using ondemand....I'm gonna run smartass today and see what happens....
Sent from my Inspire 4G
Mine is at 768 all time, with just one profile that kicks when battery heat crosses 46 C that sets max speed at 537.
Adjusted both to 614 and 384 respectively after looking at above posts.
OC'd and [email protected]
using setCPU and being on CM7, i overclock to 1.7 ghz while the screen is on, using the interactive gov. i also set up a "screen off" profile that is underclocked to 247? mhz so that while my phone sits in my pocket for the majority of the day or on my desk, etc, etc.... it conserves quite a bit of power.
ive been using this set up since i got my inspire on cm7 (whenever that had its first RC) and im getting anywhere from 48-60 hours of usage.
my daily usage includes: tethering, streaming audiogalaxy, ghosttown, pandora. camera stuffs, calls, texts, 2 email accounts syncing, twitter, facebook, calendar, palmary weather updates, and much more stuff. so im going to stick to this set up until someone says they can get more usage with all that going on.
I run min(250 IIRC) and max(1.5) using on-demand.
I was overclocked at 1800 but my phone would freeze sometimes to where i had to pull my battery. So I tried 1000 but 2 days and then 1500. I noticed little difference in battery us and speed. I stuck with 1500 but after reading this thread i am gonna try 750. I never used any battery monitoring widgets. Im gonna try that. I use Leedroid GB btw.
I'm running at 1.2ghz with Coredroid and am happy.
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!
trying to make some custom setcpu profiles and curious if anyone knows what the lowest safe cpu speed for when the screen is off and also while in a call and the screen is off?
Right now I'm on VI and I'm running 368 max and 245 min which is the lowest min for this rom. I always run the lowest on min and 1 higher for max on sleep settings. I don't encounter any issues.
Sent from my HTC Glacier using xda premium
Don't go below 200 when screen is off. You'll get the "sleep of death" at the most inconvenient times.
estallings15 said:
Don't go below 200 when screen is off. You'll get the "sleep of death" at the most inconvenient times.
Click to expand...
Click to collapse
I have never dealt with that issue.
Sent from my HTC Glacier using xda premium
coupetastic-droid said:
I have never dealt with that issue.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Well don't do it or you will
Sent from my MyTouch 4G using xda app-developers app
OP, you may want to look into andrev_oc or virtuous oc daemon. Both are superior to setcpu profiles.
estallings15 said:
OP, you may want to look into andrev_oc or virtuous oc daemon. Both are superior to setcpu profiles.
Click to expand...
Click to collapse
Nope, they aren't, i have programed scripts for both and I own SetCPU. Stick with SetCPU
Sent from my HTC Glacier using xda app-developers app
bas3balman said:
Well don't do it or you will
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
I have already gone under 200mhz for sleep frequencies. Android revolution goes under 200 and I would run it under 200 always till now that I'm on VI.
Sent from my HTC Glacier using xda premium
I run lowest at 187MHz @ 700mV without any problem. I also set my screen off freq to that. Never tried one below that freq.
Here's a little info on using an overclocking daemon vs setcpu taken from the virtuous unity thread.
Introduction to the new Overclocking Daemon
This ROM features a completelynew wayof Overclocking and managing screen states.
The History But before explaining it further, let's talk about previous solutions. There are several different approaches to achieve "screen-state-scaling". That means basically thatthegovernor changes if you turn the screen off and changesbackto normal when turning the screen on.
This is mainly used to restrict the amount of CPU usage (the frequency in fact) during screen off. This can lead to a major battery life increase.
The solutions so far were:
Apps likeSetCPU,which changeautomaticallythe governor based on profiles Integrated solutions in the governor itself
Both these solutions have major problems.
The one with a tuner app is always a little laggy right after turning on the screen because SetCPU (or any other CPU tuner) needs some time to change the governors (up to 7 seconds). This leads mostly to major lag in the lockscreen.
The second solution is the smartass governor. It has already a screen-state-scalingincluded,so it reduces the frequency when the screen turn off. This could be a really nice solution but it has some problems too. Smartass most of the time is not really stable and has problems with its frequency scaling.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
ibuddler said:
I run lowest at 187MHz @ 700mV without any problem. I also set my screen off freq to that. Never tried one below that freq.
Click to expand...
Click to collapse
Thats very low. Surprised you do not get any issues.
Wish I could find the thread, but I was on a custom ROM that set the minimum CPU frequency to something below 200 by default, and I couldn't send text or MMS messages. Really weird.