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

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.

Discussion of battery life after linux 3.4 upgrade

It seems that in general battery life has taken a hit for those on a 4.2.2 ROM with the new 3.4 kernel, though the extent of the difference varies. For me personally, I used to get <1.5% per hour drain at idle. After the 3.4 upgrade, with NO other changes, I get around 4% per hour. When I view the BBS stats the number of wakelocks/alarms don't really seem all that different, so it looks like the 3.4 kernel just uses more juice to do the same amount of work. Undervolting doesn't seem to help much, if at all.
I've brought this up in other threads but it wasn't very productive, so I figured it might be worth it's own thread. Does anyone have any idea what exactly might be causing the increased drain? Has anyone figured out and tips/tricks for getting back to 3.0 level battery usage?

What rom/release and 3.4 kernel/release are you using? Which ones have you tried?

Same thing
I am seeing the same thing as you. I use to get really good battery life during standby and now it isn't very good. However, some time (for a couple of hours) it will be back to what it used to be (i can see the slope in battery usage flattens out), but then it just goes back to being crap.
I hope somebody can offer some help...

xBeerdroiDx said:
What rom/release and 3.4 kernel/release are you using? Which ones have you tried?
Click to expand...
Click to collapse
I've tried pretty much every release of task's AOKP both with and without Ktoonsez's kernel. Battery drain has been about the same with both kernels.

I am on task and ktoonsez latest. I average 24-30 hours of battery life with 4 or more hours of screen time.

Change your governor and scheduler. Those can make a huge difference. I prefer on demand, you should experiment with each scheduler. Maybe try one scheduler each day
Sent from my SGH-I747 using Tapatalk 2

Franky_V said:
Change your governor and scheduler. Those can make a huge difference. I prefer on demand, you should experiment with each scheduler. Maybe try one scheduler each day
Click to expand...
Click to collapse
I use ktoonservative. It's hard to believe that any of the others would significantly increase my battery life, but I suppose it's worth a shot...

Have you tried JuiceDefender
JD really works for me.

Overclocking of LG G4

Hi everybody,
I want to know if we can overclock our Snapdragon 808 to 2GHz (ARM A72 cores) with a modified kernel.
Also, If somebody is going to work on this challenge.
Thanks!!

Androsesp said:
Hi everybody,
I want to know if we can overclock our Snapdragon 808 to 2GHz (ARM A72 cores) with a modified kernel.
Also, If somebody is going to work on this challenge.
Thanks!!
Click to expand...
Click to collapse
A57 cluster, probably yes. I'm also working on a kernel, but I intensely dislike Overclocking because it isn't all that useful. The key to performance is with optimisation, not with raw power. So I'm most likely not going to include it, sorry.

What about underclocking and/or undervolting?
I think performance is good enough as it is, but would like to get better battery life.

I would like to be able to undervolt in order to relieve the bugging high temp warning. This phone rarely uses max performance. So, overclocking is not really a priority. Maybe a custom hotplug.

Crappy cpu. No point messing with it.
Sent from my A0001

GUGUITOMTG4 said:
I would like to be able to undervolt in order to relieve the bugging high temp warning. This phone rarely uses max performance. So, overclocking is not really a priority. Maybe a custom hotplug.
Click to expand...
Click to collapse
Hotplugging has been dropped not long ago. You'd basically need to reinvent it. Plus it costs more power than it would save

And what about undervolting to prevent excessive heat, @mythos234?

yea i guess undervolting is the only benefit here coz 2 ghz wont be hard to achieve but getting that overheating msg sooner aint worth it...
next thing u know is accessory back plates with mini fans to keep the phone cool...
seriously tho what good is the extra power for ? the phone is already fast with the correct setup (not that i saw any lag when it was stock)

anyone knows how to see the cpu binning in this phone?

oile said:
And what about undervolting to prevent excessive heat, @mythos234?
Click to expand...
Click to collapse
Excessive Heat?

mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
A number of people have gotten over-temperature messages, sometimes with the phones even shutting down.
This has been reported with using navigation, I believe, and I know people have reported it when shooting video. High screen brightness is likely a contributor. But there are examples of the phones running too warm.
Personally, I'd be more interested in cooler running, and longer battery life, rather than increased peak performance. So underclocking, if anything.

Well, the overclocking is not necessary, but is an opportunity to know the limits of the chipset. Moreover, with it we could know if we can make undervolting to our phones and make it more battery efficient with an underclocking kernel, when we need it.

RedOCtobyr said:
A number of people have gotten over-temperature messages, sometimes with the phones even shutting down.
This has been reported with using navigation, I believe, and I know people have reported it when shooting video. High screen brightness is likely a contributor. But there are examples of the phones running too warm.
Personally, I'd be more interested in cooler running, and longer battery life, rather than increased peak performance. So underclocking, if anything.
Click to expand...
Click to collapse
Happens to me too when gaming. The problem I observe is that Indeed, it is not excessive heat. But LG thinks otherwise.
You can actually underclock using Kernel Auditor and disable cores. Unless you meant Undervolting.

mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
Wanna check out periscope and comment back ? Atleast I know that app will push the phone to its limits.
Sent from my LG-H818 using XDA Free mobile app

Currently using Kernel Adiutor to disable both A57 cores and the phone screen does not heat up like before... Battery life has improved from what i saw yersterday. Continuing testing today. Only problem i have is the damn phone will enable one of the A57 cores after a while which i dont like. I need my settings to stick.
Any Kernel Dev know which files are causing this? Tab 3 had something like this but a couple of files changed solved the non sticking settings on cpu.
Overclocking/underclocking sure but just disabling cores would work for most.
Sent from my LG-H815 using Tapatalk

mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
lol, you're funny.

marcadam said:
lol, you're funny.
Click to expand...
Click to collapse
I haven't had any popups or heat related reboots, so I was wondering what the matter is here.
On every phone I see complaints over heat so I wondered if something is to it here or if it's the usual. And if there are overheating warnings and shutdowns, then there might be indeed something in the bush.

Try charging your phone in the car whilst using google maps to get to an important meeting, and then take a call just for good measure............and boom, there you have your own little meltdown.

marcadam said:
Try charging your phone in the car whilst using google maps to get to an important meeting, and then take a call just for good measure............and boom, there you have your own little meltdown.
Click to expand...
Click to collapse
That happens on every phone I ever had though. It's advised to not use a device while charging at all, so if you stress it to 120% while charging, of course it heats up..

@mythos234 is a pleasure to have you here (speaking as xiaomi mi2s owner too xD)
What Temps do you reach using cpu intensive apps?

Poor battery life amnd heat with cyanogenmod and

When navigating Google maps my device gets fairly hot to the touch.
I am running cyanogenmod nightly with greenify to keep background apps down
In the past CM was always better battery life and lower temps. Has this changed? How do I get the best battery life out of my device? Flash another kernel? Go back to stock? Do I have a hardware problem?
Also my battery does not report 4900 mah in battery apps when fully charged. Any idea about this?
Thanks in advance!

Cyanogenmod cant take exynos octa and gets hot i had that issue couldnt fix had to go back to stock

rookie12 said:
Cyanogenmod cant take exynos octa and gets hot i had that issue couldnt fix had to go back to stock
Click to expand...
Click to collapse
So I may have solved my problem. I think you're right Cyanogenmod might not have a good setting for this CPU. Idownloaded kernel auiditor and switched to power save mode and underclocked the CPU and now I am getting ridiculously good battery life!
Loving this little tablet again.

berardi said:
So I may have solved my problem. I think you're right Cyanogenmod might not have a good setting for this CPU. Idownloaded kernel auiditor and switched to power save mode and underclocked the CPU and now I am getting ridiculously good battery life!
Loving this little tablet again.
Click to expand...
Click to collapse
can you share the steps and your settings?

berardi said:
So I may have solved my problem. I think you're right Cyanogenmod might not have a good setting for this CPU. Idownloaded kernel auiditor and switched to power save mode and underclocked the CPU and now I am getting ridiculously good battery life!
Loving this little tablet again.
Click to expand...
Click to collapse
Yea mate can you share

SayWhat10 said:
can you share the steps and your settings?
Click to expand...
Click to collapse
rookie12 said:
Yea mate can you share
Click to expand...
Click to collapse
Sorry guys been busy.
So I am still on CM 12.1 nightly and getting good battery life now. Below is what I found helps:
1. Underclock and change CPU governor. This tablet haa 4 codes I believe 1900 mhz each. This is really overkill for most tasks. Your preference may vary for responsiveness, but I have settled on around 300-500mhz per CPU for my purposes. If you play games you can set profiles and turn up the CPU for those games if you like.
2. Install xposed framework - this is kind of a prerequisite for amplify and greenify
3. Install and configure greenify - this makes your apps chill and not use too much battery
4. Install and configure amplify - manages your wake locks and alarms so as not to drain battery
5. Install , tweak gravity box how you like it.
I think the biggest difference for me is the underclocking .. My tablet doesn't get hot when navigating anymore. I really couldn't deal with that because I'm thinking about the battery inside getting fried with heat. The other programs just add bonus battery and memory

This is interesting. I had also been on CM 12.1 and it was working pretty smoothly except the tablet at times got too hot to hold in your hand. It was also completely useless as a daily driver s it gave me max 2hrs screen on time (instead of 6.5 hrs) and for some reason it would take half a day to recharge the battery. Overall, not really very usable. I am now back on stock and took forever to unload all the samsung junk, optimize wakelocks etc, covert to F2FS etc. It is working OK now, but still nowhere near as smooth as CM12.1 was running on it before. Too bad because I love this tablet especially the fact I can just put my second sim card in and make phone calls etc (T705)
Can you maybe share what sort of general battery life you are really getting with the setup your described?
Clocking the CPU down to a 1/4 of the normal maximum speed seems very drastic, is it at all usable after?
Thanks!