What exactly does overclocking a phone do? And how is it better? And how is it worse?
I just installed Kamma's GSM kernel and im overclocked at 1.8 ghz. My phone seems a bit smoother but I don't notice any battery life loss. So my question is, what are the downsides and upsides of overclocking?
Also, if anyone uses CPUMaster, what are their settings?
If you don't notice a hit on battery life, then there is no harm done at keeping it @ 1.8Ghz, in reality and in regular computers, overclocking TECHNICALLY reduces the life of the CPU, but not by a lot, and chances are that if it does die out because of it, you would have a new computer/phone by that time.
It's not too serious, plus the actual native speed of our processor is 1.5Ghz, not 1.2 which is what it comes underclocked at. Don't worry about it, you're fine.
First of all, I am totally new to this forum.(I mean as an registered user)
Before that I always had the thing from the forum what I needed.
Now here is my question,
If i overclock the processor speed of my android device to a higher position, isn't it gonna take more battery power than usual?
Phone model: Xperia Live With Walkman
Boot loader: unlocked
Root Access: Rooted
Kernel: Rage 3.2
ROM: Real ICS r6
overclocking is going to drain your battery obviously.
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
saqib nazm said:
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
Click to expand...
Click to collapse
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Saimoon said:
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Click to expand...
Click to collapse
Power consumption = Voltage x Voltage x cpufreq x some constant for your device. If you OC (raise the cpufreq) you will have more power consumption and more heat generation because most of the power is dissipated as heat and the heat is what damages your cpu. It is probably impossible to kill your cpu in one go, because your device should shut off when it begins to over heat (this will look like a random reboot). But you will slowly degrade the over all performance of your cpu and eventually you get to a point where you see a lot of random reboots. So if you decide to OC you probably want to also undervolt as well. This is because power consumption (and heat) scale with the square of the applied voltage. One rule of thumb is that your maximum cpufreq is actually determined by the voltage. For example, my cpu is rated to be stable at 1 GHZ and 1200 mV, so when I OC and UV, I scale the cpufreq as high as I can go, as long as the voltage is not greater than 1200 mV, for me this is 1.5 GHz.
Also remember that your cpu governor will have a big effect on your power consumption and it is probably doing a good job keeping the cpu running in the low range of the cpufreq table, so you are unlikely to see big effects of OC or UV on real life battery consumption.
every chipset is different, even though the brand and model is the same. noone can guarantee you any safe value to overclock.
Thanks Giving!
Thanks Everybody for helping me out!
I am applying 1.402 GHz :laugh:
Overclocking is not the only thing you have to think of in order to improve your phone's overall performance. The most important issue for me is choosing the right kernel and applying the right governor + I/O scheduler. From my experience with Mini (i have tried ALL available kernels and most of ROMs) I can surely say that now with my phone (ICS .587, custom ROM + kernel) overclocked to 1.5 GHz battery with minimal use (20 mins calls, 40 mins WiFi per day) lasts at least 60 hours. When I bought my phone (GB, no OC, all stock) battery was struggling to stay alive for 24 hours with the same minimal use. Conclusion: first pick the right kernel and ROM, then OC.
If someone would teach me that would be great!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Better battery life. But be careful with undervolting. It can cause phone to be unstable. Under clocking is more forgiving. If you are going to do either I would suggest only making small changes and then use phone for several hours to settle in. If all good then try next step lower and test until you find the limit of your phone. Then bump it back up to last stable setting.
There are no noticeable benefits.
jimmer411 said:
There are no noticeable benefits.
Click to expand...
Click to collapse
I agree, its mostly the placebo effect regarding lag, a variable effect regarding battery life, due to user apps, and downright dangerous regarding overheating.
But many people whine when its not available for a kernel. I don't have a very high opinion of its necessity.
Battery life in our phones is dominated by the screen and radio (cell and wifi) but I find that undervolting at least reduces the heat when I'm doing something intensive like SNES emulation. Lag in our phones is also primarily a software issue (I have other Android devices with the same hardware running at the same MHz and it's a smoother experience).
Not that my Note got hot, it's just less warm.
ZacksBuilds said:
If someone would teach me that would be great!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
There's no reason not to under volt.
UC=Under clock
UV=Under volt
OC=Over clock
OV=Over volt.
Newer generations of chips have tremendous tolerances. If you were to look at the S3, a Qualcomm built SoC that was a bit long-in-the-tooth by the time the Note was released, you'd see that in many cases, there were phones that featured the chip, but were clocked lower... I.E at 1,000 MHz.
Most chips are designed to run faster than they do, at least for short periods of time. Modern chips use temperature and load to designate the running frequency.
When Qualcomm releases a chip, they need to be sure that 99% of the units they produce, can run with a near-flawless level of stability. Because of this, they often run chips slower, and at a higher voltage than is actually needed. The result is, that Qualcomm or Samsung might design a chip rated for 2ghz, and release their first device with the chip running at 1.5ghz. This is common. Each piece of silicon is slightly different due to manufacturing differences. Chips are made on giant discs, with hundreds of chips on a single disc. The chips in the center are generally considered to be of a slightly higher quality, requiring less voltage, or capable of running at a higher frequency, sometimes both. Because of this, each device is capable of slightly more, or slightly less. The challenge is for Qualcomm to set the speed and power usage for every chip-- the challenge for us, is to see if we can run the chip at a higher frequency, while drawing less power....because power =heat, and power= battery life.
There are two different ways to approach customizing frequency and voltage to your needs.
One: If you could run your Note at 1,900mhz, instead of 1500mhz, and draw the same amount of power, that'd be considered a success case. Your device would be faster, without a hit in battery life.
Two: Or, if you could run the device at the same speed, and lower the voltage (saving battery life), this would also be considered a success.
Sometimes, but rarely in the mobile space, you'll get lucky and receive a prime piece of silicon, and you'll be able to over clock, WHILE undervolting...resulting in a faster phone that uses battery life.
Ranger was correct...clock speed changes on the order of +/-20 percent are hardly noticeable. However, power requirements grow exponentially at higher frequencies, and on a mobile device, they're noticeable. While a device might require 1.2 volts at 1.5 GHz, and 1.3 at 1.6ghz, it might also only require 1.05, or 1.0 volts at 1.4ghz. These numbers are theoretical, and shouldn't be used-they arent even close to correct. They're used merely to illustrate that to over clock, chips often require more power than over clocking is worth, in heat (and heat past a certain point will instantly fry your device, or will reduce the lifespan of the chip).
These are general ideas on over clocking. If you want to know something specific, ask away. When over clocking/underclocking, the governor used (a set of conditions that tells the CPU when to change from, say 300mhz (when the screen is off, and the device isn't being used), to 1.5ghz, when both cores are being used, and fully loaded.
If you want to save battery life, a combination of build.prop radio tweaks, modem tweaks, under clocking profiles, and using a custom governor can significantly increase standby time, and noticeably, but not too significantly increase usage time. Its important to know though, that the screen is the hungriest part of our device, and brightness is the the quickest setting to adjust to gain battery life.
The same is true for performance. Kernel, OC profiles, build.prop and launcher tweaks, GOU over clocking, etc. All in combination can have a noticeable effect, because performance is the net sum of dozens of moving parts.
Sent from my SGH-I717 using XDA Premium HD app
Jamesyboy said:
There's no reason not to under volt.
UC=Under clock
UV=Under volt
OC=Over clock
OV=Over volt.
Newer generations of chips have tremendous tolerances. If you were to look at the S3, a Qualcomm built SoC that was a bit long-in-the-tooth by the time the Note was released, you'd see that in many cases, there were phones that featured the chip, but were clocked lower... I.E at 1,000 MHz.
Most chips are designed to run faster than they do, at least for short periods of time. Modern chips use temperature and load to designate the running frequency.
When Qualcomm releases a chip, they need to be sure that 99% of the units they produce, can run with a near-flawless level of stability. Because of this, they often run chips slower, and at a higher voltage than is actually needed. The result is, that Qualcomm or Samsung might design a chip rated for 2ghz, and release their first device with the chip running at 1.5ghz. This is common. Each piece of silicon is slightly different due to manufacturing differences. Chips are made on giant discs, with hundreds of chips on a single disc. The chips in the center are generally considered to be of a slightly higher quality, requiring less voltage, or capable of running at a higher frequency, sometimes both. Because of this, each device is capable of slightly more, or slightly less. The challenge is for Qualcomm to set the speed and power usage for every chip-- the challenge for us, is to see if we can run the chip at a higher frequency, while drawing less power....because power =heat, and power= battery life.
There are two different ways to approach customizing frequency and voltage to your needs.
One: If you could run your Note at 1,900mhz, instead of 1500mhz, and draw the same amount of power, that'd be considered a success case. Your device would be faster, without a hit in battery life.
Two: Or, if you could run the device at the same speed, and lower the voltage (saving battery life), this would also be considered a success.
Sometimes, but rarely in the mobile space, you'll get lucky and receive a prime piece of silicon, and you'll be able to over clock, WHILE undervolting...resulting in a faster phone that uses battery life.
Ranger was correct...clock speed changes on the order of +/-20 percent are hardly noticeable. However, power requirements grow exponentially at higher frequencies, and on a mobile device, they're noticeable. While a device might require 1.2 volts at 1.5 GHz, and 1.3 at 1.6ghz, it might also only require 1.05, or 1.0 volts at 1.4ghz. These numbers are theoretical, and shouldn't be used-they arent even close to correct. They're used merely to illustrate that to over clock, chips often require more power than over clocking is worth, in heat (and heat past a certain point will instantly fry your device, or will reduce the lifespan of the chip).
These are general ideas on over clocking. If you want to know something specific, ask away. When over clocking/underclocking, the governor used (a set of conditions that tells the CPU when to change from, say 300mhz (when the screen is off, and the device isn't being used), to 1.5ghz, when both cores are being used, and fully loaded.
If you want to save battery life, a combination of build.prop radio tweaks, modem tweaks, under clocking profiles, and using a custom governor can significantly increase standby time, and noticeably, but not too significantly increase usage time. Its important to know though, that the screen is the hungriest part of our device, and brightness is the the quickest setting to adjust to gain battery life.
The same is true for performance. Kernel, OC profiles, build.prop and launcher tweaks, GOU over clocking, etc. All in combination can have a noticeable effect, because performance is the net sum of dozens of moving parts.
Sent from my SGH-I717 using XDA Premium HD app
Click to expand...
Click to collapse
So what I understood is this: instead of having let's say, your note running at 1.2ghz consuming 15% battery per hour you can have it at 1.5ghz consuming the same battery life?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app