Related
Can someone point me to where I can learn how to use set cpu and set voltage properly. Just installed superotimized kernel and wondering how to take full advantage of it
p4ranoid4ndroid said:
Can someone point me to where I can learn how to use set cpu and set voltage properly. Just installed superotimized kernel and wondering how to take full advantage of it
Click to expand...
Click to collapse
overclocking is pre-enabled, under volting can be done through an app the link is in the thread. there are 2 settings. try about -50v each if that works fine bump one down to -75mv at a time. test the phone over a day or two and see how it runs, see if it has sleep death after a few periods of inactivity, especially extended periods, see if it has sleep death while charging, which seems to make a difference that will test the low setting.
see if the phone shuts down without freezing, and see if it shuts down without freezing while charging, the heat in the battery makes a big difference, play some 3d games. if you have freezing issues you can disable overclocking under different situation with set cpu or se t the volts to a more conservative setting.
Dani897 said:
overclocking is pre-enabled, under volting can be done through an app the link is in the thread. there are 2 settings. try about -50v each if that works fine bump one down to -75mv at a time. test the phone over a day or two and see how it runs, see if it has sleep death after a few periods of inactivity, especially extended periods, see if it has sleep death while charging, which seems to make a difference that will test the low setting.
see if the phone shuts down without freezing, and see if it shuts down without freezing while charging, the heat in the battery makes a big difference, play some 3d games. if you have freezing issues you can disable overclocking under different situation with set cpu or se t the volts to a more conservative setting.
Click to expand...
Click to collapse
I've been told that undervolting can improve the battery time. Of course, lots of varying opinions of how good/bad it may be to overclock.
If I want to just undervolt, is that possible with SetCPU?
Dani897 said:
overclocking is pre-enabled, under volting can be done through an app the link is in the thread. there are 2 settings. try about -50v each if that works fine bump one down to -75mv at a time. test the phone over a day or two and see how it runs, see if it has sleep death after a few periods of inactivity, especially extended periods, see if it has sleep death while charging, which seems to make a difference that will test the low setting.
see if the phone shuts down without freezing, and see if it shuts down without freezing while charging, the heat in the battery makes a big difference, play some 3d games. if you have freezing issues you can disable overclocking under different situation with set cpu or se t the volts to a more conservative setting.
Click to expand...
Click to collapse
ewingr said:
I've been told that undervolting can improve the battery time. Of course, lots of varying opinions of how good/bad it may be to overclock.
If I want to just undervolt, is that possible with SetCPU?
Click to expand...
Click to collapse
Interesting stuff...
I too would like to know if it is possible to simply under-volt. Does anyone know the optimal settings for SetCpu with the Captivate...or does it vary depending on each users profile/ phones?
So Ive been playing around with various settings for set cpu and voltage control and all has been well so far. The only problem im having is voltage control seems broke. I try to open the all but it just black screens. I tried to clear the memory and unistall and reinstall and still have the same problem. Any ideas?
http://forum.xda-developers.com/attachment.php?attachmentid=432086&d=1288709102
^you can under volt setirons kernel and disable overclocking with this app.
i find my battery life to be less than stock with this kernel, i need to see if it is a common issue, maybe because it is not a captivate kernel. but in the past with unhelpfuls kernel for 2.1 battery life was awesome.
spartan062984 said:
Interesting stuff...
I too would like to know if it is possible to simply under-volt. Does anyone know the optimal settings for SetCpu with the Captivate...or does it vary depending on each users profile/ phones?
Click to expand...
Click to collapse
It's going to depend on the individual CPU in your phone. Your best result is to start at a given clock speed and begin lowering voltage in the smallest step possible, test for stability, repeat until you begin to notice instability (or you just run out of voltage options). You can just undervolt without increasing clock speed any, or you can not undervolt yet raise clock speed, or you can overclock and undervolt, depending on how your particular chip reacts. Some might need additional voltage to stabilize the snapdragon at 1.2Ghz while others (mine for example) is stable Able @ -100mV and 1.2Ghz. Overclocking silicon is the ultimate in YMMV.
Another thing to bear in mind is that increasing clock speed necessarily increases power consumption. There is no way around this. So a chip at 1.2Ghz will use more juice than 1Ghz even with the same voltage. It's difficult to say at this point whether, say, the Snapdragon @ 1.2Ghz and -100mV uses more or less power than the same chip @1Ghz and stock voltage. It's absolutely possible that the former uses more power, which would explain why you see at least one claim here of battery life decreasing even when voltage settings are left untouched.
hawkeyefan said:
It's going to depend on the individual CPU in your phone. Your best result is to start at a given clock speed and begin lowering voltage in the smallest step possible, test for stability, repeat until you begin to notice instability (or you just run out of voltage options). You can just undervolt without increasing clock speed any, or you can not undervolt yet raise clock speed, or you can overclock and undervolt, depending on how your particular chip reacts. Some might need additional voltage to stabilize the snapdragon at 1.2Ghz while others (mine for example) is stable Able @ -100mV and 1.2Ghz. Overclocking silicon is the ultimate in YMMV.
Another thing to bear in mind is that increasing clock speed necessarily increases power consumption. There is no way around this. So a chip at 1.2Ghz will use more juice than 1Ghz even with the same voltage. It's difficult to say at this point whether, say, the Snapdragon @ 1.2Ghz and -100mV uses more or less power than the same chip @1Ghz and stock voltage. It's absolutely possible that the former uses more power, which would explain why you see at least one claim here of battery life decreasing even when voltage settings are left untouched.
Click to expand...
Click to collapse
Thanks for clarifying Hawkeye! I will report back on in a few days once i have tested out a few profiles. In my opinion, I feel that it is best to leave Over-clocking at default and maximize battery utilization with setcpu. However, the thought of over-clocking the Dragon beast is VERY tempting. Who wouldn't? I will definitely check out the differences when playing games and such.
spartan062984 said:
Thanks for clarifying Hawkeye! I will report back on in a few days once i have tested out a few profiles. In my opinion, I feel that it is best to leave Over-clocking at default and maximize battery utilization with setcpu. However, the thought of over-clocking the Dragon beast is VERY tempting. Who wouldn't? I will definitely check out the differences when playing games and such.
Click to expand...
Click to collapse
I have to tell you, I'm not personally very fond of SetCPU on this device, even though I paid for the app (ugh). With raspdeep's voltage control app and SetIron's OC/UV kernel, the CPU defaults to 1.2Ghz at stock voltage, which for a basic setup is fine. Voltage Control app is phenomenal for adjusting in increments of 25mv at a time...one setting is for high clocks (1Ghz - 1.2Ghz) and the other is for < 1Ghz. It's probably best actually to start with the lower clock setting in Voltage Control, as your phone will spend the lion's share of it's time at those clocks and so that is where you should see the most gain in battery life. My only gripe is that I can't get the boot settings to stick on the Captivate so I have to go in and adjust them each time I reboot the phone. no biggie there.
SetCPU, on the other hand, has caused me loads of problems in the past, including causing the phone not to wake up from sleep and just atrocious battery life, I assume from constantly polling the CPU clock to measure clock speed. I have not experienced any of that with Overclock Widget, but I also don't use any of the independent clockspeed controls in the app...basically it's just a widget to display clock speed the way I use it. Otherwise, Setiron's kernel gives the 200mhz overclock and I just let the Hummingbird deal with changing clocks on its own. Jmo, but it works for me with no resulting battery drain beyond the additional I expect as a result of the extra 200mhz.
edit: whoops, long day. hummingbird in my post from above, not snapdragon. I need a drinky poo.
hawkeyefan said:
I have to tell you, I'm not personally very fond of SetCPU on this device, even though I paid for the app (ugh). With raspdeep's voltage control app and SetIron's OC/UV kernel, the CPU defaults to 1.2Ghz at stock voltage, which for a basic setup is fine. Voltage Control app is phenomenal for adjusting in increments of 25mv at a time...one setting is for high clocks (1Ghz - 1.2Ghz) and the other is for < 1Ghz. It's probably best actually to start with the lower clock setting in Voltage Control, as your phone will spend the lion's share of it's time at those clocks and so that is where you should see the most gain in battery life. My only gripe is that I can't get the boot settings to stick on the Captivate so I have to go in and adjust them each time I reboot the phone. no biggie there.
SetCPU, on the other hand, has caused me loads of problems in the past, including causing the phone not to wake up from sleep and just atrocious battery life, I assume from constantly polling the CPU clock to measure clock speed. I have not experienced any of that with Overclock Widget, but I also don't use any of the independent clockspeed controls in the app...basically it's just a widget to display clock speed the way I use it. Otherwise, Setiron's kernel gives the 200mhz overclock and I just let the Hummingbird deal with changing clocks on its own. Jmo, but it works for me with no resulting battery drain beyond the additional I expect as a result of the extra 200mhz.
edit: whoops, long day. hummingbird in my post from above, not snapdragon. I need a drinky poo.
Click to expand...
Click to collapse
LOL. No Worries. I myself made the same mistake. I thought something was odd with my post. SnapDragon...Hummingbird....Bulbasaur.....I knew what you meant. lol
Still not having any luck with the voltage control app. Ive tried flashing different roms to see if it would work. I undervolted it to 100/75 the first time i did it and now i cant change. Only a little worried
i guess there was an issue with the set on boot scripts not working. supposedly that is fixed, i dont know for sure though, i haven't updated.
From what I'm gathering, in order to undervolt, you must have a kernel to su pport that, for example Setirons.
I'm not necessarily interested in overclocking, as it performs well as is. Of course there are arguments that overclocking may ultimately harm the phone, and arguments that by the time that happens, you'd be ready for a new phone. In any event, if I start getting slower, I may interest in overclocking.
Does anyone know if dramatic improvement in battery performance with underclocking?
I've noticed quite a bit of a difference, just pretty difficult to tune it precisely. (Coming from a person who enjoys overclocking computers a little too much). I just wish there was an app that would test each frequency and then let you know which one failed (without having to manually set it).
So I have a few apps... Voltage Control, SetCPU, No-Frills CPU... but I've honestly been a bit weary to use them. I want the best battery life since I'm a heavy user, but I also don't want to overclock/set voltage to a point where I'll screw up my phone. I'll admit that I'm a novice user when it comes to voltage/overclocking, but not when it comes to ROMs, kernels, bootloaders, etc. I work with those all the time, but really trying to get the most out of the battery and CPU.
There's this thread I found that has someone's settings on it, but don't know if its good or how much this guy knows(no offense to him):
http://forum.xda-developers.com/showthread.php?t=1356211
Anyone got any insight or perhaps screenies of their optimally tested settings? VERY VERY appreciated to anyone that can help.
jgruberman said:
So I have a few apps... Voltage Control, SetCPU, No-Frills CPU... but I've honestly been a bit weary to use them. I want the best battery life since I'm a heavy user, but I also don't want to overclock/set voltage to a point where I'll screw up my phone. I'll admit that I'm a novice user when it comes to voltage/overclocking, but not when it comes to ROMs, kernels, bootloaders, etc. I work with those all the time, but really trying to get the most out of the battery and CPU.
There's this thread I found that has someone's settings on it, but don't know if its good or how much this guy knows(no offense to him):
http://forum.xda-developers.com/showthread.php?t=1356211
Anyone got any insight or perhaps screenies of their optimally tested settings? VERY VERY appreciated to anyone that can help.
Click to expand...
Click to collapse
there is no rule. every cpu is different. very different. my captivate took a lot of effort to get a meer 1300 mhz but my infuses get 1600 no problem at all. some infuses wont go to 1600 but more will go to 1500 than galaxy s's. they probably held out the best testing cpu's for the higher clocked phone.
for battery life try clocking @ 800 mhz and dont use screen off profiles just because it looks like a good idea to slow the cpu when you arent really using it(causes problems if the max freq is too low with some kernels) and test stability with your uv settings, go down a little at a time, for max frequency uv from the top down, for battery life go from the bottom up and disable the upper freqs if they become unstable. this is because rapid voltage changes can contribute to instability. too much differential will cause crashes if the uv is extreme or the oc is extreme.
at some point though the cpu settings will have a limited effect. the radios use battery as well. manage your screen brightness and try edge only with the screen off using any number of apps that manage the radio. try one of entropys kernels to avoid a feature of the wifi chip (or was it bt) from sucking power when in proximity of another device with the same chip. turn off sync if you dont need push emails from gmail or real time facebook updates and if you really need battery life get in the habit of togging wifi and bt and gps on and off depending on need. i do none on this because i always found the battery life adequate on samsung phones but on my aria, well it was a must and prolly why people hate android. htc and battery life dont go together unless you manually manage the phone functions.
That's a great bunch of information. I currently keep my Brightness at 0%, GPS off, Wifi only ON when I'm at work when the charger is plugged in.
I guess I'm more concerned with the undervolting than the overclocking. I'd rather preserve the battery life with undervolting... the overclocking isnt a HUGE concern, but it'd be nice to see. Regardless, if you have any "ideal" UV settings, or ones that have worked for YOUR Infuse(assuming you have one), then I'd love to see them.
at one point i had -200mv on every freq from 100-1600mhz and no crashes. i started manually editing the uv script (voltage control is only able to write -200 into the script unless you have the pay version) and forgot what i ended up with. but my first infuse was exceptional in that area. some infuses freeze above 1400 mhz no matter what voltage settings are used. about -50 seems to be safe 99% of the time with minor or no overclock across the board but you could probably go -50 down low and -100 from 400mhz up to 1200 and -50 or -75 on overclock freqs. with underclock or atleast no overclock it's probably safe to go -100 to -150. it may be safe to go much more than that as well but on a small number of phones that might be too far as it is. cpus are made on such a small scale that microns of inconsistency make large percentages of difference. many dont pass testing and qc. some are borderline for the application, some are exceptional. the smaller the architecture gets the more potential the design has for speed but the larger the variance in performance is given a manufacturing technique. obviously the manufacturing gets better and better combating this so that they can make smaller architectures they also have redundancy built in, but sometimes they just disable features of a chipset and market it as an economy version if they have a low pass rate. ever see a 3 core cpu for a pc? most are manufactured as 4 cores and on many motherboards the bios can unlock the 4th core with somewhat unpredictable results.
Again, some really great info for the technical guys such as myself. What is the best way to test the UV settings? The built in tools and stuff in SetCPU? Or is there another way that would be more effective and/or would get more realistic results?
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
k-semler said:
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
Click to expand...
Click to collapse
uhh well.... yea and no. there are a few things you need to understand about microprocessors. no two are alike. they are built on a scale of a few nanometers and any difference causes a significant difference. to keep production numbers up there is a line they have to draw between performance potential and stability. more chips will be stable at lower clocks so they pick an speed they can get a high production number out of. sometimes a whole line of chips is produced with exactly the same core. chips that pass the highest get boxed as the highest performing and priced. chips that dont pass will either have specific features turned off, cores turned off or be underclocked and sold as lower models. in addition to that the top performing models are actually over priced, and often many more pass the tests than they need so perfectly good processors are intentionally disabled to fill the market for lower speed processors, so yes the cpu may be "underclocked" in a sense. but i don't know if that really applies to the infuse because i don't know if there are any chips in the same family that have a higher rated clock speed, if there are they aren't used in phones.
in example, on my pc i have a 3 core processor, it's actually a 4 core and i can even turn the 4th core on in bios, but a certain percentage of that particular model of chip will be unstable with the 4th core active.
another thing to understand is how the clock speed is set. there is a buss and a table of multipliers and dividers. so as one part of the chip oscillates at one frequency the multipliers and dividers say how may times per oscillation the other components go. the cpu speed changes by changing these multiplier values. the problem is that there are only so many multipliers the cpu is designed to use. this is a hardware limitation and can't be overcome so at some point the only way to get more clock speed is to change the buss speed which affects the entire system and will cause instability in most cases. occasionally you can get around this if you change the multiplier values for other componants as well but it's probably not a good idea to mess with it. the hummingbird chip only has multipliers to go to 1600mhz regardless of stability unless you mess with the buss, one developer got the galaxy s to 1700 with buss overclocking but some things didn't really work at that speed and it took a lot of changes to other system clocks. snapdragon chips can go to higher clocks and process numbers better but the hummingbird is better for graphics and multimedia which is more important on a modern phone imho.
so yeah 1600 is it, as far as practicality goes anyway. there are a few infuses that can only go to 1400-1500 as well and galaxy s phones which have the same clock limitations but are only rates for 1000mhz rarely go to 1600, but a few do, my captivate was absolutely peaked out at 1300, believe me i tried to get it higher, i tried a lot of things with voltages to try to get it stable, but even 1300 took some doing. it took a long time before developers even produced a kernel for the sgs that used clocks over 1200 because many of the early builds of the sgs series were much like mine and were not stable at high speeds.
Beautiful. :thumbup:
Sent from my SGH-I997 using xda app-developers app
Running: Asus Transformer TF101 (with Tegra 2 chip)
OS: EOS Custom ROM 78 (Jelly Bean) -- And THANKS to 'em!
Short Question: What the heck are those minimum/maximum MHz settings' optimal numbers?
Long Question: My TF101 w/ EOS Nightly #78 has an overclocking feature in it. Very cool. There are not one, but TWO, separate settings for the chip -- a minimum MHz (starting at 200MHz or something) and a maximum MHz (all the way up to 1600MHz). But after I messed some with it (and like a dunce did not write down the original values) I experienced some random reboots, usually after I closed the lid a while and then reopened it.
So, my question's long version (which is actually a number of questions), follows...
* What are the original values of the Tegra 2 chip in one of these babies? I mean, 1000MHz (1Ghz) is probably the maximum default setting, since that's the chip's official rating. But what's the minimum setting supposed to be at?
* Can I do something as crazy as to tell it to run minimum of 1200MHz and maximum of 1600MHz? In fact, I'm trying that right now and it seems to be working.... but I doubt I'll leave it that way even if it does (makes me nervous about messing up the hardware).
* What optimal settings have others tried with this chip in this (TF101) unit.... or even in other Tegra 2 based tablets?
Thanks for reading. Looking forward to comments.
shonkin said:
Running: Asus Transformer TF101 (with Tegra 2 chip)
OS: EOS Custom ROM 78 (Jelly Bean) -- And THANKS to 'em!
Short Question: What the heck are those minimum/maximum MHz settings' optimal numbers?
Long Question: My TF101 w/ EOS Nightly #78 has an overclocking feature in it. Very cool. There are not one, but TWO, separate settings for the chip -- a maximum MHz (starting at 200MHz or something) and a maximum MHz (all the way up to 1600MHz). But after I messed some with it (and like a dunce did not write down the original values) I experienced some random reboots, usually after I closed the lid a while and then reopened it.
So, my question's long version (which is actually a number of questions), follows...
* What are the original values of the Tegra 2 chip in one of these babies? I mean, 1000MHz (1Ghz) is probably the maximum default setting, since that's the chip's official rating. But what's the minimum setting supposed to be at?
* Can I do something as crazy as to tell it to run minimum of 1200MHz and maximum of 1600MHz? In fact, I'm trying that right now and it seems to be working.... but I doubt I'll leave it that way even if it does (makes me nervous about messing up the hardware).
* What optimal settings have others tried with this chip in this (TF101) unit.... or even in other Tegra 2 based tablets?
Thanks for reading. Looking forward to comments.
Click to expand...
Click to collapse
Generally its all up to your specific chip and how much it can handle as all hardware isn't created equal especially Tegra soc's... the stock speed is 1GHz for the TF but could easily run higher... i would only run your min so high if doing benchmarking not everyday use.. it will kill your battery faster, it would tho benefit benchmarking Because it would run at the highest speed and not have a chance to jump to a lower speed... wont do any damage to the chip since it has built in thermal throttling anyways... my suggestion would be setting your min to the lowest and With the max speed start at 1.2GHz with some stability tests, or heavy use at different OC speeds to find your chips sweet spot with both stability, Battery life and performance.. and have fun
DJLamontagneIII said:
Generally its all up to your specific chip and how much it can handle as all hardware isn't created equal especially Tegra soc's... the stock speed is 1GHz for the TF but could easily run higher... i would only run your min so high if doing benchmarking not everyday use.. it will kill your battery faster, it would tho benefit benchmarking Because it would run at the highest speed and not have a chance to jump to a lower speed... wont do any damage to the chip since it has built in thermal throttling anyways... my suggestion would be setting your min to the lowest and With the max speed start at 1.2GHz with some stability tests, or heavy use at different OC speeds to find your chips sweet spot with both stability, Battery life and performance.. and have fun
Click to expand...
Click to collapse
I'm not sure where the "thanks" button is yet here, but will try to figure it out. Wait.... I just did.
Tonight I backed the minimum down to the 800 vicinity (whatever that number is) and left the top number at 1600. My recent test has been to run Angry Bird, which is not the most stable program. It runs just fine at this setting. The battery is draining fast, though.
So you are suggesting that taking it all the way to the basement minimum-wise will still give me fairly stable top end? I keep wondering if there's any relationship at all between the two numbers, if at some point they don't affect one another adversely if too far apart? This idea is based on no knowledge whatever.
So any furhter thoughts welcome.
shonkin said:
I'm not sure where the "thanks" button is yet here, but will try to figure it out. Wait.... I just did.
Tonight I backed the minimum down to the 800 vicinity (whatever that number is) and left the top number at 1600. My recent test has been to run Angry Bird, which is not the most stable program. It runs just fine at this setting. The battery is draining fast, though.
So you are suggesting that taking it all the way to the basement minimum-wise will still give me fairly stable top end? I keep wondering if there's any relationship at all between the two numbers, if at some point they don't affect one another adversely if too far apart? This idea is based on no knowledge whatever.
So any furhter thoughts welcome.
Click to expand...
Click to collapse
It is best to leave the min freq as per default and push only the max freq. Then, you can set application profiles whereby you will allow an oc if you play a specific app(this feature requires an app that is called setcpu). This is to allow you to gain the best battery life(what you did is okay as well, but you'll have less battery life as the proc is running at 800mhz at min)
Otherwise, you can do it manually by setting the governor. For example, when you want to play games, set the governor to performance and oc your proc. When you don't want to play games anymore, then set it back to interactive or ondemand(or any other suggested governor for your device) to allow battery saving
wcypierre said:
It is best to leave the min freq as per default and push only the max freq. Then, you can set application profiles whereby you will allow an oc if you play a specific app(this feature requires an app that is called setcpu). This is to allow you to gain the best battery life(what you did is okay as well, but you'll have less battery life as the proc is running at 800mhz at min)
Otherwise, you can do it manually by setting the governor. For example, when you want to play games, set the governor to performance and oc your proc. When you don't want to play games anymore, then set it back to interactive or ondemand(or any other suggested governor for your device) to allow battery saving
Click to expand...
Click to collapse
I have setcpu but after mucking about with it managed to end up with an unstable system (spontaneous reboots, esp. after closing then opening lid and "waking up" the TF101). Currently I'm just using the EOS Rom's own system settings and having low end all the way to minimum (200 something) and top end at 1500+. The 1600 mhz setting is apparently a problem for this machine (the spontaneous resets again). But at 1500 whatever it seems just fine
One other issue, very important to all of us (harhar), is that Angry Birds seems unstable since I updated to this custom EOS rom. I noted elsewhere that someone said simply turning off wireless would disable ads and stablize the game. I've not tried that yet. Losing angry birds for me would not be a major blow.
Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
OC 806 can damage your phone for ever manage carefully this
Sent from my LG-P500 using Tapatalk
And what are the safest levels? And best governors? Im actually using smartass min 480 max 729
Overclocking will not "damage your phone for ever." Some of the P500s are stable at higher clock speeds than others, which is typical of mobile CPUs (even the two cores of my Sensation's CPU are stable at different maximum clock speeds). IIRC, my Optimus T was only stable up to 729 MHz. If you try to overclock higher than your phone is capable of, then it will freeze or reboot. There really isn't a "safest" level; any clock speed that your phone is stable at is going to be perfectly safe. Run a stability test or benchmark app from the Play store to check stability. IIRC, another easy way to test stability on the P500 is to open a camera app. The camera tends to crash the phone when the CPU is clocked too high. If you manage to crash the phone by doing any of that, then I recommend dropping down to a lower clock speed. Otherwise, the phone is fine and you can test a higher clock speed. FWIW, I'm pretty sure that most P500s are stable up to 729 MHz, but many of them are not stable higher than that.
I personally like to use Interactive governor. I think I used Interactive with min 480 and max 729 on my Optimus T. Governors Explained
chalo99 said:
Hi, I have some questions with kernels, overcloak and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
Click to expand...
Click to collapse
1. I use smartass as governor (well on the jenkins build). It has a balanced battery and performance I think.
2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.
3. Well overclocking on android depends on the ability of the kernel to handle overclocking situations. Some kernel can handle overclocking very well that the noticable errors are up to a minimum level. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.
unless yo go y.o.l.o over your hardware.
4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.
5. Before, we use to have different kernel developers and different rom developers. as the the passed by and newer devices are being developed, some migrated to newer devices and abandoned the development for our beloved phone. Now I think only 1 developer is still developing (original development not just cuztomizing and stuffs it with design) androidmeda (check "jenkins armv6") and the kernel included in the rom is sufficient enough to handle overclocking (used it and set the freq to 320 - 710 at smartass). I also use sweetnsour's kernel before but i think he too abandoned the development)
5. k
engr_exxi said:
2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.
Click to expand...
Click to collapse
That isn't true. Processor manufacturing is inexact, so some processors end up with higher clock speed capability than others. As the maker of a device, you have to set the clock speed low enough that ALL of the processors in ALL of the devices function properly. Setting the clock speed conservatively means that most or all of the devices are actually capable of functioning at a higher clock speed, which in most cases -- and certainly in the case of the P500 -- is completely safe. And it is extremely naive of you to believe that every processor or computer you buy is running at the "best and safest" speed as tested by the manufacturer. CPUs are often significantly underclocked simply to allow manufacturers to differentiate pricing. The same thing is done with finished products, including smartphones. For example, my HTC Sensation has a Qualcomm MSM8260 clocked (originally) at 1200 MHz. The HTC Sensation XE has the exact same processor clocked at 1500 MHz.
3. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.
unless yo go y.o.l.o over your hardware.
Click to expand...
Click to collapse
Again, it is nonsense to say that overclocking this phone "is not really safe." You won't find one example anywhere of a person who has damaged this phone by overclocking it. These things don't get hot enough at any clock speed to damage the hardware.
4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.
Click to expand...
Click to collapse
4.a. Heat is probably the only legitimate concern with overclocking a smartphone, and that's exactly why there is no risk with the P500 -- it doesn't get anywhere near hot enough, at any clock speed, to cause any damage.
4.b. This shouldn't be a problem. If your phone is not setting clock speed on boot, then a crash/reboot will send your phone back to the original clock speed. Even if you make a mistake and change a clock speed that is being set on boot (which I actually did by accident just yesterday), you can boot directly into recovery and restore a backup.
4.c. Who cares? As I said before, if your system is unstable as a result of overclocking, then you should lower the clock speed. That isn't a problem.
4.d. *sigh*
But to each his own. If you don't want to go "yolo" with your antiquated $50 smartphone, then by all means, keep it at 600 MHz. Nevertheless, there is absolutely no way that you would damage it by overclocking, regardless of what you may believe.
Well, its overclocking and not overcloaking.
Small error, but make changes in the OP
rhar**** said:
Well, its overclocking and not overcloaking.
Small error, but make changes in the OP
Click to expand...
Click to collapse
I wrote it bad in the title, but in the middle of the post it was OK. Thanks anyway, ****ing spanish that you read it like you write it, or viceversa.
chalo99 said:
Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
Click to expand...
Click to collapse
The phone won't work above 729MHz. And the only risk i can thinknof is depleting battery life faster.
Im actually using interactive min 480 max 806.
That permit no lag and normal reactivity.
Obviously there is a battery drain than normal.
I've also use a seeder application.