Since detule has pushed in patches that require an app to overclock now instead of inserting the appropriate lines in the startup.txt file, I am looking to get a better understanding of what exactly the line in the startup.txt file did and how to achieve similar settings in an app like setCPU.
I have setCPU, and set it up to run the default program at 710MHz both the Max and the Min. I am not really interested in battery saving features of the program or anything else. I just want it to run at 710MHz all the time. I thought it pretty much did this when using the startup.txt command set to 710400.
My question is, am I correct that if I set it up setCPU that way is that mirroring what the command did or am I going to get worse battery life then I did before because the app does something different?
I know the phone still sleeps with the app set that way. What happens in sleep with both the startup.txt command or this app? Does Android knock the processor down when going into sleep by either method or both?
Shifting only the MAX to a desired frequency achieves the same as using, what used to be, the command line method and specifying oc_freq_khz.
Shifting the MIN to match MAX will result in poorer battery life, though your phone will run constantly at the desired frequency.
When going into suspend, the driver first down-shifts the clocking frequency and then powers down ARM11 completely regardless of the OC settings.
detule said:
Shifting only the MAX to a desired frequency achieves the same as using, what used to be, the command line method and specifying oc_freq_khz.
Shifting the MIN to match MAX will result in poorer battery life, though your phone will run constantly at the desired frequency.
When going into suspend, the driver first down-shifts the clocking frequency and then powers down ARM11 completely regardless of the OC settings.
Click to expand...
Click to collapse
So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower? I have the minimum set down to 245MHz now, hopefully I won't see too much lag with that.
slickdaddy96 said:
So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower?
Click to expand...
Click to collapse
It would down-shift to 245, unless under load.
slickdaddy96 said:
So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower? I have the minimum set down to 245MHz now, hopefully I won't see too much lag with that.
Click to expand...
Click to collapse
You probably won't. The chip just goes to 245 if it is just idling. Under load, it'll snap back up to your desired frequency. It is kinda like the i7 2600K when in Turbo Core mode. It'll drop to 1.6 gh/z when doing nothing, then snap up to whatever it is set for when under load.
My settings are 787max and 122 min (This is ACL's OMGB NAND, but it'll probably be similar) and I don't notice lag in comparison to just leaving it at 787.
i need something to speed this thing up a little.... my electrify broke
moparfreak426 said:
my electrify broke
Click to expand...
Click to collapse
um, what?
wizardknight said:
um, what?
Click to expand...
Click to collapse
My rebadged motorola photon(electrify broke) and kind of had to switch back this touch pro 2 (rhod500)
Sent from my MSM using XDA
moparfreak426 said:
My rebadged motorola photon(electrify broke) and kind of had to switch back this touch pro 2 (rhod500)
Sent from my MSM using XDA
Click to expand...
Click to collapse
If you are using kernel 3.3.6 just grab your favorite overclocking tool from the market. If not, go to the thread for the rom you are using and ask for help.
wizardknight said:
If you are using kernel 3.3.6 just grab your favorite overclocking tool from the market. If not, go to the thread for the rom you are using and ask for help.
Click to expand...
Click to collapse
2.67.96 I think..... need to look for kernal 3.3.6
Sent from my MSM using XDA
Related
Thats right, just loaded it up after rooting this bad boy and it is working just fine!
I am not responsible if you brick your device in the process.
UPDATE!
Ok so here is what is needed to run this badboy without problems.
Use only the conservative option (least problematic and no sleep comas)
I dont use the widget, i already know the speeds i set it at.
The settings stick even after a reboot, but when you click on the setcpu icon they revert back and you lose your settings. If that happens just go back and click on detect auto speeds and set up your speeds again.
Happy clocking!
what version? 2.0.1?
Were you able to overclock it past the 1ghz?
I rooted mine today and installed setCPU which worked flawlessly but I am not able to move the slider past 1ghz.
I loaded it on mine and while it *appears* to work, it doesn't seem to effect the clocks any.
heck just underclock your phones to save battery lol
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
jroid said:
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
Click to expand...
Click to collapse
To see if it's working set it to underclock and then get into an adb shell and run the command: cat /proc/cpuinfo
It should display cpu data that includes the current clock speed.
I don't know if this helps but when I was in the Quadrant Standard app it has the system info. I hit it, scrolled down to cpu and it said
Current: 400 mhz, Max: 1000 mhz, Min: 100 mhz,
and I just checked it now and it said my current clock was 800 mhz, so i guess the cpu scales dynamically based on what the load is and what we are doing, thats a pretty great power saving feature.
Select 'Auto Detect'.
I believe you need an oc'd kernal to be able to move the slider past 1ghz.
Also, the dev has stated that it should be set to 'conservative', not 'ondemand'. 'Ondemand' was causing random shutdowns on the Galaxy S.
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Koblek said:
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Click to expand...
Click to collapse
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Has anyone noticed any significant battery conservation with this?
MINUS Stl said:
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Click to expand...
Click to collapse
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
i am still having problems with setcpu even on conservative mode. i have stopped using setcpu completely for now.
wbexpress said:
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
Click to expand...
Click to collapse
Auto detect...
Sent from my SGH-T959 using XDA App
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
mygti02 said:
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
Click to expand...
Click to collapse
What are your exact settings in profiles, advanced and overview?
any one running their phone at 1Ghz all the time?
+1, hah2110 please post your settings if they're working for you so a noob like me can learn some things!
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
i think you have to wait for the source code for the kernal to be released and tinkered with to get anything useful from all that...but who knows
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Odinist said:
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Click to expand...
Click to collapse
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
SuperFly03 said:
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
Click to expand...
Click to collapse
pretty much what I did, minus everything but the screen off
I always set the screen off on my evo 4g to 245 max, and will probably do the same here. Kinda waiting for kernal source code to be released so I can use the smartass governor. I always liked that one.
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
I cannot wait to tinker once HTC releases the kernel source!
mthorn79 said:
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
Click to expand...
Click to collapse
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
nosympathy said:
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
Click to expand...
Click to collapse
Ok I'm not an idiot, I know quadrant scores don't mean anything but some people use it as a gauge to get an idea on how their phone is. (If u feel it does nothing for you then don't use it if u don't want to no one asked you to)
If you know anything about phones you know certain people's will vary in speeds, I'm just posting my experience...this IS afterall a "Post Your SetCPU Settings' thread, so don't be getting all uppity.
Sent from my ADR6400L using Tapatalk
Jimmy058910 said:
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
Click to expand...
Click to collapse
Yes. I think they releases it within 45 days or something like that. It will most certainly be here soon.
Sent from my ADR6400L using Tapatalk
Any incoming call issues with Screen Off set at 245?
Steeler86 said:
Any incoming call issues with Screen Off set at 245?
Click to expand...
Click to collapse
no and their shouldn't be, unless you down the road, since you couldn't do it now, use one of the governors like Conservative which tend to really slow the phone down. On my Evo 4G it used to take a good 30 seconds to unlock the screen is I used that with screen off at 245Mhz.
1570 for me on stock rom.
I got 2000+ quadrants on stock ROM. SA for setCPU, I can't get my CPU to clock down by force with any app. I think the kernel source is going to be needed. Probably have perflock on like they did on my inc. Let me know if setCPU works please.
SetCPU works, you just have to hit the menu button and click "disable perflock"
1376 on VirusRom but it is soooo snapppy
Seems to be working for me. 39% battery after 12+ hours. Just with the "screen off: max245" setting.
Sent from my ADR6400L using XDA App
We finally got the source code!
Do I need to flash this to overclock
http://forum.xda-developers.com/showthread.php?t=1016916
or can I wait for SetCPU to update?
You should share what speed and voltages you are running at, I figured it would be helpful to give other people ideas of where to begin trying their voltages at for undervolting purposes. So, what's your lowest voltages at the highest clock speeds?
I'm using SetCPU's standard voltages. 1.8/.38 normal, .87/.38 screen off and over 130F, 1.2/.38 battery less than 50%, 1.8/1.2 plugged in. Getting 4-5 more hours per charge!
Sent from my PG86100 using XDA Premium App
Here's the values I've currently got in my Permatemp Root .bat file (thanks Eugene!): scpll_l_val=24 vdd_uv=1060000
That gives me 1.296 ghz at 1.06 volts. I know 1.3 ghz isn't much of an overclock, but this phone is already so fast (especially compared to my old Hero, lol) that I'm not really craving any more speed ... what I'm most interested in is undervolting for max battery life. From what I've read the stock voltage at 1.2 ghz is 1.18 volts, so I'm a little under that right now. I tried 1.00 and 1.03 volts and got reboots every time, but 1.06 volts runs rock-solid reliable for me at 1.3 ghz.
is that really even noticable? the LCD draw most of the power typically
oldjackbob said:
Here's the values I've currently got in my Permatemp Root .bat file (thanks Eugene!): scpll_l_val=24 vdd_uv=1060000
That gives me 1.296 ghz at 1.06 volts. I know 1.3 ghz isn't much of an overclock, but this phone is already so fast (especially compared to my old Hero, lol) that I'm not really craving any more speed ... what I'm most interested in is undervolting for max battery life. From what I've read the stock voltage at 1.2 ghz is 1.18 volts, so I'm a little under that right now. I tried 1.00 and 1.03 volts and got reboots every time, but 1.06 volts runs rock-solid reliable for me at 1.3 ghz.
Click to expand...
Click to collapse
Someone in the OC topic was asking about UV at stock speeds. You're close enough to stock that you should qualify. You should go post your results in that thread too. They'd be happy to see them.
I'm running @ 1.78GHz with a vdd of 1300000. I'm going to try and go lower... maybe 12800000.
I have it overclock to 1728mhz but dint know where to adjust the voltage. Does setcpu does this or i need a different program to read voltage/change voltage?
Sent from my PG86100 using XDA App
eduardmc said:
I have it overclock to 1728mhz but dint know where to adjust the voltage. Does setcpu does this or i need a different program to read voltage/change voltage?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
You adjust the voltage when you type the ADB command to OC. If you're using a script that does it for you, you will need to edit that script and look for the vdd_uv= line.
bitslizer said:
is that really even noticable? the LCD draw most of the power typically
Click to expand...
Click to collapse
What do you mean by "is that really even noticable"? It's certainly calculatable ... it's an 11.3 percent improvement in battery usage by the CPU. If you're saying that's not very much, well, it's all relative. If you're saying you're not interested in saving a little battery when it won't cost you anything to do so, that's fine with me. If you're saying that no power-saving effort is worth any consideration because the LCD is the biggest power draw of all and that's the only one that matters, then why did Qualcomm bother to develop asynchronous cores and low-power audio modules and low-power GPS modules? I mean, hey, the screen is all that matters, right?
Or did I misread your statement?
Edit: Sorry for coming across as so argumentative, I just don't understand why you're taking the position you are.
oldjackbob said:
What do you mean by "is that really even noticable"? It's certainly calculatable ... it's an 11.3 percent improvement in battery usage by the CPU. If you're saying that's not very much, well, it's all relative. If you're saying you're not interested in saving a little battery when it won't cost you anything to do so, that's fine with me. If you're saying that no power-saving effort is worth any consideration because the LCD is the biggest power draw of all and that's the only one that matters, then why did Qualcomm bother to develop asynchronous cores and low-power audio modules and low-power GPS modules? I mean, hey, the screen is all that matters, right?
Or did I misread your statement?
Edit: Sorry for coming across as so argumentative, I just don't understand why you're taking the position you are.
Click to expand...
Click to collapse
+1! Would have thanked you, except I'm at my limit.
I'm at 35 @1450000. I know I can go lower, but if I overclock, I want stability not battery life
On another note: I can't wait until we have source, custom kernels, and I finish up the viperMOD app to get support for the E3D. Will be one awesome beast undervolted!
I'm at 1.56ghz and 120000 voltage.
Runs stable, get a nice speed boost without killing my battery. Am going to try a lower voltage. I've read the could will default to stock speed if you go too low though. Guess I'll find out.
Sent from my PG86100 using Tapatalk
felacio said:
I'm at 1.56ghz and 120000 voltage.
Runs stable, get a nice speed boost without killing my battery. Am going to try a lower voltage. I've read the could will default to stock speed if you go too low though. Guess I'll find out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
No, if your voltage is too low, your phone will freeze or instanly reboot on you.
-viperboy- said:
No, if your voltage is too low, your phone will freeze or instanly reboot on you.
Click to expand...
Click to collapse
Well. I can handle that. Lol. Guess I'm going lower! Wish me luck!
Sent from my PG86100 using Tapatalk
I am currently testing scpll_l_val=22 vdd_uv=1010000 for undervolting purposes, 1000000 caused a reboot, 1010000 has been holding up well under stress tests..
If one of you guys who are overclocking could test this video clip and either diceplayer or the diceplayer free trial in the market - I would appreciate it:
http://www.movie-list.com/forum/showthread.php?t=27232
Supposedly - the Samsung Galaxy S2 can play 1080P + AC3 MKV's smoothly. But the Evo3D and Sensation lag a bit according to the developer. I tested this file with my evo3D and it looked like my Evo3D stuttered every 3 seconds or so. I'm just wondering if an overclock would smooth out playback - but I haven't installed temproot.
For those of you overclocking just for battery savings, I am currently testing
adb shell insmod /data/local/tmp/8x60_oc.ko scpll_l_val=22 vdd_uv=1003100 and have been stable so far, this is the absolute lowest I can push it at 1.2Ghz on my phone, can anyone else match this or go lower? I think it will be helpful to start establishing these values now so kernel makers will have some ideas of how far they can push our phones.
P0ll0L0c0 said:
If one of you guys who are overclocking could test this video clip and either diceplayer or the diceplayer free trial in the market - I would appreciate it:
http://www.movie-list.com/forum/showthread.php?t=27232
Supposedly - the Samsung Galaxy S2 can play 1080P + AC3 MKV's smoothly. But the Evo3D and Sensation lag a bit according to the developer. I tested this file with my evo3D and it looked like my Evo3D stuttered every 3 seconds or so. I'm just wondering if an overclock would smooth out playback - but I haven't installed temproot.
Click to expand...
Click to collapse
Speed = 1.5GHz.
The default gallery player plays it perfectly, but there's no sound.
RockPlayer plays it very choppily, but has sound.
Dice player plays somewhat smoothly and has sound, but there are lag moments every 3-6 seconds as you said.
It's a software issue.
PaulB007 said:
For those of you overclocking just for battery savings, I am currently testing
adb shell insmod /data/local/tmp/8x60_oc.ko scpll_l_val=22 vdd_uv=1003100 and have been stable so far, this is the absolute lowest I can push it at 1.2Ghz on my phone, can anyone else match this or go lower? I think it will be helpful to start establishing these values now so kernel makers will have some ideas of how far they can push our phones.
Click to expand...
Click to collapse
Right noe I'm sitting at 29 (1.56ghz) with a UV of 1170000. Tried 1150000 but phone immediately restarted. And 1160000 restarted after a while. This seems stable so far. Haven't totally stressed it yet though.
Sent from my PG86100 using Tapatalk
nabbed said:
Speed = 1.5GHz.
The default gallery player plays it perfectly, but there's no sound.
RockPlayer plays it very choppily, but has sound.
Dice player plays somewhat smoothly and has sound, but there are lag moments every 3-6 seconds as you said.
It's a software issue.
Click to expand...
Click to collapse
Thanks for the check! I was wondering if there would still be lag with an overclock - that's disappointing. Supposedly the SGS2 handles files like it with no problem.
OC Script
Here is a batch file I created to make it easier to OC. Basically just the Rooting script with a menu to select the speed with delays built in.
Rename from oc.txt to oc.bat if you wish to run the file.
You will most likely need to change the voltages to match your phone. My phone has been very OC friendly.
Currently running 1188mhz @ .97 Volts with no issues. I have been able to OC up to 1890mhz @ 1.32 volts.
Have not tried to go lower on the voltage at 1188mhz yet...
JDC4429
Undervolting and profiles.
I have tried a crap ton of different undervolting setting, but none work
Also the profiles in set cpu don't seem to work for me. I have a few of them set and it always sits on the top one I need some guidence with both please!
Another thing my xda premium app isn't pushing my notafications yes its set
Sent from my MB860 using xda premium
Undervolting is a delicate process. It takes time to find the max undervolt that is stable. With that being said, try undervolting everything by the lowest amount which is -25mv. Check to see if that is stable. If so proceed to go further. Remember lower freq will typically undervolt farther than higher frequencies.
As far as profiles go your probably not using the priority values right. The higher priority is what determines which profile setcpu uses. So for instance if you want a safeguard against overheating, you could set the profile for when the cpu goes above 55C to throttle the processor way down. If you set this profile to 100(max) it will overide all other profiles at 98, 99, 75, 50...etc. Also this may be obvious to some but be sure to tick(enable) the profiles button. If thats not ticked then it doesnt matter how many profiles you have set up. It simply wont use them.
jack_slapped said:
Undervolting is a delicate process. It takes time to find the max undervolt that is stable. With that being said, try undervolting everything by the lowest amount which is -25mv. Check to see if that is stable. If so proceed to go further. Remember lower freq will typically undervolt farther than higher frequencies.
As far as profiles go your probably not using the priority values right. The higher priority is what determines which profile setcpu uses. So for instance if you want a safeguard against overheating, you could set the profile for when the cpu goes above 55C to throttle the processor way down. If you set this profile to 100(max) it will overide all other profiles at 98, 99, 75, 50...etc. Also this may be obvious to some but be sure to tick(enable) the profiles button. If thats not ticked then it doesnt matter how many profiles you have set up. It simply wont use them.
Click to expand...
Click to collapse
When I was on alien rom, I tried 25 on all and it restarted after like a minute. What worked for me was 25 25,50,50,75,75,100 fromm bottom to top. I tried it with cm7 and total no go lol
Lemme tryi 25 on all and see what I get and I didn't know that. They all werent working, so I set them all to 100 lmao, I understand that now
Sent from my MB860 using xda premium
Aparently its been running 125,125,50,75,75,75,75bottom to top cm7 with 1.3 kernel.
It did restart a couple min ago randomly. Will keep posted
Sent from my MB860 using xda premium
Glad your getting some results. If it restarts even once it means at least one of your undervolted freq isn't stable. With your settings I would wager its in the uper freq considering your undervolt in the lower freq isn't too extreme. You might try decreasing the undervolt for your upper freq to -50 -50 -50 starting at the top. Might help to stabilize bc higher freq just require more voltage. If that proves to be stable continue trying to reduce the lower freq as much as possible. Mainly bc if you set your profiles right(screen off is the most important really) your phone will spend the majority of its time on the 200mhz freq. Thus the more undervolt on that freq should theoretically give the most benefit from undervolting. This is just all from personal experience. I'm no guru. Just spent way too much time adjusting voltages on phones . And of course having the upper freq undervolted as much as possible cant hurt either.
jack_slapped said:
Glad your getting some results. If it restarts even once it means at least one of your undervolted freq isn't stable. With your settings I would wager its in the uper freq considering your undervolt in the lower freq isn't too extreme. You might try decreasing the undervolt for your upper freq to -50 -50 -50 starting at the top. Might help to stabilize bc higher freq just require more voltage. If that proves to be stable continue trying to reduce the lower freq as much as possible. Mainly bc if you set your profiles right(screen off is the most important really) your phone will spend the majority of its time on the 200mhz freq. Thus the more undervolt on that freq should theoretically give the most benefit from undervolting. This is just all from personal experience. I'm no guru. Just spent way too much time adjusting voltages on phones . And of course having the upper freq undervolted as much as possible cant hurt either.
Click to expand...
Click to collapse
25,50,50,50,50,75,75
Still getting a reboot:'(
Only good thing about the reboot is it turns on instantly
PROFILES CONFIRMED WORKING trying to indwrvolt this thing
I think I'm gonna order another battery too bc this one isn't getting the 16 hours it was, I cant say much bc I'm screwing with the settings hardcore xD I will show.all settings in a sec
Sent from my MB860 using xda premium
Sent from my MB860 using xda premium
Blahhh
Put blah there so it would post lol. Also going to download a stress test or quadrent thing to test the stress and find maximum uv
Sent from my MB860 using xda premium
Undervolting COMPLETE=D
QUAD SCORE! OCED 1.3 CM7
Right now I'm thinking my battery life is going to be amazig and if I turned the data off when not using it... omg I would last like 2 straight days prolly=D
So pumped to test everything morrow!!
Side note:800mhz or above wont go past 75 >:/
Had really important question to ask you but forgot
Also tried putting 215 to 275 that was a no go lol. My question was is there a battery manager and info like the stock one for cm7?!!!
Sent from my MB860 using xda premium
Smittyzz said:
Undervolting COMPLETE=D
QUAD SCORE! OCED 1.3 CM7
Right now I'm thinking my battery life is going to be amazig and if I turned the data off when not using it... omg I would last like 2 straight days prolly=D
So pumped to test everything morrow!!
Side note:800mhz or above wont go past 75 >:/
Had really important question to ask you but forgot
Also tried putting 215 to 275 that was a no go lol. My question was is there a battery manager and info like the stock one for cm7?!!!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
well my battery was draining mad quick so I am not overclocking It anymore unless I want to show off or play games lol, lost 20% in one hour. Now its stable and undervolted
Sent from my MB860 using xda premium
First off, regarding SetCpu and over / undercloking, dev has said it'll only underclock/overclock ONE core at a time. It's a bug and he's working on it from what I understand. If both cores are needed to be in use at the same time, no over / underclocking will be applied. Secondly, profiles work as they should in SetCpu, so that's a problem on your end. Third, the undervolting can't be more than 100mv differnce between jumps. See screen shot.
http://www.multiupload.com/YUK0KPXZLJ
Phalanx7621 said:
First off, regarding SetCpu and over / undercloking, dev has said it'll only underclock/overclock ONE core at a time. It's a bug and he's working on it from what I understand. If both cores are needed to be in use at the same time, no over / underclocking will be applied. Secondly, profiles work as they should in SetCpu, so that's a problem on your end. Third, the undervolting can't be more than 100mv differnce between jumps. See screen shot.
http://www.multiupload.com/YUK0KPXZLJ
Click to expand...
Click to collapse
I understand the 100 thing and I got the undervolting and profiles done. I hope he gets both cores supported soon and thank you dmfor the reply
Sent from my MB860 using xda premium
Yea Im skeptical about not setcpu not having support for dual cores... Did some searching on the net and couldnt find anything to support that. As far as not the tegra 2 not being able to do over 100mv jumps. That's not true. My lowest frequency is 600mv (-150) and my next frequency is at 750mv. That's a 150mv difference right there... And I'm completely stable. Its entirely dependent on your processor. They are all different and respond differently to undervolting. You just have to find what works for you. Generally though the lesser the jumps in voltage will give you more stability.
a good kernal helps too im useing faux123 v2.0 0C1.3 its undervolts quite well
us/alienv4UL/OC1.3{webtop2sd{fixed}
Are there any benefits for doing so and if so, what are the best sets for it???
Sent from my MB860 using xda premium
yes battery life can be improved significant also with the overclocked kernal you need higher voltages to remain stable.
Just to make sure you know you need to have a custom kernel flashed such as faux's kernel to do either of these things.
As for values it really is a by phone thing some people will be able to drop voltages quite a buy while other can't drop at all typically though at lower clock speed voltage can be drop much more on my phone at 1000mhz it has a 50mV drop but at 216 its a 275mV drop
Sent from my MB860 using XDA App
jonnyboyC13 said:
yes battery life can be improved significant also with the overclocked kernal you need higher voltages to remain stable.
Just to make sure you know you need to have a custom kernel flashed such as faux's kernel to do either of these things.
As for values it really is a by phone thing some people will be able to drop voltages quite a buy while other can't drop at all typically though at lower clock speed voltage can be drop much more on my phone at 1000mhz it has a 50mV drop but at 216 its a 275mV drop
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Okay, I understand you. At this moment I have the 1.3 kernel from faux. I know some people said that certain voltages can crash your phone, so I wanted to make sure I had help before I messed something up.
*EDIT*
I have it set to 1.1 mhz
Sent from my MB860 using xda premium
Use SetCPU. A good way to undervolt is to decrease all clock speeds by 25mV to start. Play around with your phone and games to see if anything freezes up. Then keep lowering 25mV at a time until you start seeing instability, then put it back up 25mV to where it is stable and you should be pretty good.
phreshy said:
Okay, I understand you. At this moment I have the 1.3 kernel from faux. I know some people said that certain voltages can crash your phone, so I wanted to make sure I had help before I messed something up.
*EDIT*
I have it set to 1.1 mhz
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Quick tip: Before you start messing with voltage settings go to SetCPU's main screen and press Menu>Safe Mode Instructions>Extract Zip.
I hardly ever see this mentioned, but if for any reason you select "Set at Boot" when testing out settings and get stuck in a bootloop, flashing the zip that is extracted will put you in "Safe Mode" and none of your settings will be applied, allowing you to correct the unstable ones.
Thank you all for your help. I have the voltage clocked at 1125mv from 1200mv (1200mhz) mv and 500mv from 750mv (216mhz). Everything seems to be running smoothly, but haven't been able to run an appropriate test for battery life yet.
Sent from my MB860 using xda premium