Related
I have upgraded my Galaxy W to Jelly Bean using Custom Room (4.2.2) Cyanogenmod 10.1 alpha 2. maybe later alpha 3.
Everything runs well. but why my phone's battery drains so fast? and please help me HOW TO SOLVE IT AND MAKE IT LAST LONG TIME???
THANKS VERY MUCH....
Backup your apps, factory reset your phone. If battery drain problem persists, install Greenify or deep Sleep battery saver from Google Play to better manage battery resources.
Lim Wee Huat said:
Backup your apps, factory reset your phone. If battery drain problem persists, install Greenify or deep Sleep battery saver from Google Play to better manage battery resources.
Click to expand...
Click to collapse
Thank you for your suggestion... I will try....
Electro Tobib Muhajir said:
Thank you for your suggestion... I will try....
Click to expand...
Click to collapse
when you just flashed the battery will definitely be shorter. Let it recharge for a few cycles before determining whether its good or bad battery life. Keep in mind however that even at full potential, the battery will not last for more than 2 days even at light usage.
if battery life is more important to you compared to "the newest OS" and whatever extra features it brings with it, then I highly recommend installing acro's CM9 RC2 (yes it is ICS) as the 2.x.x kernel is far better at battery life than 3.x.x (i'm currently testing it and I can already feel the difference! I believe I can reach 2.5 days at modest usage but I will have to update you on that after my first few discharge cycle for battery to reach potential after flashing new rom). I do, however notice a few annoyances with RC2 (not sure if its really the ROM, or the custom kernel i'm using, or Nova Launcher is to be blamed), so if it continues to bug me I may just switch back out to latest ICS =p.
If keeping with the latest JB is important for u, best thing you could do is download a custom kernel for it that supports UV(undervolting), then get IncrediControl and tune down your UV based on some voltage tables you can find in FAQ. This alone won't bring you a HUGE improvement in battery life but its definitely an observable difference. On top of UV, try to UC(underclock) your CPU to 1GHz. Most daily functions, apps and games (depending on how intensive it is) will work perfectly smooth even at 1GHz. IMO, the most important point of UCing is you will notice a very significant difference in the heat of your battery (ie backcover of your phone). Heat is generally bad for the battery (shorter life + faster draining) so UC is definitely a good thing to do =). Of course, on top of all those, get greenify and wakelock detector(WLD) from market to control your not-so-frequently-used apps. Use WLD to track down what is keeping your phone awake (hence drain more battery) and use greenify to hibernate all the not-so-frequently-used apps you have (example of things you DON'T want to greenify: whatsapp and gmail as you don't want to kill these 2 programs when you lock your screen. You want to continue receiving whatsapp messages and gmail when you locked your screen right? XD! Examples of things you SHOULD greenify: games, music player. Maybe some of the games or other apps may keep a background service active, secretly using your battery even though the last time you used it was 2 days ago!)
Finally, if your wonder is about 1-1.5 years old, chances are your battery is already bloated (perhaps you can feel your battery through the backcover of your phone even!) A bloated battery is a dangerous and short-capacity battery. Even with the best rom you may only push through a day from 100-0%. If your battery still looks fine but your phone is nearing its birthday, go ahead and do some online shopping (ebay or local equivalent, like malaysia we have Lelong.com.my) and get a battery for your phone. Its usually much cheaper than buying from telephone shops.
EDIT: Adding on to all of that, choosing a good governor+i/o scheduler combo is important as well. If our phone is similar with the S+, smartassv2+sio(i've used this, its quite smooth and battery is good) OR OnDemand+noop is thought to be very good in terms of battery life and responsiveness. Lulzactive is also very good but its not so easy to tune it so i usually would stay away from it. Do bear in mind that although the former 2 combo is good, it still highly depends on how you use your phone so there will not be a universally best governor+io combo. Both of those suggested by me are supposingly best in responsiveness as well as deepsleep battery conserving (only if the assumption that our roms work the same as the roms tested in S+, which MAY NOT be true).
TL;DR? try smartassv2+sio (u may change this using IncrediControl, get from playstore). Then if you are not satisfied with your current performance/battery life, you may continue experimenting by changing governor and i/o scheduler one at a time. If you are doing the testing, make sure to have some way to record your tests if not you will 100% be deceived by placebo!(with actual numbers you will clearly see whether your feeling is placebo or if there really is an improvement)
I'm having some seeeeerious battery issues with alpha3. With just 15 minutes screen usage in a day, battery settings says my screen used up more than 20% of the battery! This just for consulting the time and the weather.
oribunokiyuusou said:
I'm having some seeeeerious battery issues with alpha3. With just 15 minutes screen usage in a day, battery settings says my screen used up more than 20% of the battery! This just for consulting the time and the weather.
Click to expand...
Click to collapse
Sounds like your battery is bloated. Can u show me a screenshot of your battery graph and app usage?
oribunokiyuusou said:
I'm having some seeeeerious battery issues with alpha3. With just 15 minutes screen usage in a day, battery settings says my screen used up more than 20% of the battery! This just for consulting the time and the weather.
Click to expand...
Click to collapse
that 20% is not actually the 20% of the battery juice. It is 20% of whatever amount of battery is drained due to the display being ON. Like if your battery is used from 100% to 90%, then only 2% is used by the display.
I am not sure if I could explain what I mean.
EDIT: Hmmm maybe I misunderstood what you said... If that is the case, disregard.
And also my galaxy W will use all of its battery charge when the display is constantly ON for about 3-5 hours.
Actually, I've figured out what it was. It was Google Now. Chewing away at the battery without saying a word anywhere in the battery screen. I am now back to my old 3 days battery.
you need to install cpu spay from google play and you need look deep sleep time.
this reaction is typical if your coming from a stock or at least cm9.
there has been a lot of arguments about battery life of cm10 and above.
in my opinion, there really is a difference, i mean cm10+ drains battery faster.
and the reason being is of course the features there is in cm10++.
if you're after battery life, stay with stock or cm9 (for now).
but if you feel like your in with cm10+ and you don't want to go back like me, then may want to try these tricks:
1) using Titanium Backup, freeze the apps that you don't really use.
- in my phone i froze pico tts, voice search, talk back, etc. (i even froze google search )
2) i use an app called "autostarts", it can disable auto starting of app including those of the system.
- in my phone, i disabled google maps in every activity. ex. after startup, connectivity changed, wifi connected, widget updating
3) disable system settings which also contribute to battery draining.
- disable location service when your not using it
- disable automatic backup/restore
- disable haptic feedback
- disable autosync
- disable the top battery drainers when not in use (wifi, mobile data, gps, bluetooth)
- and many more just explore
4) do not use so many widgets (my home screen has 0 widget)
5) do not use live wallpaper
6) charge only using the original charger, not from other phone/brand, not from a usb port
- the best way to charge is to avoid using the phone until it's fully charged
7) finally, install only apps that you really need. just keep a backup of your not so often used apps and install only when you need them
If you think about it, everything i wrote above contradicts with the original concept of Android.
But that's life, sometimes you have to trade something in order to achieve another.
Our phone was baked as Gingerbread, now we want to make it taste like Jellybean.
We have all the ingredients, but we don't have a jelly bean pan to make the candy molds.
So we improvise, we work around, we do some shortcuts, we make alternatives, certainly it will cost something.
egagah said:
when you just flashed the battery will definitely be shorter. Let it recharge for a few cycles before determining whether its good or bad battery life. Keep in mind however that even at full potential, the battery will not last for more than 2 days even at light usage.
if battery life is more important to you compared to "the newest OS" and whatever extra features it brings with it, then I highly recommend installing acro's CM9 RC2 (yes it is ICS) as the 2.x.x kernel is far better at battery life than 3.x.x (i'm currently testing it and I can already feel the difference! I believe I can reach 2.5 days at modest usage but I will have to update you on that after my first few discharge cycle for battery to reach potential after flashing new rom). I do, however notice a few annoyances with RC2 (not sure if its really the ROM, or the custom kernel i'm using, or Nova Launcher is to be blamed), so if it continues to bug me I may just switch back out to latest ICS =p.
If keeping with the latest JB is important for u, best thing you could do is download a custom kernel for it that supports UV(undervolting), then get IncrediControl and tune down your UV based on some voltage tables you can find in FAQ. This alone won't bring you a HUGE improvement in battery life but its definitely an observable difference. On top of UV, try to UC(underclock) your CPU to 1GHz. Most daily functions, apps and games (depending on how intensive it is) will work perfectly smooth even at 1GHz. IMO, the most important point of UCing is you will notice a very significant difference in the heat of your battery (ie backcover of your phone). Heat is generally bad for the battery (shorter life + faster draining) so UC is definitely a good thing to do =). Of course, on top of all those, get greenify and wakelock detector(WLD) from market to control your not-so-frequently-used apps. Use WLD to track down what is keeping your phone awake (hence drain more battery) and use greenify to hibernate all the not-so-frequently-used apps you have (example of things you DON'T want to greenify: whatsapp and gmail as you don't want to kill these 2 programs when you lock your screen. You want to continue receiving whatsapp messages and gmail when you locked your screen right? XD! Examples of things you SHOULD greenify: games, music player. Maybe some of the games or other apps may keep a background service active, secretly using your battery even though the last time you used it was 2 days ago!)
Finally, if your wonder is about 1-1.5 years old, chances are your battery is already bloated (perhaps you can feel your battery through the backcover of your phone even!) A bloated battery is a dangerous and short-capacity battery. Even with the best rom you may only push through a day from 100-0%. If your battery still looks fine but your phone is nearing its birthday, go ahead and do some online shopping (ebay or local equivalent, like malaysia we have Lelong.com.my) and get a battery for your phone. Its usually much cheaper than buying from telephone shops.
EDIT: Adding on to all of that, choosing a good governor+i/o scheduler combo is important as well. If our phone is similar with the S+, smartassv2+sio(i've used this, its quite smooth and battery is good) OR OnDemand+noop is thought to be very good in terms of battery life and responsiveness. Lulzactive is also very good but its not so easy to tune it so i usually would stay away from it. Do bear in mind that although the former 2 combo is good, it still highly depends on how you use your phone so there will not be a universally best governor+io combo. Both of those suggested by me are supposingly best in responsiveness as well as deepsleep battery conserving (only if the assumption that our roms work the same as the roms tested in S+, which MAY NOT be true).
TL;DR? try smartassv2+sio (u may change this using IncrediControl, get from playstore). Then if you are not satisfied with your current performance/battery life, you may continue experimenting by changing governor and i/o scheduler one at a time. If you are doing the testing, make sure to have some way to record your tests if not you will 100% be deceived by placebo!(with actual numbers you will clearly see whether your feeling is placebo or if there really is an improvement)
Click to expand...
Click to collapse
thanks a lot. that's very helpful for me..
klacenas said:
this reaction is typical if your coming from a stock or at least cm9.
there has been a lot of arguments about battery life of cm10 and above.
in my opinion, there really is a difference, i mean cm10+ drains battery faster.
and the reason being is of course the features there is in cm10++.
if you're after battery life, stay with stock or cm9 (for now).
but if you feel like your in with cm10+ and you don't want to go back like me, then may want to try these tricks:
1) using Titanium Backup, freeze the apps that you don't really use.
- in my phone i froze pico tts, voice search, talk back, etc. (i even froze google search )
2) i use an app called "autostarts", it can disable auto starting of app including those of the system.
- in my phone, i disabled google maps in every activity. ex. after startup, connectivity changed, wifi connected, widget updating
3) disable system settings which also contribute to battery draining.
- disable location service when your not using it
- disable automatic backup/restore
- disable haptic feedback
- disable autosync
- disable the top battery drainers when not in use (wifi, mobile data, gps, bluetooth)
- and many more just explore
4) do not use so many widgets (my home screen has 0 widget)
5) do not use live wallpaper
6) charge only using the original charger, not from other phone/brand, not from a usb port
- the best way to charge is to avoid using the phone until it's fully charged
7) finally, install only apps that you really need. just keep a backup of your not so often used apps and install only when you need them
If you think about it, everything i wrote above contradicts with the original concept of Android.
But that's life, sometimes you have to trade something in order to achieve another.
Our phone was baked as Gingerbread, now we want to make it taste like Jellybean.
We have all the ingredients, but we don't have a jelly bean pan to make the candy molds.
So we improvise, we work around, we do some shortcuts, we make alternatives, certainly it will cost something.
Click to expand...
Click to collapse
yups...nice suggestion... thanks very much...:good::good::good:
Lim Wee Huat said:
Backup your apps, factory reset your phone. If battery drain problem persists, install Greenify or deep Sleep battery saver from Google Play to better manage battery resources.
Click to expand...
Click to collapse
THANKS...
oribunokiyuusou said:
I'm having some seeeeerious battery issues with alpha3. With just 15 minutes screen usage in a day, battery settings says my screen used up more than 20% of the battery! This just for consulting the time and the weather.
Click to expand...
Click to collapse
me too.... more than 20%, whereas my battery is in sleep screen and in the lowest brightness
Me too
Sent from my GT-I8150 using xda app-developers app
smeone here is right about cm9 rc2 i just flashed it and used a while.. battery seems to be 2x longer than 4.4 kitkat
here is there link
http://mygalaxywonder.blogspot.sg/2012/09/cyanogenmod-9-cm9-alpha-build-8-for.html
Magpir said:
smeone here is right about cm9 rc2 i just flashed it and used a while.. battery seems to be 2x longer than 4.4 kitkat
here is there link
http://mygalaxywonder.blogspot.sg/2012/09/cyanogenmod-9-cm9-alpha-build-8-for.html
Click to expand...
Click to collapse
No....no....no....
That link will redirect you to a website that has kanged Arco's hard work and NOT given due credit....
Here is the correct, original link....
http://forum.xda-developers.com/showthread.php?t=1576874
........right here on XDA...
This might be my S2, or it might be my W...but it's definitely CM
Hi,
since a week I have the rom on my xperia pro. It is very fast, no problems. Only bad battery life. I use the kernel from the zip, 3.4.62-nAa+ [email protected] Sep 26 2013.
Can you help me? Which 4.2 or 4.3 ROM is much better in battery life? Which kernel can I use with this roms?
Accu consumtion shows 55% display. The brightness is on minimum, like 15-20%, backlight for buttons off, backlight for keys 25%. Is this a true treshold (55%)? on my stock rom is was 5 - 10%.
Is there a principiell difference between speed/battery-life on 4.1/4.2/4.3 android versions?
Can I change kernel (I know how to install) without news rom installation or wipe all/data/factory? should I delete dalvik cache? Is it enough?
thanks a lot! I hope you hae tipps for better rom AND battery life
best regards
samu
Same problem here
I'm sorry, i can't give a solution,
furthermore i am looking myself for a reason.
I have exactly the same problem with my MK16i, same CM-Version since about a week.
With a maximum use of approx 20 minutes a day, the battery hardly lasts 24h!
What is this? I see no "big" background processes running. Display : 35-40%, hibernation/ idle: 35-40%.
As if something is working in the background to make me insane!
samu91 said:
Hi,
since a week I have the rom on my xperia pro. It is very fast, no problems. Only bad battery life. I use the kernel from the zip, 3.4.62-nAa+ [email protected] Sep 26 2013.
Can you help me? Which 4.2 or 4.3 ROM is much better in battery life? Which kernel can I use with this roms?
Accu consumtion shows 55% display. The brightness is on minimum, like 15-20%, backlight for buttons off, backlight for keys 25%. Is this a true treshold (55%)? on my stock rom is was 5 - 10%.
Is there a principiell difference between speed/battery-life on 4.1/4.2/4.3 android versions?
Can I change kernel (I know how to install) without news rom installation or wipe all/data/factory? should I delete dalvik cache? Is it enough?
thanks a lot! I hope you hae tipps for better rom AND battery life
best regards
samu
Click to expand...
Click to collapse
1. Please don't compare ROMs for battery life, test them out yourself as comparing of ROM is not allowed.
2. Either use kernel in ROM zip(img file) or Raven's Dark Kernel. No other kernel will work with CM10.1
3. You can change kernel without flashing a new ROM, but the kernel must be compatible with the ROM or it will not run.
4. To save battery life, turn off your data connection when not in use, dim the brightness of the display, kill all background processes.etc. Please search for ways to save battery life.
paccocino said:
I'm sorry, i can't give a solution,
furthermore i am looking myself for a reason.
I have exactly the same problem with my MK16i, same CM-Version since about a week.
With a maximum use of approx 20 minutes a day, the battery hardly lasts 24h!
What is this? I see no "big" background processes running. Display : 35-40%, hibernation/ idle: 35-40%.
As if something is working in the background to make me insane!
Click to expand...
Click to collapse
If you have root, use greenify.
僕のLT18iから送られてきた
CM10.1
I use cm10.1 LegacyXperia with the darkKernel and with the Nova Launcher. Actualy I think this is best combination für performance, battery life and stability. I tryed beansteak 4.2, 4.3, LegaxyXperia 10.2 and others.
Please Try and tell us your opinion
I'm trying to improve the performance, battery life, and stability of my phone. A few days ago, I found out about Android Tweaker 2. I use the auto tweaker and tasker profile features and am wondering if they would conflict with Greenify if I were to install it.
My auto tweaker is set to balance performance with battery life, and to only use safe tweaks. My tasker profile is set to hard (aggressive RAM management values) with persistence on boot. Note that "tasker profile" here has nothing to do with the Tasker automation app. By "tasker profile," Android Tweaker means multitasking profile.
I have not changed anything in the system tweaker, OTA tweaker, app manager, smart actions, or multitasking sections.
Would this setup conflict with Greenify, or would I probably be okay using both? I'd like to try Greenify so that I can increase my battery life. Thank you.
Well, I went ahead and did it (installed Greenify and set it up) and as far as I can tell my phone is working fine. It's much less laggy, and so far Greenify has cut my battery usage in half. That's with heavy usage too- a lot of screen on time tweaking things.
Between Android Tweaker, Greenify, Nova Launcher (more lightweight than Trebuchet), zipaligned apps, smartassv2, 1.3GHz overclock, some Xposed modules, uninstallation of unused system apps and custom ROM apps, and better use of widgets and quick settings, I think I may have made my phone far less frustrating than it use to be. Time will tell, but I may actually be able to enjoy it now. Maybe I don't need new phone after all.
I wouldn't think so. Greenifys sole purpose is to minimize background data use of apps when in idle. I've ran both exposed and android tweaker 2 which is the new version and didn't see any issues until android tweaker 2 started force closing with certain tweaks but with bit still being in the beta stage that's normal for a few issues. Only issues u may probably have will be in exposed itself cuz the sources have only been tested on 4.2 ROMs even tho they will work on any jellybean ROM. Hope this was of some help to you and if so feel free to hit the thanks button
Here is updated Thermanager, which could be flashed in recovery. I have made some changes after I played Asphalt game for about one hour. With this update, on performance governor the temperature never went higher than 58. And we are talking 1 hour straight. I doubt you can have that on stock. What was interesting that performance governor produced less heat than interactive, which supports my claim that when cpu jumps frequencies, it creates additional overhead.
Now, regarding myths and fiction about stock rom not overheating. There are some dudes on this forum who complain that their Z1 overheats to 70+ on custom roms when they play their beloved games; on stock, they say, there is no overheating.
Here is a short answer. You, guys, don't know what you are talking about.
Custom roms (and custom kernels) give you tools that are not available in stock. You just have to learn how to read/use them. Here is one example: some roms allow you to have internal cpu temperature on screen. Now that you have it, you watch. When it hits 70, you panic, but if you touch the back door, it will be barely warm. So, when you are on stock and without temperature reading, you think your phone is not overheating, while it can still have 65-70.
I used a modified version of M5 kernel compiled with GCC 5.2.1 Ubertc; CPU at 2457; performance governor, inteliplug balance with touch boost disabled; GPU overclocked to 600 with msm-adreno-tz idle wait 30 and workload 3; swapiness 10; enthropy 1024 read/write. That was on DU rom, but I bet the result would be the same on Jaguar and some other custom roms.
lol, that dude is Me, and I will try this, in the stock rom I can see an process running as overheat manager or something, I think it might have to do something with it. I'm sure that my device got heated very much, I didn't meant to offense but you seems to got it wrong. btw I will try this. I use Jaguar atm.
Thanks
I don't think that my phone won't reach 60 C on stock, but I like watching YouTube, so I can see how fast it warms. (I have xposed module that shows me cpu temp even on stock). And as much as I can say my phone warms faster on custom roms than on stock. No matter what governor I use.
Also all animations (like status bar showing) are kind of laggy on custom roms. I don't know it it got better in past 2 months, but last time I used custom rom my phone reached 50C even only with chrome.
Interesting thing is that this all (including animations) is not present on 3.10 kernel, but there are no usable roms at the moment with 3.10 kernel, so I have to use stock.
SuperLamic said:
I don't think that my phone won't reach 60 C on stock, but I like watching YouTube, so I can see how fast it warms. (I have xposed module that shows me cpu temp even on stock). And as much as I can say my phone warms faster on custom roms than on stock. No matter what governor I use.
Also all animations (like status bar showing) are kind of laggy on custom roms. I don't know it it got better in past 2 months, but last time I used custom rom my phone reached 50C even only with chrome.
Interesting thing is that this all (including animations) is not present on 3.10 kernel, but there are no usable roms at the moment with 3.10 kernel, so I have to use stock.
Click to expand...
Click to collapse
So, what's the temperature your xposed module shows on stock under stress?
optimumpro said:
So, what's the temperature your xposed module shows on stock under stress?
Click to expand...
Click to collapse
Usually after 20-30 minutes of YouTube it's around 53-54°C
SuperLamic said:
Usually after 20-30 minutes of YouTube it's around 53-54°C
Click to expand...
Click to collapse
Which browser or is it a youtube app? I have similar temps on Firefox and about 44-48 when using Chromium (not chrome).
ScatteredHell said:
lol, that dude is Me, and I will try this, in the stock rom I can see an process running as overheat manager or something, I think it might have to do something with it. I'm sure that my device got heated very much, I didn't meant to offense but you seems to got it wrong. btw I will try this. I use Jaguar atm.
Thanks
Click to expand...
Click to collapse
Overheat manager: whatever it is, all it does is throttling and thermanager does the same on custom roms. So, the trick is to throttle enough without you noticing any lags...
optimumpro said:
Which browser or is it a youtube app? I have similar temps on Firefox and about 44-48 when using Chromium (not chrome).
Click to expand...
Click to collapse
It's a YouTube app. Really? It's weird, maybe I'll try, but I can see the difference on battery time when I come home from school - on stock I have ~70% and on custom roms I have ~50. Anyway I'll try and report after few days.
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
SuperLamic said:
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
Click to expand...
Click to collapse
OK. Nice to hear that about battery life and overheating. With regard to lagging: it is not cpu, but rather animations. Either disable them completely in developer options or in DU you can go to tweaks and pick and choose whatever animation you want. I just disable all animations and have absolutely no lag.
SuperLamic said:
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
Click to expand...
Click to collapse
Oddly enough, I find custom ROMs hae smoother animations than stock, in my phone. But I don't have good battery life when compared to stock..
I want to know how to disable CPU cores to save power. It was possible on my nexus 5. but on my nexus 6p and now on my htc 10, I'm not sure if it's possible. I read that it's would need a kernel rewrite or something along those lines.
So does anyone know how to do this? I'm running latest LeeDroid ROM if that helps. thanks :good:
That's what I also wanted to know about the 10.
I had the mind before and there I could run with only one core, if not needed the other three cores. But if I needed power, the 4 cores are running.
It would be great, if there is an option in kernel settings to run all the cores only if they are really needed.
So the 10 is only a battery eater... Especially with sense roms I don't come through the day without charging.
On CM 14 or AOSP the battery is much more better, but with better core management it would be famous.
anyone got any info on this?
less cores doesn't mean better battery life, look at u11, "octa-core" and getting better battery life than 10 and anything else. it's een like if you have less cores, the cores which are online have to do all the work and might end up with locked max freq which will result in heat and more drain. so just keep the core control like it is and maybe just underclock
drago10029 said:
I want to know how to disable CPU cores to save power. It was possible on my nexus 5. but on my nexus 6p and now on my htc 10, I'm not sure if it's possible. I read that it's would need a kernel rewrite or something along those lines.
So does anyone know how to do this? I'm running latest LeeDroid ROM if that helps. thanks :good:
Click to expand...
Click to collapse
It is possible to disable cores with the custom kernel, and I believe force them to remain off at boot, but the HTC 10 uses a big/little cluster CPU setup and disabling cores isn't how you want to conserve power in my humble opinion.
The HTC 10 and some other modern devices uses BIG.little core ARM processor technology.
So the hardware and software is optimized to use all the cores to chase the best battery life and performance. I'm guessing that unless it's very specific usage scenarios, if you manage to force disable the cores with a custom kernel, you'll see both performance and battery life drop.
I would highly recommend installing a custom kernel, and tweaking the kernel settings while letting the hardware make full use of the BIG.little cluster system for efficiency. For high performance, I'd recommend one of the sense based kernel's that uses the HTC PnP Manager system. Something like Flar's ElementalX or TBalden's cleanslate kernel.
For battery efficiency, since you're really wanting to customize things for the best efficiency and battery life, try out the Helix kernel, by zeroinfinity. It's using a technology to optimize control of the processor based on "EAS" technology. EAS stands for "Energy Aware Scheduling" and zeroinfinity has written his "Helix Engine" to control the power profiles and thus power consumption of different apps, and you can customize the profiles to put any other apps you have in the profiles you want them.
This was a very basic and non technical summary, you can find tons of info on the kernels in the OP of each kernel thread. I would recommend making a backup with TWRP and trying both ElementalX and Helix kernels and seeing what works best in your usage scenario, before you start trying to force disable cores.
Here's a quick article I found on google, I'm at work and only briefly skimmed it, so no promises it's any good, but you can google BIG.little procs on Android mobile devices to find more imformation. https://community.arm.com/processors/b/blog/posts/ten-things-to-know-about-big-little
CharliesTheMan said:
It is possible to disable cores with the custom kernel, and I believe force them to remain off at boot, but the HTC 10 uses a big/little cluster CPU setup and disabling cores isn't how you want to conserve power in my humble opinion.
The HTC 10 and some other modern devices uses BIG.little core ARM processor technology.
So the hardware and software is optimized to use all the cores to chase the best battery life and performance. I'm guessing that unless it's very specific usage scenarios, if you manage to force disable the cores with a custom kernel, you'll see both performance and battery life drop.
I would highly recommend installing a custom kernel, and tweaking the kernel settings while letting the hardware make full use of the BIG.little cluster system for efficiency. For high performance, I'd recommend one of the sense based kernel's that uses the HTC PnP Manager system. Something like Flar's ElementalX or TBalden's cleanslate kernel.
For battery efficiency, since you're really wanting to customize things for the best efficiency and battery life, try out the Helix kernel, by zeroinfinity. It's using a technology to optimize control of the processor based on "EAS" technology. EAS stands for "Energy Aware Scheduling" and zeroinfinity has written his "Helix Engine" to control the power profiles and thus power consumption of different apps, and you can customize the profiles to put any other apps you have in the profiles you want them.
This was a very basic and non technical summary, you can find tons of info on the kernels in the OP of each kernel thread. I would recommend making a backup with TWRP and trying both ElementalX and Helix kernels and seeing what works best in your usage scenario, before you start trying to force disable cores.
Here's a quick article I found on google, I'm at work and only briefly skimmed it, so no promises it's any good, but you can google BIG.little procs on Android mobile devices to find more imformation. https://community.arm.com/processors/b/blog/posts/ten-things-to-know-about-big-little
Click to expand...
Click to collapse
was a good read, thanks! based on the quote from below from that website sounds like the little cores can drive the most battery savings the most .... which is my goal.
The LITTLE cores can be implemented to target lower leakage and a more moderate performance point, independently from the physical implementation of the big cores that are often tuned for higher frequency.
Click to expand...
Click to collapse
and seeing that you were a tester for helix htc 10 kernel, is it designed to with stock based ROM or just any magisk based ROMs? I did see that ASOP is not supported.
drago10029 said:
was a good read, thanks! based on the quote from below from that website sounds like the little cores can drive the most battery savings the most .... which is my goal.
and seeing that you were a tester for helix htc 10 kernel, is it designed to with stock based ROM or just any magisk based ROMs? I did see that ASOP is not supported.
Click to expand...
Click to collapse
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
CharliesTheMan said:
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
magisk version works same as the version which writes to system
CharliesTheMan said:
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Great I also use supersu not magisk, probably same old school thing...also too tough getting things to play nice with magisk IMO. So for supersu do i just install v012 r1 systemless kernel and it should just work w/ leedoird? did you notice any functions on lee droid not working?
also do you underclock? recommend any kernel managers?
drago10029 said:
Great I also use supersu not magisk, probably same old school thing...also too tough getting things to play nice with magisk IMO. So for supersu do i just install v012 r1 systemless kernel and it should just work w/ leedoird? did you notice any functions on lee droid not working?
also do you underclock? recommend any kernel managers?
Click to expand...
Click to collapse
It's version 17, you'll download it from this post https://forum.xda-developers.com/showpost.php?p=73068312&postcount=1216 , sorry that link you had shouldn't be there, but systemless is the magisk version but now there's only one version, and the Aroma installer will let you choose the normal non-magisk version.
In the installer, there's a question that asks about installing custom scripts, I use the @ZeroInfinity script, the one from @roger81 and @TotallyAnxious are good too so you can't really go wrong, but I recommend starting with zero's, and you can reflash to experiment once you get going good with it. Rogers is great for battery life but his is a little more custom and extreme, which is why I'd start.
I use EXKM kernel manager, but I really recommend not changing many settings at first. Definitely leave the governor default with this kernel. I would run it like it comes out of the box, and see how your apps and battery life goes, and if you have apps causing a lot of drainage, maybe add them to the helix engine profiles before you start changing clock speeds.
You'll notice with EXKM the core frequencies reported in real time will look different from how it looks with a stock based kernel, but don't let that scare you.
My only other recommendation is if you use any other power saving apps like greenify or doze (I don't use any of them personally but some do) I would first get used to the kernel without them, so you kind of have a better idea of baseline.
CharliesTheMan said:
It's version 17, you'll download it from this post https://forum.xda-developers.com/showpost.php?p=73068312&postcount=1216 , sorry that link you had shouldn't be there, but systemless is the magisk version but now there's only one version, and the Aroma installer will let you choose the normal non-magisk version.
In the installer, there's a question that asks about installing custom scripts, I use the @ZeroInfinity script, the one from @roger81 and @TotallyAnxious are good too so you can't really go wrong, but I recommend starting with zero's, and you can reflash to experiment once you get going good with it. Rogers is great for battery life but his is a little more custom and extreme, which is why I'd start.
I use EXKM kernel manager, but I really recommend not changing many settings at first. Definitely leave the governor default with this kernel. I would run it like it comes out of the box, and see how your apps and battery life goes, and if you have apps causing a lot of drainage, maybe add them to the helix engine profiles before you start changing clock speeds.
You'll notice with EXKM the core frequencies reported in real time will look different from how it looks with a stock based kernel, but don't let that scare you.
My only other recommendation is if you use any other power saving apps like greenify or doze (I don't use any of them personally but some do) I would first get used to the kernel without them, so you kind of have a better idea of baseline.
Click to expand...
Click to collapse
Bonus points for being the least confusing AROMA installer I have used! and I used zero's as well. thanks for all your help! and one last thing.. isn't doze built into android nougat? or am I highly misinformed.
drago10029 said:
Bonus points for being the least confusing AROMA installer I have used! and I used zero's as well. thanks for all your help! and one last thing.. isn't doze built into android nougat? or am I highly misinformed.
Click to expand...
Click to collapse
It is you're correct, but there's a lot of "super doze" and dozingest doze around" sort of mods and tweaks people use, it's the extra modified stuff I would avoid for now, until baseline is established. However once you get things ironed out, @RogerF81 (if I spelled that Right) has tons of good info on further tweaking. He once tweaked his battery life to something like 7 or 8 hours screen on time with the Helix EAS kernel. That's just showing off.
Glad you like the Aroma installer, it nearly killed the poor dev trying to get it set up when he first started implementing it, he still probably throws keyboards if I ask for a black theme lol.
Sent from my HTC 10 using Tapatalk