Hi,
I have run into some results from users showing that overclocking is indeed counter productive on the s4 as it would bench lower due to throttling as a result of overheating. Has anyone else actually benefited from overclocking it? If so let's see some screeniez actually proving that it is worth to overclock and at what point the throttling begins to take effect from CPU overheating.
Ward
i had very good resoults but with overclocking gpu not cpu. Everyithing was smoother with overclocking GPU, so i recommended that you overclock GPU and you will get best resoults for daily use. Otherwise overclocking CPU is still good but dont promise any real life perfomance, i have overclocked mine for like 200Mhz along with gpu and get best possible resoult for daily usage. But i can tell you that battery is not happy about this U need powerbank in you pocket to get through day.
Compared to my stock Note 10+, my stock S4+ is so slow it's not even worth comparing.
You only have so much to work with... better architecture, faster chipsets and memory make substantial improvements in the newer platforms even with no overclocking.
At least until Android 10, then things start going to hell... scoped storage sucks.
So far Pie is the Android OS's zenith in my opinion.
Related
hi, is there any way to overclock the processor on the xperia?
By over clocking do you mean take the Xperia beyond its theoretical headline Limit of 528 mhz ?
I have looked at this but the new processor does not seem to be supported by many of the commercial solutions avaliable.
However SpeedBooster posted on the Turbo Speed X1 thread, allows you to set higher processor priority for the programs you choose, giving them a larger slice of the processor pie, its not overclocking as such, but it does make the processor work faster for the programs you choose.
I have used it for a few days with no serious problems, howvere having the processor running faster will drain battery faster, I have noticed this, but it is within acceptable limits for my needs,
I prefer the extra performance over the extra miliage.
Can you do a benchmark and post the results?
Would help a lot to start making a comparison between devices.
Is this what you're looking for:
Hi all guys! I have a couple of questions and would like to hear some experiences and thoughts in general about overclocking in Android.
First a couple of more specific questions which I would like to have answered, if possible. If it's not possible, please give me your general thoughts anyway about overclock instead of moving to the next thread, please.
- Are there any kernels which allow overclocking beyond 1536 MHz?
- If so, did anybody try those frequencies? What was the result?
- Are there any people who for some reasons did NOT manage to have stable 1536 MHz?
- Are there any reliable reports of people frying their phones due to overclocking?
- Are there any easy ways to undervolt the CPU (at standard frequencies, not overclocked) in order to save some battery charge?
My very little OC experience is based on this: I have been running for some days a ROM based on a kernel which allowed OC up to 1536 MHz. I installed CPU Master Free, did some tests and found out, to my surprise, that the phone will run @1536 MHz without any noticeable issues. I never kept it at that frequency for more than 5 minutes I think, because I was afraid of excessive heat, but the phone never got really hot, just a bit warm. I ran some system benchmarks (Quadrant and another one which I can't recall right now) which stressed a bit the CPU and did not encounter any crashes. I also did this with performance governor which keeps the CPU constantly to the max frequency I think, and still no probs. Since everything works so fine and was that easy, I was wondering why don't everybody always run with the HD2 @1536 MHz. Is it only for battery issues? Please share your ideas about this and OC on the HD2 under Android in general.
Thanks.
The problem with overclocking isn't just overheating or too much power. With overclocking you are also increasing the say, amount of data being passed through the cpu. If the cpu's bus size isn't fast or big enough to handle it, it will ultimately slow down or malfunction.
So you should get the picture of overclocking now. Note however there are some safe speeds for overclocking.
Onto your next question as to why everyone doesn't overclock to the max speed. The reasons are: paranoia and safety of device
You have to know that not every chip is made exactly the same, they are modeled after the same design but are never made the same. So that mean whilst some people's phones may be able to handle extreme overclocking, like yours, others may not be able to, and malfunction/overheat. Malfunctioning like, cannot make phone calls, wifi/GPS doesn't work, etc.
So I hope this was informative.
Not everything you have said was new to me, but you were informative.
...although I would really be surprised to have issues with phone calls for instance caused by excessive overclocking...
Do you personally keep the HD2 overclocked?
Anybody else?
When I had my HD2, I rarely did so. Reason being is that I found no need to. The only times I did do so was to see if the phone actually was faster. In my results however I found no big difference so I didn't bother.
Well, the phone is indeed fast without OC, but you can feel the difference if you are performing some CPU intensive tasks. For example, unzipping a 200 MB ROM archive, or importing 1300 SMS from a backup. A temporary OC can save you maybe 1 minute or 30 secs, which aren't absolutely worth the time you spend learning to overclock the device, but never mind, even if you only saved 5 secs it's worth it for the satisfaction.
Ah I see your point. I was only looking in the perspective of simply tasks such as browsing internet/market, games, gallery.
Figure it this way. When you overclock a pc, (and if you're doing it safely/correctly) you have usually spent extra money on liquid cooling systems. Or at the very least, bigger fans, bigger heatsyncs, etc. Even with all that, you could very easily blow out a cpu or other component when you overclock.
Now, on a cell phone, you're running a MUCH higher risk. First off, there is NO extra cooling, and considering the size of our phones, and how thing they are, there's really no room for airflow. So while yes, it may work for you, in general I always say getting those couple extra frames per second out of your game are not worth the potential damage to the device.
Overclocking on actual computers has gotten much safer in the last few years, because the chip designers are putting more effort into keeping the chip cooler under load. Cell phones are not designed to overclock (even one as sweet as the hd2.)
Lastly, when overclocking a system (desktop), you usually change more than just the cpu clock speed. You'll usually have to adjust the voltage to compensate, and in some cases adjust memory timing as well as bus speed. None of this happens when you overclock on the hd2, all you do is change the clock speed.
It's not set in stone, but there's a very real possibility that you can do permanent damage to your device when overclocking. And, you may not notice the damage right away. Also keep in mind, these are mass produced cpu's, and there are slight variations in each chip. (Hence why some people can overclock higher and keep stability, while some phones with the same chip get picky if you even overclock 10mhz )
I've never seen the point in overclocking the hd2, you really don't get any real world speed out of it, it's a placebo at best. (And please don't start showing me or quoting benchmarks, they're useless, and extremely easy to make little changes in the roms to artificially boost benchmark scores.)
Edit: For more info, because I'm tired of typing, check these links:
http://en.wikipedia.org/wiki/Overclocking
http://www.webopedia.com/DidYouKnow/Computer_Science/2005/overclocking.asp
Great info mstrk242,
Thank you!
All benchmark info is skewed. Tried 1500mhz and the only app I noticed a difference on was gun bros. A new more efficient version of rom made it run fine at 998mhz. Not worth the extra wear and tear on your device. Simply changing things like your launcher can have larger effects.
Sent from my HyperDroid powered HD2!
hi guys i just want to know what is the max overclock of the cpu and the gpu for the nexus 7 ( please has to be has safe as possible, i dont want to damage the tablet too much, and yes i know that overcloking will reduce the life of the tablet) I want to get the best performance out of this tablet!!!!!
Note: battery drain is not a problem!!! I will use the nexus 7 for gaming most of the time and also browsing!!!
Please I really want to know i created an account on this site for this!!!
Most people can go to 1600 on the CPU. Any real world performance increase from the stock 1300 is negligible.
I wouldn't overclock the GPU past 446 (+30) because anything higher creates a lot of heat and people have reported benchmarks actually being lower once you go much higher than that.
Sent from my Nexus 7 using xda premium
Thanks
Thanks for the help
If someone wants say something else go head
More Help the better
Hi, tbh you'll probably not notice much if you overclock the cpu to 1.6ghz as percentage wise it isn't a large jump. Things may feel a little zippy at times though, in my house I have acces to two n7's, one stock and one overclockable to 1.6ghz. Ran tests between them and the 1.6ghz was fractionally faster, the difference was very small. Overclocking the gpu to 600mhz vs 416mhz at stock made a huge difference, as it it made some games actually playable. Despite the crap Nivida spit out about the tega 3 soc, it's GPU is comparatively weak. Over-clocking the GPU will give immediate performance increase in a lot of games. After doing heat and clock speed tests myself, I've found anything in-between 416-600mhz to give near enough liner performance increase and heat to be long term sustainable depending on the voltages your device can handle. Overall, I doubt CPU overclocking will give you much benifit, but if you play games the gpu overclock will. If your worried about heat from overclocking the gpu a lot, you can always use this kernel http://forum.xda-developers.com/showthread.php?t=1937146, which gives you full GPU clock and voltage control so you can undervolt your gpu to reduce heat. I wouldn't run at 600mhz unless I could undervolt the gpu as much as I have and I use that kernel because of it. I have my gpu overclocked to 600mhz running at 1225mV, which is only +25mV above stock voltage for 416mhz. Although most heat is generated from the transition period of the transistor charging/ discharging, undervoting does give a large positive effect on heat output if it's large enough. But 600mhz is a high GPU clock and the highest I'd recommend, tbh I would say 520mhz is a really good compromise between heat, performance and battery, especially if you under-volt the GPU at that frequency for most people if your not as annal with FPS as I am :silly:
Thanks Too
Thanks Too
I'm glad I have registered in this forum because people are so cool in here and they help alot compared to other foruns!!!
Thanks again for the Help!!!!
AW: Nexus 7 Overcloking
You all probably have seen those 2GHz oc screenshots.Are those real?I'm not wanting to try this I'm just curious.
Sent from my Nexus 7 using xda premium
They are probably real
yes i have almost sure they are real, but puting the nexus 7 in 2Ghz will, i think will damage a lot the tablet!!!
The 2 GHz kernel was a test to see how far the Nexus 7 could be pushed. This kernel wasn't released for obvious reasons so yes, those pics/ benchmarks were true.
I know that the Note 3 got the Snapdragon 800 8974AA(GPU clocked at 450 MHz).
So i ran the latest GFXBench 3.0(Manhattan offscreen) and got a score of 11.1, which is even better than the scores the Snapdragon 800 8974AB(GPU clocked at 550/578MHz) got.
How can this be?
mull54 said:
I know that the Note 3 got the Snapdragon 800 8974AA(GPU clocked at 450 MHz).
So i ran the latest GFXBench 3.0(Manhattan offscreen) and got a score of 11.1, which is even better than the scores the Snapdragon 800 8974AB(GPU clocked at 550/578MHz) got.
How can this be?
Click to expand...
Click to collapse
maybe its caused by throttling down due temperature
Maybe memory of Note 3 is faster and larger than other phone, which shouldn't be Samsung because S5 uses AC version. I think Note3 has very fast RAM and if other phone has slower (read cheaper) RAM it could bottleneck there. Also, as the other poster said the other phone could be thermally throttling, especially if the benchmarks were run multiple times to get average. You figure people running benchmarks would know better, but who knows.
Hundsbuah said:
maybe its caused by throttling down due temperature
Click to expand...
Click to collapse
Yeah maybe that's the case.
pete4k said:
Maybe memory of Note 3 is faster and larger than other phone, which shouldn't be Samsung because S5 uses AC version. I think Note3 has very fast RAM and if other phone has slower (read cheaper) RAM it could bottleneck there. Also, as the other poster said the other phone could be thermally throttling, especially if the benchmarks were run multiple times to get average. You figure people running benchmarks would know better, but who knows.
Click to expand...
Click to collapse
The thing is that, other Note 3 get's around 9-10 FPS, which is normal for a 8974AA SoC. So either some Note 3's got the AB(which is unlikley) or Samsung is cheating again and overclocking the GPU to AB levels only for the Bench.
mull54 said:
Yeah maybe that's the case.
The thing is that, other Note 3 get's around 9-10 FPS, which is normal for a 8974AA SoC. So either some Note 3's got the AB(which is unlikley) or Samsung is cheating again and overclocking the GPU to AB levels only for the Bench.
Click to expand...
Click to collapse
Samsung never overclocked anything, what they did in the past is ramp up frequency to maximum before benchmark started running, so there was no delay to get CPU/GPU to full speed, like you have with on demand governor. I don't believe it's cheating because you can set the governor to run full click yourself (if rooted) and benefit from this as well with any game/ benchmark. It also shows how inefficient ondemand governor is and maybe we should be using different governor setting which is interesting topic all by itself. I remember there was similar "scandal" few years ago in graphic card business, where drivers were optimized for particular benchmarks. Well, now all video drivers are optimized for specific, mostly graphic intensive games and we all benefit from it by having better performance, from lesser hardware. Maybe this could also benefit all of us by giving us better governors, so the phones can run faster with the same hardware, instead of being artificially slowed down with poor choice of governor settings. As far as other Notes running slower, thermal throttling due to multiple benchmark runs to get average would be my wild guess. Or maybe you deleted factory bloatware and change settings to make your phone faster, but no, you don't have AB version.
I've switched from those S7 and Note 5 ports which lagged and had big delays opening apps to JDC OptimizedCM13 ROM which has basically no lag whatsoever. I read around that the kernel is what controls the CPU but the one I'm using (default one with the ROM, alucard kernel) doesn't support over clocking. What I'm trying to do is disabled core 3 and 4 to make a dual core processor but over clock the first two. With PC gaming people have always recommended fewer faster cores rather than more slower cores. Same with the Apple iPhones, it makes sense that fewer very fast cores would make the UI much smoother and from benchmarks it looks like Android doesn't use that many cores too often. I'm not doing any gaming, just light tasks only so I'm trying to save a little bit of battery but also make my phone smoother.
My specs are i9505 with Optimized CM13 ROM, default Alucard kernel. Using the TWRP 3 recovery (the ROM thread recommended it).
TL;DR a kernel for i9505 MM that allows over clocking and disabling cores.
There are none such kernels available for marshmallow.
And you reasoning isn't quite right.
It may be true that sometimes fewer, more powerful cores, might be better, but this is mainly due to the fact that the app, or program, wasn't made with multi-core devices in mind, and as such, doesn't benefit from a multi-core structure.
Another thing is that a few hundred MHz won't make a huge difference. Especially since you won't be able to go high enough due to the processor becoming unstable.
The highest I could ever go was 2.1 GHz, but even this wasn't stable. After about 1 day it would freeze.
Remember, phones and ROMs are required to meet certain battery life requirements. As such, they usually come with a balanced configuration.