Develop Bugs

battery drain and Snap with CM6?

CM6 is definitely great, I think without question it is a vast improvement.
The only issue I have is my battery life is ABSOLUTELY HORRIBLE. Could be the worst battery life I've had with any phone. But maybe that's just the EVO, with it's big screen and speedy processor. I underclock to 384 mhz sometimes but then the thing slows down and even freezes. I have 3 different batteries and they all perform about the same (not good.) Before I had a partial wake issue but that's gone, and battery life still stinks. I've also tried calibrating but nothing really seems to make it better.
I hear the snap thing is good for battery life but I everytime I open that thread I get a headache. I love this phone and am obsessed wtih it but that thread is a bit much even for me!
Can anyone give me a quick and dirty explaination of what snap is / how to use snap? Which kernel to flash? Some day I hope to digest that mammoth of a thread, but right now I'm too busy reading texts for college and Just want better battery life.
Thanks!

Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.

nyc_zx10 said:
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
Click to expand...
Click to collapse
Yeah, I tried System Panel but the things eating my battery were mostly system things, like Browser. I guess I could give it another go.
Why are Juice Defender reviews so bad? I've considered it before also, maybe will try playing with it again

snap 8.2 is the current release. you can try any of the kernels, but i would avoid the 7.0/7.1 SD Card implementations since that technology has been put on the back burner for a bit.
Snap allows you to you Overclock and Undervolt (aka: UV).
Overclocking of course is for speed and Undervolting may save battery.
all EVOs are not created equal. some like undervolting some do not. so snap is available in multiple flavors. each with a different UV floor. the lower the floor the more potential battery saving..but also the more chance for a random reboot or wifi/gps acting funny. remember UV retards the amount of power so things can act goofy. the different UV floors are 800mv - 925mv. for example...i use the 8.2_900 because it works well with my EVO. the 8.2_800 booted great but after a while started rebooting itself. 8.2_850 just hung at bootup. the 8.1 kernels didn't work for me at all. 7.3b1 was great.
HAVs is adaptive..so don't get stressed if your device fails to boot properly the first time. wipe the cache/dalvik and try again.
so download a few of the 8.2 kernels.
make your nandroid
begin trial and error (I'd suggest starting at 800, 850 then 900 to get a feel)
don't be afraid to wipe the Cache and Dalvik multiple times.
don't worry about the whole thread. just grab the last few pages and read the OP. then feel free to ask.
i also recommend setCPU. you can find some threads for SetCPU configurations to help. BUT....make sure SetCPU is disabled when flashing the new kernel. once you get a working kernel you can enable SetCPU...but during testing phase it will give you gray hair.
jmxp69 said:
Just a few quick thoughts on voltages/freqs after seeing a handful of discussion in the thread:
1) Every 8.2 kernel has voltages lower than stock. The default stock voltage @ 245 is something around 1050.
2) No real effort is made to UV at the top end. It's a little lower, but the objective at the highest CPU frequency is not to UV. Most of the benefit of UV comes at the low end of the scale when your phone is idle (most of the time). Less voltage = less draw.
3) nHAVS scales voltage at each step. There is a min.max voltage at every cpu frequency. This range is fairly small--50-75mv, but it enables HAVS to decide based on feedback from the CPU which one to apply. And the max at each step is lower than stock. So no matter how you slice it, even if you're running 925, you are undervolted. This becomes a question of how undervolted.
4) OC is not about undervolting, it's about overclocking. The differences is voltage vs. frequency. OC means we're increasing the CPU frequency beyond stock which is 998mhz in the case of Evo. If you move your SetCPU slider beyond 998mhz, you're overclocking.
The objective of overclocking is speed. The objective of undervolting is battery savings. Snap gives you both. We overclock when we increase the fequency with SetCPU. We undervolt automatically via nHAVS. As of this writing, UV is handled in the kernel, it happens most at the bottom end of the frequency scale.
I hope this helps clear up some of the questions. Great conversation by the way.
Click to expand...
Click to collapse

GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol

Thank you Dragin!!!
That helps a lot! So once you have Snap setup at what you feel is "good" does your phone seem to perform as well as before you had it undervolted? Man, sounds like a pretty involved process - maybe I better wait until I can really sit down and play with it.

goodelyfe said:
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Click to expand...
Click to collapse
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App

foueddyf said:
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I think he's talking about when ur figuring out the best setup

Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App

I had the same issue, left to stock with kingx.
Sent from my PC36100 using XDA App

nyc_zx10 said:
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you know what in particular Juice is doing to give you better battery life? like what does Turn off certain things based on conditions or?
That is some good battery life.

Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App

nyc_zx10 said:
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Meh... see I really don't want to do those things. I can turn off data sync myself and just have gmail forward me a text message when I have an email. I just was hoping there was a way to get decent battery life without going back to the days of Winmo
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)

berardi said:
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
Click to expand...
Click to collapse
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.

DraginMagik said:
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
Click to expand...
Click to collapse
Thanks man, appreciate the breakdown.
You have inspired me, I'm going to bite the bullet and try this snap7.5_925 kernel. I'll report back my luck
I do enjoy this stuff, really - just right now it would be irresponsible for me to spend too much time on it. School comes first right now.

DraginMagik said:
... after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
Click to expand...
Click to collapse
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.

loupy said:
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
Click to expand...
Click to collapse
Yeah dragin, don't hog those sweet settings! I'm enjoying Snap 7.6 and it seems to be helping out my battery life a bit, but I'd love to see your SetCPU details.

I've found that the issue for me is bluetooth. If I have it on constantly my battery will drain 10-15% per hour. With bluetooth off it's only draining 1%-2% per hour.
Seems like the bluetooth needs work on CM6 in order to have the efficiency that the other ROMs i've tried (Fresh and EViO) have. Nonetheless, I'm sticking with CM6 and just use the bluetooth when necessary.

I have the same issue with bluetooth on CM 6.0.0. I am running the stock kernel that comes with cyanogenmod, so this is definitely not a snap issue. There was a bug submitted about a month ago:
code.google.com/p/cyanogenmod/issues/detail?id=2136
I *really* hope this can get fixed for the 6.1 release, but it is currently listed with a low priority. I really love CM6, but basically making bluetooth unusable for more than a few hours really makes me struggle with the using this rom.

Why not the 7.6 with turbo...just wonderin

[Q] Safe Overclocking speed

How fast can I overclock my chip to in my Rhod100 safely?
I'm using OCT I.5

CPUs are all different from on another. A "safe" speed for one person may not be for another. Best bet is to experiment by trying the next increment up, and test to see if there is any instability, SOD, etc. If everything looks okay, try the next increment up.
Some people on the overclocking thread seem to be having good luck at the lower-700s, with dynamic OC'ing turned off. I have mine set for the default 652 MHz setting (but with dynamic OC'ing off) just to be on the safe side.

You do not increase voltage, so overclocking to any value should be safe. In the worst case you just hang the device, but a softreset fixes this. I found the 710Mhz frequency to be 100% reliable.

Thanks Guys. Been a big help

i dunno, depends on software and rom. i personally do 768 no dynamic, all settings 0 at 1000ms on energy cookie 23138 sep 14. no reset needed for a month or so. and when it did it was user error lol.
but u just gotta play with it. expect to reset a few times. and id keep all settings on 0 at 1000 ms. just me.

Jackos said:
You do not increase voltage, so overclocking to any value should be safe. In the worst case you just hang the device, but a softreset fixes this. I found the 710Mhz frequency to be 100% reliable.
Click to expand...
Click to collapse
710 is the most reliable ive seen from public opinion

I did a bit of research and found out the chip is capable of 850mhz.
I've got mine running at 806.4 and seems to be runnning fine. I switched the stepping off. Feels awesome.

uncleswoop said:
i dunno, depends on software and rom. i personally do 768 no dynamic, all settings 0 at 1000ms on energy cookie 23138 sep 14. no reset needed for a month or so. and when it did it was user error lol.
but u just gotta play with it. expect to reset a few times. and id keep all settings on 0 at 1000 ms. just me.
Click to expand...
Click to collapse
How can no reset be needed for a month if your rom version is only 3 days old?

enahs_ said:
How can no reset be needed for a month if your rom version is only 3 days old?
Click to expand...
Click to collapse
i lol'd

enahs_ said:
How can no reset be needed for a month if your rom version is only 3 days old?
Click to expand...
Click to collapse
i meant from reset needed from sod's or other issues.
energy has been my rom of choice for quite some time. every version has been fully compatible for me with oct. thats what i meant to say

Can someone link to the overclocking software? I'd like to give it a try.
How about battery life and temperature? Does overclocking to 710 reduce battery life and increase the phone's operating temperature? If so, by how much?

gromky said:
Can someone link to the overclocking software? I'd like to give it a try.
How about battery life and temperature? Does overclocking to 710 reduce battery life and increase the phone's operating temperature? If so, by how much?
Click to expand...
Click to collapse
There Are 2 Overclocking Apps You Can Find Them
Here http://forum.xda-developers.com/showthread.php?t=725290
&
Here http://forum.xda-developers.com/showthread.php?t=698374

Does overclocking the phone kill your battery? I already only get two days of battery life.

Yes, I noticed decreased battery life with 710Mhz OC.

gromky said:
Does overclocking the phone kill your battery? I already only get two days of battery life.
Click to expand...
Click to collapse
I get three days with NRG ROM, but I have pretty light use. However with OC it is no worse than before.

Also using Energy ROM, have experimented overclocking at 650 MHz, and now 710 MHz for the past few days (based on suggestions in this tread, actually!). Haven't noticed a significant reduction in battery life. I get around 2 days also. 2 days has been pretty typical on the Rhodium for me, with the stock ROM and Energy, and moderate usage. Most comments on the main overclocking thread seem to indicate that battery life is not greatly reduced. Just anecdotal comments, of course. Don't think anyone has done any halfway scientific testing.

~8mA more during sleep
~40mA more during stress
That's why you don't notice a big difference during "normal usage". Try not to use the device for some days (I know it's hard ;D) with overclocking and without so you will notice the difference. Like I said in another thread: We do not measure the battery life while using the device - because this isn't measurable and doesn't give any reliable results.
It's like the percent battery driver - any clever person should notice that this cannot be described as precise.

Im using 787MHz dynamic oc with no problem at all. It doesnt seem to affect battery life either, but then again Im not using Sense.

Jackos said:
~8mA more during sleep
~40mA more during stress
That's why you don't notice a big difference during "normal usage". Try not to use the device for some days (I know it's hard ;D) with overclocking and without so you will notice the difference. Like I said in another thread: We do not measure the battery life while using the device - because this isn't measurable and doesn't give any reliable results.
It's like the percent battery driver - any clever person should notice that this cannot be described as precise.
Click to expand...
Click to collapse
I'm not exactly sure what point you are making. My observation is that with or without OC, the length of time my phone can be used before recharging is approximately the same, i.e., I don't detect any decrease in battery discharge.
Since my usage patterns are the same for both cases, this variable drops from the equation.

So, you need to run the program every time the phone boots? Or does the program remember its settings?

[Q] Decks or Cm7's best kernel (SVZ vs Tiamat vs Godmode)

Hi guys, i've been looking into many threads and reading a lot of posts and asking a lot of questions. however i know that their is not for sure answer to this but i would like to see what you guys believe to be your best kernel for battery and performance. i have seen people say it is Godmode (v9), Tiamat v4.1.0, Tiamat v3.3.7, and Savaged-zen v2.2.1. (ALL of these ARE with SBC-OFF). i just want to know what is you best kernel at the moment for your evo with decks or cm7.
Side Question: what is the difference between the governors: (Interactive, InteractiveX, Smartass, SmartassV2, Savaged-zen, and Lag Free)?
- Thank You

I like Tiamat 4.1.0, but I can't help you for your side question. I'm still new to development and rooting

kendallc123 said:
I like Tiamat 4.1.0, but I can't help you for your side question. I'm still new to development and rooting
Click to expand...
Click to collapse
i know you said your new but im just wondering have you tried any other kernels?
and what is your battery life with Tiamat 4.1.0

I've used damn near every kernel available for CM7. And by far the BEST kernel for battery life is Savaged Zen. I'm on a stock battery and it just seems to last forever. Add to that the fact that the battery lasts all day without sacrificing performance at all. Every phone is different and you may or may not see the same results. This is just what has worked for my phone. Honestly, your best bet is to get flash happy with various kernels until you find one that gives you the performance and battery life that you're looking for. By the way, I use SVZ Manager with my kernel so that I can toggle SBC on and off as I please. It's a nice apk that gives you some flexibility.
**CLICK HERE**

Green_Arrow said:
i know you said your new but im just wondering have you tried any other kernels?
and what is your battery life with Tiamat 4.1.0
Click to expand...
Click to collapse
I've tried Tiamat 4.0.8 and a Savaged Zen kernel (can't remember which version). They both gave me about 12 hours of battery life on an average day(for me). But an average day for me is going to school, so I'm not on my phone as much. I haven't gotten to really test the battery life because I haven't looked at it on the weekend when I'm not at school. But like Concordium said, every phone is different! Try them all!

Tiamat 3.3.7 sbc
Sent from my PC36100 using XDA App

Concordium said:
I've used damn near every kernel available for CM7. And by far the BEST kernel for battery life is Savaged Zen. I'm on a stock battery and it just seems to last forever. Add to that the fact that the battery lasts all day without sacrificing performance at all. Every phone is different and you may or may not see the same results. This is just what has worked for my phone. Honestly, your best bet is to get flash happy with various kernels until you find one that gives you the performance and battery life that you're looking for. By the way, I use SVZ Manager with my kernel so that I can toggle SBC on and off as I please. It's a nice apk that gives you some flexibility.
**CLICK HERE**
Click to expand...
Click to collapse
at the moment i am using the latest svz kernel with the svz manager as well. i have been flashing many kernels and for a while i was happy when i used the godmode kernel my phone lasted me 1 day and 6 hours, however he is no longer updating his kernels =( i'm hoping to find another kernel such as that one that will give me around the same results ^_^

Green_Arrow said:
at the moment i am using the latest svz kernel with the svz manager as well. i have been flashing many kernels and for a while i was happy when i used the godmode kernel my phone lasted me 1 day and 6 hours, however he is no longer updating his kernels =( i'm hoping to find another kernel such as that one that will give me around the same results ^_^
Click to expand...
Click to collapse
I liked Godmode. But it didn't seem to give me as good battery life as savaged zen has given me. Each phone is different though.

Concordium said:
I liked Godmode. But it didn't seem to give me as good battery life as savaged zen has given me. Each phone is different though.
Click to expand...
Click to collapse
well im testing this one out at the moment and it has given me so far 17 hours and 20 mins, still at 31% battery, im just not sure if it'll do better than godmode did, at the moment im running it on the smartass kernel and i ran godmode on interactive so maybe that is the prob... however another issue is i've heard that svz is no longer updating as well... do u know if this is true? and one random thing that only a few people have told me is that they run on performance and overclock their phone and get the best battery from it, is that possible or a lie?
Edit: it lasted 20 hours and 53 mins, so since it didn't do as good as GodMode did then im gonna try the tiamat 4.1.0 now cause it has first place in the poll atm.

Green_Arrow said:
well im testing this one out at the moment and it has given me so far 17 hours and 20 mins, still at 31% battery, im just not sure if it'll do better than godmode did, at the moment im running it on the smartass kernel and i ran godmode on interactive so maybe that is the prob... however another issue is i've heard that svz is no longer updating as well... do u know if this is true? and one random thing that only a few people have told me is that they run on performance and overclock their phone and get the best battery from it, is that possible or a lie?
Edit: it lasted 20 hours and 53 mins, so since it didn't do as good as GodMode did then im gonna try the tiamat 4.1.0 now cause it has first place in the poll atm.
Click to expand...
Click to collapse
Its true that its not being updated anymore. It sucks but I plan to ride it out as long as the kernel functions properly with CM. Once it starts screwing up then I'll switch.
Those who say they get the best battery life by overclocking and putting their phone on performance are full of crap. Performance governor is basically the polar opposite of Powersave. Performance keeps your cpu constantly running at a high frequency. Logic states that overclocking to 1.13 ghz and perpetually running at that frequency requires more power than running at 245 mhz. The more power required the less time your battery will stay alive. Powersave gives you best battery life but gives you crap performance. Interactive, Smartass, and Ondemand give you a balance of performance and battery life. Performance gives you the best performance but crap battery life.
By the way, do you really need a phone that can stay off the charger for more than 21 hours? :-x

Concordium said:
Its true that its not being updated anymore. It sucks but I plan to ride it out as long as the kernel functions properly with CM. Once it starts screwing up then I'll switch.
Those who say they get the best battery life by overclocking and putting their phone on performance are full of crap. Performance governor is basically the polar opposite of Powersave. Performance keeps your cpu constantly running at a high frequency. Logic states that overclocking to 1.13 ghz and perpetually running at that frequency requires more power than running at 245 mhz. The more power required the less time your battery will stay alive. Powersave gives you best battery life but gives you crap performance. Interactive, Smartass, and Ondemand give you a balance of performance and battery life. Performance gives you the best performance but crap battery life.
By the way, do you really need a phone that can stay off the charger for more than 21 hours? :-x
Click to expand...
Click to collapse
no i do not but! 3 days of the week im at school doing nothing for 8-10 hours so... i think if my phone can run longer than a day w/o charging then it mean i can play games on my phone while waiting and by the end of the day i'll still have battery. and does it make sense for someone to get better battery life on interactive than on smartass?

Green_Arrow said:
no i do not but! 3 days of the week im at school doing nothing for 8-10 hours so... i think if my phone can run longer than a day w/o charging then it mean i can play games on my phone while waiting and by the end of the day i'll still have battery. and does it make sense for someone to get better battery life on interactive than on smartass?
Click to expand...
Click to collapse
Well Smartass, as I've heard it described, is sort of like Interactive 2.0. It's basically the interactive governor but better. Unfortunately, I do not know enough of the exact specifics of the governors to tell you which SHOULD be getting better battery. I would just run each of those governors and see which one works better for you.
And I thought your phone already lasted 21 hours with a decent amount of usage. You need to test the governors/kernels in the exact situation you are going to be using the phone. Interactive, Ondemand, and Smartass would all manage the phone pretty much the same if you just leave it alone and let it sit till the battery drains. but they each manage the power allocation supplied to the cpu very differently during actual use. One ramps up the voltage quickly while one scales it up more gradually. So take your charger with you to school, in case you run into trouble, and use the phone as you believe you will be using it in the future. Then you'll have a more accurate idea of which setup works best for you.

Concordium said:
Well Smartass, as I've heard it described, is sort of like Interactive 2.0. It's basically the interactive governor but better. Unfortunately, I do not know enough of the exact specifics of the governors to tell you which SHOULD be getting better battery. I would just run each of those governors and see which one works better for you.
And I thought your phone already lasted 21 hours with a decent amount of usage. You need to test the governors/kernels in the exact situation you are going to be using the phone. Interactive, Ondemand, and Smartass would all manage the phone pretty much the same if you just leave it alone and let it sit till the battery drains. but they each manage the power allocation supplied to the cpu very differently during actual use. One ramps up the voltage quickly while one scales it up more gradually. So take your charger with you to school, in case you run into trouble, and use the phone as you believe you will be using it in the future. Then you'll have a more accurate idea of which setup works best for you.
Click to expand...
Click to collapse
just wondering what do you keep your cpu settings at: the governor, cpu min & max?

When I am plugged into my wall charger I keep it at 1113/245. I use Performance for benchmarking and testing since I don't need to worry about battery life and Smartass when doing everything else. For normal every day use I have it at 1036/245/Smartass, Interactive, or Ondemand. I don't really have a preference between the three governors since they all make my battery last more than long enough. So it usually comes down to whichever my clumsy finger happens to accidentally select first. If I happen to not go home and need more life then I'll drop to 729/245/Conservative or Powersave. I use conservative if I still need to be able to use the phone a bit and powersave if I want my phone to just sit there and look pretty till I get back home.

Concordium said:
When I am plugged into my wall charger I keep it at 1113/245. I use Performance for benchmarking and testing since I don't need to worry about battery life and Smartass when doing everything else. For normal every day use I have it at 1036/245/Smartass, Interactive, or Ondemand. I don't really have a preference between the three governors since they all make my battery last more than long enough. So it usually comes down to whichever my clumsy finger happens to accidentally select first. If I happen to not go home and need more life then I'll drop to 729/245/Conservative or Powersave. I use conservative if I still need to be able to use the phone a bit and powersave if I want my phone to just sit there and look pretty till I get back home.
Click to expand...
Click to collapse
why is ur lowest 245 and not 128? sorry if im bugging you

Green_Arrow said:
why is ur lowest 245 and not 128? sorry if im bugging you
Click to expand...
Click to collapse
You're not bugging me man. This place exists so people can ask questions and get help.
I keep my min at 245 because I've read, in multiple places, that allowing it to go any lower is not something your cpu really appreciates. Just like there is such thing as too high with your clock speed there is also a too low. And everywhere I have seen 245 is the preferred low end. I am not 100% sure as to why but I would assume that it is because your cpu needs at least a certain amount of power to run the basic processes required to keep your phone functional. Similar to a computer. Lower the cpu too much and it just can't do what it needs to.

Concordium said:
You're not bugging me man. This place exists so people can ask questions and get help.
I keep my min at 245 because I've read, in multiple places, that allowing it to go any lower is not something your cpu really appreciates. Just like there is such thing as too high with your clock speed there is also a too low. And everywhere I have seen 245 is the preferred low end. I am not 100% sure as to why but I would assume that it is because your cpu needs at least a certain amount of power to run the basic processes required to keep your phone functional. Similar to a computer. Lower the cpu too much and it just can't do what it needs to.
Click to expand...
Click to collapse
i see do u happen to know of a good thread that talks about this? cause i keep mine at the lowest because i read that its better for battery life, but they never said anything about it being bad

Green_Arrow said:
i see do u happen to know of a good thread that talks about this? cause i keep mine at the lowest because i read that its better for battery life, but they never said anything about it being bad
Click to expand...
Click to collapse
I don't remember there being a thread dedicated to this. I just remember it from posts I saw within different OC/UV threads. Do a Google search for it and see if that returns any results. Like I said, I doubt you'll find a full dedicated thread. But you may be able to find the individual posts where it's mentioned.

Concordium said:
I don't remember there being a thread dedicated to this. I just remember it from posts I saw within different OC/UV threads. Do a Google search for it and see if that returns any results. Like I said, I doubt you'll find a full dedicated thread. But you may be able to find the individual posts where it's mentioned.
Click to expand...
Click to collapse
thank you, you have been really helpful ^_^

With Tiamat 4.1 and juicedefender I get the best battery performance and v6 supercharger I have a smooth screen with no problems or lag at all.

Ktoon's KT747 2/8/13 Kernel vs Task650's 2/10/13 Kernel

What are your guys' opinions on the performance of these two kernels? From what I've gathered it seems like KToon's kernel is meant for overclocking, but then what would one use task's for?
Task's recent update to his kernel makes me want to try it because I've been using KToon's kernel with the ktoonservative governer and row scheduler UV'ed a little bit but unlocked to 2.1GHz and have been having some pretty bad battery life in mu opinion, do you think switching to task's kernel would be better on the battery?
Well what do you guys think?

Fun Fact for the day. Versus threads get shut down in no time here on XDA.
P.S- Why wouldn't you just try it first before making a thread about it? Kernels take about 3 seconds to flash. Also. No one can tell you that you will get better battery life on one or the other considering all of the variables. We are all in different locations, use different apps, have different settings, and we all use our devices differently. You need to try them both out and see which one works better for YOUR device.

Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.

berryman13 said:
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
Click to expand...
Click to collapse
I'm not giving you are hard time. I'm just telling you the facts here. If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Which no one can tell you one is better than the other for. Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.

I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.

gilo123 said:
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.

task650 said:
If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
Click to expand...
Click to collapse
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
gilo123 said:
Ithey're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.

berryman13 said:
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Click to expand...
Click to collapse
He cannot answer this question honestly. He doesn't have your device. You're not understanding. He can have the best battery life possible on my kernel but if you use it, you could have the worst battery life possible. IT'S DEVICE DEPENDENT. Will you please just do yourself a favor and take 3 seconds, flash the kernel, and see. You say you've tried them both, but you are also asking about playing games and what not with them? You would know if you had tried them dude. Same goes for the governors & schedulers. You would also know that if you had actually tried them both. I need to ask you this. Why won't you just try them and see for yourself. Are you really the type of person to flash what people tell you to your expensive device?
Look dude. I'm only trying to help you here. I'm not quite sure why you wouldn't just take my advice here. I have quite a bit of experience with this stuff and I'm trying to help you get the best experience possible. But it seems as though you think that personal opinions of others are whats best for your device when in all reality they are not. Real life testing is what will prove to be best for your device. Trust me.

berryman13 said:
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
Click to expand...
Click to collapse
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app

liltitiz said:
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Comprehensive list. I like it. Now I gotta figure out which gov I'm gonna use when I flash the underwear kernel.
Thanks everybody for their input, if anyone else has anything to say then please go for it!
Wiping cache + dalvik and flashing underwear kernel then fixing permissions and rebooting and gonna take a look around performance control to see whats up.

task650 said:
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
Click to expand...
Click to collapse
Ohh Thnx man. While you're here any suggestions as to how I go about fixing/finding out which apps are responsible? Also,any combinations/settings you might recommend trying with your kernel,despite the phone dependent variables and what not. Thnx )

Running the underwear kernel today, changes frequencies min and max to the farthest it can go. Will report back with my results.
Sent from my SGH-I747 using xda app-developers app

Sorry man, but no need to report back here as it has already been stated that each User's experience will differ upon usage, apps, personal habits, planet alignment,... Boils down to a flash and see type thing.
Thread Closed
Here is some info on Governor and I/O schedulers. Obviously it isn't going to include Ktoonservative or ROW but you get the idea.

Has anyone tried intersectRaven's latest kernel?

I just installed this http://www.intersectraven.net/huawei-watch/ kernel so i have no stats to share. I was hoping someone else had some statistics on its performance and battery life. If not I will report back my experience.
Edit 1 - after 1 day no crashes and performance seems smooth. I didnt notice any better or worse battery but there seems to be less options for the CPU governor. When using powersave governor the battery life is pretty great but of course the UI struggles. The only governors available are userspace, performance, ondemand and powersave

..

MuF123 said:
Did you have any random reboots with skin's kernel?
Also - is there init.d support?
Thanks!
Click to expand...
Click to collapse
i got reboots from Skin's even after setting things as suggested throughout the thread. I do not see init'd mentioned in the change log for Intersect's but i'm not technical enough to say that it isn't there simply because of the change log. I'm also using his February 2nd version which isn't even listed on the link i placed above (you can find many versions by clicking the parent directory link).

not really a point in installing any custom kernel now since 6.0 is about to drop any day now.

Motawa88 said:
not really a point in installing any custom kernel now since 6.0 is about to drop any day now.
Click to expand...
Click to collapse
all about one's perspective. I can repsect that but i want better batter and performance every scond i have my watch and it literally take me less than minute to intall it so ill keep tinkering until it drops (could be weeks). Either way, id also like to know which dev to focus on when it does drop and this one seems to update pretty frequently so it may be likely that this one's is ready before Skin's. Ill try both though, you can count on that!!

mallman said:
all about one's perspective. I can repsect that but i want better batter and performance every scond i have my watch and it literally take me less than minute to intall it so ill keep tinkering until it drops (could be weeks). Either way, id also like to know which dev to focus on when it does drop and this one seems to update pretty frequently so it may be likely that this one's is ready before Skin's. Ill try both though, you can count on that!!
Click to expand...
Click to collapse
No. My point was that the custom kernel won't work after the update. I used invisible kernel the whole time but now I hate wait for 6.0 and hopefully the kernel will be updated.

..