Database Develop

Droid Gone Wonky After 1.1ghz overclock

I just overclocked my droid using the tazkern 1.1 Besides being miserably slower than before when I boot up, It doesn't even give me the option to go up to 1.1 ghz. Any suggestions?

suggestion:
and don't take this wrongly in any way..
Stop overclocking so much!! It's a damn phone, not a gaming rig. That and also you really risk of damaging of your CPU and other internals...
My Milestone is running stock. It stays cool and is fast enough. This is after i tried some weeks running it on 800 Mhz. It gets too hot and that also during conversations.

I get where you're coming from but still, I was just getting a lil tired of the the thing lagging every time i opened the app drawer or market. I actually fiddled with it a little after I posted that and got it to run perfectly. And I think Im fixing to try out a 1.2ghz kernel just to see what happens. So far there's been no overheating or crashing.

ECC is kicking in and making your phone slower. Use a lower clock, your phone doesn't support it.

Actually its running quite smoothly so far. Ive been running it for around 30 mins now and its super fats, smooth, and appears stable. Ive tested it on youtube tho and its getting pretty warm.

Mines runs all day, every day at 1.2ghz. The quirks are not from the overclock. Thbey were always there.

Thats what Im on now. I think Im using the slayher 1.2ghz kernel.

Droid or Milestone?
If Droid, you're in the wrong forum. This is the Milestone one.

I have mine at 720mhz overclocked and it works fine,i dont have any heat problems,i always check the battery tempeture via SETCPU app,always is at 30C to 32C,not more than 32C!!!
I love it more tha my iphone

I think people need to learn the risks of overclocking.
You may say its stable and running fine and "just a little warm" but you are infact destroying your CPU.
If you touched your computer case and "it was a little warm" you would be worried.
Consistently hot systems aren't expected to last anywhere near as long a cooler systems. Thermal fatigue in silicon results in cracks in transistors, and transistor mounting failures, in particular. Of course, just one transistor failure on a complex system such as a motherboard or graphics card can result in the entire system failing. And a replacement board being an appropriate fix.
Source: http://ezinearticles.com/?The-Effect-of-Heat-on-CPUs-and-Computer-Systems&id=2310508
For computer CPUs, but you get the idea.

Oh dont worry. I turn my phone by the time it burstsinto flames. And btw i apologize but i did post this in the wrong forum. Oops.

droid doesnt equal milestone. development is different due to locked kernel / bootloader..
but saying that. i use 1.2ghz with 70 vsel, or 1ghz with 60 vsel.
its a little lower voltage, but i assume it saves battery.
might not be stable for you, but i've been running it for 8 days straight now..
i dont use a lower voltage cuz i heard it damages the cpu. i stay within safe tested voltages
Link to german oc voltage testing
milestone users have to rely on a kernel module to overclock.
DannyDroid said:
words
Click to expand...
Click to collapse
overclocking damaging the phone? please.. the omap 3430 has the same CPU as the 3630
3630 is upclocked to 1.2ghz and is in the droid 2. i suggest you checking out T.I.'s website. our cpu is clearly capable of reaching these speeds without damage.
Besides. i've had my milestone ever since it came out. I've been overclocking it since it became an option and my phone has never died.
but saying all that. an inexperienced user playing with voltages can seriously damage their phones if they dont know what they're doing. too high or low of voltage or speed can result in a brick.
EDIT: sry for bringing up the droid/milestone thing again, i didnt read the post above me lol

1xinfusion said:
droid doesnt equal milestone. development is different due to locked kernel / bootloader..
but saying that. i use 1.2ghz with 70 vsel, or 1ghz with 60 vsel.
its a little lower voltage, but i assume it saves battery.
might not be stable for you, but i've been running it for 8 days straight now..
i dont use a lower voltage cuz i heard it damages the cpu. i stay within safe tested voltages
Link to german oc voltage testing
milestone users have to rely on a kernel module to overclock.
overclocking damaging the phone? please.. the omap 3430 has the same CPU as the 3630
3630 is upclocked to 1.2ghz and is in the droid 2. i suggest you checking out T.I.'s website. our cpu is clearly capable of reaching these speeds without damage.
Besides. i've had my milestone ever since it came out. I've been overclocking it since it became an option and my phone has never died.
but saying all that. an inexperienced user playing with voltages can seriously damage their phones if they dont know what they're doing. too high or low of voltage or speed can result in a brick.
EDIT: sry for bringing up the droid/milestone thing again, i didnt read the post above me lol
Click to expand...
Click to collapse
The OMAP 3430 is a 65nm chip while the 3630 is a 45nm chip. Newer smaller manufacturing processes = cooler chips. They are NOT the same chips by far.
Furthermore, you realize that many memory chips are made equally. Then the memory manufacturers go and test out different batches. The ones that clock higher can be stamped as higher clocking or faster timing memory. They may be made the same, but usually the better made batches go to the higher end parts. The same goes when Intel makes CPUs. The crappy CPUs with some problems become Celerons. It might've been a Core 2 Duo or i7 or whatever, but Intel goes and disables cores/cuts off memory if it was not a good batch.
You can't look at models and go "well that CPU can do it, why can't mine."
If people have knowledge of CPU overclocking here where you understand that people look for certain serials/batches of Core i7s for best overclockability. Even though to Intel they all meet i7 930 specifications, there's still separation within the i7 930 crowd. Certain batches are better. Maybe not good enough to be an i7 950, but still better than the worst i7 930.
The other question is: What is stability? How do YOU determine what is stable? apps not crashing? In the overclocking world we run Linpack tests for like 24 hours before calling computers stable. Just because you can boot into Windows or Android or play Angry Birds for 3 hours doesn't mean much. It doesn't mean you don't suffer from bugs from overclocking. It's hard to say unless you do a full stress test on your CPU.

The 3600 OMAP is clearly superior to the 3400 series, but I do think that the latter is more overclockable.
I've had no overheating issues at 900MHz, 56 vsel, don't feel the need for higher frequency.

Will, this is all starting to go over my head. I'll just sit in the corner n twiddle my thumbs.

Just think of the 3600 as a 2010 Intel i7 chip and the 3400 as last year's i7 CPU...same platform and architecture but smaller manufacturing process and (probably) a bit faster at the same clock speeds, with the same features.

applebook said:
Just think of the 3600 as a 2010 Intel i7 chip and the 3400 as last year's i7 CPU...same platform and architecture but smaller manufacturing process and (probably) a bit faster at the same clock speeds, with the same features.
Click to expand...
Click to collapse
I was just trying to get at the same idea
I might have been too exact in my words but this is what i meant
and something fyi is that the OC capability of both chips are "capped" at 1.2ghz ... its just dangerous and unstable after that.
heat wise ? I'm inclined to believe that heavy wifi / 3g usage provides a higher source of heat than our petty oc-ing. Our cpus are clearly capable of this. true you make a good point. smaller architecture = cooler and less power. but the heat is probably out of the question. i use setcpu to display my temp. it never goes past the rated temperature. in fact it always stays at around 35c
when using wifi/3g on the other hand.. no need to say. the fact that these chips have no thermal barrier between them and the fact that the heat is able to be felt on the surface on your phone... in such close proximity to the radio chips, the cpu is not going to be heated by oc but by these other factors.
its safe to say you should lower your 3g / wifi usage to reduce thermal stress on your phone
stability wise... I'm not the one to stress test or w.e for long periods of time, but the link i've attached to my previous post shows a lot of people who have.
maybe you should check that out. I'm just here to relay information.

I have mine overclocked to 800 and it stable and quicker than stock its not all cpu its the amount of free memory you have at any given time

here is another very interesting page. this time regarding the droid
http://www.droidforums.net/forum/droid-hacks/20406-max-temp-while-overclocking-12.html
be aware that a lot of the temperatures are in fahrenheit.
highest temps of these guys average around 40-50 Celsius, way below the rated temp

Actually, mine has been running smooth this past week or so with no abnormal heat or crashes.
Sent from my Droid using Tapatalk

[q] overclocking noob question

So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.

Nerz said:
So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.
Click to expand...
Click to collapse
i have never seen the cpu get hot in my phone. it gets unstable before any heat is detected, but my phone is not very overclockable, i can get 1.3 with much care to the uv settings. i wouldnt worry about heat until the 1.4 mark, even then you are probably fine. the newer qualcom chips have been set to run at 1.9ghz and dont burn up they are on the same size architecture as ours. these arm chips run at such low voltages that heat is not really a big problem. i dont think anyone on the board has killed a hummingbird from overclocking it.

I think your speaking pre-emptively about not burning up.
Just because the chip doesn't instantly melt doesn't mean your not risking electro migration.

Nerz said:
So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.
Click to expand...
Click to collapse
this chip has a built in fail safe and can run as long as it can handle it automatically freezes or reboot your phone above its capable limit. If you want real time monitoring of your cpu clock speed/usage, ram usage and battery temp download Temp+CPU V2 widget from the market pretty good app. enjoy

[Q] Shouldn't we just shift the base clock speed to 1.5GHz?

Technically speaking all TouchPads, black or white ones have the same SoCs, the APQ8060. It's factory clock should be 1.5GHz, which the white TouchPads are set on, but the black ones are all clocked at 1.2GHz.
So if we treat it as a 1.5GHz base shouldn't we 'technically' have more overclock head room, ignoring the fact that we don't have proper kernels for that anyways?
I'm just curious on why the CM7 builds didn't use the SoC factory clock and instead followed the HP settings. Because with the kernel as it is, we can get to a maximum of about 1.8GHz using any basic overclocking program which is only about 20% over the factory speed.

they might have lowered the voltage in addition to running it at 1.2 as opposed to 1.5G. that means even if you want to set it back to 1.5G, settings still need to be looked at closely. running it at default 1.5G does not give you more overclock head room either, as the final speed that your particular touchpad cpu can run does not depend on that.

iamsamsamiam said:
Technically speaking all TouchPads, black or white ones have the same SoCs, the APQ8060. It's factory clock should be 1.5GHz, which the white TouchPads are set on, but the black ones are all clocked at 1.2GHz.
So if we treat it as a 1.5GHz base shouldn't we 'technically' have more overclock head room, ignoring the fact that we don't have proper kernels for that anyways?
I'm just curious on why the CM7 builds didn't use the SoC factory clock and instead followed the HP settings. Because with the kernel as it is, we can get to a maximum of about 1.8GHz using any basic overclocking program which is only about 20% over the factory speed.
Click to expand...
Click to collapse
HP most likely turned them down for battery life concerns (a rather common practice, Apple used to do this on the iPhone before they started making their own chips) and then undid it to justify a higher price on the white models. CM most likely is keeping it so that battery life will be comparable once its issues are worked out.

For now 1.2ghz is fast enough for me, i would rather have the better battery life.

Well, if i remember correctly, in WebOS there was no battery or heat issues changing the clock speed to 1.5GHz. Basically, the battery life was the same and the system temperature was about 2 degrees higher, and was well within the safe range. It just seemed like there was no benefit in clocking it down.
Maybe there are a battery benefits in Android, but as it stands the battery expectancy in Android is about 30-40% less than the WebOS usage range.
Moving the clock speed to over 1.5 might raise the temperature a bit, but even in WebOS people didn't see that much of a usage change (but that could be because there's nothing really to run on WebOS).

There is another thing to consider, all chips are not born equal, every fabricator of chips does what they call binning and I'll quote an article that can describe it better than I can
from - http://www.edn.com/blog/Between_The_Lines/35926-Karma_for_MPUs_is_chip_binning_burning_up_.php
"Chip binning has always been fascinating to me on many levels. What is it? It’s essentially a practice in which chip manufacturers design a chip to hit a targeted speed grade, say for example 2GHz, but after the chips are manufactured and tested, manufactures find some of the chips perform at the targeted speed grade of 2GHz, some perform at higher than 2GHz, and even more perform at lower speeds than that targeted specification number (some of those lower performing chips may perform at 1.8 GHz, others at 1.5 GHz and some at 1 GHz…and lower). But instead of throwing out the chips that didn’t hit the targeted performance specification, some semiconductor vendors, especially microprocessor vendors, sell most of them to us, the consumer. They simply put them in bins according to speed grade and price them accordingly."
Click to expand...
Click to collapse
So the 1.5GHz units may very well be of greater quality than the chips that ended up in our 1.2GHz units and by raising the base to 1.5GHz many people could end up with unstable Touchpads.

[Q] Overclocking my SGS to 1.2GHz

Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-

Shadow Life said:
Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Click to expand...
Click to collapse
Yes you can, depending on the kernel you use, oc your phone even up to 1.5 ghz.
Flash Glitch, MNICS, Devil or Semaphore Kernel for ICS roms
Do so with care as OCing WILL degrade your processor faster.

It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem

Oc SGS 1.2Ghz
nwsk said:
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Click to expand...
Click to collapse
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,

Shadow Life said:
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Click to expand...
Click to collapse
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.

upichie said:
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
Click to expand...
Click to collapse
+1

CPU Binning and undervolt

Hi,
I saw BravoMotolora's article about CPU binning, and I thought that it would be great if we compare CPU bin and voltages.
It will be great to know the relationship between voltage and PVS number.
Please follow this procedure
1. Install a custom kernel that lets you do undervolt, e.g. franco.Kernel
2. Do what BravoMotolora said
3. Undervolt your N5 by 25MV
4. Run Antutu
Then, you might see your N5 rebooting or giving you a Antutu score.
If you get the score, go and try the procedure again
I got to -50MV with PVS1 N5.
Please post your results(undervolt that you did and your N5's PVS) here!

Can you not do this?

Do not do what? I mean most of guys here will do undervolt to save battery anyway so won't it be good to share some intel?
Sent from my Nexus 5 using XDA Premium HD app

I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.

you do realize that many custom kernels set their voltages different than default/stock, and differ among themselves? for example, if you go -50mV less on using franco kernel, and go -50mV less using trinity kernel, it means nothing because their voltages differ to begin with. i mean you cant really compare each others voltages that way. you would need to write your voltages in real numbers, and cpu speed steps.

I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app

johndrmr said:
I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
Click to expand...
Click to collapse
agreed. i personally do better with underclocking, than with undervolting.

simms22 said:
agreed. i personally do better with underclocking, than with undervolting.
Click to expand...
Click to collapse
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though

This phone does pretty well arlt idle I think. Can't imagine you would see much gain from UV.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app

klin1344 said:
I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.
Click to expand...
Click to collapse
I have a PVS 2 and can undervotl -75mV accross the board and -87.5mV at 300Mhz.
So 2,26Ghz I can run at 0.975 Volt.
CM11 with Bricked Kernel.
Together with Sync off, Google hotword off and optimized automatic brightness I get constantly 5 - 5,5 hours screen on time with websurfing, mail and music stream.
Marcel

menting said:
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though
Click to expand...
Click to collapse
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.

rajendra82 said:
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.
Click to expand...
Click to collapse
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.

simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.

simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
I agree with you here. 1036 mhz is a great CPU speed for running the device and most apps. Most games UC the CPU for better battery temp like in PPSSPP. Less temperature throttle and more stable frames per second.
Benchmarks are a difference story though but who cares about those. UC is lag free, and buttery smooth so why not?
Sent from my Nexus 5 using Tapatalk

zz_marcello said:
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.
Click to expand...
Click to collapse
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.

simms22 said:
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.
Click to expand...
Click to collapse
You can do everything you are already doing, but also undervolt, and your battery life will increase, without affecting your performance. Your performance will be different than my performance (because I don't underclock), however imperceptible as it may be. So undervolting is still better than not undervolting, even for you.

Using EX kernel 3.27, underclocked to 1.5Ghz, undervolted to "700 min" and using "stock" thermal throttling setting. Rock solid and it barely even gets warm now. Responsiveness and performance is only a touch worse than stock; the only places I really notice any performance reduction is in intensive games and app install times. Battery life is massively improved.