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
im not sure what to do at this point. the title says it all. i have already reflashed ive tried wiping cache and dalvik. i have tried both tiamat and savaged zen. ive tried different cpu governors. i just dont know what to do. my phone is running like complete crap and it randomly reboots.
a little history, i had the phone overclocked to 1.19ghz for all of 2 days and saw no inrease or decrease in percormance so i went back to 998mhz. the phone still ran just fine. last week i decided to attempt a undervolt. i got as low as 825mv before having issues, so to be safe i kept it @ 850mv. now it ran just fine for a few days but i started having issues with more cpu intese apps so i removed vipermod all together after setting voltage back to stock. thats where i am now. my phone has gotten worse and worse and worse and im just not sure what it is.
You can unroot it and run a RUU on it, taking it completely back to stock. If it's acting up with stock everything, then it must be a hardware problem. I would try that.
Lol I don't mess with over clocking . You can spank your phone. If its still doing that after you flash a regular ROM with the stock kernel then it is spanked. Best thing is wipe everything go to a ROM like cm7 run it stock no over clocking and see.
spencer88 said:
You can unroot it and run a RUU on it, taking it completely back to stock. If it's acting up with stock everything, then it must be a hardware problem. I would try that.
Click to expand...
Click to collapse
i have no idea what that means. ill have to look it up.
as far as the phone being overclocked im not to worried about it causing any damage. simply because increasing the clock freq wont cause damage unless it over heats. and i made sure it got nowhere near overheatig. the only way to damage a cpu by overclocking is to overvolt which i have never done. correct me if im wrong. not only that but the phone ran just fine overclocked and for a week after being set back to stock. i didnt start having issues until i tried undervolting. but that could cause any damage that i know of. however my experience is with overclockig computers not phones.
also i dont want to mislead youguys and make it seems like its worse than it really is. my phone is completely usable, its just sluggish and reboots randomly. im posting this on my phone right now.
I have three evo's two are box stock and one is rooted, and is running cyanogen mod 7 kernel and rom.
The problem is the linpak and quadrant score on the modified evo are actually lower than the stock evo. For example the stock evo is doing a linpak of 30 while my modified evo is only doing about 21. Likewise my quadrant score tends to be pretty low. I have to clock my modified evo to the max to pass the stock evo.
What gives why is my evo overclocked to 1.13 with custom kernel and rom slower? I set the profile to performance.
A while back while using the tiamat kernel I set my overclock to 1.2 and the phone just froze and shutdown did I damage the phone. This happened several times because it kept on rebooting. Today I set the clock 1.190 and the phone froze and shutdown again. Right now I am running the Cyanogen Kernel and no issues so far but why is my phone so slow. Both evos don't have much apps at all only one or two(excluding the stock sprint apps on the stock evo)
Thanks for your help
so what do u need to overclock ur phone for? does it dial faster? can u talk and hear phone calls faster? does it ring faster? I don't understand????
I forgot to mention that on quadrant my modified evo ranks below evo 2.2+ on that quadrant score chart. Is my phone defective?
{ParanoiA} said:
so what do u need to overclock ur phone for? does it dial faster? can u talk and hear phone calls faster? does it ring faster? I don't understand????
Click to expand...
Click to collapse
I'm just curious and want to learn more. Why do you guys overclock?
I see people avg's with my my current setting are around 40. Im thinking defective phone.
Should I flash the stock rom back on and un-root and bring the phone back?
rebooted the phone and now the score is just getting crazy low 6.509 mflops
Overclocking an EVO doesn't really do all that much. It's only 200 MHz more.
Desperately need help the touch screen doesnt work and this was all the sudden
Overclocking can cause some instability, like the locked-up screen. Pull the battery and wipe cache and dalvik.
And benchmarks aren't worth anything, they can be easily tricked. Real-world usage matters. Personally, I underclock for more battery
Sent from my PC36100 using XDA Premium App
Search the general section for supercharge script. Go to first thread and then go to original thread linked in there. Follow steps and dl update8. Run it as explained. Enjoy ur extremely faster phone. It changes memory management and stuff
Thanks for your helps guys.
Tropicalbrit your right. I really forgot the point of the phone is to see how well it works daily. In all reality I love my evo even though its not getting a high score. I was mainly just curious to see if I damaged my processor from overclocking and crashing.
I booted into recovery and used CW and booted back into a copy of sense I had. I did that linpak test again a was suprised to see how it scored 31. That's higher than CM7! So does this mean my processor is not damaged?
I will eventually go back to CM7 because I love all the effects and battery life was extended significantly. I should just probably stick with the stock kernel.
Thanks for all your help guys
I may try that supercharge script soon though if its safe.
Littleazn248 said:
I have three evo's two are box stock and one is rooted, and is running cyanogen mod 7 kernel and rom.
The problem is the linpak and quadrant score on the modified evo are actually lower than the stock evo. For example the stock evo is doing a linpak of 30 while my modified evo is only doing about 21. Likewise my quadrant score tends to be pretty low. I have to clock my modified evo to the max to pass the stock evo.
What gives why is my evo overclocked to 1.13 with custom kernel and rom slower? I set the profile to performance.
A while back while using the tiamat kernel I set my overclock to 1.2 and the phone just froze and shutdown did I damage the phone. This happened several times because it kept on rebooting. Today I set the clock 1.190 and the phone froze and shutdown again. Right now I am running the Cyanogen Kernel and no issues so far but why is my phone so slow. Both evos don't have much apps at all only one or two(excluding the stock sprint apps on the stock evo)
Thanks for your help
Click to expand...
Click to collapse
You are running a governor which down clocks the processor. Quadrant does not tax the processor enough to hit your Max CPU speed. Set min and Max to 998 and test again. Try performance(for best results) or interactive/ondemand governers. You can change the settings in the CyanogenMod settings/ performance/ CPU settings menu.
Sent from my PC36100 using XDA Premium App
Overclocking a phone doesnt do much other then cause over heating. If someone can give me a good reason to overclock I will gladly change my opinion.
Stock is set to optimal performance. IE HTC has performance tested the phone on this ROM and has proven no ill effects.
Custom ROMS are works in progress they have a lot of benefits and for some, are exactly what they are looking for.
tnerb123 said:
Overclocking a phone doesnt do much other then cause over heating. If someone can give me a good reason to overclock I will gladly change my opinion.
Stock is set to optimal performance. IE HTC has performance tested the phone on this ROM and has proven no ill effects.
Custom ROMS are works in progress they have a lot of benefits and for some, are exactly what they are looking for.
Click to expand...
Click to collapse
Opinions r like assholes. And I don't agree with the way urs smells
Well, to sum things up, my phone has never been so slow and laggy ever since flashing Faux's ultimate kernel (v0.0.6u). (Not blaming anyone other than myself, just sayin)... Anyway, I have the feeling something internal went horribly wrong. Seeing that no other kernel other than Faux's ultimate had GPU turbo boost @ 320/220Mhz, I thought it would be nice to try it out with BeastMod 4.2. After using OC Daemon to set my CPU gov to ONDEMAND and stock clock speeds, I did the usual and tested the rom throughout the day. Battery live was insanely awful. The phone seemed to draining at a rate comparable to using YouTube on 4G, EVEN WHEN THE SCREEN WAS OFF!. Oh, and it got pretty warm, not hot, but noticeably warmer than usual. Knowing I would not be able to flash a new rom/kernel till later that day, I simply shut my phone off for the time being. When I got home, I discovered the problem. Even after switching back to... let's say Bullet w/ Juggernaut, I noticed that scrolling through anything, playing a game, running a benchmark (especially this one), caused the phone to slow down, hiccup, pause, lag, whatever you want to call it. In Quadrant, the fps for the 2d test was hitting high 20's before, and now, it jumps about the teens goes as low as 8fps. Score: 1801...2130... Am I running a dual core? Not anymore it seems... Feels like the second I touch my phone, thermal protection kicks in or something else is choking it and preventing my phone from being smooth like it used to be. Even tried underclocking to sensation speeds (1188). No help at all. Still craps out on me. I'm beginning to think I fried something inside. Broken Adreno? Hope not... Any ideas?
Note: Yes, I followed all ROM and kernel flashing procedures. I may be a noob (literally), but I do know how to flash properly.
Maybe try a factory reset and Odin back to stock to start from scratch.
Sent from my SGH-T989 using xda premium
Exodian said:
Maybe try a factory reset and Odin back to stock to start from scratch.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I'll give it a shot. Hoping Christmas Eve is lucky this year.
Running EL29 Odexed Blue Rom with EL26 stock kernal.
Just came from eVo 4G and have no idea if its worth it and if so what setting.
Any advice would be appreciated.
Sent from my SPH-D710 using XDA App
I've not done the undervolting yet but I'm thinking about it just still reading on what I want to do. I did however do the overclocks for a few days and imo only I really saw no need for it from the stock settings so I just went back to normal. The phone is fast enough for me even playing games that extra 1-2-3-400 mhz really didn't show that much of a difference.
Again this is my opinion others see the need for it I just didn't.
cidica said:
I've not done the undervolting yet but I'm thinking about it just still reading on what I want to do. I did however do the overclocks for a few days and imo only I really saw no need for it from the stock settings so I just went back to normal. The phone is fast enough for me even playing games that extra 1-2-3-400 mhz really didn't show that much of a difference.
Again this is my opinion others see the need for it I just didn't.
Click to expand...
Click to collapse
Thanks for you're opinion. Let me know how the undervolting goes if you decide to do it.. I wonder if vipermod would work with this device. I had it with my evo and it was pretty easy to use.
feelingnerdi said:
Thanks for you're opinion. Let me know how the undervolting goes if you decide to do it.. I wonder if vipermod would work with this device. I had it with my evo and it was pretty easy to use.
Click to expand...
Click to collapse
I think viper mad some stuff for the phone. I know he has a rom out for the phone already so maybe his tweaks are there you could always check the dev section.
My phone had freezing issues at anything higher than 1.4ghz, but even then the only real difference I saw was quadrant scores. Games ran the same, in fact I think the UI actually was choppier when OC'ed. Never really looked into it much though.
I don't even know why I tried it in the first place, I never said to myself "gee, this could be faster.." I guess coming from an HTC Hero it was a habit.
this phone does NOT need to be over clocked; it is so much faster than your Evo, that you won't believe it!
Undervolting and under clocking can give you extra battery life; do a search on the Dev thread, and you will learn lots about it..