Hi,
My LG P500 (Rocking 512MB!) has a custom recovery since february, now. Since then I've been switching ROMs a lot, the first being CM11 which I switched really quickly to CM7, rock stable and fast, still one of the best ROMs I've tested. Also tried CM12 (KitKat), AOKP, VoidForever and Oxygen.
Using Oxygen at the moment, being the lightest and fatest, really stable.
Naturally I've been playing around with CPU frequencies since february too which was really useful in the long run. Underclocking and underclocking, while I did not kept the LG overclocked 100% of the time.
I did more benchmarks and stuff on Oxygen, testing out more overclock frequencies stability - people complaining of fried CPUs are rare to my knowledge (Well, didn't read much), and anyway, I can now find the LG P500 for 30-50$ used. My LG starts rebooting from 787 MHz, so I generally can use 729-768 MHz for a few time. I always depend on which factors, how much times does it actually takes before the device reboot due to unstability/unstable overclock, which I would like to know why, the hardware logic behind the reboot.
729 MHz has been really stable since a long time - I don't know if it's just me, but I feel like the CPU might be weakening after all this time, if it's possible at all? Not sure. But it does happend that it randomly reboot on 729 MHz still, pretty rare. Doesn't matter thought, if the CPU happens to die, I'll just buy another cheap one I guess.
But what is the actual cause of these reboots, overclocking sure push the CPU more than it should, so in theory it shorten battery life, and CPU lifespan too, also produce more heat. Which makes senses that when the phone get too hot, it reboot due to a thermal protection, same thing goes for computers.
Still sometimes, battery isn't that hot anyway, 32 degrees? 30? I've never exceeded 40 (Which is really rare, while charging - at this point I stop using the phone for a while) Apparently, LG P500 does not support showing the CPU temperature, tried, no succeed.
So is the CPU going too hot in that case? I'm aware I couldn't do anything to, hm, make overclock more stable, impossible besides lowering the frequency, but I'm just curious, would just like to know the logic, why does the phone choose to reboot? Just simply crashing? Hm, may I ask, what causes this crash? Entirely hardware related, right? I've tested overclocking with different kernels, while Android 4.0 had a worse tolerance to higher overclock, doesn't matter which kernel, my device can never get above 768 MHz without an instant crash. Why is the crash instant ?
Would like to know the logic behind overclocking affecting stability, please. Is that explainable? Exclusively hardware crashing? Or hm, does the software report any kind of alert at some moment, I don't know?
(On a side-note, never managed to overclock my PC CPU, Intel Core i3-2350M Sandy Bridge, apparently locked. Not ready to do this (Not the same price value obviously!), just wanted to see if that was possible on my laptop and so, how. Never figured that out, well, doesn't matter)
Thanks
Related
No doubt, Overclocking is usually dangerous. (overheating and so on)
Many user know that from Desktop-PC, Notebook Range ect.
Permanent OC will decrease lifetime of your hardware.
Also many user know that Intel, AMD/ATI ect. have Safety Devices for too higher OC.
My Question:
Which Safety Device have the SnapDragon from Qualcomm?
AFAIK the GPU is integrate into the CPU.
That doesn't make these things easier.
Greetingz from Berlin/Germany
Most time i think, there is only a short peak of using the Cpu, so it shouldn't damage it,but on Games im not so sure if it doesn't get problems. But when you go on a undervolt Kernel i think is is not so dangerous.
Greetings from Karlsruhe
OC to 1190Mhz interactive mode, hold my phone just now, quite cold
Chris X. said:
No doubt, Overclocking is usually dangerous. (overheating and so on)
Many user know that from Desktop-PC, Notebook Range ect.
Permanent OC will decrease lifetime of your hardware.
Click to expand...
Click to collapse
I don't agree that overclocking is dangerous if you're careful with it. I can't remember the last time I had a PC that wasn't overclocked, and I've never had one fail on me.
As long as you don't put the voltages too high & make sure the temperature is kept cool, it's not very risky or dangerous - it's just taking the hardware above the usually conservative guaranteed fully-stable speed set by the manufacturer.
With the HD2, it shouldn't be too different - as long as it's not overheating, it should be fine.
Also, if it's running stable at 1.1ghz, then that indicates that it's happy running at that speed.
The only possible side effect I could think of it potential data corruption if overclocking the CPU/GPU also overlocks a memory bus or whatever. There is no indication so far that this is happening to those who overclock.
I'm not sure about safety features, but I think the phone would become unstable before safety became a concern.
i agree with davidmc0 but this is in the wrong section as this a personal issue
As we can see in many forums, people like to overclock their phone to increase It's performance although overclock can increase battery live and may broke their phone. I think the increased performance can only be felt through benchmark software. The effect on the apps is almost negligible specially on high end phone (like our Note). Why do you overclock your phone and use overclock on daily usage (I understand if the reason of overclocking phone is for satisfaction) ?
Never saw the slightest reason to overclock my phone.
Emulators and because I cannot resist getting extra performance. My captivate was a beast OCed.
Some people don't get it others do...like everything in life. Some don't get how we can live with a phone this big but we do...
Sent from my GT-N7000 using XDA
On GB (LC2) I overclocked to 1.6gHz and it made everything run smoother (screen transitions, opening and closing apps etc.
On ICS I haven't felt the need to OC. It runs super smooth and fast as it is.
But maybe I'll get bored some time in the future and do it just for something to do...
I'm on stock GB LC1 CF rooted and I OC to 1.55.
Differences when I open apps. They open faster. And not that huge battery life drain because cpu stays at 1.55 a little time and for me the faster app opening matters
*only 2% at 1.55 (not even 1h from 40) - with CpuSpy
Sent from my GT-N7000 using Tapatalk 2
Its not bout whether its "important" or not... Its more like, If you can...then why not!? I did overclock my sgnote till 1.6ghz at 1.7 it would reboot.
Its like gettin more for less
Just as Overclock with your desktop, some take a step further by changing heatsink, better ventilation, water cooling, etc.
Exactly, its just free power and if you are not dumb, you are not going to kill anything. This is not the dark ages of overclocking and those fears people seem to still carry from those times.
Take for example on GB running 1.6Ghz Nenamark2 scores me about 34fps or so..Damn close to my record with the Captivate which is 33.5! Then I ran 400Mhz on the GPU and boom..53fps...that is some kick ass gains there. While I will probably run 300Mhz mostly, if I find a game that needs the extra performance, I know I have it there so why not use it.
This is not the dark ages of overclocking and those fears people seem to still carry from those times.
Click to expand...
Click to collapse
Very true.
On my desktop I have an Intel i5 2500k (original 3300 MHz) OC to 4500 for daily use and when needed 5 GHz.
From 1 year and a half the CPU runs like this and never had any stability issue. And my PC kinda stays on A LOT.
So yes, we don't live in the dark ages of overclocking. Why people STILL HAVE FEAR OF OC!?
These days OC is very easy. Most of the times you can't broke a device / component from OC, because the "drivers" of some microcontrollers from your motherboard won't let you (a lot of protection these days )
Indeed. Plus if you are too afraid then dont push higher voltage, just OC with stock voltage as much as your CPU can do.
My nexus 10 froze two times today ( pretty normal, it usually freezes about 5 times a day) but today, a strange sound came out of it ( "rrrrrrrrrrrrrrrrrr" )
I don't know if it were the speakers or if it came from somewhere inside the tablet... I am very disappointed, I sold my transformer tf101 because it froze 3 times in a week, that was already to much for me. Why can't Google just fix it ? Or are they working on a fix ?
Inse
Sent from my Nexus 10 using XDA Premium HD app
Are you on a custom kernel? That sounds similar to the CPU crashing and hanging, thus the repeated noise
try setting your cpu governor to performance if you have a custom rom or kernel. solved the issues with rebooting for me (for the most part)
Well, you have to determine why the tablet is rebooting. If the device is getting noticeably hot and there is a "slideshow" effect then it is a indicator that it is being thermally throttled. Changing the governor won't necessarily fix this and in some cases can exacerbate it.
If you are indeed on a custom kernel, then then the kernel crashed. If its a reoccurring event then I would look at flashing a different kernel (Ktoonz or another) and seeing if that fixes the issue.
I haven't installed a custom kernel or custom rom, I not even rooted. On the left side of the camera ( when holding in landscape) the tablet gets very hot while playing simple games like pudding monsters. Is that normal ? Happens it to anyone else ?
Send from my lovely Sensation XL,
If I succeed helping you (rare) don't forget to hit the thanks button
There is currently a theory (tested by members and mostly supported by gathered data found in this thread) that the CPU does not have a temperature sensor and instead estimates temperature based on an equation. According to the member who did some testing, the equation is way off from the actual temperatures. This can cause freezing (due to lag from thermal throttling) which would account for the sound or the random reboots as the temperature equation reaches a critical point and reboots the device.
I would pay attention to the KT Manta kernel thread as there's some interesting research going on over there. I can say having used that kernel from day one, 100 MHz to 1.7 GHz and extremely undervolted I haven't experience a single instance of throttling or rebooting. The only reboots I've had were when I was dialing in my undervolts. I tried messing with the GPU voltage, but mine appears to be somewhat picky and I really couldn't undervolt the GPU much. The CPU on the other hand undervolts like a champ.
However, if the theory that Samsung uses an equation to determine temperature and not an actual sensor, undervolting will have zero effect on "temperature" though it will save battery. Having never encountered thermal throttling (even after significant game play and other activities) I can't speak to that issue. Though I can say that with my undervolt settings, the battery lasts a crazy long time and I have absolutely no performance issues.
So I've been following this section for months and just got my a2017u 2 weeks ago. I'm rooted with tenfars tool still locked on b20. I've noticed in the last few weeks a tapering off of new and useful info for this phone and would really like to see what and where everyone is with it? LSpeed? Kernel Auditor? Or any tweaks that have helped either performance or battery life!!! Looking for anything to make this already great phone better!!! TIA
I have been using EX Kernel manager to tweak the settings as kernel auditor was not working properly with the big.LITTLE arrangement. I have upped the readahead value and underclocked the cpu to 1036mhz on the little cores and 1401 mhz on the big cores. working still as snappy and getting +2h SOT. I'm a heavy gamer and Asphalt 8 still plays as fluid as before, even better tbh due to less heating.
If you don't like to underclock, you could try these:
http://forum.xda-developers.com/htc-10/development/pnp-tweak-custom-butterfly-ghostpepper-t3431307
+2h? That's really good! I know overclocking can/could/might damage the CPU. Does underclocking have any of the same risks? I'm rooted and unlocked atm. So no warrenty anyway
aPexalpha said:
+2h? That's really good! I know overclocking can/could/might damage the CPU. Does underclocking have any of the same risks? I'm rooted and unlocked atm. So no warrenty anyway
Click to expand...
Click to collapse
Overclocking can't really harm anything. The excess heat might but it would take a long time and really high temps (you couldn't keep the device in your hands). The only thing you risk by overclocking is a system crash. Just reboot, lower the clock values and voilà ! So no, underclocking can't hurt anything. Overvolting however poses a real threat to the integrity of the components. It's quite the same thing as in computers (except for the heat, you don't always realize it's too hot in a computer).
That being said, is overclocking still even possible on smartphones nowadays ? Just for the fun of it because it's not needed in the least on the Axon 7 .
That's impressive results ! Not sure those hours are needed since the battery is doing well with the software power saver but still a good thing to know.
Still any extra sot is welcome. I'm not a gamer, don't really have any apps that truly need the full power of the sd820 so might give it a shot. Greenify does wonders for standby time.
Not sure if the built in 'intelligent country control' does anything tbh
I'm on my phone most of the day whether it be YouTube play music, texts,calls,etc.. I'm just hoping to find a balance between battery and my multitasking ADHD LOL
Nik2424 said:
I have been using EX Kernel manager to tweak the settings as kernel auditor was not working properly with the big.LITTLE arrangement. I have upped the readahead value and underclocked the cpu to 1036mhz on the little cores and 1401 mhz on the big cores. working still as snappy and getting +2h SOT. I'm a heavy gamer and Asphalt 8 still plays as fluid as before, even better tbh due to less heating.
If you don't like to underclock, you could try these:
http://forum.xda-developers.com/htc-10/development/pnp-tweak-custom-butterfly-ghostpepper-t3431307
Click to expand...
Click to collapse
Mine keeps switching back to 'normal' modes with CPU full on. Any idea how to fix that?
aPexalpha said:
Mine keeps switching back to 'normal' modes with CPU full on. Any idea how to fix that?
Click to expand...
Click to collapse
Yup, I had that problem too initially.
First, I made system changes persistent upon reboot by running this command in Terminal emulator(you can also use adb shell):
reboot disemmcwp
Secondly, you have to disable smart power in the quick toggles.
Once this is done, set your new max values, select the arrow next to it to make it applied on every boot and then reboot your device. It should work.
Note: Everytime you open the EX Kernel manager you will see the speeds jump to max for like 1 sec but if you actually check the cpu statistics you'll see that your settings are sticking and the max clock speed was just for everytime you open the app.
The smart power! I forgot that thing controls the CPU.
So that round arrow thing means apply on boot? I selected that, figured it meant something like that.
Cheers!
Hi there,
Is it possible to overclock the cpu and gpu?
If so how? Or which rom/kernel?
Running G model 4gb ram
Even if you can, it will chew the battery and heat up.
RobboW said:
Even if you can, it will chew the battery and heat up.
Click to expand...
Click to collapse
Not a problem as I would only be using it sometimes not permanently
Kendal21 said:
Not a problem as I would only be using it sometimes not permanently
Click to expand...
Click to collapse
in theory it is, we had a a kernel that OC'd the CPU way back then, but the SoCs on the Axons are probably low-binned - shutdowns and stuff like that are commonplace
But still, do you know what OC does to a phone? New phones are thermally constrained devices, starting from the snapdragon 800 series onwards. remember the sd805/810 disaster? Well...
If you run your phone at 100% load, it will run at max speed (1.56/2.15) for a very short time (say, 30 seconds), until the SoC reaches a specific temperature. After that it'll go down to a more manageable frequency, eventually going even further down or staying at 1.8 ghz, depending on your specific situation (the pink thermal blob might be bad).
That's why VR mode sets your cores at around 1.8 ghz, to keep them from going hot and lowering frequency even more. Sustained performance is better than burst performance on gaming.
Day to day usage is another matter, because more frequency won't mean thermal throttling when opening apps or unlocking the phone, beside the obvious battery usage
TL/DR: Be prepared to make your own kernel if you want to OC. It might not work