Let's discuss, I don't know enough about it. But if the processor would overheat it could break right?
Aronuser said:
Let's discuss, I don't know enough about it. But if the processor would overheat it could break right?
Click to expand...
Click to collapse
Do you mean "safe"? ("security" is about criminals hacking your phone, "safety" is about not damaging things or self).
I'd say it's like with PC overclocking - if you don't do anything crazy (like increasing voltages too much) then you're safe.
From what I can see, we can overclock our phones with voltages *lower* than stock, so that's as safe as it's going to be
There's also a related safety issue: if your phone crashes, its filesystem "might" become broken and the phone "might" not boot. I haven't seen that happening, but having a nandroid backup is just common sense.
Yep, wrong term. Instead of 'secure' should change it to 'safe'.
Like overclocking in any environment, risk is involved. One has to weigh the pro and cons themselves. But, unless you want higher benchmark result or lagging in games - one doesn't need to overclock.
sysKin said:
Do you mean "safe"? ("security" is about criminals hacking your phone, "safety" is about not damaging things or self).
I'd say it's like with PC overclocking - if you don't do anything crazy (like increasing voltages too much) then you're safe.
From what I can see, we can overclock our phones with voltages *lower* than stock, so that's as safe as it's going to be
There's also a related safety issue: if your phone crashes, its filesystem "might" become broken and the phone "might" not boot. I haven't seen that happening, but having a nandroid backup is just common sense.
Click to expand...
Click to collapse
TNCS said:
Yep, wrong term. Instead of 'secure' should change it to 'safe'.
Like overclocking in any environment, risk is involved. One has to weigh the pro and cons themselves. But, unless you want higher benchmark result or lagging in games - one doesn't need to overclock.
Click to expand...
Click to collapse
Thanks guys, well yeah i meaned "safe" sorry.
Related
I thought I'd put this together given the amount of questions and apparent lack of knowledge on what you're getting yourself into with overclocking. While it's a one-click-wonder with SetCPU and JuiceDefender, it's not that simple when it comes to what it's actually doing to the phone.
The first thing you need to know is this:
All devices are not created equal!
Even when they come off the production line together they may not be capable of even getting close to each other with an overclock. This is down to numerous variables, the most important of which is the processor itself. Processors are manufactured in batches from something called a wafer (basically a big chunk of silicon), that batch is then tested to a maximum stable speed and then marketed at a slightly lower speed for the sake of rock solid stability. Dual/multicore processors may have a faulty core disabled and be marketed as something else (hence AMD's Tri-Core processors). This is the reason overclocking works, and the long and the short of it is just because Person A can get 1.3Ghz running stable, doesn't mean Person B can.
So, now we know that whingeing that my Desire can get 1300Mhz but yours crashes every time you go above 1100Mhz is irrelevant, we can move on to the risks. Overclocking is dangerous. That's not an exaggeration, so let me reiterate...
Overclocking is dangerous, You can potentially kill your phone stone dead.
But yet again it's not that simple. Yes, in very rare cases a processor will just go bang and give up, but most of the time other things will happen, behind the scenes, that you won't know about until it's too late.
The basic premise of overclocking is to get a faster processor clock speed. A small jump can probably be attained just by upping the speed itself and be perfectly stable. Going higher is where the problems start. If you start getting crashes/freezes/reboots then the next step is to increase the voltage to the processor to make it more stable, but more voltage means more heat, and excess heat is bad. This can either cook the processor as a whole or a group of transistors. This is more of a problem on a device like the Desire as where do you put the extra cooling?
Another problem is that more voltage can fry an IC track, and/or arc across to a track it shouldn't be on. This could do nothing, but it could also kill a single transistor on the processor or other chips in the device, or maybe multiple transistors and it can also lock them open or closed. This takes us back to random reboots, freezes, and crashes - but this time it can't be fixed.
Then theres a twist. Undervolting can also break things. A transistor is either on or off, and if it doesn't get enough power one of three things can happen - it can work fine, it can not work at all, or it can continually switch until it breaks (what an example? go and flick a light switch on and off until it stops - and it might not be the bulb that goes). If it decides not to work when other parts think it should, guess what happens.
So, bear this in mind when overclocking. If you start getting ANY issues test at stock speed. If you still have issues and/or you kill your phone, it's your own fault.
Mods - I've put this here as it's the place most people seem to ask about OCing, please move it if i'm wrong...
Nicely written and informative. Users must always take their own responsibility when trying to do something "out-of-spec" with their device. I didn't know undervolting could break things though.
It's far far less common and it's not the actual undervolting that causes the issue - it's the power requirements of the device. If you're unfortunate enough to have something keep tripping - it's kind of like when a PSU goes and keeps clicking, there's not quite enough power to flick to On permanently so it just ticks at you till you turn it off or it gives up completely. 9 times out of 10 you'd be fine, but theres always that chance.
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
My phone freezed several times a day with defrost. But no freez with MIUI/OpenDesire. I dont know why but Defrost §$%#s my phone
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
It can be that it is your ext3 partition if you have one...i had a user with freezes...and i did not know what it was...i say him...make all new...he flasht a original rom...root again with unrevoked...flasht my rom again and it was the same...freezes...so he formated the card...and maked a new ext3 and now he have no more problems with freezes
with kind regards..Alex
Good write up. Hopefully people will actually read this and understand the risks before they start pushing zip files with overclocked/undervolted kernels. Personally I've never overclocked any mobile device since I'm not comfortable with the risks that may lead to long term damages.
great job! thumbs up! vote for sticky or linking this in one of the stickys
i'm familiar with overclocking since i've been doing it to my PCs for years. i'm wondering if aosp roms push the phone harder or something than sense based ones?
reason i ask is i've tried a few aosp roms (open desire, defrost etc) and all the various kernels i've tried cause a reboot after a while - 30 mins, upto a few hours. now, i tried richard trips sense kernel and OCd with that no problems at all. very weird
p,s all Ocing was on the relatively small 1113mhz.
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.
thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.
Hello all.
I know its a tablet, and people tend to not overclock often - but I just wanted to know if anyone has overclocked a bit?
If so, how far have you gone, is it stable, and is the heat sink coping?
punkmilitia said:
Hello all.
I know its a tablet, and people tend to not overclock often - but I just wanted to know if anyone has overclocked a bit?
If so, how far have you gone, is it stable, and is the heat sink coping?
Click to expand...
Click to collapse
We first need a custom kernel that supports it.
I'd rather have a better governor than overclocking. The tablet seems to have some sluggishness in stepping up and down though recent firmware fixes have alleviated that.
Diogenes5 said:
I'd rather have a better governor than overclocking. The tablet seems to have some sluggishness in stepping up and down though recent firmware fixes have alleviated that.
Click to expand...
Click to collapse
Oh, I agree for normal android usage. Overclocking is just something that interests me, especially for future emulation. For some reason I recall only needing to root to overclock - but then again that was like 2-3 years ago so maybe kernel is a requisite or my memory has faded, rofl.
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
What part of "you won't save more than 2%" you didn't understand?
ilusi0n_ said:
What part of "you won't save more than 2%" you didn't understand?
Click to expand...
Click to collapse
Well, i don't really understand WHY it doesn't save more than 2% of the battery life. Afaik, EXUV does reduce heat and improve battery life by miles. But that's what I thought. In reality which is this, im not rly sure why that even with EXUV, it still cant save more than 2% of the battery life.
Sent from my S800 China Phone
TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
I'm not technically expert with things like this but I have read an article/ blog before that undervolting may damage a phone since it was designed to work with that specific voltage. So, I actually didn't do that even UC or OC. Just saying.....
Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)
r25txe said:
Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)
Click to expand...
Click to collapse
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/samsung-kernel-msm7x30/commit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware
sir mordred said:
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/sa...mmit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware
Click to expand...
Click to collapse
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.
So to sum all this up. We just have to leave the CPU & voltage tables alone since it damages hardware?
Via the Internet
It's not that you have to, but that chip designer recommends it.
r25txe said:
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.
Click to expand...
Click to collapse
That was also the POST that I'm referring to that I've read :good:
Hi everybody,
I want to know if we can overclock our Snapdragon 808 to 2GHz (ARM A72 cores) with a modified kernel.
Also, If somebody is going to work on this challenge.
Thanks!!
Androsesp said:
Hi everybody,
I want to know if we can overclock our Snapdragon 808 to 2GHz (ARM A72 cores) with a modified kernel.
Also, If somebody is going to work on this challenge.
Thanks!!
Click to expand...
Click to collapse
A57 cluster, probably yes. I'm also working on a kernel, but I intensely dislike Overclocking because it isn't all that useful. The key to performance is with optimisation, not with raw power. So I'm most likely not going to include it, sorry.
What about underclocking and/or undervolting?
I think performance is good enough as it is, but would like to get better battery life.
I would like to be able to undervolt in order to relieve the bugging high temp warning. This phone rarely uses max performance. So, overclocking is not really a priority. Maybe a custom hotplug.
Crappy cpu. No point messing with it.
Sent from my A0001
GUGUITOMTG4 said:
I would like to be able to undervolt in order to relieve the bugging high temp warning. This phone rarely uses max performance. So, overclocking is not really a priority. Maybe a custom hotplug.
Click to expand...
Click to collapse
Hotplugging has been dropped not long ago. You'd basically need to reinvent it. Plus it costs more power than it would save
And what about undervolting to prevent excessive heat, @mythos234?
yea i guess undervolting is the only benefit here coz 2 ghz wont be hard to achieve but getting that overheating msg sooner aint worth it...
next thing u know is accessory back plates with mini fans to keep the phone cool...
seriously tho what good is the extra power for ? the phone is already fast with the correct setup (not that i saw any lag when it was stock)
anyone knows how to see the cpu binning in this phone?
oile said:
And what about undervolting to prevent excessive heat, @mythos234?
Click to expand...
Click to collapse
Excessive Heat?
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
A number of people have gotten over-temperature messages, sometimes with the phones even shutting down.
This has been reported with using navigation, I believe, and I know people have reported it when shooting video. High screen brightness is likely a contributor. But there are examples of the phones running too warm.
Personally, I'd be more interested in cooler running, and longer battery life, rather than increased peak performance. So underclocking, if anything.
Well, the overclocking is not necessary, but is an opportunity to know the limits of the chipset. Moreover, with it we could know if we can make undervolting to our phones and make it more battery efficient with an underclocking kernel, when we need it.
RedOCtobyr said:
A number of people have gotten over-temperature messages, sometimes with the phones even shutting down.
This has been reported with using navigation, I believe, and I know people have reported it when shooting video. High screen brightness is likely a contributor. But there are examples of the phones running too warm.
Personally, I'd be more interested in cooler running, and longer battery life, rather than increased peak performance. So underclocking, if anything.
Click to expand...
Click to collapse
Happens to me too when gaming. The problem I observe is that Indeed, it is not excessive heat. But LG thinks otherwise.
You can actually underclock using Kernel Auditor and disable cores. Unless you meant Undervolting.
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
Wanna check out periscope and comment back ? Atleast I know that app will push the phone to its limits.
Sent from my LG-H818 using XDA Free mobile app
Currently using Kernel Adiutor to disable both A57 cores and the phone screen does not heat up like before... Battery life has improved from what i saw yersterday. Continuing testing today. Only problem i have is the damn phone will enable one of the A57 cores after a while which i dont like. I need my settings to stick.
Any Kernel Dev know which files are causing this? Tab 3 had something like this but a couple of files changed solved the non sticking settings on cpu.
Overclocking/underclocking sure but just disabling cores would work for most.
Sent from my LG-H815 using Tapatalk
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
lol, you're funny.
marcadam said:
lol, you're funny.
Click to expand...
Click to collapse
I haven't had any popups or heat related reboots, so I was wondering what the matter is here.
On every phone I see complaints over heat so I wondered if something is to it here or if it's the usual. And if there are overheating warnings and shutdowns, then there might be indeed something in the bush.
Try charging your phone in the car whilst using google maps to get to an important meeting, and then take a call just for good measure............and boom, there you have your own little meltdown.
marcadam said:
Try charging your phone in the car whilst using google maps to get to an important meeting, and then take a call just for good measure............and boom, there you have your own little meltdown.
Click to expand...
Click to collapse
That happens on every phone I ever had though. It's advised to not use a device while charging at all, so if you stress it to 120% while charging, of course it heats up..
@mythos234 is a pleasure to have you here (speaking as xiaomi mi2s owner too xD)
What Temps do you reach using cpu intensive apps?