Database Users

Best battery life kernel on sense rom?

Hey guys, in your opinion what gives the best battery life on a sense ROM like Mikshift? BC's 1.5GHz, 1.8GHZ or X99, Scary Kernel, ect. Just curious what some of your experiences are..

PaulB007 said:
Hey guys, in your opinion what gives the best battery life on a sense ROM like Mikshift? BC's 1.5GHz, 1.8GHZ or X99, Scary Kernel, ect. Just curious what some of your experiences are..
Click to expand...
Click to collapse
I have been running mikshift since the beta along with bcnice20 oc uv 1.5 kernel with amazing battery life, if I forget my charger I don't even worry the standby time of that set up is just amazing ran for 24 hours on wifi with about 5 hours of using the net,tapatalk and about 75 texts and was at 50% at 24 hours of being unplugged its the only setup ill run, sometimes ill throw the 1.8 on there just to show everyone I can go that high but its never needed. I run at 1516 max 368 min conservative with a screen off profile for 806 max and 368 min no complaints here at all!! Its actually the only setup I'm willing to run!
Sent from my PG06100 using Tapatalk

Go with the x99 kernel without changing any settings. Just flash and leave it alone. Easy 2 days like that
Sent from my PG06100 using Tapatalk

What Kernel are you guys using on the lastest CM7?

How many .35 kernels are available? I'm only aware of Umaro's and the stock CM kernel. I'm trying to achieve better battery life, so what kernel are you guys using?
So far, using Umaro's, I'm getting regular battery life, nothing special. Haven't tried the stock CM kernel.
Are they any other undervolted kernels available?

durps said:
How many .35 kernels are available? I'm only aware of Umaro's and the stock CM kernel. I'm trying to achieve better battery life, so what kernel are you guys using?
So far, using Umaro's, I'm getting regular battery life, nothing special. Haven't tried the stock CM kernel.
Are they any other undervolted kernels available?
Click to expand...
Click to collapse
There aren't any others so far. Umaro's kernel is really good for battery life, however it's not up to date with the latest kanged nightly from yesterday.

Ahh, I see. Thanks for the info.
What cpu settings are you running?

durps said:
Ahh, I see. Thanks for the info.
What cpu settings are you running?
Click to expand...
Click to collapse
Right now I'm using a kanged nightly with the "stock" cpu settings of 245MHz min and 1024MHz max, but with the interactive governor. With Umaro's kernel I had at 245 min, 1017 max and the Smartass governor. The smartass is pretty good on battery.

u made all the right moves all i would do is dim screen and keep runnimg apps low.
pimped out g2

btw pyromod 2.0 345 ghz min 1405ghz max on smartass. i fully charge bout 1 a day
pimped out g2

Pershoot released his kernel the other day pretty nice and smooth
Sent from my HTC Vision using XDA App

Alright I'm sleepy so this will be in rambling form but...
I've tried Umaro's and I'm not sure if it was the undervolting (which I haven't looked into tweaking) but my phone kept stuttering no matter which governor I used. I was using Htcclay's Super CM7 1.8 with cpu set to 245/1113
I also used the stock kernel that's been on CM7 with no problems and average to good battery life (10-15 hours of active use: texting, browsing, few calls, and playing the occasional game)
Most recently I've used Pershoots which I had heard worked great. I myself love it. Almost same battery life as stock kernel but everything felt just a little bit smoother performance wise.
Here's a link to Pershoot's thread:http://forum.xda-developers.com/showthread.php?t=847672

The stock cm kernel in my opinion is finally good enough that it doesn't need changed. I have always flashed pershoots and occassionally others, but it truly does not need supplemented IMHO.
Sent from my HTC Vision using XDA Premium App

I'm using savaged zen, and I get around two days of battery on a charge, with normal use.
Min: 368 max: 768
Sent from my HTC Vision using XDA App

Using Pershoots latest kernel, have nothing but good things to say about his kernels. Always my go to kernel.

fedtemis said:
I'm using savaged zen, and I get around two days of battery on a charge, with normal use.
Min: 368 max: 768
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
You're running that on Vision? I can't seem to find it for our device.

Stock CM7 kernel here. I run 245/806 Interactive with automatic brightness. I've found that when wifi is on, keeping the cell radio @ 2G only works wonders. Wifi is set to sleep on screen off, but not when plugged in. 1 day 7 hours on this charge so far with 23% left. I would consider my use light to moderate.
HTC Vision (G2) - CM7 B95 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!

durps said:
How many .35 kernels are available? I'm only aware of Umaro's and the stock CM kernel. I'm trying to achieve better battery life, so what kernel are you guys using?
So far, using Umaro's, I'm getting regular battery life, nothing special. Haven't tried the stock CM kernel.
Are they any other undervolted kernels available?
Click to expand...
Click to collapse
I'm wondering where can I download the Umaro's kernel. I check out his github (https://github.com/umaro/htc-kernel-msm7x30) only to find out that the source is available.

800mhz is enough

Quick, and great battery. Overclocking is pointless unless you play games on your phone, or care about your quadrant score.
Sent from my Nexus S 4G using XDA App

Yup, I agree with you

+1
I had a Milestone for 1.5 years on stock ROM (that is 550Mhz), pretty much served most of my needs perfectly....you know, the normal stuff you use your phone for.

I rarely notice my phone is underclocked... with smartass governor, it's more responsive than stock clocks with a less responsive governor.
Battery life doesn't seem improved, but I know that my weak signal is causing the problem here.

synaesthetic said:
I rarely notice my phone is underclocked... with smartass governor, it's more responsive than stock clocks with a less responsive governor.
Battery life doesn't seem improved, but I know that my weak signal is causing the problem here.
Click to expand...
Click to collapse
I Sunni it's different for me.. When in use it seems to drain about the same but last night I set the phone down around 11 worth 84% battery life and got up at 6 with 78% still and that's setting the governor to smartass

It's bad for me because my phone goes without signal about half the time in my apartment. I'll be moving soon so it's not a huge issue, but it is kind of disconcerting to feel my phone heating up from just sitting around doing nothing.

synaesthetic said:
It's bad for me because my phone goes without signal about half the time in my apartment. I'll be moving soon so it's not a huge issue, but it is kind of disconcerting to feel my phone heating up from just sitting around doing nothing.
Click to expand...
Click to collapse
You could try disabling the governor and let one like, setcpu do it? Before I went Incredikernel I set up a profile in setcpu that whenever my screen was off it wouldn't run any faster then 128MHz but when on was set for either on demand or performance. Using two governors at the same time causes lag I've found so you'd have to be running a rom that doesn't already have one (that you can see and change) built in

Yea, this is true. OC'ing I thought it was giving me speed, but I actually took the time to really see the speed on OC'ing and to me it dosent seem to change. Well maybe alittle bit, but still. But yea, so I just hit 1ghz and I just leave it there.
Pete's latest w/Yennob-Base2 kernel at 1ghz and its going good.

kijp15 said:
Yea, this is true. OC'ing I thought it was giving me speed, but I actually took the time to really see the speed on OC'ing and to me it dosent seem to change. Well maybe alittle bit, but still. But yea, so I just hit 1ghz and I just leave it there.
Pete's latest w/Yennob-Base2 kernel at 1ghz and its going good.
Click to expand...
Click to collapse
Yeah I honestly can't tell a difference between running at 998 MHz and 1,113 MHz other than a physically hotter phone and faster battery loss lol

IAmTheOneTheyCallNeo said:
Yeah I honestly can't tell a difference between running at 998 MHz and 1,113 MHz other than a physically hotter phone and faster battery loss lol
HTC-Incredible on Android 2.3.5
CyanogenMod-7 Nightly (8/18)
Chad's Incredikernel-GB #9 (SA)
Click to expand...
Click to collapse
Ahaha, yea. Everytime I would hit 1.3ghz or 1.4ghz for the fun of it, my phone would get that way too. It would get hot and it feels like it would explode in my face and yea battery life would drop like crazy.

Personally, I find myself running into a wall with RAM more than with processor power. I really hope the next Nexus at least doubles it.

No problems with overclocking: http://forum.xda-developers.com/showpost.php?p=16791637&postcount=124

Well the SuperOSR is only for nexus s.. If there was one for the ns4g, well then after reading that, I would be OC'ing like a maniac.

zorak950 said:
Personally, I find myself running into a wall with RAM more than with processor power. I really hope the next Nexus at least doubles it.
Click to expand...
Click to collapse
This. I'm really feeling the loss of RAM coming from a mytouch 4G. That extra 256MB really made a difference. Using juwe's RAM optimization script seems to help, though.

Ehm, how can Ram be a problem?
Android is managing it itself and can't run out of it, usually.
Sent from my Nexus S using XDA App

rentaric said:
Ehm, how can Ram be a problem?
Android is managing it itself and can't run out of it, usually.
Click to expand...
Click to collapse
Things get killed that you don't want getting killed, and when it starts to run low things slow down considerably. It's not that something won't run, but it may run badly, or cause other apps to close that you were multitasking on, which is inconvenient.

I average 16 hours with normal for me use, which is a lot of texting, Facebook, internet browsing, listening to music.
Sent from my Nexus S 4G using XDA App

Skimp Killah said:
I average 16 hours with normal for me use, which is a lot of texting, Facebook, internet browsing, listening to music.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
How so? I normally get around 9-10 hours max with moderate use, also depending on the signal i get half the time.

I use netarchys latest bfs kernel with proton to undervolt all CPU frequencies to -20mv. And I have the CPU limited to 100-800mhz, with the on demand governer. With those 2 thing I get 15-16 hours everyday. I also usually let my batter get down to atleast 5% before charging.
Sent from my Nexus S 4G using XDA App

Skimp Killah said:
Quick, and great battery. Overclocking is pointless unless you play games on your phone, or care about your quadrant score.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
it's true
i always Under clock the phone with SetCPU to save battery life

Savage Zen/Tiamat kernel

On CM7 I dont have ondemand governor with the tiamat or savage. Only with stock CM7 kernel. What should I use instead?
Also does it take a while to notice improve me with these kernels?
Also those with awesome battery life on stock battery are you leaving wifi on? I get about half those times but I leave 3g on all the time.
I wish I could get through an 8 hour work day with 5hrs of screen on time on my battery.
Usually on my yoobao 3000mah I get 4.5hrs on screen time with no charging throughout the day lasts about 17hrs that way.
If I switch back to my stock battery I wouldnt be getting that would I?
CM7.1 nightly
yoobao 3000mah battery
tiamat 407 kernel. Everything under volted by 50mV but I do not think it is sticking.

churro7 said:
On CM7 I dont have ondemand governor with the tiamat or savage. Only with stock CM7 kernel. What should I use instead?
Also does it take a while to notice improve me with these kernels?
Also those with awesome battery life on stock battery are you leaving wifi on? I get about half those times but I leave 3g on all the time.
I wish I could get through an 8 hour work day with 5hrs of screen on time on my battery.
Usually on my yoobao 3000mah I get 4.5hrs on screen time with no charging throughout the day lasts about 17hrs that way.
If I switch back to my stock battery I wouldnt be getting that would I?
CM7.1 nightly
yoobao 3000mah battery
tiamat 407 kernel. Everything under volted by 50mV but I do not think it is sticking.
Click to expand...
Click to collapse
i prefer the SavagedZen 2.2.1 kernel with savagedzen. but would suggest trying the smartass and interactiveX governors to see which one you and your phone prefer. some folks like the 3.06 version of Tiamat, you may want to ask folks in the tiamat thread about the diff between 4.07 and 3.06 (not positive on the version numbers).
i'd suggest running each for a couple days to see how it feels.
i use Tasker to activate my wifi when i arrive at work and at home...the rest of the time my wifi is off unless i turn it on.
the "5hrs of screen on time" may be an issue, the screen draws a lot of juice. perhaps if you verify your undervolting is sticking, used no widgets, do not use live wallpapers, set everything to sync once or twice a day you'd get further...but thats kinda no fun and i still don't think you'd get 5hrs.
i've had a light day on my phone...1.5hrs of screen on and i'm at 16hrs w/ 44% left. standard battery.

How can I verify the UV settings?
smartass is laggy

You guys should d/l System tuner. You can change your Governor with that app

Some guys swear by the SavagedZen kernel but it's reached the end of it's development life, the SavagedZen team is no longer supporting or updating the kernel and it hasn't been updated in almost 3 months. My personal experience with the kernel notwithstanding, I think that's reason enough to stick with Tiamat.

Turn brightness to 30 or 40%. Get a mugen 4500 mAh. Problem solved...your welcome.
Oh and there is ondemand in sz221. I am currently using tiamat 407 SBC conservative governor and my settings. No undervolt and working very nicely
I own a stock, gailio 2000mah, and siedio 3500. My 3500 never has a problem making a heavy day of use. I'm guessing that 4500 def wouldnt

churro7 said:
How can I verify the UV settings?
smartass is laggy
Click to expand...
Click to collapse
you can use vipermod to set and verify your uv settings. there are other apps as well. but i find the script works well.
in CM7 you can set your governor and clock speed via:
menu -> settings -> Cyanogen Settings -> Performance -> CPU Settings
no 3rd party app is required. (unless you wish to use "profiles" like those available with SetCPU)
you may find interactiveX to be more responsive.
yes, SZ is not currently being developed and tiamat just released v407.
i may try the new tiamat kernel to see if it plays nice with my phone.
note: the new tiamat is based on 2.6.38.8 and SZ is based on 2.5.38.7.
thus far my EVO has shown a definite preference for SZ over Tiamat. /shrug
i always feel like i'm carrying around a pregnant EVO when i put on the 3500mh battery. LoL

My Evo also never ran tiamat well after 337 but 407 is running great

I avg five hours display on time. I have Deck's AOSP ROM and I turn off background data and sync twitter and email manually. I use Gemini App Manager to prevent apps from auto starting. I'm using a S-Z CFS kernel interactive x governor with SBC. I rely on 3g during my commute and wifi while at work and at home. I use the web, youtube and the xda app extensively. I don't think it is possible to have five hours screen on time using 3g only. Sprint's network is not that strong.
Sent from my PC36100 using XDA App

Safe Overclock Speeds?

I've read many threads where people say they have their G2 up around 1.5 and I'm just wondering what is considered a safe OC speed?
Some of the threads say there isn't much noticeable difference after 1.2, can any of you confirm this?
I'm on meXdroid right now and I've been keeping it at 1.2 but it gives me the option of going up to 1.516, so I'm wondering if there's any damage that might be done if I go with the max.

kingston73 said:
I've read many threads where people say they have their G2 up around 1.5 and I'm just wondering what is considered a safe OC speed?
Some of the threads say there isn't much noticeable difference after 1.2, can any of you confirm this?
I'm on meXdroid right now and I've been keeping it at 1.2 but it gives me the option of going up to 1.516, so I'm wondering if there's any damage that might be done if I go with the max.
Click to expand...
Click to collapse
I'm running CM7.1 at a max of 1.4 without any problems. Not sure there is such a thing as completely "safe" when overclocking, but I also read about many who are at 1.5 or higher. I did notice a slight improvement going from 1.2 to 1.4 on my phone, but nothing substantial.

its safe to oc at 1.5 the thing is you wont be gaining a lot of performance but you will be draining more juice

After 1.2 the only thing you get is more battery consuccion.
The safe way is keeping the cpu ondemand or conservative between 245 - 1200.
If you want safe battery you can use setcpu and make 2 profiles one in screen off (powersave 245-368) screen on (ondemand 245-1200).
Note: for miui screen off profile have to be (245-768) because (245-368) cause delay in incoming calls.
And remember always the scale depends what kernel you use.
I using now pershoot 2.6.35.14
Is good with battery life so i recommended to you.
I was using ILWT kernel v1.5.1, is more better on battery life but i notice some problems went i use maps.
I hope that help you
Sent from my HTC Vision using xda premium

Ive also looked into this quite a bit and most people say around 1200mhz is the sweet spot for battery and speed.

also overclocking depends on kernel

I've ran mine at 1.42 using Unity sense as a daily driver.

pedroflovera said:
After 1.2 the only thing you get is more battery consuccion.
The safe way is keeping the cpu ondemand or conservative between 245 - 1200.
If you want safe battery you can use setcpu and make 2 profiles one in screen off (powersave 245-368) screen on (ondemand 245-1200).
Note: for miui screen off profile have to be (245-768) because (245-368) cause delay in incoming calls.
And remember always the scale depends what kernel you use.
I using now pershoot 2.6.35.14
Is good with battery life so i recommended to you.
I was using ILWT kernel v1.5.1, is more better on battery life but i notice some problems went i use maps.
I hope that help you
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
The OP is using meXdroidmod which has "tweaKr" script so no need for set CPU and he also has option to adjust voltages and many other tweaks. MeXdroidmod is awesome!
To the OP, just keep it at 1.2 . Like others have mentioned...just wasting juice if any higher.
HTC Vision(G2), meXdroidmod Ghost Chili AIO ROM/ICS CM7 theme.

I have mine at 1.6Ghz set on performance screen on, 368-768 ondemand screen off. I'm a medium/light user and will have around 20-30% left when i plug it in at night.
The amount you can overclock while still maintaining decent battery life really depends on if you're a light/medium/heavy user - because the charge is only being rapidly drained while the screen is on (if you have a sensible screen off profile set up). Light users can afford to run at high speeds on performance govenors, heavy users should run at lower speeds with conservative governors.
As for how safe overclocking is i'm not completely sure what the limits are, but there are people who run their G2's at 2Ghz and get no problems... the biggest danger is probably heat damage to the phone, but the battery will fail before you get to temperatures that will damage the phone so i wouldn't worry about that. The other concern is reducing the life of the cpu, however the longest you will have a phone is around 2 years, and an overclocked cpu will still last far longer than this.
Hope I helped answer your question, I am running Miui btw.

I have a 2.7ghz kernel on cyanogen 7.1 and I call it the Turbo charged g2
Sent from my HTC Vision using XDA App

The maximum speed our G2 can go is 2.03 but if you want battery and spped i recommend setting it up in between 0.9 and 1.3
Hope it helps!

the 7x30 processors are designed to run up to 1.5 so basically it's not oc. and the Desire z/G2 come with underclocked kernels on stock

Currenty oc my dz to 1.5ghz. Can oc to 1.9ghz without any problem.
Sent from my HTC Vision using XDA App

lolocabra said:
the 7x30 processors are designed to run up to 1.5 so basically it's not oc. and the Desire z/G2 come with underclocked kernels on stock
Click to expand...
Click to collapse
seriously?! it can run 1.5ghz without burning the cpu??

Steven How said:
seriously?! it can run 1.5ghz without burning the cpu??
Click to expand...
Click to collapse
Yup, a lot of people are running 1.2 or 1.5 daily.
Sent from my T-Mobile G2 using XDA App

i always thought they took Desire's 1GHz cpu and put it underclocked in the dz... so i oc it to 1GHz...
—————
|RIROZIZO|
—————

Steven How said:
seriously?! it can run 1.5ghz without burning the cpu??
Click to expand...
Click to collapse
That's incorrect from what I've read the CPU the g2 has is a 800 stock its not underclocked or nothing that's how it came From HTC but its a 2nd Gen snapdragon and their for very recealient and efficient and their for can be overclocked .. and from what I have seen and read this CPU has been overclocked more then any other CPU on a phone ... its bad ass!
Oh yeah .. I'm running mine at 1.4max and .122min with ondemand on g-light 2.0.1 rom and no over heating
Sent from my T-Mobile G2 using XDA App

Wow,wat if I run at 384mhz-1.2ghz and the battery become pretty hot? :/
Sent from my HTC Vision using XDA App

andslide said:
I have a 2.7ghz kernel on cyanogen 7.1 and I call it the Turbo charged g2
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Mind give me the link to download the 2.7ghz kernel XD ?
Sent from my HTC Vision using XDA App

Safely ocing to 1.4 on my daily rom.
Sent from my HTC Vision using Tapatalk Pro with Swype