[Q] General question and statement about modding. - G2 Q&A, Help & Troubleshooting

Can someone tell me what Custom Rom will give a better battery life AND better performance? Now before everyone attacks me...performance can AND is measured in benchmarks...And there's tons of benchmarks out there..Don't say the typical response that "benchmarks are not the same as real world usage" bla bla ...it's pretty darn close anyways...I've tried CyanogenMod and is great for battery, however cuts the phone in half on the processing side..Clean ROM, Paranoid, I have tried most...any suggestions?

Custom ROMs do have certain tweaks to increase battery life and performance, but they're usually set one way or another. To have your device running smoothly all the time, your CPU needs to cycle all the time. But that means more functions and thusly, more battery drain.
If you want the best of both worlds, you'll need to install a custom kernel with a wide selection of governors. It helps to set actions and have scripts running to determine how to best utilize your CPU, or you can just set the governor manually each time you need to change your performance parameters.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.

Related

SetCPU...Beneficial for Battery Life?

I've seen a few different posts in some of the kernel threads debating whether SetCPU is helping or hurting battery life. SO, I'm just kind of curious to see what results are on a larger scale? Based on your own experiences, do you have SetCPU installed and if so, does it help or hurt battery life generally? Also, if you do have it installed, do you use profiles? What are the most beneficial settings to use?
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
5. It's been discussed ad nauseam.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
SetCPU is not intended for battery life? Go to the Market and look at the description. If I posted this in the wrong section I apoligize. But, I think you are mistaken with your comment about SetCPU not being intended to increase battery life or increase performance...
THATTON said:
SetCPU is not intended for battery life? Go to the Market and look at the description. If I posted this in the wrong section I apoligize. But, I think you are mistaken with your comment about SetCPU not being intended to increase battery life or increase performance...
Click to expand...
Click to collapse
SetCPU only sets clock speeds and governors already in the kernel. If you just install SetCPU and adjust no settings your battery life will not change. Thus, "does SetCPU help battery life?" is utterly and completely meaningless.
Discussion of different governors and clock speeds has occurred (and is still occurring) ad nauseum and is really more suited for the General forum.
Thread moved as it does not pertain to N1 development.
I see very little gains from setcpu but I use it because I purchased it from the market and why not use it if you bought it right?
This method does not apply to drug addiction LOL
-Charlie
bri3d said:
SetCPU only sets clock speeds and governors already in the kernel. If you just install SetCPU and adjust no settings your battery life will not change. Thus, "does SetCPU help battery life?" is utterly and completely meaningless.
Discussion of different governors and clock speeds has occurred (and is still occurring) ad nauseum and is really more suited for the General forum.
Click to expand...
Click to collapse
lol Why would you download an application, not use it, and expect results?
If you throttle your CPU down you WILL get better battery life. My phone is set to never go over 600mhz and I get bettter life with it than if I turn off setcpu altogether.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Hey djmcnz thanks for the indept look at this app but more importantly thanks for showing respect to those of us who are just learning. We all have to learn information at some point and there are people that forget that at one point some one had to tell them.
Thank you for the clarification on that! Djmcnz-that was exactly what I was looking for in terms of an answer. I really appreciate you taking the time out to explain everything for me and anyone else that may have been curious.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
Don't know why you're so pissed off by a thread...
1. Not a very big issue. We have mods here to take care of this.
2. I don't know if SetCPU affects battery life or not but similar thing on a PSP device does increase the battery life. I have tried it on my PSP and setting the clock speed to the lowest acceptable level (depending upon what you're doing) does help maximizing the battery life.
3. You're absolutely right here.
4. Don't know what to say man.. but being a little humble doesn't hurt....
I never meant to be rude. I always get pissed off when people post in wrong sections Seriously. If people post in right section it just frees up moderator time. And about CPU nexus CPU has same voltage for many frequencies like 998,960 have same voltage. Going so down doesn't mostly benefit. So setcpu is only good for overclocking IMO. Display uses most of the power along with radio n CPU is one of those in middle of usage maybe 3rd or 4th. So underclocking will give a big battery boost is just a placebo. Atmost 10 minutes more is what underclocking can provide. N its not worth sacrificing the performance. Go for something underpowered if u want to underclock IMO. So setcpu serves more purpose of power than battery
I use it for the cool widget and standby/idle profile. B-)
you know what?youre allright.i follow your threads and you explain things well for someone like me learning all this ****.i got no time for keyboard commandos.thanks for the explanation.
djmcnz said:
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Click to expand...
Click to collapse
djmcnz said:
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Click to expand...
Click to collapse
HUH English Please
Kidding
mikey1022 said:
huh english please :d
kidding
Click to expand...
Click to collapse
34567890
Personaly done many tests and the result was:
Test config: WiFi tethering all the way, screen 100% Playing video all the time 2G only
4:10 @ 245Mhz hard
3:30 @ 998Mhz hard
No use actually - using N1 on 245Mhz is impossible - too sluggish.
SetCpu is ussefull:
1) If u have OC kernel to set OC mode for games like Asphalt
2)For letting android vary frequence ondemand instead of 998 all the time
3)For downclocking while in sleep mode (why use full power when u dont use it?)
4)For using Failsafe profile, to prevent battery and hardware damage.
That's all.
No use trying saving battery setting profiles like 100% - 998, 50% - 576, 20% - 499. This is useless.
On UV kernels the same thing +\-30 minutes battery life. And UV kernels themselfs dont give segnificant battery life increase, only lags and unstability ti system.
Dont believe me try yourself - Create yourself some actions fo testing and repeat them 2 time (Min cpu and Max cpu) on any kernel. Results will be very close.
SeriousX said:
3)For downclocking while in sleep mode (why use full power when u dont use it?)
Click to expand...
Click to collapse
The CPU steps down to it's minimum speed by itself. It never uses more juice than it needs to.
As far as i know, it is always at maximum, but maybe im wrong and you are right - then theres even less sence in this app.

[Q] Real world noticeable benefits of Over clocking G2?

Hey,
So I'm on the fence about perma rooting and over clocking my G2, but i have a few questions:
1) Will my battery life suffer greatly due to over clocking say to 1Ghz or 1.4Ghz?
2) Are there any real world noticeable real world performance gains besides benchmark scores?
3) Will perma-Rooting it decrease performance? (Back when i had the mytouch 3g, the phone never felt as snappy after i rooted and installed custom roms, as compared to stock).
Thanks
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
thedarkpassenger said:
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Launcher42? that's a heck lot of upgrade from Launcher2 I'd like to check it out
but he's right overclocking is not going to eat up your battery much. Heavy graphic ROMs do however suck up battery and performance. I personally like to stick to rooted stock roms and tune up here and there to fit my personal needs.
You should however read carefully and make sure to understand every steps you're doing if you want to root your phone.
androidtoy09 said:
Launcher42? that's a heck lot of upgrade from Launcher2 I'd like to check it out
but he's right overclocking is not going to eat up your battery much. Heavy graphic ROMs do however suck up battery and performance. I personally like to stick to rooted stock roms and tune up here and there to fit my personal needs.
You should however read carefully and make sure to understand every steps you're doing if you want to root your phone.
Click to expand...
Click to collapse
thedarkpassenger said:
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Alright I'm going to give it a shot later tonight probably, i forgot about the SETCPU profiles where you can have the phone under clocked while the screen is off. That should definitely give me better battery life. Ill be back to post results
kcm117 said:
Alright I'm going to give it a shot later tonight probably, i forgot about the SETCPU profiles where you can have the phone under clocked while the screen is off. That should definitely give me better battery life. Ill be back to post results
Click to expand...
Click to collapse
Good luck and I'm sure you will enjoy your G2.
Oh, and don't forget to show it off to your friends. Let them see how this thing "Fly"
I oc to 1.4+ with setcpu and a few profiles set up i get much better bat life then stock. Im also running a sense rom which feels sluggish until you oc. At 1.4 it runs smooth as can be with live wallpapers plus all the pretty sense animations. The only problem i have is i hate the sense dialer and msg system also i want to change the "personalise" tab....do people really change theyre settings everyday that they need a dedicated button for it? Anyway i digress
Sent from my HTC Vision using XDA App
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
convolution said:
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
Click to expand...
Click to collapse
No, that's not entirely true BUT with SetCPU you can profile it with different mode which can benefit the battery life.
kcm117 said:
Hey,
So I'm on the fence about perma rooting and over clocking my G2, but i have a few questions:
1) Will my battery life suffer greatly due to over clocking say to 1Ghz or 1.4Ghz?
2) Are there any real world noticeable real world performance gains besides benchmark scores?
3) Will perma-Rooting it decrease performance? (Back when i had the mytouch 3g, the phone never felt as snappy after i rooted and installed custom roms, as compared to stock).
Thanks
Click to expand...
Click to collapse
I don't notice any difference in battery and I have the 1.9ghz kernel. I normally keep it at 1ghz though. I enjoy it overclocked. My games run incredibly smooth, when navigating my phone it literally almost feels like it knows what i'm pressing a split second before i do and benchmarks rape the face off anyone else I know with an android phone. It's just sooo smooth. It really boils down to being the kind of person who likes to hold a powerhouse of a phone in the palm of their hand. (Literally) with even just the 1.4ghz OC you'll never have to ask yourself "can my phone run this without being sluggish?" because the answer is yes, it can probably even run two or three instances of whatever made you question yourself in the first place without being sluggish. Any if you're worried about custom roms from the past, just remember how outdated your old android is compared to this one. No offense because I can relate, I used to have a G1 that is now a hand-me-down to my brother and whenever he asks me to mod something on it, I'm just amazed at how slow it is and really don't know how I tolerated it for the last 2 years. I mean I'd score a 150 quadrant on the G1 (on a good day) but with my full OC on, the G2 scores 3000~3100. That's roughly 20 times faster...
Bottom line is that you won't need to worry about "will this make my device sluggish?" for quite some time.
Hey
Alright guys i got the phone perma rooted now, but i havent installed an OC kernel yet, two questions.
-Which kernal should i install if i want 1.4Ghz? there seems to be two threads with 1.4ghz kernels
-Do i need to install Bacon Bits for the kernel?
kcm117 said:
Alright guys i got the phone perma rooted now, but i havent installed an OC kernel yet, two questions.
-Which kernal should i install if i want 1.4Ghz? there seems to be two threads with 1.4ghz kernels
-Do i need to install Bacon Bits for the kernel?
Click to expand...
Click to collapse
just install cm6.1 and setCPU and you will be fine, then you can tweak it up to 1.42 if you like or whatever you want it at
Any heat related issues? Let's say I get into a zone and play some graphics intensive game 6 hours straight on USB power at 1.4Ghz? Wouldn't that put out more heat then the G2 was design to handle possibly shortening its life span?
convolution said:
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
Click to expand...
Click to collapse
It doesn't. However, overclocking is misnomer. What we really mean is over and UNDER clocking. For example with SetCPU is can create a profile that greatly slows down my CPU when the screen is off. This saves the battery a lot, since my screen is nearly always off.
Also, I can create profiles that slow down the CPU as the battery lowers in order to offset the fact that I overclock the CPU when the battery is fuller.
manvstech said:
Wouldn't that put out more heat then the G2 was design to handle possibly shortening its life span?
Click to expand...
Click to collapse
Probably could shorten the life span. I keep phones for a year or two, though, and shortened life span for me isn't an issue. The phone becomes outdated before the CPU gives up.
cparekh said:
It doesn't. However, overclocking is misnomer. What we really mean is over and UNDER clocking. For example with SetCPU is can create a profile that greatly slows down my CPU when the screen is off. This saves the battery a lot, since my screen is nearly always off.
Also, I can create profiles that slow down the CPU as the battery lowers in order to offset the fact that I overclock the CPU when the battery is fuller.
Click to expand...
Click to collapse
^This.
I've gone a full 10 hours with my battery still reporting 100%.
Sent from my HTC Vision using XDA App
my default sense rom does not feel sluggish at all.
this oc is not really required from my point of view. and it also does not increase battery. the thing what increased is the underclocking when screen is off.
and this you can do even without overclocking. and THEN it brings even more gain.
an example of "real world" for me is how well my g2 plays PSX games on the emulator. I have it overclocked at 1.5 on setcpu and it runs chrono cross pretty much flawlessly with no noticeable slow down.
i use setcpu for underclocking since i don't do enough just yet to overclock, i haven't noticed any battery increase just yet and i've been using it for a few days now. i almost questioned my self if i was losing battery life due to my system mhz always fluctuating? is this a possibility? i just added a profile for screen off 245/245 but i still had to choose on demand? what should i put there. thanks for ur help everyone
I installed the bacon bits 1.4ghz kernel and setup some setcpu profiles.....battery life is much better now.
Sent from my T-Mobile G2 using XDA App
screen off profile doesn't work with G2
noone has any proof it does change anything.
with or without widget running

Clock speed

I'm running the cm 7 build 32. I was wondering how would I clock my cpu for better battery life?
Sent from my HTC Glacier using Tapatalk
What's the best cpu controller?
Sent from my HTC Glacier using Tapatalk
Hijacking your own thread? Heh.
CM7 comes with its own CPU adjustment capability. No 3rd party app is required. From a Home screen, press the options button, select Settings>>CyanogenMod settings>>Performance. READ the warning in the pop-up window. Press OK. Select CPU settings. Set your min and max, etc. Complain publicly when your level of overclocking produces heat, battery consumption, and software failures. Do the same when your level of underclocking produces unwanted behavior.
Lather, rinse, repeat.
There are 3rd party applications that can also adjust CPU clock speed, and adjust depending on usage / battery consumption. The most popular is SetCPU. Another is CPU Tuner.
There is also another Android kernel that some users are using with CM7, which has yet again some rules for modifying performance as states change. It's called the "smartass" kernel.
I personally recommend leaving the clocks alone, especially in the cm kernels. Zinx has stated numerous times that he hasn't modified any of the voltages, so overclocking isn't the best idea. Also, underclocking can cause more battery drain than just leaving it as is.
These phones are fast as is, no need to go crazy and start messing with them other than to show off your quadrant scores.
Well I'm looking to set for better battery cause I do a lot on my phones. I already killed the cm7 in one day without charging. I just wanna make it where it last the day
option94 said:
I personally recommend leaving the clocks alone, especially in the cm kernels. Zinx has stated numerous times that he hasn't modified any of the voltages, so overclocking isn't the best idea. Also, underclocking can cause more battery drain than just leaving it as is.
These phones are fast as is, no need to go crazy and start messing with them other than to show off your quadrant scores.
Click to expand...
Click to collapse
Sent from my HTC Glacier using Tapatalk

set cpu

OK for those that boast supreme bat life and performance please share your "EXACT" setup for set CPU, rom, kernel etc. Pretty please.
btucker2003 said:
OK for those that boast supreme bat life and performance please share your "EXACT" setup for set CPU, rom, kernel etc. Pretty please.
Click to expand...
Click to collapse
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.
The best thing I did was uninstall setcpu and let the custom kernel work,
Sent from my Nexus S 4G using xda premium
Currently running Taboonay 2.1b with rtrip's custom kernel 3.4 - it had issues with setcpu so I uninstalled it and am letting the kernel do it's thing - OC'd t 1.4 and it's smooth and fast but still has a decent battery life despite running a bunch of stuff, games, music, email and navigation - wifi on always...
Standby is about 3.5 days / on constantly about 7.5 hour life, so..yeah...Me likey..
YMMV
kjy2010 said:
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.
Click to expand...
Click to collapse
LOL, I was wondering the same thing about "boast supreme bat life and performance". This reminded me of my days of tuning cars and we we used to say "Fast, cheap, and reliable. You can have 2 of the 3."
OP, all machines won't react exactly the same way and people use their tablets for difference purposes, so having others post exactly what they have setup probably isn't the best way to go. First, you need to find a kernel that works and is stable for everything you need. Kernels are changing all the time, sometimes they move two steps forward and 1 step back before they are stable again and support everything a user needs (docking, NTFS mount, cifs, 3G etc.). After you find a kernel that is stable and suits your needs using the defaults, then you can take it a step further if you wish.
If you want a performance minded setup, setup a profile (in setcpu or one of the others) using the desired clock speed. Try 1.4 or 1.5 Ghz to start as that seems to work for most. Use the governor recommended by the kernel developer for best results. The more you over-clock, the more battery you will consume.
If things are stable with the default voltages, then experiment with under-volting to get the best battery life you can for your performance profile. Start with the recommended voltages with your kernel and adjust down -10uV at your max CPU frequency to find out how much voltage you can reduce and still have a stable system. Make sure you run through all the things you typically do and give it a good workout before moving down to another voltage. Using benchmarks can be helpful for finding stability, but may not match how you use the tablet in the real world.
If you want the best battery life, then experiment with under-clocking to 912MHz and then try under-volting that clock speed to find your stable point. You could then setup a setup "battery mizer" profile for that.
If this sounds too difficult and time consuming for you, then do as the others have stated and just install a custom kernel that does what you need and let it work for you. It should give you a good "in-between" setup. For me, I am addicted to 1.5GHz as the increased smoothness from stock is very noticeable for me. I can recharge every night after 6 hrs or so, so this works great for me. If I go on the road and need to take it easy on the battery, I use another profile to get better battery life for the time being.
Hope this helps you out.
kjy2010 said:
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.
Click to expand...
Click to collapse
_motley said:
LOL, I was wondering the same thing about "boast supreme bat life and performance". This reminded me of my days of tuning cars and we we used to say "Fast, cheap, and reliable. You can have 2 of the 3."
OP, all machines won't react exactly the same way and people use their tablets for difference purposes, so having others post exactly what they have setup probably isn't the best way to go. First, you need to find a kernel that works and is stable for everything you need. Kernels are changing all the time, sometimes they move two steps forward and 1 step back before they are stable again and support everything a user needs (docking, NTFS mount, cifs, 3G etc.). After you find a kernel that is stable and suits your needs using the defaults, then you can take it a step further if you wish.
If you want a performance minded setup, setup a profile (in setcpu or one of the others) using the desired clock speed. Try 1.4 or 1.5 Ghz to start as that seems to work for most. Use the governor recommended by the kernel developer for best results. The more you over-clock, the more battery you will consume.
If things are stable with the default voltages, then experiment with under-volting to get the best battery life you can for your performance profile. Start with the recommended voltages with your kernel and adjust down -10uV at your max CPU frequency to find out how much voltage you can reduce and still have a stable system. Make sure you run through all the things you typically do and give it a good workout before moving down to another voltage. Using benchmarks can be helpful for finding stability, but may not match how you use the tablet in the real world.
If you want the best battery life, then experiment with under-clocking to 912MHz and then try under-volting that clock speed to find your stable point. You could then setup a setup "battery mizer" profile for that.
If this sounds too difficult and time consuming for you, then do as the others have stated and just install a custom kernel that does what you need and let it work for you. It should give you a good "in-between" setup. For me, I am addicted to 1.5GHz as the increased smoothness from stock is very noticeable for me. I can recharge every night after 6 hrs or so, so this works great for me. If I go on the road and need to take it easy on the battery, I use another profile to get better battery life for the time being.
Hope this helps you out.
Click to expand...
Click to collapse
Hah! Well thanks but I'm pretty sure I didn't say "overclocking" but gotcha thanks for the feedback and answers. I was merely looking for setups compared to what I'm running now. TIA

[Q] No 'Battery Life' ROM for the Nexus 7?

Correct me if I'm wrong, but I've seen loads of ROMs all about adding speed to the Nexus 7, and most of these ROMs also advertise better battery life, but I've not found any that actually have better battery life than stock, and I haven't seen any ROMs with a main purpose of increasing the battery life.
Also, it might be just me but I'm really satisfied with the speed of the stock ROM so I don't see much need to speed it up!
Franco Kernel did increase my battery life but I can't use it on 4.2.2 as it locks up my device into deep sleep. Other kernels I've tried have increased performance but not battery life. I have tried Elite Battery Saving kernel but that's for an old version of android, so to revert back in kernel would be reverting lots of the changes in kernel that have been done by Google I think (I know there were a lot of changes from 4.2.1 to 4.2.2?)
So my question is, is there a ROM / Kernel combination out there that is just trying to increase the battery life?
Thanks a lot. No disrespect to the hardworking devs that work on speeding up the Nexus 7; it's just my personal opinion.
Roms have little impact on battery life. Its primarily going to be a combo of the kernel and your own unique settings. Want to see anecdotes regarding other users' results with different kernels? There a thread for that.
Sent from my Nexus 7 using Tapatalk HD
As najaboy stated, it's a combination of kernel and user settings.
Note that custom kernels have governors, which regulate cpu core active states, and mhtz. Suggest you read up on custom kernel governors to get the most.
Also, we have a thread pertaining to this;
http://forum.xda-developers.com/showthread.php?p=38092846#post38092846
As "Best Rom-Kernel" threads are not allowed, however, that thread is dedicated to it.
Thread Closed.
MD

Categories

Resources