could anyone suggest a safe clock speed for the play? i want to get a bit more power from the stock 1ghz processor but i don't really want to overdo it
Honestly, clock speeds are phone specific. For example, my phone might do just fine at 1.5, but your phone may not be able to go past 1.3, so you need to find your safe zone yourself.
Get an app that handles overclocking, SetCPU, AnTuTu CPU Master, etc. I use Rom Toolbox Pro. Move your CPU one step up, then play around for a while. If your phone doesn't bug out, go ahead and try the next one, until it won't go any higher without bugging out.
Make sure you don't lock your speeds at boot until you're sure it's safe.
I wouldn't recommend going above 1.6ghz even if your phone supports higher frequencies. It tends to get hot quite quickly at such high frequencies, and could be detrimental to the battery
thank you for the advice... ill try to see how my phone reacts to different clock speeds... and not go over 1.6
seagheart89 said:
could anyone suggest a safe clock speed for the play? i want to get a bit more power from the stock 1ghz processor but i don't really want to overdo it
Click to expand...
Click to collapse
i usually use 1.6 or 1.8 i feel that you should never oc it to the max it is allowed.
Depends entirely on the 'yield' of each individual processor, most can run over 1ghz but some can't, so to be safe all processors are set to the lowest safe speed.
My XP is stable at 1.8ghz. 1.9ghz causes occasional reboots, 2.0ghz is an instant crash.
Remember your unit will only get warm if the CPU is being worked hard, if it's idle then it will stay cool even at higher clock speeds. Using a more active CPU governer such as 'smartass' or 'interactive' will keep clock speed down when not required.
Also remember you can't overclock on the stock kernel.
Same here, I accidently overclocked to 2Ghz, instant crash. But 1.6Ghz is fine, yet eats battery like it's the cookie monster on crack.
Related
Okay, so my question is basically how stable is overclocking your g2? I typically keep it at 800 when I use my phone normally, than 1.5ghz for games. I wante d to keep my g2 at 1.5ghz forever.. is that bad?
My battery obviously increases in temp..
I just use 1GH. It's enough for all game now. and didn't see any bad to battery or phone
I've had my DZ for about three weeks now and all this time I've had it consistently overclocked to 1843MHz. At that high of a speed, I had to let the phone cool down after 20 minutes of use.
Just today I flashed pershoot's 1516MHz kernel and noticed no heat issues after ~45 minutes of consistent use (temps < 40C).
I have had my g2 for.... However long they been out. I have always been overclock to at least 1.5 with zero heat issues. I ran 1.8 and even 1.9 for a good long time as well. Those speeds have heat issues ones that required a battery pull a few times because it started heating up faster then i could shut down the phone. If your going to OC at those speeds makes sure you set temp profiles with alarms.
Sent from my HTC Vision using XDA App
ARM processors, like our snapdragons, are a lot more forgiving on the overclocking front than what you might find in your desktop, for instance.
I still treat overclocking on my phone like I do my computers, though... setcpu has a stress test built in that you can use if you're curious how "stable" your overclock is. but in my experience, I've found that you can get away with just playing around with it and using the phone normally and seeing how it reacts to different clockspeeds.
right now, I run it at 1.1ghz (24/7). I have run it at 1.5ghz (24/7) in the past for PSX/N64 emulators, but I've found with my new setup (pretty light; no widgets, very few things going on in the background, stripped as many unnecessary apps as possible, and not using any animations or fancy bits) that 1.1ghz is more than enough to be able to play the games I play on any emulator smoothly.
you should be fine at any speed that is currently available in the overclocking kernels we have with the exception of flippy's 1.9ghz kernel, which does require some monitoring to keep things cool and stable. but it still does vary from phone to phone. if you're running at 1.5ghz and the phone isn't doing anything wonky, then you shouldn't worry about it. if you're running it at 1.5ghz and you're experiencing stability issues, random force closes that aren't fixable through conventional methods, or heat issues, you should probably back off a bit.
some people have problems at 1.2ghz, some people are running at 1.9ghz all the time and never have problems... just find what works best for normal usage with your device and go with it.. it's not like we keep these things for more than a couple of years anyway, and the processor will be capable of handling the [stable] overclock for that period of time.
im always at 1.2ghz. 768 as min, interactive gov (when i use CM7) and battery has been fine, havent noticed any major issues. hard to tell if it was the rom bugs or OC being the issue but from what i read all my issues others have at various speeds so im guessing it was rom related
i think it depends on the rom.
when i use the Pyromod rom i dont need overclock but for other roms like sense roms those I require OC. I always keep it at 1400 when needed.
I have a og evo I want to know why when I overclock to 1.2ghz it freezes my phone why does it do that ?
Sent from my Nocturnal 4G using xda premium
Each Evo is different. Some of them can't handle that high overclock, or can't be undervolted very low. Each one is different, each has its limits.
I don't understand the big deal with overclocking. It burns your battery faster. I personally underclock, with little to no lag and is good enough for my casual gaming needs
Mine doesn't like a clock much at all. I can get about 1.1 before it starts locking up but even then it hangs a lot. I honestly don't see a difference from 1.0 to 1.2. Get a decent rom, good kernel and try out the v6 script an I almost guarantee you will like that better.
beaumontcali48 said:
I have a og evo I want to know why when I overclock to 1.2ghz it freezes my phone why does it do that ?
Sent from my Nocturnal 4G using xda premium
Click to expand...
Click to collapse
Well for us to be able to help you, you would need to provide us with more details on how you are trying to accomplish this.
I use no frils cpu but have also tried setcpu and viperMOD I know that's the best way to overclock but is very confusing. Have any step by step instructions to of to 1.2 I know having higher voltages helps as well.
Sent from my Nocturnal 4G using xda premium
Sent from my Nocturnal 4G using xda premium
Overclocking is overrated. If you need to overclock for every day usage, then something is wrong - at least in my opinion. Resource intensive gaming is different, but you shouldn't need to overclock for browsing, texting, casual games, etc.
Try out the V6 Supercharger script. I'm not currently using it, but have in the past and it seemed to make my phone more snappy. A lot of people swear by it and it's a great script, definitely worth a shot. There are other things you can do to speed up your phone without overclocking. I'd try other options first since overclocking will chew through your battery. Increase the dalvik vm heap size, there are plenty of free apps on the market to help with this task. Uninstall apps you don't use, I'll bet that you never use some of the apps on your phone. Back them up with Titanium Backup and you can restore them if you ever need them again.
In case you didn't already know, the Evo can't overclock past 1.2, I'm not 100% sure why - it has something to do with the processor.
Supersonic Evo 4G | MIUI | Tapatalk
I never oc over 1075 and only when plugged in if i play a game I need to oc.for I just activate my charging profile and plug up and play 1.2 ghz is a good chance of doing serious.damage as these older scorpion processors get very very hot at that clock speed so they lock up to try and protect themselves from heat damage or they shut down the phone 1075 is as high as you should need to go for any games the evo can handle on the subpar gpu
Sent from my Classic-EViLizED-ToMAToFiED-EVo4g-
beaumontcali48 said:
...also tried setcpu and viperMOD I know that's the best way to overclock.
..
Click to expand...
Click to collapse
I'm pretty sure viperMOD is more for undervolting than overclocking, which are not suppose to be combined together. I am running vipermod with max voltages - 50. Other nite was playing snes9x and was getting some lag with a game so I bumped max CPU up to 1.2. Phone went into a bootloop and had to superwipe and reflash everything. Don't know if its b/c vipermod + 1.2 CPU or just bumping up CPU. Didn't try it again.
Support TrevE!!
shift
Get a shift. Mine runs fine at 1.9. But usually run it art 254-1200 on demand.
{ParanoiA} said:
I'm pretty sure viperMOD is more for undervolting than overclocking, which are not suppose to be combined together. I am running vipermod with max voltages - 50. Other nite was playing snes9x and was getting some lag with a game so I bumped max CPU up to 1.2. Phone went into a bootloop and had to superwipe and reflash everything. Don't know if its b/c vipermod + 1.2 CPU or just bumping up CPU. Didn't try it again.
Support TrevE!!
Click to expand...
Click to collapse
You can overclock and undervolt together just fine. You just need to ensure that every frequency has a high enough voltage to run the processor at that step. My Evo is overclocked and undervolted just fine, although IIRC I can only push it up to 1.1 GHz . My tablet is 1ghz to 1.6ghz and is undervolted as well, though.
merge rls 2.0, iron monkey, Droid overclock because of the profiles options. I set up four profiles including one for temp. sometimes i'm underclocking and sometimes overclocking but only up to 1.19 to prevent freeze and boot loops. Only downside is right at open Droid overclock needs su permission but that is my choice since profile changes at open.
Very snappy afterwards.
Sent from my PC36100 using XDA Premium App
When I had the 4G, I was never able to go above 1118, or somewhere around that. It would have freezing issues.
On my evo shift, I was able to do 1.7 gHz (compared to stock 800 mhz) ok. 1.6 pretty reliabily, and I could run 1.5 all day long. Some guys could do 1.9. It just depends on the phone.
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
tommy0823 said:
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Shoot the brutha a link
TrevE Supporter!
tommy0823 said:
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
What? Overclocking and undervolting are two completely different things, and they aren't mutually exclusive. Unless you can provide a good reason as to why it's counter productive to do both, I don't buy that at all. Just checked my phone, my overclock requires an extra 25 mV for all three steps I've overclocked. 25mV isnt much, and it certainly isn't going to kill my battery that much faster.
Besides, the only time the CPU is going to be entering these high power modes is when it needs to do work, and it's better to do work as fast as possible to go back to sleep. Would you rather wake up, do a mundane task for 5 minutes, then go back to sleep or wake up, do a task at 2x the speed while only consuming 30-50% more energy, then going back to sleep after only 2.5 minutes?
HUGI is real.
Sent from my Transformer TF101
Yea shot me the link too bro.
Sent from my PC36100 using xda premium
First let me say I don't use viper mod or any voltage controlling mod.
On sense 3.0 roms such as mikg I over clock to 1152 and set the minimum to 384 and its smooth as butter. No problem and battery lasts all day.
On aosp however such as decks (I'm on it now) I underclock to 499 and leave the min at 254. Smooth as always and battery lasts forever.
Anything past 1152 is going to cause problems (at least in my experience) also the rom/kernel can effect how much you can overclock.
Sent from my PC36100 using xda premium
Gary13579 said:
What? Overclocking and undervolting are two completely different things, and they aren't mutually exclusive. Unless you can provide a good reason as to why it's counter productive to do both, I don't buy that at all. Just checked my phone, my overclock requires an extra 25 mV for all three steps I've overclocked. 25mV isnt much, and it certainly isn't going to kill my battery that much faster.
Besides, the only time the CPU is going to be entering these high power modes is when it needs to do work, and it's better to do work as fast as possible to go back to sleep. Would you rather wake up, do a mundane task for 5 minutes, then go back to sleep or wake up, do a task at 2x the speed while only consuming 30-50% more energy, then going back to sleep after only 2.5 minutes?
HUGI is real.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Its counter productive because it is giving less to something that needs more. (Don't take this post as me trying to be a ****. Just voicing how someone explained it to me a while ago)
Think of this as cars.
Lets say you have a nice fancy v8 mustang. Stock, everything is well, balanced.
If you start adding parts and get it pushing out 1000 horsepower (overclock) your most likely gonna need more feul (voltage) or at least stock amount flowing into the engine just to keep it running.
Now lets say you got that same 1000 horsepower gas destroying mustang and you start to lower the amount of gas flowing into the engine (undervolt (done in vipermod)) cylinders (CPU) wont get enough gas, it wont work, and your stuck going no where.
So if that made sense (did to me) then you can see why they are counter productive. Unless your using vipermod to overvolt (which idk if you can since I don't use it) then you can disregard this whole post
Sent from my PC36100 using xda premium
Your car analogy is completely irrelevant. You can look up the exact voltages that the CPU runs on at every frequency, *even when overclocking*. Overclocking an Evo 1ghz to 1.2ghz takes maybe a 5% bump in voltage, and that 5% extra power is only going to be used *when the CPU is running at max speed* (which is only when there is a lot of work to do), and even then, it's *still better to let the CPU run at max speed with a tiny bit more power consumption than to cap the CPU at a slower speed and make it work for even longer*. Intel calls it HUGI, Hurry Up and Get Idle.
I know what I'm talking about, and I wish people would stop trying to argue with me based off of second hand speculation. I do this for a living, after all. There is absolutely nothing wrong with overclocking and undervolting, and it's the best way to get the most battery life *and* performance out of your phone, period.
Sent from my Transformer TF101
Gary13579 said:
Your car analogy is completely irrelevant. You can look up the exact voltages that the CPU runs on at every frequency, *even when overclocking*. Overclocking an Evo 1ghz to 1.2ghz takes maybe a 5% bump in voltage, and that 5% extra power is only going to be used *when the CPU is running at max speed* (which is only when there is a lot of work to do), and even then, it's *still better to let the CPU run at max speed with a tiny bit more power consumption than to cap the CPU at a slower speed and make it work for even longer*. Intel calls it HUGI, Hurry Up and Get Idle.
I know what I'm talking about, and I wish people would stop trying to argue with me based off of second hand speculation. I do this for a living, after all. There is absolutely nothing wrong with overclocking and undervolting, and it's the best way to get the most battery life *and* performance out of your phone, period.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Hmm, *interesting*. I believe the best answer to the OP was covered rather well earlier. It's all about your rom/kernel/hardware combination. With all the variables to consider as relevant, your best bet is to experiment and find what works for your device. Don't check set on boot untill you are confident the set-up is stable. Higher is not always better with overclocking. My device runs blazingly well underclocked @768max. Gets insanely great battery @499max. However my quadrants are better @ 1036 than at 1190.
Great thing about android is you can experiment and learn through trial and error.
Sent from my PC36100 using xda premium
Hi friends,can the doomkernel really reach 2ghz?indeed i don't want to burn my xperia but my question is only for curiosity and eventually for testing(but not at 2ghz xd).i know that overclock kill the duration of the battery but what is the max rocksolid frequency?and anyone tested the 1.9/2 ghz ?is it stable?is the performance really increased with overclock?thank you very much
It depends on your specific device for whether 2.0ghz works or not. For mine, 2.0ghz does work (voltage 1500), though I don't use it since I never need that much power. The performance does increase quite a big with overclocking, but it's usually not actually necessary.
About the 2Ghz.
I have DooMKernel 2Ghz installed, but whenever I actually put the slider (on setCPU) on 2Ghz, my phone reboots. The highest I have ever performed a benchmark was 1,7Ghz, but it became very hot. You can try to push it to 2Ghz though, on my phone trying hasn't caused any problems.
1.5 to 1.6 Ghz is the Safest for Xperia Play
So 1.5 ghz... Is fine for xperia play.. But, is what all u talking about related to processor speed.. I m not understanding this concept of overclocking.. N does this overclocking really makes to run the play fast than it is now at 1 ghz...??
Silverstarjigar said:
So 1.5 ghz... Is fine for xperia play.. But, is what all u talking about related to processor speed.. I m not understanding this concept of overclocking.. N does this overclocking really makes to run the play fast than it is now at 1 ghz...??
Click to expand...
Click to collapse
overclocking is the process of making the CPU operate faster than specified by the manufacturer. It does indeed make the phone faster, but also makes the battery life shorter.
I've done it, don't really care to though seeing as how it drains the battery way too fast. But it just depends, some phones can handle it and some can't even if they are the same exact phone model
I heard there was a problem with stability issues before. Has it been fixed?
Also, do any of you guys feel the need to OC in the first place?
iArtisan said:
I heard there was a problem with stability issues before. Has it been fixed?
Also, do any of you guys feel the need to OC in the first place?
Click to expand...
Click to collapse
I tried OC'ing to 1,4 for a short time, didnt get any instabilities.
Which leads me to question two. No I don't feel the need to OC this phone, it is still good enough to cope with everything i throw at it.
The worst that will happen is that it will run a little hotter than normal. I was running Trinity Kernel on RasCream ROM clocked at 1.5GHz and it was fine, nothing crashed, no reboots, all was well.
Besides; It's a Nexus, it was built for this!
This varies for everyone
Sent from my GT-I9300 using Tapatalk 2
Meh. It all varies. No 2 chipsets are the same. What may work for someone else may not work for you. Trial and error is the only surefire way to find out.
Hi,
I agree with what has been said above, all the CPU's are not equal but actually the progress made by the kernel devs allows all (or almost) phones to run at 1.3* Ghz (1.34/1.35 Ghz, it depends of the kernel) without any issues.I think it's for all, actually I don't remember a user with issues at 1.3* Ghz...
And for most phones 1.5 Ghz is fine.For some others, above 1.5 Ghz is problematic but it depends also of too many factors.
Now it's not like it when the Genx came out, where 1.3 Ghz was the limit of CPU overclock for all the phones.
And many people can run stable at 1.65 Ghz, also it depends of the kernel.
For me for example my max CPU freq usable each day, so stable is 1.72 Ghz with Glados kernel, above (like 1.8 Ghz) it runs fine for 30 mins, sometimes 1 hour, but after always freeze/reboot... maybe my CPU can't reach this CPU freq or maybe my settings are wrong (voltage) ...
I agree, an extreme overclock like 1.72 Ghz is not really necessary for all day (heat, battery life, etc...) but a little overclock like 1.5/1.53 Ghz and you a difference in certain case (openning some apps, general UI, browsing, etc...).
But if we have the ability to test and play...why not... ,in any case for me it's yes, I like overclock and test the possibilities/limits of my phone, different settings...
Everyone does as he wants and it depends on what you want (battery life,a little more power in some situation like playing or a higher bench score ).
Well considering Texas instruments recommended highest clock speed for this processor is 1.5 ghz I'd say your fine. Anything above that is dependent on how well your chip set will handle it. Besides who honestly has needed to OC for anything other than benchmarks?
Sent From My Sprint Galaxy Nexus
There is definately some sort of bug in my note 2 or all note 2 cpus
Iv been trying to find out why nova3 and mc4 have random lag spikes and then smooth gameplay. At first like many people said
Gameloft games arent optimized well i belived that. While thats true to some extent heres what iv found
Using set cpu or tegrak to force the cpu at max clock fails after hitting 38c
Thus causeing lag in game
No matter what setting iv tried the moment my phone hits 38c the cpu
Locks back to 800mhz. My phone is rooted yet there is no way i can maintain the clock at 1.6ghz
Im now using androd revolution rom and that hasnt helped either. Does anyone else have this issue?
To test run nova3 or mc4 any level and stay in there moveing around after the phones warm enough(around 38c for me) youll notice
Stuttering. Check ur cpu and ull find its downocked to 800mhz
Dear nielo360,
Probably, you are reading the battery temp not the cpu temp since note2 cpu throttles at 80 c...
Try system tuner pro application to read real cpu temp...
If you are overclocking or wanna lock the cpu to max speed then you should do undervolting by installing custom kernels like perseus...
Try to undervolt both cpu and gpu...
Also try to lower your brightness to stay away from extra heat that screen makes...
Issue discussed before so you can refer to here :
http://forum.xda-developers.com/showthread.php?t=2058119
Hope all these helps...
Kind Regards..
Sent from my Amiga Note
Thanks for the reply, i did follow the thread and undervolted my cpu running at 1.3ghz 1025mv however my phone reaches 67c true temp and throttles very easily any idea if this normal i cant play any 3d games unless im sitting near a fan or ac. Every says they throttle at 80c
It is set to throttle for good reason. It may b irritating but I would let it be and not tamper with it.
Sent from my GT-N7100 using xda app-developers app
nielo360 said:
There is definately some sort of bug in my note 2 or all note 2 cpus
Iv been trying to find out why nova3 and mc4 have random lag spikes and then smooth gameplay. At first like many people said
Gameloft games arent optimized well i belived that. While thats true to some extent heres what iv found
Using set cpu or tegrak to force the cpu at max clock fails after hitting 38c
Thus causeing lag in game
No matter what setting iv tried the moment my phone hits 38c the cpu
Locks back to 800mhz. My phone is rooted yet there is no way i can maintain the clock at 1.6ghz
Im now using androd revolution rom and that hasnt helped either. Does anyone else have this issue?
To test run nova3 or mc4 any level and stay in there moveing around after the phones warm enough(around 38c for me) youll notice
Stuttering. Check ur cpu and ull find its downocked to 800mhz
Click to expand...
Click to collapse
The stuttering in mc4 has been driving me crazy.
I also used a tool to measure cpu and find that the game runs well for the first few matches and then it does tend to lock itself at 800mhz and the sideshow begins.
My phone doesn't get that hot, but something is definitely going on. I really hope that gameloft can optimize this game. These games running on ios are so much smoother that it's embarrassing for Android "super phone" users.
Sent from my Galaxy Note 2 using Tapatalk 2
The problem is not the cpu its the gpu throttleing as samsung has for some odd reason overclocked it. The fix for this is a bit tricky
If you use tegrak ultmate Do not force gpu lock at 533mhz this will underclock the cpu automaticly and make it unstable after a few mins instead
Set level 0 gpu 533mhz stock
Undervolt if your like
Set level 1 440mhz
1025
Seg level 2 440mhz
1025mv
.. leave the last level at stock 166mhz
Cpu you can scale it or leave it doesnt matter mine is locked at 1.3ghz
This works great for the most part and u wont notice the downclock as the clocks will move between 533 and 440 during heat.
nielo360 said:
The problem is not the cpu its the gpu throttleing as samsung has for some odd reason overclocked it. The fix for this is a bit tricky
If you use tegrak ultmate Do not force gpu lock at 533mhz this will underclock the cpu automaticly and make it unstable after a few mins instead
Set level 0 gpu 533mhz stock
Undervolt if your like
Set level 1 440mhz
1025
Seg level 2 440mhz
1025mv
.. leave the last level at stock 166mhz
Cpu you can scale it or leave it doesnt matter mine is locked at 1.3ghz
This works great for the most part and u wont notice the downclock as the clocks will move between 533 and 440 during heat.
Click to expand...
Click to collapse
i found that the real throttling problem is a security protocol that Samsung roms have. When the battery reach 41C the cpu throttles (no matter if its only at 60C cpu temp)
i dont know how to deactivate that protocol...but if you want, try CM10.1 or any other AOKP or AOSP roms and you´ll see that there is no cpu throttling unless the cpu reach 80C.
you´ll need "stability test" app (cpu stress testing, and you can watch battery temp), and "system tuner" app (to watch live cpu temp during the stress test)