Related
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
Yesterday I put the netarchy havs less kernel on my phone and with some stress testing and general testing found that it worked well at 1.15 mhz. I carried it around all day messing with it no problem. Today, the real test came when I ran GPS on my phone in my car. The phone lasted about 3 minutes of GPS before it started rebooting. Then my 4g was broke from it somehow. Anyhow, I restored my phone and all seems well now.
I still want to mod the voltage and clock speed. Any advice on this? The phone always gets hot when I use GPS because it uses a lot of processor, frequently its on the charger and possibly in sunlight. When it was not overclocked or undervolted my phone NEVER reboots not once since I've had it.
Is the problem the undervolting, overclocking or both? Should i give up on this due to the way I use my phone?
Thanks in advance.
Try different kernels. I use netarchy sbc 4.2.2 more havs, works great. I also use his 4.3.4 more havs sbc. They both work for me. Battery life is awesome and gps works good. No prob here. Try those out and see what happens. Hope this helps.
Sent from my HTC EVO Phone, should'nt we all have one?
Okay so is there any danger to this? It seems like every time my phone starts rebooting from overclocking or undervolting apps start disappearing from my phone and stuff stops working.
I use amon RA 2.3 and every time I recover it works again but I was just wondering how dangerous it is for me to experiment they way I have been. I have already recovered my phone 3 times from issues like this that broke it.
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.4 more havs, overclocked to 1190 and it's as stable as can be on my phone. However, if I go over 1190 it immediately locks up and reboots.
Sent from my HTC EVO 4G with Tapatalk
kd0axs said:
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.2 more havs, overclocked to 1190 and it's as stable as can be on my phone.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah but the reboots are hurting my phone! I have to restore it due to the problems the reboots and freezing causes (sometimes I have to battery pull due to full lockup). 2 times when I pulled battery due to full lockup apps went missing from phone memory but the available space on the phone was as if the apps were still there. Another time my 4g wouldn't turn on.
Is that abnormal? Can it mess up my phone in a way that recovering wont be able to fix or is recovering generally a sure shot?
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
gpz1100 said:
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
Click to expand...
Click to collapse
Because I use the 1-1-1 power management system (see sig) my main concern is performance. I love my phone and when I use it I want it to be fast and smooth. I would *prefer* if the extra speed didn't dramatically change my battery life but I'm okay with a small decrease in battery life if the speed gain is reasonable for the tradeoff. Anyhow I thought a lot of people ran HAVS along with overclocking to have both to a degree.
Only time I charge my battery is when I am using it in the car with my car charger. At home I charge all my batteries on an external charger - my phone is a mobile device I prefer to never be bound to a cord. I sleep with my phone next to me off the charger lol.
Okay so my phone is running more HAVS now and it seems the same as before so I guess my friend is HAVS friendly. I will run this for a day to check if any reboots happen and aim for tomorrow to overclock again. It may have been the 1.19 mhz that caused the issue. I will drop it down to 1.15 or 1.1 and see if its stable.
Hey there XDA, got a question for ya.
I've had my AT&T S3 for a while now and I love the phone a lot, the only thing that is plaguing me is the battery life.
Now for a phone with dual core processors, a nice Super AMOLED screen that runs at 720, all the connections that you'd ever want, I expect it to use some battery life, but I feel like I should be doing better than I should.
When I'm browsing the internet or reddit I can watch the percentage just slowly crawl down. Within 30 min or so I've gone through 7-8% I want to say. Not 100% sure, but the numbers have been enough to make me concerned.
Currently I am running Diet ICS 08.08.12 with no major modifications other than the apps I use and Apex Launcher.
I've got my BetterBatteryStats dump and a screenshots of the battery page from System from last night. I'm attempting to use Juice Defender today (I've tried it in the past and it did alright) as well as Samgsung's battery saving mode (which seems to prevent the processor from going over 1.0 Ghz), which as of right now I'm at 36%. I feel like I can do better than that
So, thoughts? Opinions?
What kernel are you running?
mdg071191 said:
What kernel are you running?
Click to expand...
Click to collapse
I don't think Diet ICS swapped kernels, so stock as far as I'm concerned.
Alright. For stock kernel (I'm not too sure about with power saving), those numbers are fairly decent. I was able to get some better numbers on faux123's TW kernel (the 1.65ghz, not 1.85), but I can't be too sure of the exact time, as I'm currently on 1.85ghz OC, and I charge my phone nightly. You could try other kernels, and just roll back with a nandroid to this one if you do not like the difference.
As a noob I'm realizing I might have gotten pretty lucky. I've never rooted a phone (and probably won't - can't live without it if it bricks!) but I successfully rooted my Kindle on the first try and have been fooling around with various ROMs and have had only seemingly trivial issues. I started with Android Open Kang Project - otter - milestone 6. I can't even remember now the particulars of what I didn't like about it but I quickly switched to CM10 Jelly Bean with SG17 enhancements [linaro]. I liked it but had some instability with 20120916 so installed 20120920 which has been more stable for me so far. I also installed the UNOFFICIAL CM10 +3.x kernel for kindle fire but switched back alley because it didn't have a tablet UI (so odd since it's a build specifically for the kindle - did I overlook the setting???]
So my questions are:
How lucky have I been? Should I look for an older totally stable ROM and stick with it or even go back to stock?
If I do decide to continue experimenting what level of risk is it really to look for the ROM that I like - e.g. tablet UI, pretty basic, quick - vs looking solely for something rock solid.
Finally, what advice for a noob on what to look for and how to test various ROMs and any thoughts on your favorite for the Fire and why.
BTW, I also tried eye candy and did not care for it. In fact I'm irritated that my twrp was sort of hijacked with an eye candy mod and I can't figure out how to get it off. Have not loaded jandycane but want to because I can. Pushing that luck?
Sent from my Amazon Kindle Fire using xda app-developers app
I wanted to edit typos and add that use GO Launcher EX so the launcher features of the ROM are irrelevant. Don't see an edit option...
Sent from my Amazon Kindle Fire using xda app-developers app
Running custom roms are not for everyone. They normally come with some needed trouble shooting. As long as you do your needed research before hand you will be fine but there is always a risk when rewritting the OS on any device. Be it cellphone, tablet or PC.
No one will be able to tell you what is the best for your device. Its a flash and test yourself type of thing
Sent from my SGH-I777 using Tapatalk 2
sharonbw said:
As a noob I'm realizing I might have gotten pretty lucky. I've never rooted a phone (and probably won't - can't live without it if it bricks!) but I successfully rooted my Kindle on the first try and have been fooling around with various ROMs and have had only seemingly trivial issues. I started with Android Open Kang Project - otter - milestone 6. I can't even remember now the particulars of what I didn't like about it but I quickly switched to CM10 Jelly Bean with SG17 enhancements [linaro]. I liked it but had some instability with 20120916 so installed 20120920 which has been more stable for me so far. I also installed the UNOFFICIAL CM10 +3.x kernel for kindle fire but switched back alley because it didn't have a tablet UI (so odd since it's a build specifically for the kindle - did I overlook the setting???]
So my questions are:
How lucky have I been? Should I look for an older totally stable ROM and stick with it or even go back to stock?
If I do decide to continue experimenting what level of risk is it really to look for the ROM that I like - e.g. tablet UI, pretty basic, quick - vs looking solely for something rock solid.
Finally, what advice for a noob on what to look for and how to test various ROMs and any thoughts on your favorite for the Fire and why.
BTW, I also tried eye candy and did not care for it. In fact I'm irritated that my twrp was sort of hijacked with an eye candy mod and I can't figure out how to get it off. Have not loaded jandycane but want to because I can. Pushing that luck?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Rooting and installing ROMs may not be everyone's forte, but there is nothing to fear if you've done every step correctly. Many of these CM builds are nightly builds; that is they release one every short interval of time fixing small bugs encountered in the previous release. If you really want to enjoy CM, you could go for the latest stable build.
To your first question: Yeah, switch back to an older ROM. That's generally more stable and you have the whole thread to sort through if you get into some tough spot. You've been pretty lucky to have gotten so far without bricking your device, I must say. I don't recommend reverting back to stock; you'd miss a lot of the features that aren't there on the KF.
To your second one: that's totally up to you. I confess, I don't own a KF, but with the phones I've had, I've always been experimenting with them. My old Moto Razr, my Moto Ming, my Nokia 5800, my Nokia N8...the list goes on. Changing ROMs, it's kind of like an hobby of mine.
You could lean towards a better UI( I really like the one on stock KF though) or a rock solid feature rich performance ROM. It's up to you.
As to your third question: I can't really answer that sorry. I'm a Galaxy Tab user, so I don't know much about KFs. As to testing ROMs, well, you said it. Test them. There's no other way to know if you're going to like them or not otherwise.
Yes, install Jandycane. It's not pushing your luck. There's no room for error unless you're so excited that you even make silly mistakes.
You can modify posts by tapping on it, selecting Modify, then edit.
Hope I helped you some.
One ****ing minute! - Billie Joe Armstrong at iHeartRadio Music Fest 2012
It's not luck if u spent time reading n following the rooting tutorial, it's ur work, though small compared to developers. I'm exactly like u, 1st time ever use an android device, but with experience with my Nokia5800, it's easier for me to solve problems, not to panic when rooting a device .
For me, keep rooting different Roms until the most suitable for personal use is enough. As time passes, I feel tired of doing the setting again after installing every new Rom. I stick with twa 's Linaro 'til now.
I think the risk of experimenting new Rom is small because the device memory is very hard to malfunction. As long as ur PC and KF is there, u don't have to worry.
There's still a lot to learn abt android, not only rooting, I think. Right now I'm learning about OTG and how to use external devices with KF, like flash drive or microphone.
All credits and thanks to our developers such as hashcode and twa.
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the replies. I did go ahead and play around wiping and installing new ROMs starting with going back to stock all the way through pretty much the same sequence I did before with the same result LOL! I ended right back here with tw_priv's CM10. I like it very much and other than some random burps and glitches I've experienced - things others have also seen (Facebook - keyboard not opening; sleep of death - multiple times; WWF is totally messed up but that might be 100% zynga), its been pretty darn stable.
My biggest issue is that my battery life sucks! Anyone want to advise me on how to analyze/improve that?
I love reading here and learning but I'll never be a dev or even a power user. Do the dev of custom ROMs even want people like me to use them? This site is definitely not user friendly ha ha
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
Thanks for the replies. I did go ahead and play around wiping and installing new ROMs starting with going back to stock all the way through pretty much the same sequence I did before with the same result LOL! I ended right back here with tw_priv's CM10. I like it very much and other than some random burps and glitches I've experienced - things others have also seen (Facebook - keyboard not opening; sleep of death - multiple times; WWF is totally messed up but that might be 100% zynga), its been pretty darn stable.
My biggest issue is that my battery life sucks! Anyone want to advise me on how to analyze/improve that?
I love reading here and learning but I'll never be a dev or even a power user. Do the dev of custom ROMs even want people like me to use them? This site is definitely not user friendly ha ha
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
That's what you get for a $200 tablet sorry. You could look around your device forum asking for prop.build tweak that optimize battery life.
You'll understand all the big dev terms sooner or later. Its just a matter of time.
Sent from my GT-S5360 using Tapatalk 2
zelendel said:
Running custom roms are not for everyone. They normally come with some needed trouble shooting. As long as you do your needed research before hand you will be fine but there is always a risk when rewritting the OS on any device. Be it cellphone, tablet or PC.
No one will be able to tell you what is the best for your device. Its a flash and test yourself type of thing
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I know this is off topic, I'm sorry. But I don't see any risk with rewriting the OS of a PC versus a Phone. A Phone has a rom chip that is fairly easy to break. By unplugging the device during rooting, for example. But on a PC, if something goes wrong, you can always stick the disc in and try again.
On topic, with custom roms you will always run into stability issues. However, if you do not care about the latest and greatest, try a rom based on CM7. They are stable (in use for years on different devices)
x10knight said:
I know this is off topic, I'm sorry. But I don't see any risk with rewriting the OS of a PC versus a Phone. A Phone has a rom chip that is fairly easy to break. By unplugging the device during rooting, for example. But on a PC, if something goes wrong, you can always stick the disc in and try again.
On topic, with custom roms you will always run into stability issues. However, if you do not care about the latest and greatest, try a rom based on CM7. They are stable (in use for years on different devices)
Click to expand...
Click to collapse
There are many things that could go wrong when rewritting the OS on your PC that could make that not an option.
Sent from Arkham
My battery life (which wasn't terrible "cheap" tablet or not - this is the kindle fire forum, right?) got worse after I rooted it and flashed custom ROM. I had hoped it would get better since that seems to be something all the devs are after. I was hoping someone could point out settings I may not have adjusted correctly after installing. Or would that be too easy?
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
My battery life (which wasn't terrible "cheap" tablet or not - this is the kindle fire forum, right?) got worse after I rooted it and flashed custom ROM. I had hoped it would get better since that seems to be something all the devs are after. I was hoping someone could point out settings I may not have adjusted correctly after installing. Or would that be too easy?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Yes, it is the KF forum. You could try underclocking the device. That way, less CPU and more battery. If you could point out your current ROM, I'll take a deeper look and help you out.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
Yes, it is the KF forum. You could try underclocking the device. That way, less CPU and more battery. If you could point out your current ROM, I'll take a deeper look and help you out.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
I appreciate the offer! This is the first rooted device I've had. I don't really know what underclocking is but would like to learn. I'm using twa_priv's ROM 20120923 (I think - maybe 25)
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
I appreciate the offer! This is the first rooted device I've had. I don't really know what underclocking is but would like to learn. I'm using twa_priv's ROM 20120923 (I think - maybe 25)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
CM9 and CM10 roms (the one you are using is CM10) tend to have worse battery life than other ROMs. It's kind of a trade-off, worse battery for more functionality. If you want really great battery life, you could use one of the old CM7 roms. They'll likely have the best overall battery life, but won't be quite as fancy/snappy as the newer ROMs would be.
Aesrys said:
CM9 and CM10 roms (the one you are using is CM10) tend to have worse battery life than other ROMs. It's kind of a trade-off, worse battery for more functionality. If you want really great battery life, you could use one of the old CM7 roms. They'll likely have the best overall battery life, but won't be quite as fancy/snappy as the newer ROMs would be.
Click to expand...
Click to collapse
Yes, that's true.
@OP underclocking means that you simply set the CPU to operate at a give frequency. It doesn't go more than that. My Android tablet has an Intel Core i3-350M 2.26 GHz processor. Average battery life is around an hour; but then when I underclock it to 800MHz, I get close to five hours.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
Yes, that's true.
@OP underclocking means that you simply set the CPU to operate at a give frequency. It doesn't go more than that. My Android tablet has an Intel Core i3-350M 2.26 GHz processor. Average battery life is around an hour; but then when I underclock it to 800MHz, I get close to five hours.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
I have some issues w/ sleep of death. I saw a post that suggested doubling minimum CPU frequency. Is that underclocking or overclocking or neither??
Clock data: min 300 Max 1200 current 300
CPU - whatever comes in the kindle fire. :8
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
I have some issues w/ sleep of death. I saw a post that suggested doubling minimum CPU frequency. Is that underclocking or overclocking or neither??
Clock data: min 300 Max 1200 current 300
CPU - whatever comes in the kindle fire. :8
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
You're at 300 MHz? Wow! That's way too slow! I even wonder how you get most of the jobs done. You're underclocking the device. If you're having Sleep of death issues, then increase the frequency to about 600 MHz. That should take care of it. Also, that won't eat up much battery, so you should be safe. But, as suggested, you should switch to older CM7 ROMs as they have excellent battery backup.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
You're at 300 MHz? Wow! That's way too slow! I even wonder how you get most of the jobs done. You're underclocking the device. If you're having Sleep of death issues, then increase the frequency to about 600 MHz. That should take care of it. Also, that won't eat up much battery, so you should be safe. But, as suggested, you should switch to older CM7 ROMs as they have excellent battery backup.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
The KF on stock ROM operates between 400-800 MHz. It is set that low on all Custom ROMs, whatever the device may be (That is, if they have their own kernel). There is no normal frequency. It's like a car. You go in third gear or fourth gear as you wish. There are no steadfast rules that you have to go in fourth gear on a road and the fifth in another. CPU governors are how you set the frequencies. I don't know what you get on the KF, but on the other devices that I have tried, "Blackcats" is the one for day-day usage. Not too much, not too less.
Yes, that's the thing about having a fancy ROM. I have a completely transparent ROM on my Galaxy Y and sometimes, the thing goes bonkers. Since my phone doesn't have CM yet, these fancy transparent ROMs are the best bet for a flashy and beautiful ROM. On stock, I get around 1-2 days, but on these transparent ROMs, I get like 5-6 hours a day. Not too bad, considering that my completely transparent W7 laptop only stays for an hour on battery.
Sent from my asus_laptop using Tapatalk 2
sharonbw said:
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I honestly don't think your SOD (sleep of death) is due to the 300 Min frequency. I've had that set on any recent KF rom I've used without a problem (as mentioned previously, it tends to be the default value, with max being 1000 or 1200 (don't remember the exact value). It's more likely that something you have installed, or some setting that has been changed, is causing the problem.
One way to find out would be to do a complete wipe of the system in TWRP (factory reset, system, cache, and dalvik) and install whatever ROM you're interested in fresh (don't forget to install gapps too) and then see if you continue to have the SOD problems. Stick with stock settings for a while and see if something happens. Just my two cents of course.
Aesrys said:
I honestly don't think your SOD (sleep of death) is due to the 300 Min frequency. I've had that set on any recent KF rom I've used without a problem (as mentioned previously, it tends to be the default value, with max being 1000 or 1200 (don't remember the exact value). It's more likely that something you have installed, or some setting that has been changed, is causing the problem.
One way to find out would be to do a complete wipe of the system in TWRP (factory reset, system, cache, and dalvik) and install whatever ROM you're interested in fresh (don't forget to install gapps too) and then see if you continue to have the SOD problems. Stick with stock settings for a while and see if something happens. Just my two cents of course.
Click to expand...
Click to collapse
It's too early to know for sure but no SoD since I upped it. I've done clean several installs and i've had it since the first iteration using twa_priv's CM10. I'm currently running 20120923.
I'm still a little unclear on what clocking is but I guess that's a deficit in my knowledge of physics.
UPDATE: Well came back to my kindle after watching tv and it was in the SoD. Force power off and reboot and I'm back in business. I'll leave the clock speed at min 300 since I didn't notice any difference.
I'm going to do a search but anyone want to give me a link to a 'how to' for doing a logcat? (Is that even the right term? ) I don't know that the developers want to hear from me but I could at least post the log when I experience SoD.
Edit: nevermind. I found how to logcat.
Sent from my Galaxy Nexus using xda app-developers app
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.