Related
Hey all, I want to get some info on the limitations of our processor, mainly is their a ceiling on how high we can overclock our Evo's?
I am sure most of us here are familiar with the insanely fast 1.3ghz-1.8ghz(I think the top I read was 1.8ghz) speeds some newer phones are getting clocked to, the only thing that caught my eye about these speeds is that they are reported stable & usable. Coming from a Hero(a while ago) that I had to overclock to my Evo that is not really necessary to overclock was nice, BUT it would be awesome to have an Evo clocked at 1.5ghz-1.8ghz and stable as well as usable, is this even remotely doable? If not what is causing the limitation? Just curious
Edit: HAPPY THANKSGIVING, I am very thankful for my wife & kids as well as all you great guys and gals here at XDA!
Sent from my White Evo 4G
It all depends on your phone....what may run on yours may send mine into random reboot...I found mine is stable at 1.13
You may want to raise the bar a little at a time to see what you can handle....be sure not to have it set on boot till you are sure your phone can handle it....
Sent from my froyo using the xda app
matthewjulian said:
Hey all, I want to get some info on the limitations of our processor, mainly is their a ceiling on how high we can overclock our Evo's?
I am sure most of us here are familiar with the insanely fast 1.3ghz-1.8ghz(I think the top I read was 1.8ghz) speeds some newer phones are getting clocked to, the only thing that caught my eye about these speeds is that they are reported stable & usable. Coming from a Hero(a while ago) that I had to overclock to my Evo that is not really necessary to overclock was nice, BUT it would be awesome to have an Evo clocked at 1.5ghz-1.8ghz and stable as well as usable, is this even remotely doable? If not what is causing the limitation? Just curious
Edit: HAPPY THANKSGIVING, I am very thankful for my wife & kids as well as all you great guys and gals here at XDA!
Sent from my White Evo 4G
Click to expand...
Click to collapse
not exactly sure how it works on the phones but if its anything like a pc processor then it would take a kernel that can tweek voltages right like to get a 1.8 on our ever i would say it would need about a 3 step down uv but not sure if it would be stable heck at 3 step down uv it shouldn't boot unless its set oc'd on splash boot I'm pretty sure since our proc. are first gen snapdragons and the one's in the G2 and myTouch 4G are second with a smaller die ours won't be able to make it that far up with out major modification
Hmmm......so if I were to get off my ass and learn to compile a kernel I could at least attempt it, good info, thanks! At least now I have a place to start researching, I think I would be happy with a bump to an even 1.5ghz if it were stable, well if anyone else has more info I'm all ears!
Sent from my White Evo 4G
I got mine at 1.15 anything past that seems unstable 1.2/1.25 reboots automatically (cm7 nightly 88)
The FroYo kernels come unlocked to 1190 I believe. When I was running FroYo I ran 1152 all the time. You don't really need to compile your own kernel unless you really want to. All of the kernels available here are unlocked except for the stock kernels. Also 1190 was about the limit for most EVOs.
I don't have an evo, but I do have a snapdragon, use quadrant to check scores after an overclock. 1190 isn't so good. Makes lower scores than the stock 1ghz. Fsb bottlenecks at that speed, but gets a boost at 1530. I've had my snapdragon around 1600 stable all day. Low battery life though.
Sent from my HTC HD2 using XDA Premium App
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 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
OK, so I currently have my PLAY set to 1.2ghz. My first android phone I OCd from 600mhz to 1ghz and one day while playing a game I heard a loud pop noise, then my phone shut off and that was that... toast. So I have been extremely leary of overclocking now. I am aware there are users who have OCd their phone to 1.4+
My question is how safe is when I use No frills to OC is it ramping up the volts to get that extra power. Also according to the Snapdragon layout it lists the S2 in our phones as capable of 1-1.5ghz... does this mean I could technically go up to 1.5 and be OK? I have a large 3600mha mugen battery, so thats not an issue, but what I am afraid of is popping my phones brains out...
http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
Look at Snapdragon S2 section
MSM8255
Also, it sayd for phones that use the above chip.. GSM only for Xperia PLAY... if that is the case does that mean R800x users are on a differerent chip? And if so what chip is it? Thanks in advance.
jgregoryj1 said:
OK, so I currently have my PLAY set to 1.2ghz. My first android phone I OCd from 600mhz to 1ghz and one day while playing a game I heard a loud pop noise, then my phone shut off and that was that... toast. So I have been extremely leary of overclocking now. I am aware there are users who have OCd their phone to 1.4+
My question is how safe is when I use No frills to OC is it ramping up the volts to get that extra power. Also according to the Snapdragon layout it lists the S2 in our phones as capable of 1-1.5ghz... does this mean I could technically go up to 1.5 and be OK? I have a large 3600mha mugen battery, so thats not an issue, but what I am afraid of is popping my phones brains out...
http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
Look at Snapdragon S2 section
MSM8255
Also, it sayd for phones that use the above chip.. GSM only for Xperia PLAY... if that is the case does that mean R800x users are on a differerent chip? And if so what chip is it? Thanks in advance.
Click to expand...
Click to collapse
We're on the MSM8655 instead of the 8225. iirc, the difference is that it's cdma oriented as opposed to gsm
Each chip is different in what it can handle, so your best bet is to test it out, slowly. When your system starts to act funky, step down the voltage/speed levels.
Pax
Ps. Tried running mine @ 2 ghz once and was promptly rewarded with a random reboot. It takes some time, but with mine I've figured out our can run 1.6 with no issues (I tend to keep it at to stock levels because my battery sucks )
Sent from my R800x using Tapatalk 2
paxChristos said:
We're on the MSM8655 instead of the 8225. iirc, the difference is that it's cdma oriented as opposed to gsm
Each chip is different in what it can handle, so your best bet is to test it out, slowly. When your system starts to act funky, step down the voltage/speed levels.
Pax
Ps. Tried running mine @ 2 ghz once and was promptly rewarded with a random reboot. It takes some time, but with mine I've figured out our can run 1.6 with no issues (I tend to keep it at to stock levels because my battery sucks )
Sent from my R800x using Tapatalk 2
Click to expand...
Click to collapse
K, thank you Pax for the feedback.
Just thought I would open this to everyone on R800x, interested if people could point there OC status below.
Mine is still on 1.2ghz. with Performance and BFQ
Highest I can go is 1.6, but I keep it around stock or slightly underclocked, with SetCPU profiles that increase to 1.2 for games and internet apps. smartassv2 and sio for governor and scheduler.
I heard that underclocking can end up reducing battery life over time. Is there truth to this or is it just a myth?
1.6Ghz and Performance when the screen is on.
Stock when the screen is off.
Battery last all day, but I don't use heavily.
Sent from my R800x using xda app-developers app
Solar.Plexus said:
I heard that underclocking can end up reducing battery life over time. Is there truth to this or is it just a myth?
Click to expand...
Click to collapse
There's a large number of things that can adversely affect battery life, but by the time it becomes a problem, you'd most likely be on a new phone, anyway.
Sent from my SCH-I500
I tried my r800x at 1.6ghz (running Cyanogenmod 9 with stock kernal), and I was stuck in a boot loop that I had to fix through CWM Recovery. I am now running stable at 1.4ghz.
Yeah I'm on my 2nd xplay after I tried to oc to 1.6. My phone got extremely hot so I pulled the battery to let it cool. Upon booting my touch screen was non responsive. I don't ever go past 1.4 now.
Sent from my Xperia Play
Umm I got a r800x and the Max I can clock too is 1GHz but I see people up to 1.6 how do you do that?
Sent from my GBTweaked R800x using tapatalk 2
crazymonkey05 said:
Umm I got a r800x and the Max I can clock too is 1GHz but I see people up to 1.6 how do you do that?
Sent from my GBTweaked R800x using tapatalk 2
Click to expand...
Click to collapse
Custom kernel such as LuPuS or DooMKerneL
1.6 min and max. SIO, with performance governor, then I switch it after 30% and lower to powersave sio, 804-416 Max or whatever those numbers are.
Sent from my R800x using xda app-developers app
savage24x said:
1.6 min and max. SIO, with performance governor, then I switch it after 30% and lower to powersave sio, 804-416 Max or whatever those numbers are.
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
Good luck with avoiding frying your phone
R800a 1.4 GHz, sio, ondemand, with Lupus GB v5 + Xperia NXT
My play can stable oc to 1.8ghz
Sprint Samsung Galaxy S II Epic 4G Touch w/ Stock 4.0.4
Xperia Play R800X w/ supercharged stock 2.3.3 and doomkernel
Running the LuPuSv7 Kernel on AOKP Milestone 6.
Max CPU: 1612MHz
Min CPU: 249MHz
Scaling Governor: Superbad
~Set to Boot~
Runs SUPER smooth!
Battery performance; half of the day under heavy use/gaming, up to 2.5 days when I'm only calling and texting.
I recently installed Houstonn's JB port on an Optimus E973 and find the CPU throttling to be really aggressive compared to stock ICS. The port works perfectly for me (no wifi issues, etc), but the CPU will spend very very little time at 1.5 Ghz and will throttle down to 1.1 almost immediately. Its actually so severe that in terms of user experience, JB seems slower when you use the phone for more than a few minutes.
There was some discussion/consensus that the throttling on ICS was dependent on battery temp, but in JB it seems to depend on CPU temp now (throttling will still occur when battery is < 30C). Just wondering if anyone has a similar experience or can shed some light on this change? Thanks.
I am experiencing the same thing. Not noticing performance issues but noticing the throttling.
Sent from my LG-E973 using xda app-developers app
lunde20b said:
I am experiencing the same thing. Not noticing performance issues but noticing the throttling.
Sent from my LG-E973 using xda app-developers app
Click to expand...
Click to collapse
The throttling will happen no matter what - its to keep the cpu, battery, etc cool enough to prevent damage. I had throttling on ICS but it wasnt noticeable either. Most of the time the CPU would ramp up to 1.5 and get the job done quickly. Since I have upgraded it will only ramp up to 1.1 ghz for the most part (sometimes it will increase to 1.5, but that is uncommon).
I know that Quadrant is next to useless for comparing between phones, but I like to use it for monitoring changes in the performance of a single unit. On ICS, my LGOG would routinely get scores of 7300+ until the phone got quite warm and then it throttled down. On JB I have never seen a score above 6700 and the loss is entirely due to CPU score. Checking CPU Spy shows me that the CPU never hits 1.5ghz throughout the test, even when run on a cool phone.
Aha... found something of interest here.
The odd frequencies of this JB rom have been reported elsewhere.