Related
Hi everyone,
I recently stumbled upon Hakeem's thread, which details the necessary configurations to extend the battery life of the HD2 running Android. One of the key configurations is to use SetCPU to underclock the device from 1GHz to around 600MHz.
I really want to try it out, but my bf told me it might be risky. He said that since the CPU is now running at a lower clockspeed, it might lead to HD2 overheating if I were to run multiple applications (compared to the default, 1 GHz config). I'm no techie, so I really don't know if what he's saying is true.
Are there any risks associated with underclocking the HD2 using SetCPU? Thanks a bunch!
Sarah
rikou_demon said:
Hi everyone,
I recently stumbled upon Hakeem's thread, which details the necessary configurations to extend the battery life of the HD2 running Android. One of the key configurations is to use SetCPU to underclock the device from 1GHz to around 600MHz.
I really want to try it out, but my bf told me it might be risky. He said that since the CPU is now running at a lower clockspeed, it might lead to HD2 overheating if I were to run multiple applications (compared to the default, 1 GHz config). I'm no techie, so I really don't know if what he's saying is true.
Are there any risks associated with underclocking the HD2 using SetCPU? Thanks a bunch!
Sarah
Click to expand...
Click to collapse
I have used SETCPU on my device for 1 whole month, there is nothing bad happens and it is safe.
In addition, you can install this app "current widget" or put a SETCPU on your homescreen to track your device temperature. This is the safest way.
Cheers,hope this help...
As opposed to overclocking, underclocking shouldn't pose any risks. You are basicly running your CPU at a lower frequency than designed, so your device will be cooler to start with. Even when maxing your CPU load, by running a lot of apps, your CPU is operating under its designed capacity. It will therefore never get hotter than a stock HD2 running full load at 1Ghz.
Furthermore there are built in safeguards to prevent catastrophic overheating. So basicly its safe and you should have no issues. Except, maybe, insufficient CPU capacity when running a lot or a heavy app.
Hope this helps!
Sent from my HTC HD2
christarius said:
Except, maybe, insufficient CPU capacity when running a lot or a heavy app.
Click to expand...
Click to collapse
I wonder if this is what my bf was talking about.
But anyways, I'll go ahead and give it a try. Thanks you guys!
Sarah
rikou_demon said:
I really want to try it out, but my bf told me it might be risky. He said that since the CPU is now running at a lower clockspeed, it might lead to HD2 overheating if I were to run multiple applications (compared to the default, 1 GHz config). I'm no techie, so I really don't know if what he's saying is true
Click to expand...
Click to collapse
He's an idiot. If you make it faster, its generating more heat, if you pump up the voltage it makes more heat. There is no possible way for lowering it to cause it to run hotter.
If you are that concerned, create a profile in set CPUto lower CPU and use conservative when temp reaches a certain point.
Sent from my HTC HD2 using XDA App
FROM WHAT I READ that if you underclock to the wrong level you can damage things that needs a desired amout of cpu ...if not it can stop working i wll find my source and post it later
weird thread. lol you cant damage your hd2 cpu by underclocking or undervolting
rossl said:
weird thread. lol you cant damage your hd2 cpu by underclocking or undervolting
Click to expand...
Click to collapse
Agreed, just turn it back up before playing memory intensive games & apps.
You're all wrong and I dont mind saying wrong section! stick to the topic of "Development"!
Regards
Flashmore
My HD2 is locked to 245mhz - 400mhz when on a black screen (so locked.) When in use it fluctuates between 245 - 998mhz depending on usage.
had it this way for months. No ill affects and makes the battery last that little bit longer.
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
First off i take no credit for the virtuous oc daemon itself, it was developed by rmk40.
And credit goes to -viperboy- for the idea, i used his rom and really liked the oc daemon and saw the difference it makes. Check his rom out here. It has a nice interface to control the oc daemon and other features of the rom.
You can get more info here
DON'T use any apps to adjust cpu with this ie., setcpu, cpumaster, etc.
Ok, here is the deal flash the zip file the script will run by itself the only adjustment you have to make is the virtuous oc settings. This should work with any rom and probably any device i just don't have any other devices to test it on.
Here is how:
Open root explorer (or whatever file manager you use) and navigate to /system/etc/virtuous_oc, you will see 6 files named:
sleep_governor
sleep_max_freq
sleep_min_freq
wake_governor
wake_max_freq
wake_min_freq
These are the files you edit to your liking, i only edited wake_max_freq to read 1836000 or 1.8ghz
The two governor file have different settings and they are:
conservative
userspace
powersave
ondemand
performance
Again edit to your liking i left them ondemand myself seems to work good. I don't really know what the settings do exactly when it comes to these but they seem pretty self explanatory.
To see if it's working all you need to do is open terminal emulator or adb shell and type one of the following:
Current CPU frequency
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Current CPU governor
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Current min CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Current max CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
It autostarts using init.d, so MAKE SURE your rom supports init.d, if it doesn't you can still use it but it has to be started manually by entering the following in terminal emulator:
Code:
/system/xbin/virtuous_oc
If you overclock MAKE SURE your kernel supports it, I'm not responsible for any damage incurred
In the future i want to make an app to control the settings but i am still learning that part.
Big thanks to rmk40 for this awesome daemon and -viperboy- the bad ass idea !!
EDIT:
A basic rundown of the oc daemon is it scales up your cpu when you screen is on and scales it down when it is off, so your cpu is not overclocked continuously. It does save on battery as long as you don't get crazy with the overclocking.
rugedraw said:
The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
Click to expand...
Click to collapse
Added my pcm controls to the downloads, this will underclock/overclock(soon i hope) your battery when the battery reaches a specified percent. See this post for more details: http://forum.xda-developers.com/showthread.php?t=1227938
Changelog:
8/11
-Added Juwe11 ram optimization script
-Added speed up SD hack (Set at 3072) Details here
8/14
-Added Uninstaller
8/24
-Added virtuous_oc_pcm
Sweetness! To OC or UC, do you need to to increase or decrease the processor speed by certain increments? If so, please add them the OP for all of us noobs.
Thanks!
Edit: Since you didn't reserve any additional posts, feel free to shoot me a PM if you want me to add anything to this post in the future.
rugedraw said:
Sweetness! To OC or UC, do you need to to increase or decrease the processor speed by certain increments? If so, please add them the OP for all of us noobs.
Click to expand...
Click to collapse
Basically you can set them to what you want within reason, the way i do it is
1836000 is 1.8ghz
1188000 is 1.1ghz
So if you just put a . in between the first 2 numbers its roughly the ghz so
1288000 would be roughly 1.2ghz, at least that's my understanding if i'm wrong i'm sure someone will correct me. I wouldn't go crazy and set it at 2288000 that might do some damage.
Woooohooooo!!!! Im going in. Thank you sir!
hTc Evo [3D]
smokin1337 said:
I wouldn't go crazy and set it at 2288000 that might do some damage.
Click to expand...
Click to collapse
The phone would most likely reboot/crash.
Sent from my PG86100 using XDA App
DDiaz007 said:
The phone would most likely reboot/crash.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
And die! Haha
Id hate to be the one tackling that script :/
hTc Evo [3D]
Why yes, I'll take one thank you.
Dude! Freakin' awesome! I've been hoping someone would create this. Thanks!
smokin1337 said:
Basically you can set them to what you want within reason, the way i do it is
1836000 is 1.8ghz
1188000 is 1.1ghz
So if you just put a . in between the first 2 numbers its roughly the ghz so
1288000 would be roughly 1.2ghz, at least that's my understanding if i'm wrong i'm sure someone will correct me. I wouldn't go crazy and set it at 2288000 that might do some damage.
Click to expand...
Click to collapse
Actually, 1288000 is 1.3 rounded up and 118000 is the stock 1.2 speed, but I get what you're saying.......maybe I didn't do a good job of explaining myself. If you want 1.5, you can't set it at 150000......you'd have to set it at 1512000 (or something like that) because it must go up or down by fixed increments. I don't remember what the exact increments are, but I can look it up and post it if you'd like.
Edit: The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
I haven't tried using this method yet, as I'm already OC'd using viperboy's script. Maybe someone else can test this and confirm it is accurate.
Sent from my PG86100 using XDA Premium App
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Thanks rugedraw i added the frequencies to the op.
clamknuckle said:
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Click to expand...
Click to collapse
SetCPU can take up to several seconds to adjust, and it uses RAM also. A Daemon is instantaneous, and uses little to no RAM.
Sent from my PG86100 using XDA App
clamknuckle said:
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Click to expand...
Click to collapse
This is developed by Virtuous Unity for stability in OC the CPU, Set CPU uses some voltage to run and has been known to be unstable at times, this is the most stable way to control OC frequencies right from boot.
The Daemon works great (I have a version of this I'm testing on the MT4G at the moment) and there are benefits to using it, I would have to say it's important to spend some time reading information on Kernels to better understand what your using and the risks behind it.
Found Here: http://forum.xda-developers.com/showthread.php?t=1143177
( Scroll to the 4th Post for full information on the Daemon )
State-of-the-art-solution
So we (more precisely rmk40) thought of a better solution.
He wrote a native C Daemon which changes the governors instantly without any lag.
This leads to major performance improvements right after turning on the screen and in the lockscreen.
But at the moment this solution is a little bit harder to configure. We are planing to make a GUI for this, so you get the same comfort as using SetCPU.
Nevertheless you can even now adjust the daemon to your needs.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
Click to expand...
Click to collapse
smokin1337 said:
Thanks rugedraw i added the frequencies to the op.
Click to expand...
Click to collapse
No worries.........glad I can help with the little stuff. However, it seems like basic math is too hard for me. The correct increments are 54,000 and NOT 48,000. After some careful review, some of the high end OC frequencies had typo's, as well. I changed the info in myl post, but please update the OP, as well. I'm sure most people will be referring to that.
Just set this up on Rewind 2.1 and it appears to be working awesome.. definitely seems smoother then using a screen off profile in setcpu..
What I don't get is why Google doesn't incorporate something like this in all Android builds. It seems there are many things that can be manipulated to improve battery life on Android devices but that these solutions are just being ignored. Anyhoo, I don't think I will ever use SetCPU again...
Useless without voltage control
So this will work with nets kernel, and not against it? Just use it instead of setcpu?
NCspecV81 said:
Useless without voltage control
Click to expand...
Click to collapse
It definitely isn't useless without voltage control. I don't see how saving battery and using no system resources is useless. Plus, you cannot edit voltages on the E3D kernels yet, the sysfs HAVS interface needs to be implemented first.
-viperboy- said:
It definitely isn't useless without voltage control. I don't see how saving battery and using no system resources is useless. Plus, you cannot edit voltages on the E3D kernels yet, the sysfs HAVS interface needs to be implemented first.
Click to expand...
Click to collapse
I believe him. Hell, I all those frequencies I posted came from the OC script he designed for his rom.........which is awesome.
So I'm interested in undervolting using the stock CPU freq's, and I'm going to be using setCPU (obvi).
So, first question: Even if I want to use the stock frequencies, do I have to be using the OC kernel (0.2.1/1.45ghz at the time)? And then adjust the max to 1000mhz?
Second, I started up SetCPU and whenever I go to the voltage tab it forcecloses. This happens with both the stock enhanced & OC kernel, and I've tried fixing permissions to no avail.
All I really understand so far is that the end result is a table of CPU frequencies and linked voltages. I've OCed the hell out of desktops, but I'm lost here.
I'd just like to know how to get from starting up setcpu to ultimately popping out that new voltage/freq table.
I do apologize if this seems kinda stupid, I'm just trying to exercise caution lest I demolish my phone's innards. I've done it with many an intel.
If you just want stock frequencies, then there's no need for a custom kernel. I guess in that case, you could just use SetCPU for undervolting & profiles.
However, if you want overclock, you'll need a custom kernel.
If you're going to be using a overclocked kernel (i.e. the new Faux 1.45 GHz), then you will need to set the max to 1.45 GHz, and make sure SetCPU is set to start on boot; other wise it will stay at the stock clock speed of 1 GHz... So i guess if you only wanted the OC at certain times, you could set the max speed manually, only when you want to, and not select to start on boot.
I haven't really had any success with undervolting yet... always crashes on me & reboots. The best thing to do is make sure "set to boot" is not selected, when testing your undervolting, other wise you could get stuck in a loop, with the phone crashing every time it boots and tries to apply you undervolting values. I'd start at -25 for each and work from there... stress testing each choice with a benchmark app to make sure you wont reboot... if it reboots, then you know your undervolt was to much. Also remember that you can not undervolt more than -100 between each frequency, otherwise the undervolting will not make any difference.
I really like the profile options in SetCPU... you can set the screen off frequencies to the lowest two, that way for whatever reason your phone isn't running at full strength while your not using it. Also, you can set frequency speeds at custom defined battery levels.
Hope this helps somewhat.
It's unclear to me why it force closes. This may be a rom incompatibility or a SuperUser issue? I assume you've tried uninstalling it and reinstalling it? Updating your SU app? Try flashing to the latest Aura rom?
A few quick words about SetCPU:
1. When you first get started, do not set to "Set on Boot" in case you've undervolted too much and it crashes when applied. You can always check it later once you know the voltages are stable.
2. Between each frequency step there is a maximum of 100mV step off. Anything greater than that it defaults to native voltage. I think this is a Tegra2 issue.
With that said, undervolting is simple: simply slide the little slider on SetCPU to negative values. How much you can under-volt largely depends on your particular hardware and it is inconsistent across all Atrix's. My voltage table is as belows:
1000mhz: -50
912: -50
750: -50
608: -75
456: -75
312: -100
216: -100
I, however, did not test the limits of my phone. Many people will slowly increment the voltage lower until they start to get resets, and then they'll move it back to find the lowest stable point.
It has, however, been well established that minor undervolting improves battery life and diminishes heat generation. Excessive undervolting may actually hurt battery life. You can look around on this forum regarding the data. However, reasonable undervolting will improve battery life.
Thanks fellas, this helps A LOT.
I was so afraid I'd get 17 responses of "You're such a noob. Stop cluttering the forums" etc etc
At this point, I think that the problem is, for whatever reason, the FC when I tap the voltages tab.
I'm on the newest Aura (1.2.2.1) newest enhanced stock kernel from Faux123 (0.2.1) and the newest SetCPU (2.4). I'll try updating my SU (though I believe I did that right after I flashed.
I'll reintall SetCPU and report back.
Until then, THANKS BUCKETS fellas. I really appreciate the info and advice.
UPDATE: May have found the problem. When it first boots up it prompts to autodetect freq's or choose them manually (or something like that). I was afraid this would actually alter my CPU clocks right then and there and so I hit manual detect, saw something that said Tegra2 etc and clicked it. I just now hit 'menu' and set it to autodetect, tried the voltages tab, and no FC, so I think that's solved.
Thanks again for all the info guys! I'll start experimenting and let you know HOW LOW I CAN GO (ha).
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
AdiNova said:
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
Click to expand...
Click to collapse
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
xyrovice said:
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
Click to expand...
Click to collapse
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Swiftks said:
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
xyrovice said:
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
Click to expand...
Click to collapse
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
ghost_og said:
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
Click to expand...
Click to collapse
That makes perfect sense- limiting the max during the stress test. Thanks for the tip bro I really appreciate it.
Im running CM7 and just flashed "1.4 newoc 240-325-300 for cm7" and have read about undervolting, apparently it saves battery? What kind of settings is everyone running without having the phone lock up or anything with this kernel? Is there any really noticeable battery savings from undervolting? Im a complete noob when it comes to overclocking and undervolting. Would undervolting possibly damage the hardware over time? Any insight on undervolting and overclocking would be greatly appreciated. Can you provide a noob friendly walk through on how to undervolt and the pros/cons? Thanks a bunch
Edit: I see in setcpu it has differnt mV ratings depenting on the Mhz that the processor is running, can someone run me through whats a "safe" level to bring them all down to? Like at 216 Mhz its autoset to 750 mV and at 1000 Mhz its set to 1000 mV and 1400 Mhz its at 1300 mV. Also, i cant adjust the scaling, should i be using a different kernel? If so can you provide a specific one? And does scaling have a large affect?
I have the same issue with not having the scaling option. I don't really care as set CPU still does what it is supposed to.
I am using cm7 with jokers 1.3kernel uvolted -75mv across the board. I have had no issues what so ever. I did experience less battery life but I attribute that to constantly messing with my phone since rom-ing and using jokers kernel. I did learn to shut off wifi when not using it. That itself helped tremendously.
There should be no hardware damage from undervolting (only stability issues). Its overvolting is what you should be worried about and iirc those are set by the kernel dev during configuration/compiling. I don't think any dev is going to push the voltage envelope and risk hard bricking his/her device and many other users devices.
Sent from my MoPho. All typos are the phones fault.
scaling is done hardware level in tegra 2
Ok great thanks, to the both of you, for the replies. I seem to have found a pretty stable setup of undervolts and im going to run for another day to make sure before i set it to auto adjust on boot.