Database Info

[REF] Benchmark Methods (All Phones)

This thread shows the results of some benchmarks of the Android OS (using a Nexus S) where certain parameters affecting performance have been isolated to the greatest extent and then compared statistically.
Background
I teach mathematics, and also used to be a professional sound engineer.
Some of my work on measuring battery drain was published on the XDA portal here however since then further studies were conducted, revealing critical flaws in my original test setup.
Although I believe some of my finding may be generalised to other devices, please bear in mind that my device is a Nexus S, and has its own peculiarities. I have attempted to edit out findings which I believe may be specific to the Nexus S, but I have linked to the original thread in case you wish to go exploring further results, or get an overview of my methodologies, which are usually in the second post.
Please feel free to post or PM with any queries, and I am more than happy to help if you want to apply my techniques to your own device.

Results
Over my time here in XDA I've built up a few studies on the Nexus S.
Here are the links. There are summaries in each thread in the first and second (and sometimes third) posts of the main findings, but I've done some very quick and minimal overviews here also.
ICS ROM Benchmarks: this thread
-Freely available benchmark programs were used to determine which ROMs had the best performance. Among the top six were an AOSP ROM with some CM9 parts, MIUI, and Stock, all within about 1% of each other. My conclusion was that the gingerbread tweaks we all knew and loved didn't improve performance with ICS, and in some cases, enthusiastic young developers were throwing together incompatible tweaks that hurt performance.
Battery Drain Benchmarks: this thread
#1 - With screen on, the slowest processor step saves the most power (duh... )
#2 - Regardless of your choice of governor, even with extreme undervolting, you are not going to be able to increase your battery life by more than 2%. (Click here for explanation.)
For the instability introduced by UV, it seems a 2% increase in battery life isn't really worth it! REMEMBER rebooting uses so much power, a single one would more than undo any savings made by UV.
Also, undervolting seems to cause more reboots when the battery is running low. This makes sense, as the battery runs low it loses some of its voltage (which shouldn't be confused with remaining power capacity).
#4 - This is one point that everyone ought to know, but I'm including because many people seem to believe in myths: if the screen is off, and the CPU is not active, neither deep idle nor UV will have any impact on battery life.
#6 - If you have an amoled display, black saves a great deal of power. After that, red. If you have a black and red theme, this is saving you power!
#9 - For amoled displays, Kernels higher FPS mods will cause the screen to drain about more power. For instance, on the Nexus S, 65 fps drained 10% more power than 56 fps. Also, 50 fps saved about 7% power compared to 56 fps.
#11 - If you've got no reception, you might as well be in airplane mode, because searching for reception also eats battery.
#12 - If your phone can't handle OC (or UV for that matter) it's because components in general are built to cost, which means factoring in tolerances, and every chip is made as cheaply as possible within the specified tolerances. Outside of those tolerances, whether your chip can cope or not is unfortunately down to the whether you got lucky with the individual device that dropped off the manufacturing line.
ARM document on A8 fault tolerance: http://infocenter.arm.com/help/index.../Babhjhag.html
In fact I measured how UV in particular can cause errors, and saw in action the A8 using MORE power to correct the errors.
CPU Governors and I/O Schedulers: this thread
-Interestingly, CFQ generally performs very well, and deadline. Most custom kernel developers in the Nexus S section recommend a version of deadline that has been tweaked for flash storage. In one of my unpublished benchmarks deadline performed slightly better than CFQ.
Does SuperCharging work?: this thread
-This was just a short study to find out if this script is suitable for the Nexus S, but it turned out it had no effect, positive or negative. This script was probably more use on devices that had less memory. One benefit that remains is to 'bulletproof' the launcher.
Kernel Memory Allocators: this thread
-This is another short study for kernel developers to show that SLUB performs best.

[INFO] Getting better battery life and performance

You may have heard about how flashing a new ROM can improve your Android experience, but flashing a new kernel is one of the best ways to improve your phone's performance, battery life, and even add some saucy new features. Whether you know anything about either, here's what you need to know to make it happen.
What Is a Kernel?
A kernel in an operating system—in this case Android—is the component responsible for helping your applications communicate with your hardware. It manages the system resources, communicates with external devices when needed, and so on. Android uses a variation of the Linux kernel. A kernel is not the same as a ROM, even though you install them in mostly the same way. A ROM is a bit more all-encompassing. It's the operating system you use on your phone, the software your phone uses to get things done—the kernel is the bridge between that ROM and your hardware. All ROMs come with a kernel installed, but you can install a third-party one if you like—and that's what this post is about.
What a New Kernel Can Do For Your Phone
Flashing kernels isn't quite as talked about as flashing ROMs, but it can do a ton for your phone, namely in the way of battery life and performance—though it can also add extra features to your device, too. Here are some things to look for when choosing a new kernel.
Better Performance and Battery Life
This is the big change a new kernel can bring to your device. I'd separate these into two categories, but they're so intertwined that you really need to consider both when picking a kernel. There are a bunch of different kernel features that contribute to this:
Clock Speeds: In a very basic sense, higher clock speeds will improve performance on your phone. Flashing a new kernel allows you to overclock your phone, using higher clock speeds than the manufacturer intended. They can also let you reach lower clock speeds, so you can underclock your phone when you aren't using it, thus saving battery life. Your kernel will only give you the option to do so, however; if you want to overclock, you'll have to flash the kernel in question and then use something like SetCPU or CPU Tuner to tweak the clock speed.
Voltage: Higher clock speeds use up more battery on your phone because they require more voltage. However, some ROMs come with lower voltage limits, which means your phone will run just as fast, but use up less battery. Some will even overclock and undervolt your phone, though all of this comes at the expense of stability—if you notice that your phone goes into a boot loop, or reboots at random times, you'll want to either lower your clock speed or upgrade to a kernel with a higher voltage. Some ROMS have further sub-categories in this section, like Hybrid Adaptive Voltage Scaling (HAVS), which can be better for battery life (at the risk of stability) and Static Voltage Scaling (SVS), which keeps your phone at a steady voltage.
CPU Governors: Different kernels can support different CPU Governers, which manage the way your phone ramps up or down its clock speeds as you use it. There are a few different kinds you'll see, including Conservative, which focuses on battery life by ramping up your CPU very gradually when needed; Interactive, which focuses more on performance and smoothness by scaling up the CPU faster; InteractiveX, which is like Interactive but scales the CPU down when your screen is off (for better battery life); and Smartass, which is similar to Conservative but takes more factors into account when ramping up the CPU.
Task Scheduler: Kernels come with two different types of task schedulers: the Completely Fair Scheduler (CFS) and the Brain F**k Scheduler (BFS). CFS kernels are designed for regular phone use, like texting, web browsing, and otherwise multitasking apps on your phone. Most stock kernels are CFS kernels. BFS kernels focus more on whatever app is in the foreground, which is great for things like games but can be a bit laggier and a bit less stable.
These are the biggest features, but kernel developers add in all kinds of other tweaks to their kernels when possible, whether its introducing a more efficient file system, making the RAM more efficient, and so on. Again, they should list the tweaks in their description, so read up on the kernels for your specific device to learn more. I'd also recommend checking out XDA user mroneeyedboh's HTC Evo 4G kernel starter guide, from which much of this information comes.
Extra Features
Kernels can also add full features to your phone, or fix other issues that the manufacturer hasn't attended to yet. For example, while a lot of phones support Wi-Fi tethering out of the box, some—like the Motorola Droid—don't. If you find your phone isn't letting you tether using apps like Wi-Fi Tether, you might need to flash a new kernel that supports Wi-Fi tethering on your device. Kernels for Samsung phones can add support for a feature called Backlight Notification (BLN), which, coupled with an app, can turn your phone's buttons into notification lights.
Keep an eye out for features you don't want, too. For example, some HTC kernels come with a feature called Superior Battery Charging, or SBC, that can overcharge your battery for better life—but is likely to shorten your battery's life at best, or make it unstable at worst. I'd avoid kernels with this feature. You should also watch out for kernels that disable certain features of your phone—since some features are manufacturer-specific, you won't be able to get them in other ROMs or kernels. A good example of this is HDMI support on the EVO 4G.
Again, just make sure you research all the kernels available for your device, and know what you're getting yourself into before you flash. Most phones should have a large forum thread somewhere on XDA or RootzWiki that lists all the kernels available for their device. Make sure you choose a compatible one, too—the version of Android you're running determines what kernels you can use, so make sure you don't flash a Sense kernel on an AOSP ROM (like CyanogenMod), and make sure you don't flash a Froyo kernel on a Gingerbread phone—they won't play nicely together.
How to Flash a New Kernel
Once you've found a kernel you want to flash, download it to your device. It should be in ZIP format. Flashing a kernel is almost exactly like flashing a new ROM. You'll need to flash a new recovery to your phone, like ClockworkMod, which you can flash with ROM Manager. Put the ZIP file on your phone's SD card, then start up ROM Manager and go to "Install ROM from SD Card". Choose the kernel's ZIP file and continue. Note, however, that some kernels require that you flash them through your recovery mode instead of with ROM Manager—so once again, do your due diligence on its home page before you go a-flashin'.
The main difference between flashing a ROM and flashing a kernel is that you do not want to wipe your data. Wipe the Dalvik Cache only, and back up your ROM if desired (I highly recommend doing so, in case something goes wrong). Other than that, you should be golden. If you haven't flashed a ROM before, I recommend reading up on that first—but if you're familiar with that process, flashing a kernel shouldn't be a big shock to the system.
SOURCE - - - Lifehacker.com
Started from the bottom

Tha TechnoCrat said:
You may have heard about how flashing a new ROM can improve your Android experience, but flashing a new kernel is one of the best ways to improve your phone's performance, battery life, and even add some saucy new features. Whether you know anything about either, here's what you need to know to make it happen.
What Is a Kernel?
A kernel in an operating system—in this case Android—is the component responsible for helping your applications communicate with your hardware. It manages the system resources, communicates with external devices when needed, and so on. Android uses a variation of the Linux kernel. A kernel is not the same as a ROM, even though you install them in mostly the same way. A ROM is a bit more all-encompassing. It's the operating system you use on your phone, the software your phone uses to get things done—the kernel is the bridge between that ROM and your hardware. All ROMs come with a kernel installed, but you can install a third-party one if you like—and that's what this post is about.
What a New Kernel Can Do For Your Phone
Flashing kernels isn't quite as talked about as flashing ROMs, but it can do a ton for your phone, namely in the way of battery life and performance—though it can also add extra features to your device, too. Here are some things to look for when choosing a new kernel.
Better Performance and Battery Life
This is the big change a new kernel can bring to your device. I'd separate these into two categories, but they're so intertwined that you really need to consider both when picking a kernel. There are a bunch of different kernel features that contribute to this:
Clock Speeds: In a very basic sense, higher clock speeds will improve performance on your phone. Flashing a new kernel allows you to overclock your phone, using higher clock speeds than the manufacturer intended. They can also let you reach lower clock speeds, so you can underclock your phone when you aren't using it, thus saving battery life. Your kernel will only give you the option to do so, however; if you want to overclock, you'll have to flash the kernel in question and then use something like SetCPU or CPU Tuner to tweak the clock speed.
Voltage: Higher clock speeds use up more battery on your phone because they require more voltage. However, some ROMs come with lower voltage limits, which means your phone will run just as fast, but use up less battery. Some will even overclock and undervolt your phone, though all of this comes at the expense of stability—if you notice that your phone goes into a boot loop, or reboots at random times, you'll want to either lower your clock speed or upgrade to a kernel with a higher voltage. Some ROMS have further sub-categories in this section, like Hybrid Adaptive Voltage Scaling (HAVS), which can be better for battery life (at the risk of stability) and Static Voltage Scaling (SVS), which keeps your phone at a steady voltage.
CPU Governors: Different kernels can support different CPU Governers, which manage the way your phone ramps up or down its clock speeds as you use it. There are a few different kinds you'll see, including Conservative, which focuses on battery life by ramping up your CPU very gradually when needed; Interactive, which focuses more on performance and smoothness by scaling up the CPU faster; InteractiveX, which is like Interactive but scales the CPU down when your screen is off (for better battery life); and Smartass, which is similar to Conservative but takes more factors into account when ramping up the CPU.
Task Scheduler: Kernels come with two different types of task schedulers: the Completely Fair Scheduler (CFS) and the Brain F**k Scheduler (BFS). CFS kernels are designed for regular phone use, like texting, web browsing, and otherwise multitasking apps on your phone. Most stock kernels are CFS kernels. BFS kernels focus more on whatever app is in the foreground, which is great for things like games but can be a bit laggier and a bit less stable.
These are the biggest features, but kernel developers add in all kinds of other tweaks to their kernels when possible, whether its introducing a more efficient file system, making the RAM more efficient, and so on. Again, they should list the tweaks in their description, so read up on the kernels for your specific device to learn more. I'd also recommend checking out XDA user mroneeyedboh's HTC Evo 4G kernel starter guide, from which much of this information comes.
Extra Features
Kernels can also add full features to your phone, or fix other issues that the manufacturer hasn't attended to yet. For example, while a lot of phones support Wi-Fi tethering out of the box, some—like the Motorola Droid—don't. If you find your phone isn't letting you tether using apps like Wi-Fi Tether, you might need to flash a new kernel that supports Wi-Fi tethering on your device. Kernels for Samsung phones can add support for a feature called Backlight Notification (BLN), which, coupled with an app, can turn your phone's buttons into notification lights.
Keep an eye out for features you don't want, too. For example, some HTC kernels come with a feature called Superior Battery Charging, or SBC, that can overcharge your battery for better life—but is likely to shorten your battery's life at best, or make it unstable at worst. I'd avoid kernels with this feature. You should also watch out for kernels that disable certain features of your phone—since some features are manufacturer-specific, you won't be able to get them in other ROMs or kernels. A good example of this is HDMI support on the EVO 4G.
Again, just make sure you research all the kernels available for your device, and know what you're getting yourself into before you flash. Most phones should have a large forum thread somewhere on XDA or RootzWiki that lists all the kernels available for their device. Make sure you choose a compatible one, too—the version of Android you're running determines what kernels you can use, so make sure you don't flash a Sense kernel on an AOSP ROM (like CyanogenMod), and make sure you don't flash a Froyo kernel on a Gingerbread phone—they won't play nicely together.
How to Flash a New Kernel
Once you've found a kernel you want to flash, download it to your device. It should be in ZIP format. Flashing a kernel is almost exactly like flashing a new ROM. You'll need to flash a new recovery to your phone, like ClockworkMod, which you can flash with ROM Manager. Put the ZIP file on your phone's SD card, then start up ROM Manager and go to "Install ROM from SD Card". Choose the kernel's ZIP file and continue. Note, however, that some kernels require that you flash them through your recovery mode instead of with ROM Manager—so once again, do your due diligence on its home page before you go a-flashin'.
The main difference between flashing a ROM and flashing a kernel is that you do not want to wipe your data. Wipe the Dalvik Cache only, and back up your ROM if desired (I highly recommend doing so, in case something goes wrong). Other than that, you should be golden. If you haven't flashed a ROM before, I recommend reading up on that first—but if you're familiar with that process, flashing a kernel shouldn't be a big shock to the system.
SOURCE - - - Lifehacker.com
Started from the bottom
Click to expand...
Click to collapse
thanks for sharing :good:

hi..
thx a lot for useful info for me as newbie. i'd like to req. permission to copy your info to my personal note..
i'm appreciated of your kindness.
TQ

Thanks, great information
Send From Samsung Galaxy S4

muchas gracias

zaki aziz said:
hi..
thx a lot for useful info for me as newbie. i'd like to req. permission to copy your info to my personal note..
i'm appreciated of your kindness.
TQ
Click to expand...
Click to collapse
Yes you can copy.
Started from the bottom

tks it's usefful
do u recommand a kernel for best battery life?

i am using jammal rom and allucard kernel, but i only get 3460 scores and battery life is terrible. any tips?

Great info
Sent from my GT-I9500 using Tapatalk

Informative. Much appreciated.

245235568
There are plenty of apps in play store to disable wifi and 3G in order to optimize battery

i use zero lemon battery its great 7500 mAh lasts for days

kernel for best battery life?

Ive heard good things about talexop kernel

I also have zero lemon battery 7500 mAh I can get almost three days life on it without a charge
Sent from my SGH-I337M using Tapatalk

Hello .. after i instal an official lollipop using odin i notice that my battery mah drop from oroginal 2600mah to 2100mah i using many programs like aida64 and battery monitor widget and every program told me my battery is only 2100mah and i think the mah is reading from android kernel , i downgrade the phone back to kitkat 4.4.2 and the battery mah reading was correct and back again to 2600 so i think it was a mistake during the install of lollipop so i download the newer firmware available -I9515XXU1BOE3- and upgrade my firmware again but the problem come back again with wrong battery reading only 2100mah, i try to wipe the battery state and make calibration but nothing solved i downgrade the phone and upgrade it again and the problem appear every time ... could any one please help me how to solve this problem ... thanks in advance

hunter777 said:
Hello .. after i instal an official lollipop using odin i notice that my battery mah drop from oroginal 2600mah to 2100mah i using many programs like aida64 and battery monitor widget and every program told me my battery is only 2100mah and i think the mah is reading from android kernel , i downgrade the phone back to kitkat 4.4.2 and the battery mah reading was correct and back again to 2600 so i think it was a mistake during the install of lollipop so i download the newer firmware available -I9515XXU1BOE3- and upgrade my firmware again but the problem come back again with wrong battery reading only 2100mah, i try to wipe the battery state and make calibration but nothing solved i downgrade the phone and upgrade it again and the problem appear every time ... could any one please help me how to solve this problem ... thanks in advance
Click to expand...
Click to collapse
It's normal. It's just wrong reading the battery capacity in lollipop. But, actually it is 2600mAh. It doesn't matter.
Sent from my Galaxy S4

I found undervolting could save up to 25% battery on my Nexus 4. I dropped it by 100mv which sounds a lot, but the device ran just as stable for I'd say 99% of the time. The only time I ever had a problem was if I started to take burst photos on the camera. I actually looked at recompiling the Camera apk to ramp up the the voltage ever so slightly.

:::fajri13::: said:
It's normal. It's just wrong reading the battery capacity in lollipop. But, actually it is 2600mAh. It doesn't matter.
Sent from my Galaxy S4
Click to expand...
Click to collapse
thank you for your answer ... i want to know is this a common problem when upgrading to lollipop and if any one else face this problem with wrong mah battery capacity

hunter777 said:
thank you for your answer ... i want to know is this a common problem when upgrading to lollipop and if any one else face this problem with wrong mah battery capacity
Click to expand...
Click to collapse
Do not worry, it is not a common problem but I had this some months ago on a leaked TW ROM. The problem fixed itself when I flashed CM12.1.
There is no impact on battery life.

Undervolting

Hello guys
I'm not a new user in kernels or ROMs .
I have a low-decent battery life ,and I'm sure there's a way to get a better battery life with undervolting .
I want to know
what is "undervolting" ?
What is the biggest damage it can cause?
What is PVS?
How do I know ,how much I can UV?
What are the steps to undervolt?
What I gain from UV (despite battery life)?
For your info ,I'm using AOSPAL ROM +FAUX's latest 16u kernel .
Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app

http://forum.xda-developers.com/showthread.php?t=2537000
Sent from my Nexus 5 using Tapatalk

Hi,
Most of your questions have a reply:
About undervolting: http://forum.xda-developers.com/google-nexus-5/general/nexus-5-undervolting-thread-t2537000.
CPU binning: http://forum.xda-developers.com/google-nexus-5/general/cpu-binning-nexus-5-t2515593.
The "risks" are instability like hard reboot, SOD, etc.... To find a "safe" value you will need to test by yourself to find what undervolting your CPU can handle, not all CPU's are equals.
Undervolt by steps like - 25mV, don't set your new values at boot unless your are sure it's stable (or you could encounter bootloop), test for a few days under different conditions (as your use).
The gain apart battery life (but you will not gain that much as people tend to think) is a little less heat, but again nothing huge..., better is to test by yourself and see what you will gain... or not.
Battery life depends mainly of your use, apps, signal quality and settings like, screen brightness, synchro, CPU governor, etc... In my opinion check first what could be the cause of your low battery life (and what is low battery life for you???) before play with undervolting.

As said above, undervolting will get you very minor battery life increases.
More than likely you have an issue, or its just your setup and usage giving you the battery life you are seeing.
Undervolting will not change any of this.... You'll gain only minutes of battery time.
Try some troubleshooting in the below thread to see if you have an issue, or how to setup for better battery life. Read through it a bit, from the last page and work back a bit. You can post meaningful screenshots there too. From gsam or BBS.... not the stock battery screen, it has no real useful info for finding issues. Good luck!!
http://forum.xda-developers.com/showthread.php?t=2509132
Nexus 5 Battery Results

I've been undervolting many systems for many years, primarily Linux desktops and some servers, and the primary benefit is that you get less heat output which means when running cpu-intensive tasks the temperature climbs slower so the throttling of the clockspeed kicks in later, so your phone will be faster in certain situations. If you take a phone which has been idle for a while and run a benchmark, and then immediately run that benchmark again, the 2nd time gets a lower result as the phone is still hot from the 1st. This makes drawing conclusions about settings really dificult but it illustrate that throttling from heat is affecting speed.
For most users their perception will be the phone runs cooler.
You do undervolt at each step in the processor's frequency, and each step is a trial+error activity, the throttling I mention means finding a stable under-volt at the higher frequency which is labour-intensive,i.e take the max clock, and undervolt it a little, run a benchmark which forces it to run at high clockspeed, and if it passes that test then run it again at the next step down in frequency. Once you've got the most stable top clockspeed, then do it progressively for all the other voltages on the way down.
In some platforms in Linux and Windoze, we wrote scripts which save the stable voltages and then undervolts a little and runs a stress-testing benchmark and if the system hung it wouldn't save the current voltages so the previous higher voltages were safer, stick that script in a startup script area and leave the compute to do many self resets, and you've calculated your device's voltage range. I wonder if someone has that done for Android??? For a laptop the FAN would run slower saving battery time and for laptops that would lead to say 20% better battery life but on a phone it won't make much saving as no fan.
Your phone will run most of its time (like 95%) at its lowest frequency, so for effort/benefit just focusing on dropping its voltage will gain the most in the phone running cooler.
Battery life improvement is marginal, if you look at your battery stats its down to your application settings and screen brightness, i.e. how you use and what you do with your phone. So if your battery life is bad, use your phone less!
I carry a slim USB battery, it is the $/effort/benefit the best thing you can do, $20 doubles your battery life, if you get one with a 1.5A-2A output in just a few minutes when the phone doesn't mind a battery attached, will dwarth every possible tweak and hack anyone can form in benefit.

Power Users: Post Your Optimal Setup!

This thread is intended to have power users post their best configurations so as to guide the rookies in optimizing their MXPs once they get unlocked and rooted. It's also intended to compare the best setups for battery, performance, gaming, multitasking, etc.
My main interest is in battery life, although lately I've been on the XDA Labs app like crazy and it's hurting my drain.
Constructive criticism welcome on how to improve the below records!
ROM: Stock MM Canadian
Kernel: Ultra Kernel R3
Governor: Smartmax
Frequencies: 200 big, 800 little
Xposed Framework modules: Force Fast Scroll, Lucky Patcher, GravityBox (duh!), Use USB For Marshmallow, Xposed GEL Settings
Best SOT: 8 hours
Best Drain (100% to 0%): 120 hours
Other miscellaneous tweaks: Shake Flashlight as a system app instead of double-chop (works great, just don't let go)
Launcher: Still figuring that out...but Nova and DarkLauncher are worthy contenders right at the moment
Voice Assist/Google Now on long-press Home: Disabled thanks to @pijes. Settings > Apps > Gear icon > Default Apps > Voice and Assist > None
Post below, power users! What's your best setup so far?

Bro, I would like you use Greenify and DS Battery saver
As you have xposed framework installed you can use boost mode in greenify and also
DS Battery saver also has a module so activate them and then choose slumberer and phew see your battery stats
Coming to launcher, right now Arrow launcher is good and smooth and I prefer that
Thank you!

ashwath230 said:
Bro, I would like you use Greenify and DS Battery saver
As you have xposed framework installed you can use boost mode in greenify and also
DS Battery saver also has a module so activate them and then choose slumberer and phew see your battery stats
Coming to launcher, right now Arrow launcher is good and smooth and I prefer that
Thank you!
Click to expand...
Click to collapse
Cool man thanks. I'll try the Greenify and DS you recommend. I've seen Greenify a lot around XDA. I'm excited to try it.

Tesla rom(seems faster/smoother then stock/anyother rom) plus Squid kernel. Governor is set to Lionfish and I/O scheduler is set to Row with 512kb readahead. Minimum frequency for the Big cluster is 800mhz and 499mhz for the little cluster. NFC and location disabled. Best battery life I ever got was with stock with the same kernel/settings configuration, had 9 hrs SOT and nearly 24 hrs overall.

xtremeed2705 said:
Tesla rom(seems faster/smoother then stock/anyother rom) plus Squid kernel. Governor is set to Lionfish and I/O scheduler is set to Row with 512kb readahead. Minimum frequency for the Big cluster is 800mhz and 499mhz for the little cluster. NFC and location disabled. Best battery life I ever got was with stock with the same kernel/settings configuration, had 9 hrs SOT and nearly 24 hrs overall.
Click to expand...
Click to collapse
What do you mean nearly 24 hours overall - how long before you had to recharge?
I need to learn more about I/O scheduling. I've changed to Row and 512 as you recommend but where will I see the difference? When I connect to my PC? When apps access internal storage?
I've changed my governor back to lionfish. Smartmax wasn't doing it for me. 200 big 800 little. I'll look into that Tesla ROM too.
I was hoping this thread was gonna be more popular. I hope some people have gotten use out of it so far! Grow little thread, grow!

It would be awesome to see more growth in this thread! It would enable prospective buyers to talk to current owners, and figure out what they might want before they sink money into the device!
*cough*cough*
Which is exactly what I was hoping to do! Does anyone know if sweep to wake/sleep is possible with the Moto X Play? It's honestly one of the most useful features I've ever seen from rooting et al.

I'll post my setup. Been using it this way for like 2 weeks so I feel it's stable.
I'm currently running this:
Unlocked BL obviously
Stock Canada firmware (MPD24.65-18)
Rooted
Xposed Framework installed
Squid Kernel r14b
I have gravity box installed and that's really it as far as tweaks and stuff.
Averaging 5 or 6 hours SOT down to about 25% or 30%. Really depends on what I do and what network I use. Performance is great too.
I'm gonna mess around with some of this stuff tonight and see what I can do with it.
Sent from my XT1563 using Tapatalk

I'm trying the interactive governor in Squids kernel, some of the stuttering issues have disappeared. Like when I clear all recents in the task switcher screen or scrolling big web pages.
Sent from my XT1563 using Tapatalk

Marshmalux. Rooted. Xposed. Greenify. Powernap. Amplify.
Getting sot around 5.5 hours for my usage. Happy with that squid kernel latest r15. Lionfish on both cores
Sent from my XT1563 using Tapatalk

JohnHorus said:
It would be awesome to see more growth in this thread! It would enable prospective buyers to talk to current owners, and figure out what they might want before they sink money into the device!
*cough*cough*
Which is exactly what I was hoping to do! Does anyone know if sweep to wake/sleep is possible with the Moto X Play? It's honestly one of the most useful features I've ever seen from rooting et al.
Click to expand...
Click to collapse
Hey hey. Thanks for posting!
I'm sure sweep to wake is possible on the phone in some way, likely through a combination of rooting and Xposed modules. I know that GravityBox has a double tap on status bar to sleep feature.
One of the nicest features of the X Play is the Moto Display. It's nice to have the phone screen come.on showing notifications without fully waking the phone. Check out the Moto Display app on the Play Store. It's a totally sexy feature.
I'd say this phone is absolutely worth it for the battery alone. I personally feel the camera to be laggy especially with focus, so consider that if you're a shutterbug. I am very hopeful that software updates will being out the power of the camera but it doesn't have optical image stabilization so blir happens more frequently, at least for me. That could be my shake fingers though.
Feel free to ask any further questions!

brian10161 said:
I'm trying the interactive governor in Squids kernel, some of the stuttering issues have disappeared. Like when I clear all recents in the task switcher screen or scrolling big web pages.
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
Good stuff. Interactive does appear to handle web pages better. I did a Wikipedia search for The Simpsons and got a huge page. I flicked down to scroll it all at once and then Chrome froze. Hahahaba. Same with Lionfish though. Maybe I'm getting greedy thinking this phone is as powerful as my PC.
Lionfish was giving me great SOT results. Like I mentored in the OP: 8 HOURS! Was so happy to see that. Blew the socks off my Nrxus 4. I average between 6.5 and 8 usually, but WhatsApp and XDA Labs are hurting those scores now.
I haven't had to Greenify any apps yet - I only hsvr geeky ones installed anyway so they never keep the phone awake.

Gopinath15 said:
Marshmalux. Rooted. Xposed. Greenify. Powernap. Amplify.
Getting sot around 5.5 hours for my usage. Happy with that squid kernel latest r15. Lionfish on both cores
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
I think @squid2 deserves a lot of credit for extending the X Play even further. His kernel and work on TWRP make the X Play even more attractive than it is out of the box.
I prefer Ultra kernel personally because I believe the dev for that (@technoander) takes the latest releases of squid's and adds features to them. I may be mistaken but that's my impression. I'll try to clarify and report back. I should do a direct comparison of Ultra and squid's latest to be as objective as is possible with a subjective test. Hahaha.

I guess I should specify a bit further - sweep/tap2wake is really only effectively useful when the phone supports some kind of low-power state for the touchscreen, otherwise the screen has to remain on in order to use it.
I'm sure sweep2sleep would be possible, but if there's no low-power state for the screen, it wouldn't really matter for me in the end. Moto display sounds like exactly what I'm talking about, though I don't know if it includes any low power mode for the touch features, as well as the display.
I'm gonna look into this a bit more, and see if I can dig up any info. It would be a hardware feature, designed-in, so it definitely should be discoverable. I figure if I can find out all the information for one of the people who have written kernels for the phone, they shouldn't have a problem emulating the feature. It's popular enough, and with the low-power state, shouldn't be too complex to implement.

JohnHorus said:
I guess I should specify a bit further - sweep/tap2wake is really only effectively useful when the phone supports some kind of low-power state for the touchscreen, otherwise the screen has to remain on in order to use it.
I'm sure sweep2sleep would be possible, but if there's no low-power state for the screen, it wouldn't really matter for me in the end. Moto display sounds like exactly what I'm talking about, though I don't know if it includes any low power mode for the touch features, as well as the display.
I'm gonna look into this a bit more, and see if I can dig up any info. It would be a hardware feature, designed-in, so it definitely should be discoverable. I figure if I can find out all the information for one of the people who have written kernels for the phone, they shouldn't have a problem emulating the feature. It's popular enough, and with the low-power state, shouldn't be too complex to implement.
Click to expand...
Click to collapse
Cool - definitely report back - it would be nice to know if this is embedded in the hardware somewhere. I hope it is, unlike optical.image stabilization. Damn!

XxMikeMasterxX said:
What do you mean nearly 24 hours overall - how long before you had to recharge?
I need to learn more about I/O scheduling. I've changed to Row and 512 as you recommend but where will I see the difference? When I connect to my PC? When apps access internal storage?
I've changed my governor back to lionfish. Smartmax wasn't doing it for me. 200 big 800 little. I'll look into that Tesla ROM too.
I was hoping this thread was gonna be more popular. I hope some people have gotten use out of it so far! Grow little thread, grow!
Click to expand...
Click to collapse
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.

Hey developer,the banking apps I have does run after flashing a custom rom.Is there any workaround for this?.have to reflash stock after trying any custom rom.Its a pain in the as*.

xtremeed2705 said:
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.
Click to expand...
Click to collapse
Row is essentially the best scheduler. Benchmarking is weird, because by design it's an optimized test case and not a use case. Use cases will always be variable, but generally with a smartphone writes aren't too latency-sensitive. That's why Read Over Write generally works the best once your phone is settled, because reading is most of what it does. Doesn't write too often.
There are lots of custom governors, not so many custom schedulers, and lots of suggestions, but generally stock *IS* best, and if you don't understand it, you should not change it. Governors are fun to play with but even they can cause issues if poorly coded. Changing governors will give you a huge impact on battery, but also a relative impact on performance. It all depends on the use context. You'll rarely get much battery life without a performance hit unless you custom-tune settings for your own use context.
As for read-ahead, that value is iconic of exactly what I'm talking about. It is the "chunks" of data that your OS reads in one go. So if it needs 2k, or 2m, it reads a different number of chunks, but each chunk will be the size set by I/O read-ahead. Google likes 512 best. I've been told by the dev for the EX Kernel that internal Motorola devs like 128 best. Benchmarks like the biggest value possible, because they present the OS a massive pile of data and ask it to read it all as fast as possible. In that context, a large chunk size saves time. In most contexts, you read more than you need half the time. So a low value like 128 saves battery and memory.
---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------
kiran91 said:
Hey developer,the banking apps I have does run after flashing a custom rom.Is there any workaround for this?.have to reflash stock after trying any custom rom.Its a pain in the as*.
Click to expand...
Click to collapse
Android pay does this too, it's a "security" feature built-in by the devs to stop hacking. Not really necessary, but then neither are smartphones, so you take what you can get I guess. No ROM developer can work around this for you. The app is detecting any modification whatsoever. Even root may cause it.

xtremeed2705 said:
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.
Click to expand...
Click to collapse
Badass dude. 9 hours SOT is wicked.
I'm finding the phone app drains the battery like crazy. Is this to be expected?

Hey @JohnHorus - thanks for your informative post. I'm currently trying Row 128 and will report back but I doubt I'll see any real-world difference in use. Memory and battery are two soft spots for me so I'm hopeful 128 will maintain solid performance.
Looking forward to reading about others' setups!

XxMikeMasterxX said:
Badass dude. 9 hours SOT is wicked.
I'm finding the phone app drains the battery like crazy. Is this to be expected?
Click to expand...
Click to collapse
Yeah in my experience it drains the battery more then doing other things for some reason. As you can see in my 9 hrs picture I only used the phone for like 2 minutes lol.

Best CPU settings in Kernel Aduitor for good battery life

I am running MoKee with pretty decent battery life but am currently experimenting with reducing screen resolution and tweaking CPU & GPU settings (using Kernel Aduitor) to see if I can squeeze more out of a charge. Not really sure what the best settings are to maximise battery while keeping smooth everyday performance (I don't game or do any very heavy tasks or multitasking). I thought that it might be possible to get near SD625 stamina from the SD820 seeing as they are both built on the 14nm process, but the architecture is very different (ours has the quad-core big little set up with kryo, as opposed to the 625's octa-core A53 set up). At the moment I am trying it with the little cores left at default and the big cores max frequency down clocked by about 25%. I haven't changed the governors. I also down clocked the GPU max frequency a bit. Anyone have any advice regarding an optimal set up?

Not sure about the best settings but for sure I'm waiting for your feedback regarding this change and battery life. It should be improving it, but nobody knows how much.
Also I've noticed that in youtube if there is 720p or 1080p, the default setting is 720p (of course our screen is a multiple of 720p).
Are the pixels visible?

Couldn't see pixels with reduced screen resolution, even at 720p. Of course it's only rendering a lower resolution image then stretching it over the physical
1440p display. The result is just a softer image. Looks a bit strange, but 1080p wasn't too bad. However, didn't seem to have any effect on battery life and surprisingly at 720p I got a worse Antutu score than normal, so I have given up and returned to 2K.

I feel sorry for that I was really hoping for some way to increase the battery life a bit.

Hey guys... Today I found something interesting in our German Android forum. There's a group of people who are developing a great Rom for our device. It's just called the telegram Rom.
So the Rom will include scripts tweaks and a full working app for changing governors. So you will be able to get a much better battery life. The German guys talking about 20 to 30 percent extra power for our device.
The hole project behind this was founded here on xda but mainly developed for the Oneplus-3.
But in fact the whole workaround is working on any device that's running a SD820 processor.
Here is the link to the site
https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589
So maybe you like to have a look. There are also complete explanations of how the SD820 works related to energy management and voltage at minimal and maximum clock speed!
I hope this can answer your questions.

Thanks for sharing Lizard82.
I follow the thread and use AKT... i am using the profile called Project Zhana & X.A.N.A v4.2. 14 hr sot is unheard of but I am getting close to 6hrs sot with xposed loaded which I am already impressed. It is is way better then what I used to get around 3 hrs sot. I am running revolution 21s rom which is very similar to EUI and not the most optimized rom with heavy battery drain. and I am happy that this phone finally has a good battery life. Appreciate Lizard82.

The sot really depends of what you do with the phone, and what apps run when the phone is on idle. I changed the resolution to 1080p but didn't notice any difference, so I went back to 1440p. There are tons of threads about kernel Adiutor, you won't have a hard time finding it

For best battery on Nougat I did this on Nexus 7.1 and AOSP 7.1 roms with BS kernel:
- Use rom that can use Black Screen kernel 2.1/2.2 or later
- Use kernel Adiutor to change CPU governor to impulse (or Darkness)
- Set value in Govenor tuneable (locate just under CPU Governor touch it to go inside to change value) : highspeed_freq to 307200, set Powersave_Bias to 1. I changed both BIG and LITTLE CPU core in kernel Adiutor.
- I think keep AKT profile on stock/unchange no need to set it is ok