Database Info

Battery Drain? Does this help...

If you've been experiencing decreased battery life with recent versions of android or kernels you're probably pretty frustrated. The problem is that nobody seems to know what causes it or how to stop it. I was bouncing back and forth between this forum and cyanogenmod's forum and somewhere between the two I came across a new kernel made by ezterry for use with CM6.1. One of the patch contributers explained how his patch was supposed to help with battery life. I don't know if it does or not but the discussion shifted to how the adbd binary was respawning even when not connected to usb, and that got me thinking...
What if you turn off "USB Debugging" (uncheck option at Settings -> Application -> Debugging -> USB Debugging) That should keep adbd from starting at all.
The only downside is that you can't use ADB to connect to the phone from your computer when it is disabled. That may be a pain for devs and rom modders but once I've got a new build up and running I don't normally use adb anyways.
I've tried it on 3 different G1's and I am seeing increased battery life. It may not be 100% of where it was before but it is definitely better for me... either that or I'm going crazy...
So please, try it yourself and let people know here if it helps. And I apologize for the people whose work gave me this idea... I'd like to attribute your work to you but for some reason I can't find the thread I was looking at. If I (or someone else) find the thread again I'll update it here.
Update:
farmatito posted about adbd respawning here

I tried it, didn't prevent the drain.
When the battery drain circumstance occurs, you'll see from the Spare Parts / Battery History that the system has been running 100% of the time, i.e., something has prevented it from going to sleep. I see this happening even with USB Debugging turned off. Also, sometimes it still occurs even when I reboot after charging. I think a full power cycle is needed then, not just a reboot.

I also tried with USB debugging off and the battery drain was still there.
Sent from my HTC Dream using XDA App

I think it is a problem in the kernel
adb is in userspace
I know ( around about ) when it started..
but for now to get better battery reboot if you mated your phone, have a cig, a drink of milk or whatever it is you kids do after stuff that drained you

highlandsun said:
I tried it, didn't prevent the drain.
When the battery drain circumstance occurs, you'll see from the Spare Parts / Battery History that the system has been running 100% of the time, i.e., something has prevented it from going to sleep. I see this happening even with USB Debugging turned off. Also, sometimes it still occurs even when I reboot after charging. I think a full power cycle is needed then, not just a reboot.
Click to expand...
Click to collapse
Exactly my experience.

Kernel 2.6.34.7
Hi,
I had the same problem related with the battery drain when I was using Cyanogenmod 6.1. But the problem was solved when I flashed to kernel version 2.6.34.7
Regards,

My phone can idle fine for days if I'm not using it but the second I use the alarm app over night I wake up to find it in the red when it was fully charged the night before. At least for me, the alarm app is stopping it from going into "sleep" mode.

the solution was to flash a slightly older kernel, it was version 2.6.34.7, this was posted over at the cyanogen mod G1 forum. I had the battery drain issue, once I flashed the older kernel via recovery everything was back to normal.

That's good to know, maybe someone can track the changes since 2.6.34.7 and identify the problem...

cabrerachaparro said:
Hi,
I had the same problem related with the battery drain when I was using Cyanogenmod 6.1. But the problem was solved when I flashed to kernel version 2.6.34.7
Regards,
Click to expand...
Click to collapse
I would like to try your link, but what is the file which needs to be downloaded ? thx

A xx.7 kernel def does help with battery life. If your on the new spl and radio, try the ezbifftest xx.7 kernel.
Sent from my HTC Dream using XDA App

cabrerachaparro said:
Hi,
I had the same problem related with the battery drain when I was using Cyanogenmod 6.1. But the problem was solved when I flashed to kernel version 2.6.34.7
Regards,
Click to expand...
Click to collapse
Thank you for this trick. The battery life of my Dream/G1 is extended for real

Have 2.6.34.7 kernel the 14mb ram with new radio/spl?
I don't think so.... solutions?

nagash91 said:
Have 2.6.34.7 kernel the 14mb ram with new radio/spl?
I don't think so.... solutions?
Click to expand...
Click to collapse
patch 2.6.34.7 src with 2708 and compile

Firerat said:
patch 2.6.34.7 src with 2708 and compile
Click to expand...
Click to collapse
I'll do it, but before I have to prepare the mathematical analysis exam
(omg I hate it)
Firerat do you knows if I can patch the newer kernel with the old ramhack that add 10mb removing for 3D rendering?
I think would great 24mb instead of 14
(in this moment I'm using CSDIv4 with +8mb from the old ezterry's kernel and my G1 seems a nexus one )

nagash91 said:
I'll do it, but before I have to prepare the mathematical analysis exam
(omg I hate it)
Firerat do you knows if I can patch the newer kernel with the old ramhack that add 10mb removing for 3D rendering?
I think would great 24mb instead of 14
(in this moment I'm using CSDIv4 with +8mb from the old ezterry's kernel and my G1 seems a nexus one )
Click to expand...
Click to collapse
from your post I doubt you can patch anything
you seem to understand very little
sure you can patch in the old ram hack, but that will render most things unusable
in future don't ask questions implying that you can, just do it and see that you can't
fool..

Firerat said:
from your post I doubt you can patch anything
you seem to understand very little
sure you can patch in the old ram hack, but that will render most things unusable
in future don't ask questions implying that you can, just do it and see that you can't
fool..
Click to expand...
Click to collapse
Ahah yes I can.
I never compiled anything about android roms or kernels, true. But I want to begin.
I have the skills to do it, my problem is the time
I think that I have to compile kernels from source changing some piece of code.
If there are compatibility problems between patches and old kernels codes is a little bit problematic, but I don't think so.
I asked about old ram hack because I never compiled android kernel, so I don't know if the old 1.6 kernels are similar to newer kernels.
Personally I would like to exchange 3D for 10mb more, but don't know if it could break other thinks.
I don't like gallery 3D (don't like in G1, because it's too heavy)
I will try when I have time

Misutsu said:
Thank you for this trick. The battery life of my Dream/G1 is extended for real
Click to expand...
Click to collapse
If you use a 32b G1, you should try this: boot-cm_2634.7_ds_32b-oc-uv-fp-091310.zip

i just download theboot-cm_2634.7_ds_32b-oc-uv-fp-091310.zip im going to try this with cm7 or froyo lazlo because cm7 gives me the best battery life yet suprisingly hopefully bthis gives me an extra hour

ANyone know why this wont work with froyo lazlo -.- i flashed lazlo then this kernel but no luckstays at g1 lazlo works if i just dont flash this kernel

[Q] Slide2wake kernel drain free

Hey there,
i like a lot slide2wake and slide2lock, i really think it is a breakthrough feature!:victory:
The only way i can enable this feature is through Touch Control.
I've tried different kernels, but only Franco's r32 has been working with Touch Control.
When i enable the mod, the battery drains in half a day,
withouth the mod can last a day and a half. :crying:
Is there any kernel who work this mod without the huge drain?
Or is there another configuration different from Touch Control which works better?
I'm on paranoid android beta 4 custom ROM.
Thanks!

charlieBin said:
Hey there,
i like a lot slide2wake and slide2lock, i really think it is a breakthrough feature!:victory:
The only way i can enable this feature is through Touch Control.
I've tried different kernels, but only Franco's r32 has been working with Touch Control.
When i enable the mod, the battery drains in half a day,
withouth the mod can last a day and a half. :crying:
Is there any kernel who work this mod without the huge drain?
Or is there another configuration different from Touch Control which works better?
I'm on paranoid android beta 4 custom ROM.
Thanks!
Click to expand...
Click to collapse
Many kernels have slide2wake etc. TouchControl is a kernel module but kernels that advertise this feature should not need the module.
You'll have to test them all for yourself. Obviously the digitiser has to be powered to accept touch input when teh screen is off so there will always be SOME drain.

charlieBin said:
Hey there,
i like a lot slide2wake and slide2lock, i really think it is a breakthrough feature!:victory:
The only way i can enable this feature is through Touch Control.
I've tried different kernels, but only Franco's r32 has been working with Touch Control.
When i enable the mod, the battery drains in half a day,
withouth the mod can last a day and a half. :crying:
Is there any kernel who work this mod without the huge drain?
Or is there another configuration different from Touch Control which works better?
I'm on paranoid android beta 4 custom ROM.
Thanks!
Click to expand...
Click to collapse
Day and a half of battery is long for me.
I suggest downloading a kernel and tweaking the CPU clock and voltage to achieve more battery life. Chaos kernel comes to mind but I am biased because that is what I run.http://forum.xda-developers.com/showthread.php?t=2551441

rootSU said:
Many kernels have slide2wake etc. TouchControl is a kernel module but kernels that advertise this feature should not need the module.
You'll have to test them all for yourself. Obviously the digitiser has to be powered to accept touch input when teh screen is off so there will always be SOME drain.
Click to expand...
Click to collapse
Some drain is acceptable, driking battery not.
The kernel mod has been implemented (if i am not wrong) to better handle what and where the phone has to be awake than a simple app, i thought it could last better than what happened to me.
Anybody experiencing a better battery lasting with this mod enabled?
Any suggestion on the best kernel to try?
Otherwise i will test them with patience and report here

charlieBin said:
Some drain is acceptable, driking battery not.
The kernel mod has been implemented (if i am not wrong) to better handle what and where the phone has to be awake than a simple app, i thought it could last better than what happened to me.
Anybody experiencing a better battery lasting with this mod enabled?
Any suggestion on the best kernel to try?
Otherwise i will test them with patience and report here
Click to expand...
Click to collapse
That is not my understanding. My understanding is it is an external module for custom kernels. However if jernel already has function built in, touchcontrol not necessary. The Kernels specific apps have controls to cover it.
There is no BEST kernel. Read each thread of Kernels to see if it has the feature and test it yourself.
Although if Franco kernel has slide2wake etc built in, you should test that first WITHOUT touch control.

rootSU said:
That is not my understanding. My understanding is it is an external module for custom kernels. However if jernel already has function built in, touchcontrol not necessary. The Kernels specific apps have controls to cover it.
There is no BEST kernel. Read each thread of Kernels to see if it has the feature and test it yourself.
Although if Franco kernel has slide2wake etc built in, you should test that first WITHOUT touch control.
Click to expand...
Click to collapse
Will test Franco without touch control as soon as possible! Thanks pal,
i'll report what happens

charlieBin said:
Will test Franco without touch control as soon as possible! Thanks pal,
i'll report what happens
Click to expand...
Click to collapse
Okkei, i've been doing my homeworks after rootSu suggestions.
I found a somehow related question about franco's kernel
http://forum.xda-developers.com/showthread.php?t=2593181
It looks like you need to use a different kernel based on franco to use slide2wake.
So i tried one of the links, the linaro kernel http://forum.xda-developers.com/showthread.php?p=47459608
Following the instructions i created the file for the configuration and i have enabled the mod without using the touch control app.
I'll try this kernel and mod for a couple of days to see how it goes, hoping that this will make some difference.
By the way i bought franco's app which is pretty cool to set up a better configuration for any option, audio, screen and performance,
and it also works with linaro.

[Q&A] [KERNEL] [Bacon] [CM11s/CM11] Boeffla-Kernel 2.0 beta (22-10-2014)

Q&A for [KERNEL] [Bacon] [CM11s/CM11] Boeffla-Kernel 2.0 beta (22-10-2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL] [Bacon] [CM11s/CM11] Boeffla-Kernel 2.0 beta (22-10-2014). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

current
Lord Boeffla, after connecting the phone to charge the app shows the current charge value that are constantly changing and never reach the limits set in the settings. Is it correct?

Hi,
yes, depending on current battery level this is about correct.
The charging follows a "curve", so depending on fill level the charge rate changes. It goes up in the beginning and when it reaches high values 80-100, the current goes down again more and more.
This is to ensure healthy and smooth loading for the battery.
Only for some times somewhere in the middle, the configured charge rate is about to be used.
And also only if your charger can provide this charge rate in a stable way.
This is why the charge rate always slightly changes as the charger logic is constantly checking all conditions during the process.
So far my observations (was the same on Galaxy S3 etc...)
Andi

Thanks for the explanation. But I thought that in S3 current has been always a constant throughout the entire charging process. At least, BoefflaConfig showed that way. And phone is charging really fast via the USB port. I Liked Boeffla for it.

zin-renat said:
Thanks for the explanation. But I thought that in S3 current has been always a constant throughout the entire charging process. At least, BoefflaConfig showed that way. And phone is charging really fast via the USB port. I Liked Boeffla for it.
Click to expand...
Click to collapse
Hehe, no.
When you have a close look even on the S3, when it reaches towards 95% battery fill level, the charge rate drops. At least I was seeing that.
But the curves of S3 are different to the OPO. With the OPO it reduces much more early.
Andi

Lord Boeffla said:
Hehe, no.
When you have a close look even on the S3, when it reaches towards 95% battery fill level, the charge rate drops. At least I was seeing that.
But the curves of S3 are different to the OPO. With the OPO it reduces much more early.
Andi
Click to expand...
Click to collapse
Ok, I'm understand. And also small question: inactive red switches in BoefflaConfig means that these functions have been not yet implemented? In Boeffla Sound screen for example.

zin-renat said:
Ok, I'm understand. And also small question: inactive red switches in BoefflaConfig means that these functions have been not yet implemented? In Boeffla Sound screen for example.
Click to expand...
Click to collapse
Yes, this is correct. In cm11s, deactivated switches are having red lines around (due to the hexo design).
Many switches, especially in Boeffla-Sound will unfortunately never be non-red, as many features cannot be implemented due to the different audio chip.
But yes, you are right: If something is deactivated in the app, it means the kernel does not have this specific functionality implemented.
Andi

Lord Boeffla said:
Yes, this is correct. In cm11s, deactivated switches are having red lines around (due to the hexo design).
Many switches, especially in Boeffla-Sound will unfortunately never be non-red, as many features cannot be implemented due to the different audio chip.
But yes, you are right: If something is deactivated in the app, it means the kernel does not have this specific functionality implemented.
Andi
Click to expand...
Click to collapse
Thank you for answers and sorry for stupid questions!) You are the best kernel developer! I very glad you came to the 1+1.

Hi,
When I flash Boeffla Kerner or Stock CM 11S 38R kernel from Franco Kernel r28, WiFi don't turn on, he stays "Activating". Any suggestion to fix the problem?
Regards.

Yes. Read through the main thread of my kernel.
Franco kernel hacks the wifi firmware of the rom. Which breaks other kernels incl stock kernel.
Either flash the firmware over again to correct it.
Or try my firmware restore zip I provide in my main thread for exactly this reason...
Andi

Thank you so much!
Man oh man! I always knew you add good taste lord Boeffla, it's good to experience your kernel after the S3, many good memories, I remember getting as much as 24000 score on antutu when the default was 19000,and all this while saving some battery, from what I,ve experienced it's good so far. If I would ask something it would be some underclocking features and hotplug set to only one core on just one of the governors in order to save battery, it would be perfect

Does this kernel support encrypted devices (in opposite to e.g. franco kernel)?
Thanks

MoMaMeMi said:
Does this kernel support encrypted devices (in opposite to e.g. franco kernel)?
Thanks
Click to expand...
Click to collapse
Never tried that, so I do not know.
I have not taken anything out with regards to encryption, still I cannot be 100% sure on it before someone tests it.
Andi

GKti22 said:
If I would ask something it would be some underclocking features and hotplug set to only one core on just one of the governors in order to save battery, it would be perfect
Click to expand...
Click to collapse
Underclocking of CPU is of course in. Just lower the max CPU frequency.
GPU is now also reduced to a 27 MHz idle frequency with latest beta6.
And the hotplug stuff: Have a look at the hotplug profiles in beta6
Andi

Lord Boeffla said:
Never tried that, so I do not know.
I have not taken anything out with regards to encryption, still I cannot be 100% sure on it before someone tests it.
Andi
Click to expand...
Click to collapse
I took the risk - works! Great
Danke Andi!

MoMaMeMi said:
I took the risk - works! Great
Danke Andi!
Click to expand...
Click to collapse
Thanks for confirming !!!
Andi

I'm running crDroid.. Will flashing cm11 version break WiFi or does anybody know how this kernel works with this ROM? I'm assuming flashing the cm11s will work?? Thanks

Damn, its good!!

we will see some good..

suaverc118 said:
I'm running crDroid.. Will flashing cm11 version break WiFi or does anybody know how this kernel works with this ROM? I'm assuming flashing the cm11s will work?? Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56375250&postcount=555
Read that, when it works for them and I think you use the same ROM it should work for you to. BTW CM11 and CM11s are not the same so CM11s kernel is probably not working on a CM11 based ROM.

[KERNEL][LOS-14.1] Current Kernel with S2W, DT2W, L2M, L2W, Fast Charge

Hey Guys,
I will build the current Lineage OS 14.1 Kernel for the HTC One M7 with wake gestures. I will not modify or add any features except the wake gestures and fast charge, so please report bugs directly to the Lineage OS developers! If this kernel is not up to date, write a message I will build it from the latest sources (or you can do it by yourself).
Credits: flar2 (wake gestures), tathanhlam66 (merging with cm-14.1), Lineage-OS Team
Lineage OS Repository: https://github.com/LineageOS/android_kernel_htc_msm8960
This Kernel Repository: https://github.com/bbbjjj/android_kernel_htc_msm8960
Last Update: 20170308
Kernel Version: 3.4.113
Changelog:
20170308
Added "force fast charge" feature
20170306
Added S2W, DT2W, L2M, L2W
Sync with Lineage OS Sources
Configuration Interface: (for advanced users)
/sys/android_touch/logo2menu
0 - Off
1 - On
/sys/android_touch/logo2wake
0 - Off
1 - On
/sys/android_touch/doubletap2wake
0 - Off
1 - Full Display
2 - Half Display
/sys/android_touch/pocket_detect
0 - Off
1 - On
/sys/android_touch/sweep2wake
0 - Off
1 - Sweep2Wake & Sweep2Sleep
2 - Sweep2Sleep
/sys/kernel/fast_charge/force_fast_charge
0 - Off
1 - On
FAQ:
What is "force fast charge" and does it reduce lifespan of my battery?
This feature does not enable quick charging on your phone, because quick charging is already enabled. This will force the kernel to inform a quick charging compatible charger that the it should provide up to 1000 mA of current. It is completely up to your device to take this much power or not, so it will not harm your battery or the lifespan.
Is feature XYZ included in this kernel?
Please try it or look up the kernel configuration before asking in this thread.
How to enable Logo2Wake or Logo2Menu?
You can use the configuration interface above with init.d or su.d e.g. with Kernel Adiutor. Or you can use the Wake Gesture appfrom flar2 or try any other kernel configuration app.
This is a TWRP flashable zip file! TWRP 3.0.0.2 recommended. Gestures and fast charge are not enabled by default. Manage them through an application like Kernel Adiutor.
And as always flash it at your own risk.

@__BJ__ Hope you can add USB Fast Charging features also to this kernel

apknl said:
@__BJ__ Hope you can add USB Fast Charging features also to this kernel
Click to expand...
Click to collapse
Can you provide a link to a kernel which has fast charge (github)?

I dont know much about github but in xenonHD fastcharge is allways in there and here is the git link to the device https://github.com/TeamHorizon/android_device_htc_m7-common maybe it helps to finde what you are looking for
Edit: I think this is what you need https://github.com/TeamHorizon/android_kernel_htc_msm8960

saturday_night said:
I dont know much about github but in xenonHD fastcharge is allways in there and here is the git link to the device https://github.com/TeamHorizon/android_device_htc_m7-common maybe it helps to finde what you are looking for
Edit: I think this is what you need https://github.com/TeamHorizon/android_kernel_htc_msm8960
Click to expand...
Click to collapse
Found it here: https://github.com/poondog/kangaroo-m7-mkv/commit/74c6c10aa5f8cd45552206ab6943490114b24ce1
But I want to clarify, this does not >>enable<< fast charge, this will force the current notification for the charger to 1000 mA so that the charger if it supports fast charging will provide up to 1000 mA. I don't know if the device is really using it. Normal charging is 600 mA and can go up to 900 mA. So this feature will increase current by 100 mA. And again I'm not sure the battery is using this current.

I have three different charger incl the usb from pc what sure is the slowest, then there is a 1000mA charger which is a little bit faster (i dont think it really gives 1000mA) and a 1800mA charger and if i use a kernel with the fast charge option in kernel adiutor, it charges much faster and you will notice the difference a lot. Without that option, it is on my 1800mA charger, well feels like usb connection to pc xD

saturday_night said:
I have three different charger incl the usb from pc what sure is the slowest, then there is a 1000mA charger which is a little bit faster (i dont think it really gives 1000mA) and a 1800mA charger and if i use a kernel with the fast charge option in kernel adiutor, it charges much faster and you will notice the difference a lot.
Click to expand...
Click to collapse
Ok, I haven't got any special chargers. Will include this in an extra version tomorrow. Its your part to test it.

__BJ__ said:
Ok, I haven't got any special chargers. Will include this in an extra version tomorrow. Its your part to test it.
Click to expand...
Click to collapse
Sure i will love to test it, fast charge is a reason to change the kernel for me.
Now i found the fast charge commit from xenonHD https://github.com/TeamHorizon/andr...mmit/e43cad62f711f0508b97cfe6bc976cc5f7503e92

saturday_night said:
Sure i will love to test it, fast charge is a reason to change the kernel for me.
Now i found the fast charge commit from xenonHD https://github.com/TeamHorizon/andr...mmit/e43cad62f711f0508b97cfe6bc976cc5f7503e92
Click to expand...
Click to collapse
Ok here is the build, please test the force fast charge feature. Not enabled by default!
EDIT: Added to main post

Thank you for that nice Kernel, works great. And charging is now much faster even with my 1800mA charger.

__BJ__ said:
Ok here is the build, please test the force fast charge feature. Not enabled by default!
Click to expand...
Click to collapse
Thank you for your work.
I use this RR andt i have a smal issue. With your Kernel my Ambient Display will not work. If i flash back the Stock Kernel it work again.
i have no idea why this happen

hedeon76 said:
Thank you for your work.
I use this RR andt i have a smal issue. With your Kernel my Ambient Display will not work. If i flash back the Stock Kernel it work again.
i have no idea why this happen
Click to expand...
Click to collapse
EDIT: Sorry I was confused. I'm not using ambient display and can't find an option to enable it in latest official lineage os nightly. So its a feature of RR I think and its author has to support this.

__BJ__ said:
EDIT: Sorry I was confused. I'm not using ambient display and can't find an option to enable it in latest official lineage os nightly. So its a feature of RR I think and its author has to support this.
Click to expand...
Click to collapse
I was also confused and test latest lineage and can't find the ambient display option.
EDIT: I have test some Kernels. It worked with Tesla Kernel and all RR Kernel from R1ghtC i extrakt from roms
but it wont work with Lineage, Xenon and your Kernel

Any way you could add cifs support to this kernel please?

Wmapa said:
Any way you could add cifs support to this kernel please?
Click to expand...
Click to collapse
CIFS is enabled...
@hedeon76 : R1ghtC forked the lineage kernel for RR so please report this to him, I will not add support for a feature which is not available in the lineage Roms.

__BJ__ said:
@hedeon76 : R1ghtC forked the lineage kernel for RR so please report this to him, I will not add support for a feature which is not available in the lineage Roms.
Click to expand...
Click to collapse
ok, thank you

This would be needed for ambient display but i never used this feature dont know how much battery drain it will cause.

saturday_night said:
This would be needed for ambient display but i never used this feature dont know how much battery drain it will cause.
Click to expand...
Click to collapse
This looks like a feature of the rom and not the kernel.

__BJ__ said:
This looks like a feature of the rom and not the kernel.
Click to expand...
Click to collapse
Yes, you are right.
These are only the changes in the ROM.

__BJ__ said:
Can you provide a link to a kernel which has fast charge (github)?
Click to expand...
Click to collapse
Here you go:
https://github.com/tathanhlam66/android_kernel_htc_msm8960/blob/rr7.1/drivers/usb/otg/msm_otg.c

[TISSOT][INDEX]Best Oreo ROMs for battery life

Hi. I'm quite new in the custom ROMs' space, but custom ROMs are one of the reasons I've bought the Mi A1. One thing that does matter very much to me is battery life, and therefore I'm always looking for the best combination of performance and battery life. That's why I decided to "test" any stable ROM that appears in this forum, to classify them from the best for battery life to the one with the worst battery drain.
TESTING CONDITIONS
Follow these testing conditions to share your results with us and give us a better rapresentation of average battery life. I'm still defining testing conditions, but that's what I've came up with:
TEST 0 (legacy): WHOLE DAY WITH TOO MUCH MEDIA
Screen on auto brightness, 35/45% all day long
No double tap to wake or always-on display
Always testing from full 100% charge to 15% charge
Test always starts from around 6.00/7.00 AM and finishes when at 15% battery left
Wi-Fi and 4G always on. Connected on 4G from 8.00 AM to 1.30 PM, Wi-Fi for the time left
GPS and Bluetooth always off
No overclock/underclock/power savings
Google Apps mini package installed
Chrome use in the morning, at launch and at dinner, while YouTube gets me the rest of screen on time in the afternoon
TEST 1: GAMING
20 minutes of Need for Speed No Limits,20 minutes of PUBG Mobile
Screen on manual 50% brigthness
No double tap to wake or always-on display
Always testing with battery between 90% and 20%
Wi-Fi and 4G always on; connected to wi-fi
GPS and Bluetooth off
No overclock/underclock/power savings
Google Apps mini package installed
TEST 2: STAND BY 1
3h of stanby
No double tap to wake or always-on display
Always testing with battery between 90% and 20%
Wi-Fi and 4G always on; connected to wi-fi
GPS and Bluetooth on, no device connected
No overclock/underclock/power savings
Google Apps mini package installed
TEST 3: MEDIA
2h of YouTube
Screen on outo 40% brigthness
No double tap to wake or always-on display
Always testing with battery between 90% and 20%
Wi-Fi and 4G always on; connected to wi-fi
GPS off, Bluetooth on (no device connected)
No overclock/underclock/power savings
Google Apps mini package installed
TEST 0 LEGACY RESULTS
Stock Android One 8.0 + MiNT kernel
Stock Android One 8.0
Resurrection Remix (12/15/218 build) + MiNT kernel
Resurrection Remix (12/15/218 build) + Moun kernel
NitrogenOS (02/05/2018 build) + Moun kernel
Android Open Source Illusion Project (AOSiP) (09/05/2018 build) + Moun kernel
NitrogenOS (02/05/2018 build) + MiNT kernel
dotOS (06/05/2018 build) + MiNT kernel
dotOS (06/05/2018 build) + FrancoKernel r7
dotOS (06/05/2018 build) + MetaPhoenix kernel
dotOS (06/05/2018 build)
CosmicOS (01/05/2018 build) + FrancoKernel r7
CosmicOS (01/05/2018 build)
MY RECOMMENDATIONS:
Resurrection Remix the best of the bunch. Use new builds as the older ones MAY give corrupted persist partition (new ones are totally fine);
Mod edit:- above-mentioned issue was only with one old build of RR, and its been already fixed.
AOSiP the next good one. Has less feature than RR but it's worth it;
NitrogenOS has slightly better battery life than AOSiP and RR, but with fewer customizations;
ROM request closed for now. Schedule may vary based on time available to me: remember that this phone is my daily driver and that I'm alone in testing and publishing data.
The need for more tests and the need to revise the first test may also bring the need to change schedule AND retest some ROMs
P.S.: I'm probably gonna update the topic with just ROMs with their own kernels (no other kernels installed) and then a separate list of kernels. The only thing is that same kernel gives different battery life deltas on different ROMs, so it would be best to try different ROMs with the best kernels for battery life (like top 3 of the kernel list)

plese keep with the work i really want to know off all withc are the best, im not going to flash your recomendations for dayily use

I see a lot of people interested in your findings, please do continue the excellent work!
Could you try also Lineage Os? As it is official now, many people are probably going to try it?

Hats Off to ur Work bro..keep it up..
Subscribed

Shillopellos9 said:
I see a lot of people interested in your findings, please do continue the excellent work!
Could you try also Lineage Os? As it is official now, many people are probably going to try it
Click to expand...
Click to collapse
Of course. Any suggestion is welcomed. Lineage wasn't on top of my mind as it's not particularly famous for his great battery life as there are better ROMs. But as many people ask for it I'll give it a shot.
Anyway I'm on Resurrection Remix now. We'll see how it goes.
sauru.660 said:
Hats Off to ur Work bro..keep it up..
Subscribed
Click to expand...
Click to collapse
Thanks man

Dornyx said:
Of course. Any suggestion is welcomed. Lineage wasn't on top of my mind as it's not particularly famous for his great battery life as there are better ROMs. But as many people ask for it I'll give it a shot.
Anyway I'm on Resurrection Remix now. We'll see how it goes.
Thanks man
Click to expand...
Click to collapse
plese also try aim rom, i actually liked it but i flashed not RR because of some features, but from what u have tested, dont forget to the wicth rom+kernel will give the best battery, thankssss

Thanks bro for the work.
Following | Subscribed

Thanks for this post. What about Franco Kernel?

Thanks, can u try Carbon?

FISRT POST UPDATED
Apparently no other user has experienced wi-fi MAC or sensors issue on AOSiP. Being only me having had problems, I absolutely recommend it as the best option for battery life.
Resurrection Remix + Moun Kernel in the testing (looks on part with AOSiP for now). Probably update coming in the next 4 hours.
Nautilus99 said:
plese also try aim rom, i actually liked it but i flashed not RR because of some features, but from what u have tested, dont forget to the wicth rom+kernel will give the best battery, thankssss
Click to expand...
Click to collapse
OK, gonna test AIM next. Would you like AIM+Moun Kernel or AIM stock?
srb1993 said:
Thanks bro for the work.
Following | Subscribed
Click to expand...
Click to collapse
Thanks, man
Klirioth said:
Thanks for this post. What about Franco Kernel?
Click to expand...
Click to collapse
For what I've found out in my testing, MiNT kernel and Moun kernel give better battery life for now. The ROMs in which I've tested FrancoKernel had problems on their own, so I'm probably gonna test it again when the next release comes out.
GVN.Gallus said:
Thanks, can u try Carbon?
Click to expand...
Click to collapse
For sure, but after I've tried the ROMs that come before in the list.

Dornyx said:
FISRT POST UPDATED
Apparently no other user has experienced wi-fi MAC or sensors issue on AOSiP. Being only me having had problems, I absolutely recommend it as the best option for battery life.
Click to expand...
Click to collapse
Perhaps MAC changed when you flashed the kernel. I flashed LOS yesterday, MAC ok, but deepsleep issues. So I tried flashing a new kernel (moun) and then MAC gone.
Great work man! Battery life is one of the most "interesting" keypoints on custom ROMs. This should help ppl pick the right ROM first-try.
BTW, I haven't seen LOS on the list, any particular reason?

jucaftp said:
Perhaps MAC changed when you flashed the kernel. I flashed LOS yesterday, MAC ok, but deepsleep issues. So I tried flashing a new kernel (moun) and then MAC gone.
Great work man! Battery life is one of the most "interesting" keypoints on custom ROMs. This should help ppl pick the right ROM first-try.
BTW, I haven't seen LOS on the list, any particular reason?
Click to expand...
Click to collapse
Just forgot to add Lineage, but was already in consideration. Anyway in my testing I've seen better battery life on stock ROM with custom kernels than any other one. Maybe there are some optimization in the source code to do

In your next phase, could you please consider adding cardinal and carbon with void kernel?
This had given better sot for me.

Dornyx said:
FISRT POST UPDATED
OK, gonna test AIM next. Would you like AIM+Moun Kernel or AIM stock?
i would like you to test aim with the kernel that you think is better for its battery
thanks for all this work man, its really a like saver and now users will know what rom+kernel to use for battery
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
Dornyx said:
Just forgot to add Lineage, but was already in consideration. Anyway in my testing I've seen better battery life on stock ROM with custom kernels than any other one. Maybe there are some optimization in the source code to do
Click to expand...
Click to collapse
i used stock on aim, you can try moun kernel, r the one that gives the best battery
thanks for your work
Click to expand...
Click to collapse

Good job bro I'm looking forward to see screenshots

Could you test the crDroid 4.2 Rom by arunassain?
Thanks in advance

from telegram group people suggested : RR , Dot , nos and aex

Test 2 suggestions
- Manual brightness 40/60%
- Always-on and d2tw
- Same WI-Fi and 4g but with GPS and Bluetooth always-on (paired to a smartwatch e.g.)
- no oc/uc/ps
-no youtube usage at all + most common videogames (RealRacing/Clash of Clans/Candy Crush etc.) + Facebook (not the lite version)
P.S. did you try stock oreo + Franco Kernel?

naturaldai said:
Good job bro I'm looking forward to see screenshots
Click to expand...
Click to collapse
FIRST POST UPDATED
Added screenshots, a more precise testing schedule and one more ROM
Rbunchie said:
Could you test the crDroid 4.2 Rom by arunassain?
Thanks in advance
Click to expand...
Click to collapse
Of course, but I'll need more time as the schedule is already quite full
xxqxpxx said:
from telegram group people suggested : RR , Dot , nos and aex
Click to expand...
Click to collapse
dotOS and NitrogenOS already tested (have a better look at the first post). RR coming (testing yesterday, today and tomorrow). AEX is the next one in the list
Siebenmik said:
- Manual brightness 40/60%
- Always-on and d2tw
- Same WI-Fi and 4g but with GPS and Bluetooth always-on (paired to a smartwatch e.g.)
- no oc/uc/ps
-no youtube usage at all + most common videogames (RealRacing/Clash of Clans/Candy Crush etc.) + Facebook (not the lite version)
P.S. did you try stock oreo + Franco Kernel?
Click to expand...
Click to collapse
Thanks for the great suggestion. I need to better define WHAT games to test and HOW LONG to test them (like Real Racing 15 minutes, NFS 30 minutes...).
For the smartwatch thing, I'd like to test it but I have no smartwatch and can't afford it as for now.

Dornyx said:
Thanks for the great suggestion. I need to better define WHAT games to test and HOW LONG to test them (like Real Racing 15 minutes, NFS 30 minutes...).
For the smartwatch thing, I'd like to test it but I have no smartwatch and can't afford it as for now.
Click to expand...
Click to collapse
I'd say not to use time as a reference but percentage (e.g. from 60 to 50 percent Real Racing etc. measuring how much does the percentage span lasts too)