Database Info

PowerSaverKernel - Usb battery drain bugs solved [UPDATED 2011/08/07]

In this thread you will find a set a patches I've applied to pershoot's
kernel2635 source (https://github.com/pershoot/kernel-2635.git) in a
attempt to compile my own kernels and to fix the long standing and not cared of usb
battery drain bug (able to eat your battery in less than 2hrs).
A (outdated) list of the applied patches is:
001-fix_msm_clock_warning.patch
002_fix_msm_nand_warning.patch
003-2.6.35.13-sched-bfs-404.patch this is by Con Kolivas http://ck.kolivas.org/patches/bfs/2.6.35/
004-bfs_fix.patch
006-msm_evlog_fix.patch
007-hw3d_refdata.fix
008-htc_pwrsink_refdata.patch
009-board_trout_sapphire_fix.patch
010-eventpoll_fix.patch
011-dm-crypt_fix.patch
012-mt9t013_fix.patch
013-msm_smd_fix.patch
014-pm_fix.patch
016-mddi_refdata_fix.patch
017-lowmemorykiller_fix.patch
022-adb_2.6.29_forward_porting.patch
023-htc_battery.patch
024-msm72k_udc.patch
025-patch-2.6.35.11-12
026-BFQ-v2.patch
027-BFQ-v2-r1.patch
028-smd_rpcrouter.patch
029-audpp_missed_DMA.patch
030-msm_serial_hs.patch
031-irq_pm.patch
032-smd_tty.patch
033-linux-2.6.38.y.git-524429c31b486c05449666b94613f59f729c0a84.patch
034-10mb_32A.patch (MT1.2/Old 32a memory map)
035-9aa258a27b6183e8e80241e4820883eaed23139f.patch (Magic Plus (32a) extra 10MB ram)
036-kmalloc_b0937124b376946a5c93504f34ac932dffb23e3e.patch
037-2.6.36_lowmemorykiller+fudgeswap.patch
038-minfree_stats-bb4a7baa64d9a56124e1f13510e9688aeed0cc10.patch
039-msm72k_udc_fix_msm.git-1aa53ebd36088a60fcf4a498f763358598a477b9.patch
040-synaptics_warning_fix.patch
041-BFS-401-2388fb7aee855019c4a7560efb54cc7550a09743.patch
042-BFS-rr_interval_335f482a0274a640ae6ab1a0036a3b263de575b6.patch
043-i2c_msm_a146e17dd81a2e4eaf67928c945038f521409384.patch
044-BFS-1000Hz.patch
045-patch-2.6.35.12-13
046-zram.patch
047-vzalloc_for_zram_linux-2.6.38.y.git-e1ca7788dec6773b1a2bce51b7141948f2b8bccf.patch
049-pmem_c21c461ce3e32d26abebe6243039824839748dc5.patch
050-gingerbread_gadget_update.patch
051-adb_2.6.29_forward_porting.patch
052-msm72k_udc.patch
053_msm72k_udc_warning_fix.patch
054-ae9bd4d574b7b8480aee162273d58d0c3840510a.patch
055-ARM-zImage.patch
056-wifi-3e6f7025178699b354e0e9fd94331f47ebb82763.patch
057-arm-mm-cache-ecce0382ee54a765abcdc982e01a5fd30099f52d.patch
058-autogroup patches
059-patch-2.6.35.13-14
060-cpufreq_stat_fix.patch
configs for 2708, ebi0 and ebi1
Please refer to the attached patches.zip files for the latest
patch series.
Main features of this kernel are:
BFS (in the BFS versions)
BFQv2r1
Overclocking
various fixes and minor enhancements
autogroup patches (in the autogroup versions)
BUG 1 (adb):
Patches 1-2, 4-17 are rather trivial stuff as they just silence some warnings.
Patch 22 is the one that seems to fix or reduce the "usb battery drain bug"
in the sense that after applying this patch I was not able to trigger the bug
again and I've tried several times the last days. The same result was reported
by a few courageous testers that risked to install one of my precompiled kernels
and whom I would like to thank for their collaborative effort.
The steps used to trigger the bug were:
plug in usb
start adb session
remove usb plug
check if a sticky android os entry is in the battery stats (a sure sign of incipient drain)
The patch reverts f_adb.c to be more similar to how it was in kernel 2.6.29-msm.
Similar code could also be found in HTC's 2.6.35 sources for the Incredible S
at http://dl4.htc.com/RomCode/Source_and_Binaries/vivo-2.6.35-g89aa373.tar.gz
so it could also be a alternative to use this code base for future G1 kernels.
Attached you'll find also the config I used to build the kernels posted
in the ezGingerbread thread and in Enomther's thread.
I hope this patch fixes this bug also for you as it did for me
making me a happy G1 user again.
I would thank to all who collaborated to this effort with facts
or with their wise words and advices.
BUG 2 (drain after reboot with usb connected):
After studying more and more bug N°2 and thanks to the comments of the posters who sent me in the right direction
I've made a good progress. It is very early to call it a conclusive solution yet, but I was able to reboot my phone
with usb connected and after 3 hrs it is fully charged.
What did the trick was to disable:
CONFIG_SERIAL_MSM
in the kernel. I don't know what it was there for but at least
on my G1 I've tested all basic functions:
phone call
sms
data
wifi
BT
adb
music
GPS
and every thing seems to work. More test are needed tough,
there are also some minor leftovers to fix (more on this
in the next days).
For the bold a new kernel to test (tested on enomther's rom,
so I don't know if it will work on other roms).
You'll also find a VERY EXPERIMENTAL
anykernel/autokernel flashable zip archive with
EBI0/EBI1/2708+ kernels. Use it AT YOUR OWN RISK
and kindly report success or failure while flashing.
I cannot test it on all device/ROM combinations
so it may or may not work for you.
MAKE A BACKUP BEFORE USING IT so if something
goes wrong you can restore your previous rom.
I can give you very limited support due to missing
free time nonetheless patches are welcome!
Autokernel with BFS v0.401 and 1000Hz Kernel timer resolution for Froyo (discontinued):
auto-boot-2.6.35.13-farmatito-pershoot-ds-BFS+-20110428.zip
http://www.multiupload.com/8CKICMRK6B
MD5SUM 999770a413cbe93be75e00b1529f2300
Autokernel with BFS v0.404 for Gingerbread (experimental):
auto-boot-2.6.35.13-farmatito-pershoot-ds-BFS+-20110518.zip
http://www.multiupload.com/YRXWMK1AY3
MD5SUM c1373c915c8bfe3ebb470e839756a735
Standard Autokernel for Froyo (discontinued):
auto-boot-2.6.35.13-farmatito-pershoot-ds+-20110428.zip
http://www.multiupload.com/LLMKG4TRTO
MD5SUM ee3f5c53b4871076f123491c9dc388e2
Standard Autokernel for Gingerbread (stable):
auto-boot-2.6.35.13-farmatito-pershoot-ds+-20110505.zip
http://www.multiupload.com/0SJ77OM4HA
MD5SUM61a8bb913ca43a355e1eef3152b008db
Standard Autokernel for Gingerbread
with autogroup patches and memory compaction (experimental):
auto-boot-2.6.35.14-farmatito-pershoot-ds+-20110802.zip
http://www.multiupload.com/3NJ7Q0Y4TN
MD5SUM 27536ef42348dd92bb006cd8511df5d9
This kernels are unsupported they worked for me and I hope
they work for you, feel free to report problems and I will try to
fix them depending on my free time and skills.
USE AT YOUR OWN RISK. NO WARRANTY.
Enjoy
Changelog
v 20110425:
fixes to the installer automagic.
v 20110428:
BFS v0.401 + 1000Hz kernel timer resolution (BFS-version only) + rr_interval tuning.
i2c_msm HTC update
updated to 2.6.35.13
V 20110505:
revert kernel timer resolution to 100Hz
revert rr_interval tuning (BFS version)
update android gadget to gingerbread version.
V 20110518:
BFS v0.404 in the BFS versions
V 20110612
Compensate for rounding on odd-frequency clocksources
zImage fixes
Enable Memory Compaction
wifi - Don't make disabled irqs wake the device
cache-l2x0: Correct l2x0 initialization
autogroup patches
V 20110802
update to 2.6.35.14 (autogroup version only)

I'm glad to see someone working to fix the USB bug, I hope it will be squashed in pershoots official builds eventually as well

Good work! Will try it out.
A while back everything on my screen froze (time and battery level not updated) but otherwise the phone worked 100%, however the battery lasted 2 days and 20 hours (68hrs with wifi on, 3G on, 614 overclock, browsing and gmail, etc). Weird

Forgive me if my question feels like a noob but exactly how should we apply this zip file.....should I flash it?.... OR....it has to be installed through adb (or terminal emulator?)
I read the OP but couldnt make about the methos of installing it....(kinda stupid of me I know...
Is it OK to use your kernel instead of this patch?....do they have same effect?

dilwaladoctor said:
Forgive me if my question feels like a noob but exactly how should we apply this zip file.....should I flash it?.... OR....it has to be installed through adb (or terminal emulator?)
I read the OP but couldnt make about the methos of installing it....(kinda stupid of me I know...
Is it OK to use your kernel instead of this patch?....do they have same effect?
Click to expand...
Click to collapse
The patches in the zip need to be applied to the kernel sources, built and then
a anykernel zip installer must be created. Then you can flash it.
You can try also a precompiled kernel if it is compatible with your rom.
So best is to take a nandroid backup in case things go bad.
I suggest you to wait that it is included by the devs of the rom you use
if they see it fit.

Well done for keeping at it

My testing is as follows
Using the ezGingerbread binary on a clean ezGingerbread install with gapps+facebook but no wifi or sim:
The USB connection in use is just a wire to my macbook.
0) battery validation: boot system from battery only and leave for extended time.. I was at 83% after 13h.. this indicates no particular extra drain thus this test passed
1) basic test: boot while phone charging on macbook, after system is fully loaded unplug from USB, replug, unplug again.. this case the phone was drained in under 13h thus indicates the USB drain is present test failed
2) adv. test: boot phone on batter such as test 0, after test 0 drained to say 79% charge with usb slightly, the unplug usb again and leave.. hours later indicated no significant drain test passed.
3) adv. test 2: now at 60% after test2 plug into usb reboot and unplug after fully loaded.. such as in test1 drain quickly continued test failed.
Thus we seem to have a form of USB drain that is not in the 2.6.34.* kernels, however it may be possible on this kernel to avoid it by booting the phone on its own power (I did not test booting the phone on the A/C adapter, least not yet and more testing is needed to be sure there is no other oddities)

@ezterry :
so if understand it correctly it is booting/rebooting with
usb plugged in that still fails?
Do you see the same stuck "android os" entry in battery stats?
If not, than maybe it is a different bug, so more patching is needed.
UPDATE:
test:
plug in usb
reboot
wait a little while phone is charging
unplug usb
go to battery stats:
there you'll see "android os" entry
hit a few times refresh
"android os" %value decreases and after a few more refresh hits it disappears.
I think that if there is battery drain in this case it is not the same bug.
Will check the phone later to see how it behaves:
16.59 84%
18.18 77%
20.42 68%
16 % / 4hrs = 4% /1hrs (in idle state)
Looks not so bad to me... but definitely would not last
48+ hours as my battery usually lasts.
In my opinion this is not the same bug tough, because
what I and other users were experiencing was a very
fast battery drain after disconnecting from a adb
session. The latter bug is indeed fixed.

After more testing with this bug N° 2 triggered the power
consumption with my extended battery is stable at about
4%/hr. I've looked at the most likely candidates
htc_battery.c
msm72k_udc.c
but I've not spotted differences between 2.6.34.8 and 2.6.35.11
that could explain the different behaviour.
Hints and help is welcome.

Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?

VAMCAVALO said:
Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?
Click to expand...
Click to collapse
Check out post for and five on this page.
Sheesh
Lol
Sent from my Dream/Sapphire using XDA App

VAMCAVALO said:
Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?
Click to expand...
Click to collapse
There's a few ways to improve you battery life. I went crazy myself, and finally got it working great.
#1 If you're still using the original battery in your G1, it's probably time to replace it.
#2 Some roms do better with battery life, some don't.
#3 Be careful what radio you use. The radio 2.22.27.08 is probably better for USA users, while 2.22.28.25 is better for other countries.
#4 Trying disabling stuff you don't use. Turn off Auto-sync, if you don't need constant updates for E-Mail and contacts backup. You most likely don't. Disabling background data helps, but you'll need to enable it to use any data. Disabling Data under network settings has no effect in how your phone functions, but does decrease battery drain.
#5 Try changing the clock speed of your phone. Most good roms come with built in overclock, and you can change the min CPU frequency to lower then 245 Mhz. Be careful in how much you lower it, cause anything that happens on your phone will kick in the Max CPU frequency, and suck battery power.
#6 Make sure everything is working, like the camera. For months I was going crazy on my battery drain, and just recently discovered my camera wasn't working. Turns out, the camera cable was slightly disconnected. This can easily happen, since the cable sits right under the battery. Took phone apart, plugged it back in, and now battery lasts for 2 days.
#7 Of course, make sure no services are running in the background. Running applications in the background can force your hones CPU to run at max speed.
As for the USB drain bug, basically when you plug your phone in to your PC, it can drain the crap out of your battery. So charging your phone with your PC is a bad idea, and you'll have to reset it to avoid it draining so fast.

Dukenukemx said:
There's a few ways to improve you battery life. I went crazy myself, and finally got it working great.
#1 If you're still using the original battery in your G1, it's probably time to replace it.
#2 Some roms do better with battery life, some don't.
#3 Be careful what radio you use. The radio 2.22.27.08 is probably better for USA users, while 2.22.28.25 is better for other countries.
#4 Trying disabling stuff you don't use. Turn off Auto-sync, if you don't need constant updates for E-Mail and contacts backup. You most likely don't. Disabling background data helps, but you'll need to enable it to use any data. Disabling Data under network settings has no effect in how your phone functions, but does decrease battery drain.
#5 Try changing the clock speed of your phone. Most good roms come with built in overclock, and you can change the min CPU frequency to lower then 245 Mhz. Be careful in how much you lower it, cause anything that happens on your phone will kick in the Max CPU frequency, and suck battery power.
#6 Make sure everything is working, like the camera. For months I was going crazy on my battery drain, and just recently discovered my camera wasn't working. Turns out, the battery cable was slightly disconnected. This can easily happen, since the cable sits right under the battery. Took phone apart, plugged it back in, and now battery lasts for 2 days.
#7 Of course, make sure no services are running in the background. Running applications in the background can force your hones CPU to run at max speed.
As for the USB drain bug, basically when you plug your phone in to your PC, it can drain the crap out of your battery. So charging your phone with your PC is a bad idea, and you'll have to reset it to avoid it draining so fast.
Click to expand...
Click to collapse
Thank you for the answer!
#1 I already replaced the battery
#2 I am using the Laszlo Froyo and it's know for your not so good battery performance.
#3 I from Brazil but using 2708 radio...should I change it?
#4 Only 2G and all unnecessary stuff its out.
#5 I use the laszlo built-in CPU settings at Extras>Performance at 176-528 ondemand.. it is OK?
#6 I'm sorry but I didn't understand your problem at this point. Which battery
cable? Mine camera it's OK right now..
#7 I'm pretty sure that I know there is no app in background but there is some way to check this out?
a) And I tried to flash today the 2.6.35.11 kernel to see if it help because with laszlo rom, my G1 became really nice again but the battery sometimes make me not that happy.
b) When I charge at PC (often), the only thing I need to do is to reboot after unplug, right?
Thank you very much

VAMCAVALO said:
#3 I from Brazil but using 2708 radio...should I change it?
#5 I use the laszlo built-in CPU settings at Extras>Performance at 176-528 ondemand.. it is OK?
#6 I'm sorry but I didn't understand your problem at this point. Which battery
cable? Mine camera it's OK right now..
#7 I'm pretty sure that I know there is no app in background but there is some way to check this out?
Click to expand...
Click to collapse
#3 You'll have to experiment to see which radio works best for you. I used 2825 before realizing that I never tried 2708. For me, 2708 was way better, but what works best for me might not be best for everyone. Since radios are made for specific regions.
#5 I'm also using Laszlo CPU settings like you are. BTW, same rom but my battery lasts for 2 days.
#6 I worded that incorrectly. I meant to say that my camera cable was lose, and the camera wasn't working. I didn't know this, cause I didn't use the camera for months. I fixed it, and now my battery life is 10x better. The cable for the camera sits under the battery, and can easily be pulled lose by dropping the phone.
#7 Aftermarket apps from the market provide the best way to check. Though if you're sure, then don't bother. It's not hard to see if an app is running still.
a) I'm using the kernel that came with Laszlo rom, but I've found that ezBiffTestKernel20110222-2708_S.zip works great for most roms.
b) Yea reboot after you unplug it. My battery has been doing so well lately, that I can wait till I get to my car to charger it. Using my car charger to avoid charging with the PC. [/QUOTE]

Dukenukemx said:
#3 You'll have to experiment to see which radio works best for you. I used 2825 before realizing that I never tried 2708. For me, 2708 was way better, but what works best for me might not be best for everyone. Since radios are made for specific regions.
#5 I'm also using Laszlo CPU settings like you are. BTW, same rom but my battery lasts for 2 days.
#6 I worded that incorrectly. I meant to say that my camera cable was lose, and the camera wasn't working. I didn't know this, cause I didn't use the camera for months. I fixed it, and now my battery life is 10x better. The cable for the camera sits under the battery, and can easily be pulled lose by dropping the phone.
#7 Aftermarket apps from the market provide the best way to check. Though if you're sure, then don't bother. It's not hard to see if an app is running still.
a) I'm using the kernel that came with Laszlo rom, but I've found that ezBiffTestKernel20110222-2708_S.zip works great for most roms.
b) Yea reboot after you unplug it. My battery has been doing so well lately, that I can wait till I get to my car to charger it. Using my car charger to avoid charging with the PC.
Click to expand...
Click to collapse
#3 I will try 2825 so!
#5 Holy ****! Two days I can only get leaving the phone on eternal standby...
#6 Now I understand, but my camera and other functions are normal right now.
#7 I'm sorry, but what is aftermarket apps?
a) 2.6.35.11 it's know to be a better kernel on the battery performance. Right now I'm testing 35.10 and I need to wipe my battery stats because I think it can be one of the problems.
b) Ok, that is not a problem because I charge at PC lot of times, so now I will reboot after unplugging.
Well, after all of this, if nothing works, should I change my battery again? I already changed at December 10 but it is a generic one.
TKS

I just flashed the kernel and I've had good results regarding the battery drain. No more high % "AndroidOS" under the battery stats.
The only thing I found to be weird is the touch screen. It seems like the responsiveness while scrolling through the settings, homescreen, and app drawer is laggy and unresponsive. It sometimes doesn't even scroll when I move my finger across the screen. Also pulling the notification bar is very difficult as I really have to slowly drag it down.
I currently am using the newest kernel released, the 04/03 one, on CyanogenMod nightly 307 on my G1. My old kernel was the "ezBiffTestKernel20101106-2708_S.zip"
Thanks for your work on the battery drain problem.

good223 said:
I just flashed the kernel and I've had good results regarding the battery drain. No more high % "AndroidOS" under the battery stats.
The only thing I found to be weird is the touch screen. It seems like the responsiveness while scrolling through the settings, homescreen, and app drawer is laggy and unresponsive. It sometimes doesn't even scroll when I move my finger across the screen. Also pulling the notification bar is very difficult as I really have to slowly drag it down.
I currently am using the newest kernel released, the 04/03 one, on CyanogenMod nightly 307 on my G1. My old kernel was the "ezBiffTestKernel20101106-2708_S.zip"
Thanks for your work on the battery drain problem.
Click to expand...
Click to collapse
Could be due to the use of BFS, maybe I'll post a kernel without it in the next days, as I'm testing other changes
right know.

farmatito said:
Could be due to the use of BFS, maybe I'll post a kernel without it in the next days, as I'm testing other changes
right know.
Click to expand...
Click to collapse
Ah ok, but what exactly is BFS? I did a quick google search and I came across this article "http://techfreaks4u.com/blog/posts/kernel-linux-kernel-with-bfs/", but I still don't quite understand how it affects our phones.
Could you explain it in a simpler way?

First two zips froze at the G1 screen using DangerSPL & proper radio, though all of them work fine using the 2.22.27.08/2.22.28.25 radio & appropiate SPL.
The phone doesn't sleep either.
Will test performance more thoroughly tomorrow.

good223 said:
Ah ok, but what exactly is BFS? I did a quick google search and I came across this article "http://techfreaks4u.com/blog/posts/kernel-linux-kernel-with-bfs/", but I still don't quite understand how it affects our phones.
Could you explain it in a simpler way?
Click to expand...
Click to collapse
It divides cpu time more or less in equal parts to all running tasks, so all (the more cpu intensive and less intensive) have
the possibility to run in a given time period, the contra is that
the more cpu intensive tasks may slow down a little.

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.

Why did you root? Pros/Cons? Feedback please.

After giving up on a Nexus 6p with battery issues I bought a US996 V20 about a month ago and downloaded files for rooting right away. But the stock experience has been pretty good for me and I haven't actually gotten around to rooting. The phone is still on US99610d software version so it will be pretty easy to root but I'm getting sick of cancelling the updates.
I'm on the fence and would like to hear your experiences, reasoning, etc when it comes to rooting the V20.

sdc177 said:
After giving up on a Nexus 6p with battery issues I bought a US996 V20 about a month ago and downloaded files for rooting right away. But the stock experience has been pretty good for me and I haven't actually gotten around to rooting. The phone is still on US99610d software version so it will be pretty easy to root but I'm getting sick of cancelling the updates.
I'm on the fence and would like to hear your experiences, reasoning, etc when it comes to rooting the V20.
Click to expand...
Click to collapse
Yes, root, but if you could, please make a kdz for the rest of us who want root. A phone that you cannot root is a phone that should'nt exist, always root.
Edit: Pros: AdAway, Macro Programs, enhanced customization and debloating Cons: Basically none if you use MagiskSU

JerichoAbles said:
Yes, root, but if you could, please make a kdz for the rest of us who want root. A phone that you cannot root is a phone that should'nt exist, always root.
Edit: Pros: AdAway, Macro Programs, enhanced customization and debloating Cons: Basically none if you use MagiskSU
Click to expand...
Click to collapse
Thanks but not sure what you mean about the kdz. I have the unlocked version and there are already rooting instructions here.

Custom kernels which give you: Battery optimalisations: 10-30 % more battery and better performance at same time depends on which settings you chose: gouvernors tweaks..
.
Adaway, custom battery icons, more smoothness and better performance, debloat
Full controll sound: viper4android which is amazing with this dac
Full control screen colors: yellow, blue, red and more with kcal color tweaks

jody2k said:
Custom kernels which give you: Battery optimalisations: 10-30 % more battery and better performance at same time depends on which settings you chose: gouvernors tweaks..
.
Adaway, custom battery icons, more smoothness and better performance, debloat
Full controll sound: viper4android which is amazing with this dac
Full control screen colors: yellow, blue, red and more with kcal color tweaks
Click to expand...
Click to collapse
okay i am getting closer a month ago i was also discouraged about the "second screen" not functioning but it appears that has changed too!

Viper was the main reason. Adblocking is nice too but that was more of a side benefit since there are also ways to adblock without root, adaway is more convenient and flexible. Also the little things like being able to double tap to sleep in Nova using the root method works better. Performance customizations are another big thing as I keep finding more and more stuff to try (trying out AKT's mod right now to great effect so far)

About kernels

What kernels are you guys using and why? I'm on stock but willing to try out some

https://forum.xda-developers.com/oneplus-6/help/kernel-t3847767
This thread might help you.....

Currently using blu spark kernel, shifted from EX.

Im on EX. Using the stune boost recommended on the second post of his thread along with top app boost set to 1 so it gets pushed to the big cluster. Ultimate smoothness and no stutters whatsoever. I think the battery drain might be higher with the topapp setting but it lasts me the day anyways so I don't care.
I used bluspark before as well. Provided me with the best battery results but I did get some hiccups with it.
Radioactive was also speedy like EX. Didn't test it long enough to compare to the finer detail but I figured if it behaves similarly I may as well stick with EX since I'm already familiar with the work since the M7 days.

spartan268 said:
Im on EX. Using the stune boost recommended on the second post of his thread along with top app boost set to 1 so it gets pushed to the big cluster. Ultimate smoothness and no stutters whatsoever. I think the battery drain might be higher with the topapp setting but it lasts me the day anyways so I don't care.
I used bluspark before as well. Provided me with the best battery results but I did get some hiccups with it.
Radioactive was also speedy like EX. Didn't test it long enough to compare to the finer detail but I figured if it behaves similarly I may as well stick with EX since I'm already familiar with the work since the M7 days.
Click to expand...
Click to collapse
One of the perks of owning this phone it's the insane speed. I've tried Ex in the past, on the OPO mainly, to try to get some extra hours out of a worn out battery. I used to use blu on my N5 for the same reason, I remember enjoying it.
I'm wondering why would someone tradeoff stock

quimbexa said:
One of the perks of owning this phone it's the insane speed. I've tried Ex in the past, on the OPO mainly, to try to get some extra hours out of a worn out battery. I used to use blu on my N5 for the same reason, I remember enjoying it.
I'm wondering why would someone tradeoff stock
Click to expand...
Click to collapse
I am using EX kernel specifically because it supports WireGuard VPN kernel module, meaning the VPN connection to my home I have running 24/7 uses less battery and has higher throughput!
That, and the fact I have used EX kernel for many past devices, and the dev flar2 is really active with updates etc

Question S21 plus latest software. Battery life (great)

I dusted off my xda account to let you know that this latest software is great... Battery life finally doesn't drain when not used. (battery drain while not used drives me crazy, wife has iPhone... Always in use, it lasts forever)
Anyway Im the guy that never have problems, not many apps. No smart watch connected. Not rooted, not gamer, no cloud.
My battery used to drain like 15% overnight. Not anymore. It barely uses 40% a day.. Before it was about 75%.
I'm planning to freeze my software update app. Bc whatever they did is working great.
My device is more than 12 mo old, and i use the 85% charge limit (slowest possible charge). Unlocked US model directly from Samsung.

Yay.
Definitely package block updates if it's running well now.

you lucky guy! I'm waiting for the Pixel 7/7 pro and then I'll choose between them and the Zenfone 9. Samsung cheated me for the last time!
My phone is slower than my previus Op7Pro, battery drain is huge and it's always hot. I have it from July 21 but this summer the phone has been unusable under the sun or on the beach because of the huge thermal throttling. I had to splash in the swimming pool while taking photos of my children because it was very hot and went in thermal protection.
Battery life is terrible too, I've to charge at least twice a day even without using it.
Do you think is something that can be solved by the Samsung support?

deskmat81 said:
you lucky guy! I'm waiting for the Pixel 7/7 pro and then I'll choose between them and the Zenfone 9. Samsung cheated me for the last time!
My phone is slower than my previus Op7Pro, battery drain is huge and it's always hot. I have it from July 21 but this summer the phone has been unusable under the sun or on the beach because of the huge thermal throttling. I had to splash in the swimming pool while taking photos of my children because it was very hot and went in thermal protection.
Battery life is terrible too, I've to charge at least twice a day even without using it.
Do you think is something that can be solved by the Samsung support?
Click to expand...
Click to collapse
Turn off global power management, find the battery/bandwidth hogs and deal with each on a case by case basis ie optimize it. All Samsung's should be optimized for best performance.
Package Disabler is something I always use but it's not my only tactic.
Since the N10+ Samsung has lost its balance.
That said my now cool running snappy fast N10+ was once a stuttering, hot running battery/bandwidth hungry hog. It doesn't seem like the same device now, it runs like a bat out of hell. Been running like this for 2 years on the same load. All you can do is try to optimize it.
Samsung Tech support? Bah-ha-ha-ha, don't count on it. Rarely are they helpful, but occasionally you get lucky. Updates tend to break not fix things... think before you click and disable all auto updates especially firmware.

blackhawk said:
Turn off global power management, find the battery/bandwidth hogs and deal with each on a case by case basis ie optimize it. All Samsung's should be optimized for best performance.
Package Disabler is something I always use but it's not my only tactic.
Since the N10+ Samsung has lost its balance.
That said my now cool running snappy fast N10+ was once a stuttering, hot running battery/bandwidth hungry hog. It doesn't seem like the same device now, it runs like a bat out of hell. Been running like this for 2 years on the same load. All you can do is try to optimize it.
Samsung Tech support? Bah-ha-ha-ha, don't count on it. Rarely are they helpful, but occasionally you get lucky. Updates tend to break not fix things... think before you click and disable all auto updates especially firmware.
Click to expand...
Click to collapse
thanks for your suggestion, this night (when my children will fall asleep XD ) I'll try to check. Where can I find the option to disable the global power management?
About the power governor I'm using the mid option named High ( I have Optimized - High - Maximum) but I've tried the other two options and wait I've seen is bad performance (no increase in battery life) or increase of the phone temperatures with no real benefit in the daily use.
I'm hating this phone, I'm thinking to change asap, I'm waiting for the Pixels, hoping Google is able to manage the thermal issues better than Samsung.
About the support I don't mean the one by the phone, I know it's useless , I would mean if my thermal and battery problems can be related to some hardware issues.

deskmat81 said:
thanks for your suggestion, this night (when my children will fall asleep XD ) I'll try to check. Where can I find the option to disable the global power management?
About the power governor I'm using the mid option named High ( I have Optimized - High - Maximum) but I've tried the other two options and wait I've seen is bad performance (no increase in battery life) or increase of the phone temperatures with no real benefit in the daily use.
I'm hating this phone, I'm thinking to change asap, I'm waiting for the Pixels, hoping Google is able to manage the thermal issues better than Samsung.
About the support I don't mean the one by the phone, I know it's useless , I would mean if my thermal and battery problems can be related to some hardware issues.
Click to expand...
Click to collapse
It's in Device Care under battery. Individual app battery background settings don't invoke global power management so you can do that instead.
That's just the start. You probably need to use a package disabler or adb edits to disable about 70-80 bloatware apps.
This is how on my N10+'s its configured.
Unlike latter Samsung flagships the N10+ is a well balanced phone in terms of form factor, usability, functionality and power consumption.
It supports expandable storage up to 1tb.

It seems that disabling the global power management the slug mode has been disabled too. I need to check it in the next days if the situation stays like this or not. In any case I still need to block the bloatware.
Thanks for your help