yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] flar2:
Because it is already optimal.

I don't recommend changing CPU frequencies in general, because there are too many things trying to change them and you end up with conflicts.
[Nexus 6P Original Android Development] resynx:
Damn this release feels smooth flar!
[Nexus 6P Original Android Development] micmars:
Once per page seems about right for this Q&A combo...

Awesome update, as always

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] tracerit:
I looked into it further and it seems it doesn't quite save much battery, if at all according to this site http://www.gadgetguy.com.au/black-and-white-does-samsungs-monochrome-mode-save-battery-life/

I the sites mentioned to have a gray pixel, all three colors have to be lit. True black and white would work best but not all the apps will display correctly.

Either way, I'll check it out and see what comes about.
[Nexus 6P Original Android Development] jplafor1:
Double Tap to Wake

Hello flar2, I noticed that Double Tap to wake only works from the bottom half of the screen. I did see that in Kernel Auditor you can either disable it, choose half, or full; Sadly full doesn't work at all. Of course I'm using EX Manger, I just wanted to see if Kernel Auditor was able to grab all the kernel tweaks that EX has. Just wanted to tell you about my observation, even though you probably designed this on purpose to save battery life; I just thought it was worth posting anyway.
[Nexus 6P Original Android Development] bikeryder007:
Flar2 just made Facebook scroll smooth as butter. He must have made a deal with the devil himself... It's the only reasonable explanation.
[Nexus 6P Original Android Development] nathanchance:
I'd try enabling Sweep2Wake in one direction so you get his implementation over Google's. Or even just straight up switching to S2W, I like it infinitely better than DT2W. Google's DT2W may just be on the bottom, I am not sure exactly.

In Kernel Adiutor, you need to choose halfscreen so that it actually enables. The fullscreen option doesn't write the correct value to enable it.
[Nexus 6P Original Android Development] agjdsouza:
Not seeing much/any lag with touchboost disabled. Can report back after a day on whether there's any noticeable battery impact.

BTW, is anyone having recent trouble with 5 GHz WiFi? It was working fine through 0.8 or 0.9 but have had a spotty connection since (can't even see my 5 GHz connection most of the time).
[Nexus 6P Original Android Development] DeathmonkeyGTX:
I just flashed the update a few minutes ago, on stock rom with root. No 5ghz ac trouble yet, I usually stick with 2.4 to leave the AP's two 5ghz radios open for a laptop and an ac66u in bridge mode to get fast ethernet to my ht rack without the wallfish from the 9th circle of Hell. However I am testing it on the chance that you're not using the stock rom, could be your problem.

OK, still no problems with 5ghz
[Nexus 6P Original Android Development] :
Disabling touchboost definitely was a good Idea. No difference in smoothness whatsoever. [MENTION=4684315]flar2[/MENTION] can we change the cpu governor or is that also something you wouldn't recommend?
[Nexus 6P Original Android Development] Simer03:
Thanks for the update dude!
[Nexus 6P Original Android Development] __NBH__:
Even if I disable touch boost I can still see frequencies moving up when I touch the screen. I set it to 384 and I still get a jump up to around 600 on all 4 small cores. If I set one core to touch boost, all 4 cores still do it. It seems even with touch boost disabled the settings are still affecting the frequency behaviour.

Edit: OK I realise there is a difference between touch boost and CPU boost.
[Nexus 6P Original Android Development] 3ddfknmontana:
Need a battery friendly profile...
[Nexus 6P Original Android Development] wwevoxnj:
Almost all of them are good on battery. I'm consistently getting 5+ of SOT with lots of browsing, YouTube, 2 email accounts syncing, XDA, Spotify and a bunch of other apps but no gaming.
[Nexus 6P Original Android Development] wwevoxnj:
[MENTION=6558725]3ddfknmontana[/MENTION]

Here you go...

I/O fiops and read ahead 1024.
[Nexus 6P Original Android Development] brar.arsh:
Hey [MENTION=4684315]flar2[/MENTION]

Just wanted to check if I can update kernel using app or not as am on Pure Nexus rom and enforcing needs to be turned off during installation.

I have been flashing using twrp till now.
[Nexus 6P Original Android Development] Neverendingxsin:
How the hell? I do that and barely manage 3-4 hours, and this is with aggressive doze enabled.
[Nexus 6P Original Android Development] wwevoxnj:
I have greenify and doze editor as well. I do not have aggressive doze enabled with greenify. It was causing to many problems.
[Nexus 6P Original Android Development] kolyan:
I had 3 6p devices, 1st one I was able to get around 7 hours of sot, the other 2 I get around 6
[Nexus 6P Original Android Development] nathanchance:
Yes, you can use the app, just choose the Custom option so you get the Aroma installer. If you are on 11/21 or later for Pure Nexus, you can use SELinux Enforcing without any issues.
[Nexus 6P Original Android Development] mrchennyken:
Can anyone confirm that v0.11 works with SuperSU v2.60?
[Nexus 6P Original Android Development] guidojusto:
Hello [MENTION=4684315]flar2[/MENTION], today I got a random reboot while my phone was charging, I've retrieved a kernel log in case it is useful.

Thanks for the awesome kernel!
[Nexus 6P Original Android Development] Gytole:
PureNexus with this, underclocked to lowest values in Aroma and fsync disabled, still stupid fast! Always been a fan of flar2's Elemental kernels! Thanks for this!
[Nexus 6P Original Android Development] drothenberger:
Working fine for me.
[Nexus 6P Original Android Development] Neverendingxsin:
What are your doze editor settings set at?
[Nexus 6P Original Android Development] NovaSlim:
doze editor/Naptime/Greenify Agressive Doze settings should have little to nothing to do with your SOT time. It influences your wakelocks & deep sleep times.

Hint: When you screen is ON, your phone is NOT DOZING!
[Nexus 6P Original Android Development] xFierce:
Also I'm not sure of this rom specific or general android marshmallow. However I'm having trouble receiving Whatsapp messages once my phone goes into doze mode. I've changed the Whatsapp battery optimization to not optimized. However that didn't make a noticeable difference. Any suggestions?
[Nexus 6P Original Android Development] d3xt3r:
Is it me, or the battery optimization doesn't stick after being applied? I mean, u optimize all apps, n leave the screen n again enter the optimization screen, n its like nothing ever happened??
[Nexus 6P Original Android Development] __NBH__:
Have you restored after flashing new ROMs? I had a similar problem but after uninstalling and reinstalling the app, all is good.
[Nexus 6P Original Android Development] xFierce:
Ahh I have restored the app from Titanium Backup saved from a previous build of this rom. I'll try completely uninstalling and reinstalling the app.
[Nexus 6P Original Android Development] flar2:
Avoid tons of problems by doing clean installs. That means wiping data, cache and dalvik when you install a new ROM.
[Nexus 6P Original Android Development] aalupatti:
i have consistenly got around 5-6 hrs of SOT.

I do not use any battery saving app

Doze and other stuff is stock

Have around 4 emails, one exchange account, weather ( q30min ), bluetooth on always, xposed with a bunch ofmods, google now updating different stuff all the time, brightness variable but mostly bright and so on...

( today i am at 2h30 min of SOT and only 35% battery left ( since 7 am ) - Mostly due to lot of streaming via chromecast and some videos on the phone )

kernel setting - interactive. D2w enabled ( no lags ) and no other gestures.
[Nexus 6P Original Android Development] Simer03:
Yeah I also get consistently about 5-6 hours SOT. Today on WiFi all day, watching football and fantasy updates (thought both massively disappointing ) , I have almost 4 hours SOT so far at about 50% left. First day on 0.11. Obviously the battery will change each day but I'd say pretty good start
[Nexus 6P Original Android Development] Simer03:
Take it for what it's worth
[Nexus 6P Original Android Development] Neverendingxsin:
Guess I should give this kernel a shot and see what happens, been trying to improve my battery life but it just seems to drain quickly while using it.
[Nexus 6P Original Android Development] aalupatti:
Always check if there are some rogue applications
[Nexus 6P Original Android Development] wwevoxnj:
It depend more of what you have consistanly syncing more than doze but here are my settings.
[Nexus 6P Original Android Development] micmars:
And it always will...these screen on time stats are useless, and I wouldn't put too much time comparing them to your own.

As I've noted, there is absolutely nothing that a kernel or rom dev can do to stop your battery from draining while it's on, all he or she can do is lessen the pace of drain while the screen is off.

If my screen is on, I'm texting, writing short emails, in multiple hangouts, writing in Docs, searching YouTube, etc, etc...all using mobile network signal of varying strengths. In sum, I'm interacting with it. A lot.

I would love to see someone do that and get 8 hours whilst doing it...ain't happening.

The best for which you can hope is to slow your screen off drain to a trickle, and get the most from your device's battery potential while you're using it. Comparing your screen on time today to yours from yesterday is all that matters.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] Neverendingxsin:
Posts like this are why I continue to have faith in XDA.

Thanks for this :)
[Nexus 6P Original Android Development] c_86:
Where can I find that doze setting editor ?
[Nexus 6P Original Android Development] nathanchance:
Right here.
[Nexus 6P Original Android Development] c_86:
Great. Thank you. I searched the play store and didn't see it. But thank you for linking me.
[Nexus 6P Original Android Development] micmars:
Hey, thanks. I appreciate it.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] Simer03:
Yeah that dudes right. No point in comparing screen on time with anyone. I was "on pace for 8 hours SOT" but I only ended up with the usual 6ish. Battery can be deceiving sometimes
[Nexus 6P Original Android Development] drawde40599:
This isn't true at all , there are plenty of people that get 8 hours SoT that actually use there devices , and they can thank Kernel Dev's for it .
[Nexus 6P Original Android Development] nathanchance:
This is a little nitpicky... I believe the main point [MENTION=5244502]micmars[/MENTION] is making is that battery life is completely subjective. There are many factors that can contribute to battery life, some within people's control, some outside. It is pointless for people to try and compare their device's battery life to another's. Usage is different, environment is different, software is different, devices themselves are different. I'm never going to get 8 hrs of SOT because I live in an area with pretty spotty cell reception which will drain my battery but I get a full day's use out of my device. People focus too much on SOT. Furthermore, kernels are not the only place where battery life can decrease or improve, there are other places to look.
[Nexus 6P Original Android Development] drawde40599:
Yes ,that's all true . But to say Kernels/ROM's have no effect with screen on makes no sense at all and is completley false .
[Nexus 6P Original Android Development] LiquidSolstice:
EDIT: Nevermind, don't care enough to get into a pissing contest with anyone.

Latest update still working like a charm. [MENTION=4684315]flar2[/MENTION], how's the custom governer coming along? I remember a lot of devs haven't gotten their custom governers up and running yet due to the 810 and big.little?
[Nexus 6P Original Android Development] micmars:
Did I write that? If I did, I offer my regrets for a misleading post.

What I meant is that kernel devs have their main influence on the screen off drain...screen on drain will happen at such different rates depending on the individual user that the kernel dev has little influence on how you use your phone, your cell signal strength, your WiFi scanning, your screen brightness, your background processes syncing, etc.

Think of it another way...do you see an abundance of posts about chasing down usage drain or partial wakelocks?

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------

Uhm, yeah, in the general sense of my statement, yes, it is.

Relatively speaking, kernel devs have little influence on how you use your phone.

You think you're going to get 8 hours of screen on time if you're typing almost constantly in a very low signal area?

For your reference, here's what I actually wrote...

"As I've noted, there is absolutely nothing that a kernel or rom dev can do to stop your battery from draining while it's on. "

Have you encountered a kernel that prevents your battery from draining while you're using your phone?

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

---------- Post added at 07:21 AM ---------- Previous post was at 07:16 AM ----------

I wish that I had your temperance.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] steveo17:
probably a stupid question, but which root method does this Kernel use? Systemless or the standard?
[Nexus 6P Original Android Development] inffy:
Kernels don't handle root.
[Nexus 6P Original Android Development] steveo17:
pretty sure they do, being that you have to flash a boot.img to root the nexus 6p
[Nexus 6P Original Android Development] flar2:
You still have to flash SuperSU to get root, either the regular version or the latest systemless.

If you are rooted and flash elementalx, you will remain rooted.

If you are not rooted and flash elementalx, you will not be rooted.

If you are not rooted and flash elementalx and the latest systemless root, you will be rooted.
[Nexus 6P Original Android Development] steveo17:
great thanks for the info!

i flashed SuperSU 2.56 previous to installing elementalx.

If i wanted to updated to 2.6, it sounds like i need to reflash the stock kernel before updating to 2.6 right?

http://xdaforums.com/showpost.php?p=64161125&postcount=3
[Nexus 6P Original Android Development] flar2:
Governors need quite a few fixups to work properly with big.LITTLE. The HMP scheduler implementation and cpu driver on this device are from Qualcomm, and the only governor they've updated to work with it is interactive. Ondemand and others are not updated. The elementalx gov is updated to work with big.LITTLE, but not optimized at all. Still needs work and currently not as good as interactive.
[Nexus 6P Original Android Development] flar2:
You guys make some good points about battery life.

There will be small variations from one device to another, due to manufacturing tolerances (especially the battery), and due to aging of the electronics and battery.

There will be variations due to usage patterns. In other words, how you use your phone. Constantly touching the screen and flipping between apps or pages in your browser will use a lot more battery than scrolling slowly through a single news article for 10 minutes.

The temperature of your environment will make a difference. Expect worse battery life in extreme heat or cold. I live in a very cold climate, so when it's -20C and I bring my phone inside to warm up, sometimes the battery percentage actually rises by a percent or two.

The CPU governor, frequencies, and screen brightness will make the most difference in screen on time. This is where kernels can help. You can still improve battery life, but sometimes only at the expense of smoothness.

The kernel can make a difference in idle drain too, but not like in the old days. And on this device, negligible.

As phones become much more efficient, it's getting harder and harder for kernel devs to make a big difference in battery life. On phones from about 2013 and earlier, kernels could make a dramatic difference.

Stuff going on in the operating system makes a bigger difference in battery life than the kernel. Basically, I can't stand posts that say this or that kernel caused drain. No it didn't. Kernels will not cause drain, apps and services cause drain.

Some time ago, I wrote this article about the subject: http://elementalx.org/the-truth-about-kernels-and-battery-life/

As for the 6P, as I've been saying all along, battery life is excellent even on stock. I've fiddled with a few things, hexcore mode, 1248 max frequency on the little cores, disabling touch boost, etc. These can make small differences, but I don't see dramatic improvements to battery life.

That doesn't mean you can't tweak the settings and eke out some extra juice for your own usage patterns. But this will be user specific.
[Nexus 6P Original Android Development] steveo17:
what did you do to update to the latest SuperSU?

did you reflash the stock Kernel?
[Nexus 6P Original Android Development] stan79:
I'm using 470dpi instead of stock DPI and I realised that double tap to wake does not work on the top 35% of the screen. I can only double tap from 35% down to the end of screen to wake up the screen. Is that normal? Swipe left to sleep at the bottom is working fine.

I'm using the latest M ROM and tried v9, v10 n v11 of the elemental x kernel.
[Nexus 6P Original Android Development] NovaSlim:
I am on 460 dpi and swipe to wake works anywhere on screen, dt2w is trickier on this kernel and the dev recommends using it instead.
[Nexus 6P Original Android Development] joho5:
The kernel mentioning "sound control" does that mean you can boost the headphone volume past stock values? And this is done within the elementalx app?

thanks
[Nexus 6P Original Android Development] schnob:
Yes, if you have this kernel installed, go to the sound tab in EX Kernel Manager and you can make it too loud for the average human.
[Nexus 6P Original Android Development] drothenberger:
I restored a TWRP backup of stock system partition and boot partitions, installed the SuperSU zip, re-flashed ElementalX kernel and xposed, then booted into the system. I had to reinstall busybox and reactivate AdAway, but that was it.
[Nexus 6P Original Android Development] redsmith:
flar2, I have found a very strange bug using the Ex Kernel Manager app. In advanced color control, whenever I change the screen value or the contrast, I have noticed that they will keep increasing +1 each time I open the app. You can reproduce the issue by opening Advanced Color Control, setting Value and/or Contrast to anything other than 128, and then closing and reopening the app. You will then notice that both values have increased by 1. Repeat. After a while, the screen will look really funny because of the new (much greater) values. Clearing the app's data and starting from scratch is the only way I have found to stop this behavior.
[Nexus 6P Original Android Development] Simer03:
You know what helps me with battery life?? Turn off battery percentage :p
[Nexus 6P Original Android Development] steveo17:
ok great thanks. I will try this

you did this all in recovery at once or did you let the OS boot in between any of those steps?
[Nexus 6P Original Android Development] drothenberger:
I did it all at once.

Note that I only restored system because I had previously rooted with the non-systemless SuperSU and 2.60 is systemless. I think if you were on systemless before you would not need to do that.
[Nexus 6P Original Android Development] adrman:
Does EKM still require Busybox to be installed to system? I was going to try systemless root with 6.01, but as I understand things, if EKM requires Busybox in system, it xcls out the advantage since system will still be modified. Thanks.
[Nexus 6P Original Android Development] flar2:
I think it mostly works without busybox, I can't remember which (if any) settings required busybox specifically, as all the basic commands are available in stock Android.

There is a way to install busybox without touching system, but I haven't looked into it.
[Nexus 6P Original Android Development] adrman:
I'll give it a go then. I believe the alternate Busybox install people are using is user/bin. Currently, I'm using Busybox on rails and that doesn't support the above location, so I'll probably go back to Stericson.
[Nexus 6P Original Android Development] HyperM3:
I have both Faux Clock and Kernel Adiutor. Neither one gives me the option of changing the vibration. What are you guys using to change this?
[Nexus 6P Original Android Development] lynseyw:
Probably a dumb question (I did search first) but, is there a way to turn off the sound on the notification for an updated kernel. I like the update, but don't like it to wake me up :)
[Nexus 6P Original Android Development] HyperM3:
Wait, theres a notification for an updated kernel too? I never get this.
[Nexus 6P Original Android Development] flar2:
I could make it optional
[Nexus 6P Original Android Development] flar2:
EX Kernel Manager for both of these things (and much more)
[Nexus 6P Original Android Development] lynseyw:
I have the EX Kernel Manager. I only see notification on and off. I want the notification on, but the sound off. Didn't see an option for that.
[Nexus 6P Original Android Development] HyperM3:
So another kernel app I have to pay for. Are these that exclusive that one app cant work with another kernel?
[Nexus 6P Original Android Development] flar2:
No, it's not there now. I said I would add the option
[Nexus 6P Original Android Development] lynseyw:
Oh, AWESOME!! Thanks! :)
[Nexus 6P Original Android Development] flar2:
There is nothing stopping the developers of other apps from adding this stuff. I try to use standard paths where possible. The vibration option is actually there on stock, I am just the first to add support to my app.

A lot of the features on this kernel/device have been developed or discovered by me, and mostly in the past few weeks.

When you buy the app, you are supporting the development work that I do, which takes many, many hours.
[Nexus 6P Original Android Development] HyperM3:
No, I get that. Dont get me wrong, I totally appreciate what you do. I guess Im just frustrated that I have to jump from kernel to kernel when the previous developer stops developing for the ROM Im using and then have to reinvest in something new.
[Nexus 6P Original Android Development] sidhaarthm:
Hi flar2 - I manually flashed the 6.0.1 OTA on my 6P. Now after rooting (using the modified boot.img), your Kernel app says no new kernel found. Are you going to work on an ElementalX for 6.0.1 soon (or update your app) or can I manually flash 0.11 and it'll be okay on the MMB29N build? Thanks!

PS* I did read the last few pages to find an answer to this but couldn't see anything.
[Nexus 6P Original Android Development] flar2:
I push updates quickly and support my devices as long as the manufacturer does, and I plan to keep doing this for the foreseeable future.

I will look at it tonight, I'm not even home from work yet.
[Nexus 6P Original Android Development] NovaSlim:
said developer just pushed out a updated kernel for Nexus 7 2013 YESTERDAY to work with CM13(AOSP version was avaliable since M launchand already have had 5 iterations ), your paranoia about this dev dropping support is completely unnecessary:p
[Nexus 6P Original Android Development] HyperM3:
You got me. Purchased your app. Thank you for your dedication.
[Nexus 6P Original Android Development] freemini:
It works fine after flashing modified boot.img then elementalx 0.11. I'm using normal root not systemless but I doubt it makes a difference.
[Nexus 6P Original Android Development] Batfink33:
My camera breaks using 6.0.0 kernels on 6.0.1?
[Nexus 6P Original Android Development] freemini:
That would explain why camera wasn't working. So it kind of works then :).