yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] dirtyhank:
There are some threads with stock ROM, just find the right one for your particular model.

If you're using Kernel Adiutor, to disable Hotplug just go to the CPU Hotplug tab and uncheck the MSM MPDecision Hotplug. Then you have to go to the CPU tab and manually tick the checkbox for the offline cores.

Never tried this setup for long but I'm pretty sure it won't be easy on the battery ;)
[X Style (Pure) Android Development] jsminnis:
I'm not on trupure, but I think the problem was that the kernel was not patched properly for those with traditional root and now it is. I can't be positive that it's booting on trupure but I do know it is on stock prerooted. Before it was boot looping.
[X Style (Pure) Android Development] guraki:
This kernel with stock rom gave me 15 + hours of use with 4+ hours sot!!!! Both wifi and data always enabled...!!! Can't wait to see its further development...
[X Style (Pure) Android Development] MyDarkThrone:
Booting fine in Truepure 2.4

Enviado desde mi XT1575 mediante Tapatalk
[X Style (Pure) Android Development] patt2k:
Thanks for the confirmation! I am really sick of how bad battery is on this phone. I hope this kernel does well.

Sometimes I am at a point that I want iPhone 6S because of better battery life seriously lol. But I would miss to much adaway+viper4android :/
[X Style (Pure) Android Development] brusslesprouts:
this kernal has double tap to wake?
[X Style (Pure) Android Development] patt2k:
Nah
[X Style (Pure) Android Development] MyDarkThrone:
I'm really happy with the battery. Is as good as my previous one plus and performance is much better. And all with a more exigente screen resolution.

Enviado desde mi XT1575 mediante Tapatalk
[X Style (Pure) Android Development] patt2k:
Let me give you good example on my battery today around 9-30 AM I unplugged from charger after just 2 minutes of using the phone battery went down 1% another 3-4 minutes it was at 97%.

While I was going home listening to music via BT I lost another 15%.

That's how bad it is,it was same when I was on Verizon and now on T-Mobile I see no difference in battery since day 1. I once compared my gf's iPhone 6 and for 30 minutes of browsing same spot battery stayed at 100% and dropped 1% after watching some videos.

PS. the kernel now booted fine on TruePure :)
[X Style (Pure) Android Development] dirtyhank:
Well, the screen on this phone is quite a power hog. I've noticed that simply by reducing the brightness to the minimum tolerable I can squeeze almost a 20% more of SOT.
[X Style (Pure) Android Development] patt2k:
I am using TruePure and it has ambient display where only top sensors work so it's not that sensitive. Better then Moto Display in my opinion. I will be testing your kernel once battery almost dies and I will charge it to full. Thanks will be waiting for more updates with extra features:)
[X Style (Pure) Android Development] amathophobia:
[MENTION=2400758]dirtyhank[/MENTION] thank you for your kernel. Does it have undervolting?
[X Style (Pure) Android Development] jlbuck6212:
Just wanted to thank you and tell you damn good job on the kernel! I really appreciate it. Great work!
[X Style (Pure) Android Development] juancaperez2000:
This one of the gratea battery life I ever have, this ia running with True rom.
[X Style (Pure) Android Development] dirtyhank:
Nope, all the changes from stock kernel are listed in the OP. And honestly, this SoC is pretty picky so I don't know how much room we have for undervolting. In my testing with overclocking I've noticed the A53 cores won't tolerate as much increment as the A57 cores (I thought it'd be the opposite) so I'm afraid the situation will be pretty similar with undervolting, and unfortunately the A53 cores would benefit the most from undervolting.
[X Style (Pure) Android Development] guraki:
Do you have any suggested settings for more battery save???
[X Style (Pure) Android Development] Ghost9867:
Do you madre any change in the kernel setting or you only flashed the kernel ?
[X Style (Pure) Android Development] juancaperez2000:
Underclock the GPU to 450

Governor Interactive

scheduler Noop
[X Style (Pure) Android Development] Ghost9867:
and the performance is still the same ?
[X Style (Pure) Android Development] cerobles1:
So are all 6 cores running at all times? And what speed is your max? Or did you find a way to turn off some of them?
[X Style (Pure) Android Development] juancaperez2000:
I dont touch nothing there, the phone still on thr same charge at 42% and 3 hrs 40 mins SOT.

---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------

I dont see any difference on performance.
[X Style (Pure) Android Development] dirtyhank:
Sure, it's the top performance profile so battery life is secondary. In a way I wanted for people to know how good this device can perform with some aggressive settings. Then one can start tuning and find the right balance :)

That being said I'm getting close to 4h SOT with this setup on a typical day. If I don't use it that much I get the 3h SOT you mention.
[X Style (Pure) Android Development] Hitti2:
Was wondering why my battery is being eaten.

Using op profile.

Are there any power saving profiles roaming around?

Sent from XT1575, TPXMM 2.5, Frankenclark 0.5.2
[X Style (Pure) Android Development] dirtyhank:
Use the Battery Profile on OP. If you find it too conservative take a look at both profiles (Performance and Battery) and notice the differences, then start changing things and find your sweetspot ;)
[X Style (Pure) Android Development] ffonegod:
Thanks for the info.. Just a quick question.. Why you use the stock rom? Is it better in performance than the true pure rom?
[X Style (Pure) Android Development] Hitti2:
Awesome deal. Ty.

I can switch between the two now.

Sent from XT1575, TPXMM 2.5, Frankenclark 0.5.2
[X Style (Pure) Android Development] dirtyhank:
Just personal preference, stock ROM is usually more stable than custom ROMs. TruPure is mostly stock so I don't think there'll be much difference though.
[X Style (Pure) Android Development] HikingMoose:
TruPure is deodexed, so that means it is de-optimized. I always have better performance and battery with odexed ROMS. TruPure really doesn't offer anything better than stock that I ever noticed. The battery life wasn't as good, and it was laggier. Stock odexed is always the most stable.

I've requested an odexed version almost a dozen times to improve performance, but it falls on deaf ears.
[X Style (Pure) Android Development] brholt6:
The difference is pretty negligible (has been on every phone I've ever owned anyways) so there's not a lot of use for him to make an odexed version (plus its just his personal build, so if he doesn't use odexed, why make one). I switched back to TP from stock odexed and I'm actually squeezing out better battery life.
[X Style (Pure) Android Development] urimevs509:
Only managed to get 59434 on Antutu 6.0.4 on FrankenClark default settings
[X Style (Pure) Android Development] dirtyhank:
That's weird, I usually get ~70k with default settings. You probably have some background processes eating CPU cycles. Switch to airplane mode, kill all running apps and try again.
[X Style (Pure) Android Development] urimevs509:
same results as before... I'll try a fresh install, dunno if Xposed+Grennify+Amplify combo is to blame
[X Style (Pure) Android Development] dirtyhank:
I wouldn't obsess over Antutu scores anyway ;)
[X Style (Pure) Android Development] cerobles1:
Who cares about the stupid Antutu scores. Give me 10 hrs SOT, or 48 hrs of stand by.

By the way, disabling MSM MPdescision and going back to the CPU tab to manually check the cores on or off works like a wonder. Finally able to run two little cores on and turn the rest off. Whoop whoop... #winning
[X Style (Pure) Android Development] urimevs509:
I was just wondering what's wrong with my phone
[X Style (Pure) Android Development] jason2678:
I've been curious about the hotplug toggle and experimenting with this a little too. I was seeing some odd behavior on earlier revs (could easily have been operator error ;) ), but MSM MPdecision seems to do what I expect on 0.6.

[MENTION=2400758]dirtyhank[/MENTION] - if we disable MSM MPdecision does that force hotplugging back to Qualcomm MPdecision daemon?
[X Style (Pure) Android Development] dirtyhank:
No, if you disable MSM MPD hotplug is completely off. The core_ctl module is closed source and won't work with newer releases of this kernel, I had to recompile all modules.
[X Style (Pure) Android Development] Chuckleb0ne:
[MENTION=2400758]dirtyhank[/MENTION] - I keep updating to the newest kernel builds but I still never get the option of having other than just the plain old regular CPU Governors. I don't have blue active, lion heart, etc. What am I doing wrong here? I flash the kernel via TWRP all the time and it works and boots fine. I do notice though that in kernel Auditor that the kernel information (like date) never change to any of your most recent build dates.
[X Style (Pure) Android Development] SpasilliumNexus:
Are you flashing SuperSU after the kernel? That's the only thing I can think of since it attempts to restore a previous kernel upon flashing it.
[X Style (Pure) Android Development] Chuckleb0ne:
You are right. I thought that was what we were supposed to do my bad. I think I started doing that because I might have just lost root one time after flashing this kernel.
[X Style (Pure) Android Development] Degod:
Thank you [MENTION=4955328]argenteloup[/MENTION] for this setup. I use this setting and I can reach 4h 9m SOT from 99% to 12% for my heavy gaming.

I like to know if there is any different setings that I can use
[X Style (Pure) Android Development] guile50:
i've just turned off the 2 big cores, left the governor on interactive, only greenify on. No xposed (turned down my performance horribly), no battery saving apps, let's see how the battery'll handle. Performance is top notch tho (i don't use it for heavy gaming, so i think 4 cores should deliver me optimal performance.)

some observations i made: Elementalx governor ****ed up the performance. Scrolling was slow, games stuttered, apps were taking some unusually long seconds to open, not good. when i switched to interactive, everything was fine, but the battery wasa discharging kinda fast even with the screen on. now it's panned at 54% since i left the phone on the desk. (with the 2 big cores offline)

Xposed was a huge performance and battery drainer. I really dig the personalization you can make with it, but the phone was way too sluggish, and i didn't even get 3h of SOT, so i cut it. I only use Gsam to monitor the battery stats (i use it since i bought the phone, never impacted on anything) and greenify to hibernate those pesky apps like facebook.

So now i've got the 4 little cores on, smooth scrolling, app switching, animations at .5, everything is running as it should, temperature is okay (battery is around 36ºC, but the phone is even cooler than it was on 30ºc with the 6 cores online.) let's see how it handles deep sleep.
[X Style (Pure) Android Development] Sheetzie03:
As some others have mentioned previously I'm not sure it's Xposed that has anything to do with battery related issues.
[X Style (Pure) Android Development] saidmsb:
I have XT1572 and running TruPureXMM rom.. I tried most of this kernel versions and i faced random reboot in all of them without playing with kernel setting at all.. What's your thoughts?
[X Style (Pure) Android Development] dirtyhank:
Maybe you have a picky CPU that doesn't like overclocking (keep in mind not all CPUs are created equal). For instance, my initial overclocking allowed the LITTLE cores to reach 1632MHz but I got reboots while turbocharging, probably because of the heat. I decided to limit LITTLE cores overclocking to 1536MHz as this is rock solid on my device, but that doesn't mean it'll be the same on every device.

I suggest you reduce max frequencies to stock (1440MHz and 1824MHz) and give it try.
[X Style (Pure) Android Development] grifforama:
Greenify is pointless with doze.
[X Style (Pure) Android Development] pradeepvizz:
[MENTION=2400758]dirtyhank[/MENTION] thank you so much for the hot plugging thing. been something i was really wanted to experiment with. 2x a 53 and 2x a57's - going to see how my system behaves! thank you.
[X Style (Pure) Android Development] urimevs509:
Antutu [MENTION=4903032]7551[/MENTION]0 with the performance settings given on Page #1...
[X Style (Pure) Android Development] guile50:
It may have something to do with the modules, it was draining and heating up like crazy, and I didn't put any out of the ordinary apps. After removing it, everything was fine.

But I still can't break the 20h battery barrier and 3h sot.
[X Style (Pure) Android Development] HikingMoose:
I use greenify and always surpass 4hr SOT with typically over one day of uptime. But I don't use Facebook, or greenify. I had bad battery drains from greenify years ago.
[X Style (Pure) Android Development] chindynasty:
I had couple of games freeze on me with this setting. Other than that, pretty good setup.
[X Style (Pure) Android Development] Cowbell_Guy:
Somewhat off topic, but after applying the performance profile in OP, why does it always revert back to interactive at each boot? Ie why do I have to keep resetting it every time?

I'm guessing there is a simple fix? Thx
[X Style (Pure) Android Development] dirtyhank:
Which app are you using to persist changes on boot? I use Kernel Adiutor and I don't have that problem.
[X Style (Pure) Android Development] urimevs509:
Top right corner in kernel adiutor... activate "apply on boot"
[X Style (Pure) Android Development] Cowbell_Guy:
Thanks!
[X Style (Pure) Android Development] Sheetzie03:
This

---------- Post added at 12:56 PM ---------- Previous post was at 12:53 PM ----------

I use Kernel Auditor , select apply at boot and I'm having the same problem. It reverts to interactive, sometime on a reboot, sometimes without rebooting. I'm assuming maybe an issue with kernel auditor bec some have mentioned it has some bugs that need fixed.
[X Style (Pure) Android Development] urimevs509:
you have to activate "apply on boot" for each and everyone of the mods you make (CPU, GPU, Thermal) etc
[X Style (Pure) Android Development] Sheetzie03:
If by 'activate' you mean turning on or clicking the button ON to the right, yea I know. And I know there is an Apply on boot for Cpu,thermal,etc. Sometimes things still don't stick. Like I said others have mentioned bugs with Kernel Auditor, some on xda, others iv read in the reviews of the app on the play store
[X Style (Pure) Android Development] Degod:
From my understanding, the bug not come from Kernel Auditor but from your ROM. Are you using official ROM?

Because I am using official MM ROM and don't have any problem with "apply on boot" in Kernel Auditor
[X Style (Pure) Android Development] tiis:
FYI: When I limit the maximum CPUs to less than 5, 4K videos are recorded with noticeable lag!
[X Style (Pure) Android Development] ffonegod:
Hey.. I see a new profile setting for battery and performance.. U might wanna check it out http://xdaforums.com/showthread.php?p=65289840 [MENTION=2400758]dirtyhank[/MENTION]
[X Style (Pure) Android Development] Sheetzie03:
You might be right. Which rom are you running? Link?

Thanks
[X Style (Pure) Android Development] quierotacobell:
Might be this one, the official one.

http://xdaforums.com/showthread.php?t=3262242
[X Style (Pure) Android Development] Degod:
I'm not using that one. I came from 5.1.1 and then I updated to Marsmallow via OTA but I bet you can use that one :good:
[X Style (Pure) Android Development] Degod:
That is not new profile. Just a new tweak for Interactive Gov ;) which I like to try too :D
[X Style (Pure) Android Development] dirtyhank:
That's expected, the LITTLE cores alone don't have the horsepower to encode 4K video in real-time.
[X Style (Pure) Android Development] dirtyhank:
I've been working hard on this behind the scenes and finally I'm making progress:

[IMG="DT2W Teaser"]http://xdaforums.com/attachment.php?attachmentid=3644471&stc=1&d=1455348613[/IMG]

Don't ask for a release date, it'll be released when I manage to fix some quirks ;)
[X Style (Pure) Android Development] Grafidio:
In ex kernel manager it says NA for my second cluster governor when I pick bluactive, along with jumping frequencies. Anyone encountered this? (Frankenclark 6.0)
[X Style (Pure) Android Development] dirtyhank:
Read the OP, Profiles section
[X Style (Pure) Android Development] ffonegod:
Finally!
[X Style (Pure) Android Development] YankInDaSouth:
You are awesome!!!
[X Style (Pure) Android Development] CJ-Wylde:
I can't believe my heart rate increased when reading this... You are amazing! Your loyal subjects /bow down to you.
[X Style (Pure) Android Development] Rocketval:
Wake gestures (flaar) or classic dt2w? :D
[X Style (Pure) Android Development] dirtyhank:
Pretty much a classic and basic implementation based of different sources. If it turns out to work well I'll add more stuff.
[X Style (Pure) Android Development] Rocketval:
Good, better IMHO than wake gestures :D
[X Style (Pure) Android Development] Sheetzie03:
:confused:
[X Style (Pure) Android Development] Hitti2:
Not sure if this has to do with the kernel. I am thinking it has something to do with the kernel.

Whether in mms or tapatalk to submit a reply I must hit submit about three times for it to register.

Is this have something to do with touchboost?

Or is this just the phone?

And boy its making me angry, like to figure this out.

Sent from XT1575, TPXMM 2.4, Frankenclark 0.6
[X Style (Pure) Android Development] dirtyhank:
I don't think it's the kernel, I didn't change anything in the touchscreen modules.

When I switched from Nexus 6P to the Style I was bit worried about touchscreen sensitivity, it wouldn't register like half the button clicks. I soon realized I had to press harder and longer than I was used to. And this was on pure stock ROM and kernel.

I still get some missed touch events here and there when I do very brief and light touches.
[X Style (Pure) Android Development] Hitti2:
Thanx. Did not think of this. its wierd. Always the third touch.

Sent from XT1575, TPXMM 2.4, Frankenclark 0.6
[X Style (Pure) Android Development] argenteloup:
Any chance for the thunder hotplug? I'm very curious about it.

This kernel had it back in the LP,

http://xdaforums.com/moto-x-style/development/kernel-v4tk-o3-uber-optimized-t3227689
[X Style (Pure) Android Development] SpasilliumNexus:
Would it be possible to add in DriveDroid support by [MENTION=1996688]FrozenCow[/MENTION]? He's linked to the needed kernel patch for it to work correctly (it's also built in to ElementalX kernel for the Nexus 6P), and unfortunately I have no idea how to compile a working kernel without it erroring about toolchains and such.
[X Style (Pure) Android Development] dirtyhank:
Tried it and doesn't behave properly with MM, same happens with Intelliplug and MSM_Hotplug. They need some mods, maybe in the future but not anytime soon.
[X Style (Pure) Android Development] dirtyhank:
I'll take a look. I was playing with DriveDroid the other day and couldn't make it work properly.
[X Style (Pure) Android Development] Hashbang173:
Could you maybe add arm64 kexec hardboot support?

https://github.com/AICP/kernel_motorola_msm8992/compare/41e44cc5e5...a6959bcd07
[X Style (Pure) Android Development] unitz0mbie:
Are there any more profiles?
[X Style (Pure) Android Development] HikingMoose:
Why are you asking that? Isn't this only for stock ROMs, and not your custom aosp ROM... right? Can this be used on AOSP ROMs? That would be a game changer for me!
[X Style (Pure) Android Development] WelcomeToTheSkye:
It's for MultiROM support
[X Style (Pure) Android Development] HikingMoose:
Oh yeah. Crap.
[X Style (Pure) Android Development] dirtyhank:
Hi there!

Brief status report on the DT2W stuff: It's kinda working fine although there's still an outstanding issue that's bothering me. When the device goes into suspend mode (and MM is pretty aggressive about this) it always seems to miss the first tap (and even the second), effectively turning DT2W into QT2W :D

I've tried holding a wakelock and it fixes the issue but destroys battery so it's not an option. I'm running out of ideas to test, any of you guys has some insight into the matter?
[X Style (Pure) Android Development] Rocketval:
I have a falcon with cm13 + hurtsky kernel. Falcon natively doesn't have dt2w but with hurtsky kernel it works really fine. Try to PM him :)
[X Style (Pure) Android Development] ffejy462:
How does (assuming it's not proprietary or special hardware) lg have it implemented? It works every time with no noticeable battery drain.

mxpe 6.0
[X Style (Pure) Android Development] suhridkhan:
I own a LG G4 and in my experience DT2W doesn't really work 100% of the times on it either. It's more like 90%, other times you have to do QT2W!

Agree that G4's stock rom has amazing battery life. DT2W works better on G4 with aosp roms, but in exchange of slightly poorer battery life.

I believe, for DT2W we need to do a compromise between tapping accuracy and battery life.
[X Style (Pure) Android Development] HikingMoose:
I can confirm this. Just got the wife a G4 last week, and sometimes it takes more than 2 taps. Sometimes 4, I haven't used it enough to notice if it only does it after it's been at rest for a period of time.
[X Style (Pure) Android Development] ffejy462:
I had the same "issue" with my g2, but after a while you learn the timing, location, and dwell of the taps to have it working approaching 100% (only worked about 25% for the ex; she'd tap on it like crazy, then I'd double tap and it'd work every time :) ). That said, it didn't have mm.

mxpe 6.0
[X Style (Pure) Android Development] countryfolk07:
I do this too with my wife. Lol. So funny.
[X Style (Pure) Android Development] dottat:
Stock kernel with many tap to wake sounds better than no tap to wake.
[X Style (Pure) Android Development] dirtyhank:
Yeah, I agree, if I don't find a solution in the next few days I'll release it anyway. After all, there'll be time to try other approaches later.
[X Style (Pure) Android Development] BooBzi:
You can try to use Amplify if you have Xposed.

Also app thats called "Disable Service" can perform such task.

Note: You can disable location on your device, it will slower wakelocks.

---------- Post added at 12:53 PM ---------- Previous post was at 12:52 PM ----------

Is it possible to change "hotplug" on EX Kernel Manager application?

I dont see any settings regarding this on CPU section.
[X Style (Pure) Android Development] Hitti2:
Ex.kernel is lacking a lot of stuff. Should try kernel adiutor.
[X Style (Pure) Android Development] pradeepvizz:
I was wondering if you have a look into nexus 9 sources which had double tap to wake on stock Android.

Hey mate good to see you here
[X Style (Pure) Android Development] dottat:
Right back at ya. Escaping from HTC lol. This phone is pretty damn nice.
[X Style (Pure) Android Development] dirtyhank:
Believe me, I've had a look at the sources of all modern devices with DT2W and I haven't seen anything, some of the implementations are pretty much identical.

The good news is I think I've found the culprit: the Moto Sensor Hub. If I disable MSH in the kernel config DT2W and S2W work as advertised. The bad news is I can't disable MSH for good or we lose many sensors (light, proximity, ...). At least now I know where to focus my efforts :)
[X Style (Pure) Android Development] fdc77:
Can be added multirom support in next version?

thanks
[X Style (Pure) Android Development] dirtyhank:
If you mean the KEXEC stuff yes, it'll be on next release. Thanks to [MENTION=4630246]Hashbang173[/MENTION] for the commits.
[X Style (Pure) Android Development] dirtyhank:
Quick poll, any of you guys use a folio case with magnetic lid? I've noticed that disabling the Hall effect sensor notifications improves D2TW, still misses taps but not as many. If not many people use the folio or those who do can live with the lid not triggering the screen I think I'll go ahead and nuke the sensor :cowboy:
[X Style (Pure) Android Development] Cowbell_Guy:
Nope don't use at all
[X Style (Pure) Android Development] Tech_Savvy:
Go for it:)