yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] magnamentis:
those lightflow wakes do not cost that much battery, nothing significant. still it can be reduced as you see in mine.

in the second shot you see why WLD shows zero awake, because it's 0.27% = 23mA used in almost 10 hours and it's a nexus 5, on my N6

i got even better stats because the battery is bigger.

another nice thing to do is to put radio to 2G when the display is off, i use tasker for this. the difference is quite big BTW and who needs highspeed internet only for background syncing? once the screen is turned on it switches to highspeed. there is much more to it and basically OT but as my shots show it's possible with LED always on.

EDIT: have 11 LED alarms set just to give an idea while in the at least on to indicate silent mode ( white light ) is always on.
[Nexus 6  Original Android Development] shingers5:
Can anyone give me the best color calibration values and vibrations settings?
[Nexus 6  Original Android Development] magnamentis:
i think such a thing does not exist, what might look good for me ( saturated strong colors ) might look bad for pastel or warm color lovers.

it's quite easy to play with the sliders and save the settings as a custom profile.

see my setup in the screenshots:
[Nexus 6  Original Android Development] shingers5:
yea I get that but thanks for that!
[Nexus 6  Original Android Development] flar2:
I use 244 244 255 and bump saturation and contrast a tiny bit.
[Nexus 6  Original Android Development] DroidIt!:
Same :) On my N5, N6 and N7 I find having the blue value at about 15 above the red and green tends to make the white's whiter and the darks darker across all displays. Then I usually go up about 10 on the saturation and contrast. For me it seems to be a good combo across the different displays.
[Nexus 6  Original Android Development] shingers5:
thanks guys for that feedback

used latter settings and it seems fine

:good:
[Nexus 6  Original Android Development] goz5000:
Anybody else having the kernel app not keeping settings after a reboot.

Sent from my Nexus 6
[Nexus 6  Original Android Development] flar2:
Maybe you're not waiting long enough, or something is interfering, or you haven't clicked the little blue circle beside the setting to apply on boot. Or maybe some other app is preventing the boot setting service from running. Many possibilities, but I know 100% for sure guaranteed that the apply on boot settings in EXKM work under normal circumstances.
[Nexus 6  Original Android Development] goz5000:
Well I may have figured it out, greenify was putting it down so I need to try a reboot now. Thanks for responding back.

Sent from my Nexus 6

---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------

Yep that's what it was, thanks again

Sent from my Nexus 6
[Nexus 6  Original Android Development] Brotuck:
MRA58N is the latest update from yesterday, does 3.05 work fine with this release ?
[Nexus 6  Original Android Development] flar2:
I haven't tried it yet, but 99.99% sure it will.

There were no changes to the kernel in the update
[Nexus 6  Original Android Development] Brotuck:
Installed and it works fine ! :)
[Nexus 6  Original Android Development] Alxoom33:
No problems here!
[Nexus 6  Original Android Development] HumpDdumpD:
Good job flar2 you just showed up in my Google now cards! Probably getting a 6P eventually, good to know your already working on them.

http://phandroid.com/2015/11/04/nexus-6p-double-tap-to-wake/
[Nexus 6  Original Android Development] Poojan Patel:
Why any wake controls are not working??

Rom: xTraSmooth rom

Kernel: ElementalX 3.05 (default kernel)
[Nexus 6  Original Android Development] flar2:
No idea
[Nexus 6  Original Android Development] flar2:
FYI, version 2.26 of EXKM had a bug with sliders. I just released 2.27 to fix it.
[Nexus 6  Original Android Development] ConTejas2:
Working perfectly on my N6 w/ xTraSmooth. Wakes first time every time 95% of the time:D
[Nexus 6  Original Android Development] kitecarl:
Just wondering, did you flash on top of the previous version using fastboot? I am taking a wild guess we only need to flash system.img and nothing else. Thanks
[Nexus 6  Original Android Development] Brotuck:
I did flash the bootloader/radio/kernel and system. Nothing else.

After that i installed twrp-busybox-supersu and this kernel offcourse. Maybe a long route but it worls fine.

No settings were lost other then my dpi setting.

Verstuurd vanaf mijn Nexus 6 met Tapatalk
[Nexus 6  Original Android Development] elreydenj:
Are you finding that these same settings work well on your Nexus 6P?
[Nexus 6  Original Android Development] Formhault:
Check this out. Also, see this.

But all of these profiles are already preloaded in flar2's EX Kernel Manager app. I use wrinklefree_d7500... my phone's display is more on the warmer side, so I need to cool it down :silly: .

---------- Post added at 12:46 AM ---------- Previous post was at 12:45 AM ----------

I'm on Cataclysm, so I can set Smart Radio to do that for me. I didn't know switching to 2G makes that much of a difference :confused: . Didn't know 3G uses that much more battery than 2G.
[Nexus 6  Original Android Development] RandomPooka:
[MENTION=4684315]flar2[/MENTION] I flashed your 3.05 kernel on a home brew of Pure Nexus 6, built on 11/4 with the new security patches from google. The kernel itself seemed to function properly, but there may be some conflicts with the battery reporting. I'm not sure if it's something in the initram or what, but I was showing 4399% battery in the status bar, and charging, so it was increasing steadily.

Any ideas what may have caused this? It worked fine with chainfire's modded boot.img on the 10/30 build, and the only difference I can come up with is updated proprietary blobbage. I'm also wondering what else may need brought up to speed with that new 11/1 set of fixes.
[Nexus 6  Original Android Development] flar2:
Did you flash Chainfire's boot.img before EX?

Or just EX?
[Nexus 6  Original Android Development] RandomPooka:
I flashed Chainfire's boot.img prior to 3.05 .. I had a lot going on today, but I'm about to give it a shot without the boot.img to see if that makes any difference. I fully expect a bowl of bootloops, since that's what I'd gotten previously without using the boot.img

---------- Post added at 09:20 PM ---------- Previous post was at 09:19 PM ----------

Any particular logs you might want, in the event that I go ahead and recreate this situation?
[Nexus 6  Original Android Development] flar2:
Another user had this problem.

I think this is what happens:

Flashing Chainfire's boot.img overwrites the ramdisk, and then when you install EX, it has the wrong ramdisk and screws up the battery reading

Unfortunately, you probably need the sepolicy from Chainfire's boot.img to get an enforcing kernel to boot.

Things are way too complicated right now.
[Nexus 6  Original Android Development] PhilDX:
something makes me think there's going to be a lot of posts about battery usage in the pure nexus thread when the new build is released :)
[Nexus 6  Original Android Development] RandomPooka:
That's no joke! I think I need to yank apart Chainfire's boot.img and see WTF it does differently. Perhaps there's a way to patch the boot.img with a flashable zip rather than replace it, and flash EX afterwards.

Wasn't it v3.02 that still included those sepolicy changes? That one patched the init ram, didn't it? Or did it just automate the process of flashing chainfire's boot.img?

---------- Post added at 11:38 PM ---------- Previous post was at 11:35 PM ----------

Actually, being able to patch the sepolicy rather than overwrite it sounds like a much more future-proof solution that could be used on any ROM. Perhaps an option in the Aroma installer to add the tweaks to sepolicy and set as permissive or enforcing during the first flash.
[Nexus 6  Original Android Development] flar2:
sepolicy is the only change needed for enforcing kernels to work on ROMs like pure nexus. It's doable, but I'd prefer to patch the sepolicy that ships with the ROM rather than force the stock sepolicy that Chainfire has patched.

I'm also considering another, possibly better solution, but haven't worked on it yet.
[Nexus 6  Original Android Development] RandomPooka:
That's kind of where I was headed with that train of thought. I was wondering if there's a way to extract the sepolicy rules from the existing ROM boot.img, check them for the needed bits and place/replace them if missing. Selecting permissive/enforcing *should* be as simple as modifying the kernel line of the boot process, right?
[Nexus 6  Original Android Development] flar2:
Yes, I plan to set it on the command line. But I don't think the existing cmdline setting will work, even if enabled in the kernel config. I am going to do it a different way. It should be easy, I just have a long todo list now.
[Nexus 6  Original Android Development] RandomPooka:
Best of luck with it. It's slightly above my pay grade anymore. I used to be a lot more capable, but a few years away from that sort of system modification has got me rusty. Buying a Nexus device has me wanting to jump back in a muck around with things that I couldn't before.
[Nexus 6  Original Android Development] magnamentis:
no it's not the same, i don't want highpower and low power but sreen on and screen of as the triggering state. i'm also on cataclysm and have tried various times to get that done the way i want. of course the high/low power thingy is still very useful, those two things don't contradict each other but for me is important to safe battery before it's low so that it eventually never gets into low power mode at all. albeit it's good to have, after it's crippling the device, cpu wise, radio wise and so on.

i could swear that i was never below 50% battery with all my devices in the last 5 years. further back to windows phone times i don't remember to be honest, QTEK2010 and the likes it was then.
[Nexus 6  Original Android Development] MortenHeck:
Trying to install the latest kernel on Pure Nexus, but it will not boot.

I have tried to instal the permissive zip and the boot img, but no luck. It will not boot, it will only get to the android logo.

Any solution?

Nevermind, solved it!
[Nexus 6  Original Android Development] :
I had been looking at this exact thing like 2 weeks ago. The problem that I ran into was that none of the sepolicy decompilers out there would work with the mm sepolicy. They only supported up to version 29 and it's using version 30.

My plan was to take all the supersu vectors and just re-inject them into the existing sepolicy binary in the ramdisk. But, never made any headway with it... I may try to work on it again this weekend.
[Nexus 6  Original Android Development] RandomPooka:
Good luck! It's my weekend with my kids, or I'd be diving headfirst into this with you.
[Nexus 6  Original Android Development] NLBeev:
Seems to me that xTraSmooth needs a permissive kernel.
[Nexus 6  Original Android Development] chrisram88:
Time to take this bad boy for a spin. Hear great things.
[Nexus 6  Original Android Development] RandomPooka:
[MENTION=4684315]flar2[/MENTION], I think I'm going to sync and build this in a Pure Nexus build environment. Wonder if that will make any difference. I'll let you know if just building it against the same blobs helps. Will have to go and set selinux as enforcing and make a build that way and one permissive. Possibly a third with the default Pure Nexus kernel, so I've got 3 separate boot.img files I can screw around with in TWRP without having to reflash the ROM entire.

Will keep you informed
[Nexus 6  Original Android Development] :
Building it as part of a rom environment won't affect is build at all (other than the zImage being packed into the boot.img already). The entire kernel directory is built irrespective of the rom directory. The only thing that may change is the toolchain being used to build the kernel. Though, as flar2 had said that he keeps everything pretty much stock, that should be done with Google's 4.9 prebuilt already, which would cause the fewest tc related issues.
[Nexus 6  Original Android Development] RandomPooka:
Yeah, I remembered that as I was rebooting from flashing it. I'm rusty, and it was really early. Coffee hadn't kicked in yet
[Nexus 6  Original Android Development] sangiman:
Is it just me or is WiFi calling not working with this kernel on 1.10 ???
[Nexus 6  Original Android Development] flar2:
You need the version for Marshmallow.

You should update, this phone is about 100 times better on Marshmallow. Huge improvements.
[Nexus 6  Original Android Development] ICStevenC.:
I can confirm that this kernel works on MRA85N. Installed through TWRP with no issues and its working pretty well so far.
[Nexus 6  Original Android Development] ancidroide:
Hi [MENTION=4684315]flar2[/MENTION] ... I have been testing many kernels and in these days and seems like yours is the best one... The problem is that in these days I've also been testing a lot of custom roms and chroma is resulted to be my favorite one... So I tried many times,using several ways,to flahs EX upon Chroma but every time what I got was a f*ck*n* bootloop xD I'm getting crazy... Tried flashing permissive.zip but it didn't work... The only way that gave me some results was flashing the stock boot.img by chainfire and then your kernel... Phone booted fine but my battery was about of 4000% :( What can be causing this trouble??? there's a way to solve it or I can't use that rom??? Thank you in advance for this great kernel ;)

Edit: I also purchased your manager app so I wanted to use it :(
[Nexus 6  Original Android Development] nathanchance:
It has something to do with the November Security Update. Something could have changed to block Chainfire's modified SEPolicy which is giving an inaccurate reading due to SELinux? I have seen some posts already in the Chroma thread and some other threads of ROMs that have been updated to the latest security patch. I probably have no idea what I am talking about so [MENTION=4684315]flar2[/MENTION] may have something more detailed but that is my initial observation.
[Nexus 6  Original Android Development] biohaz55:
It seems that Chainfires modified boot image screws the battery %, battery options in settings and battery led's when flashing over Chroma 11/08..... it's not EX.

This boot image is needed for EX and without it EX flashing will give bootloops so the choices are stick with the earlier Chroma build or live with the probs caused by flashing the boot.img for now.
[Nexus 6  Original Android Development] Formhault:
I don't fully understand. Are you saying the way Cataclysm does it (power saving 2G/3G in Smart Radio) is flawed / worse than with Tasker? :confused:

---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------

Could you please elaborate on how exactly it is much better? I can't notice anything BIG, except that launching the Phone app and scrolling sideways in it isn't as sluggish as on Lollipop... but other than that, I fail to observe improvements in speed & such :(
[Nexus 6  Original Android Development] magnamentis:
you are thinking in negative terms, nothing is flawed because it's different or limited. with tasker you can do things exactly like you want them, this is an additon to the feature any rom comes with. this rom's features are perfect while this does not mean that there can't be more possibilities how one would want to set things up. so in positive terms that would mean to have a perfect feature set in terms of stability and wide spread usage patterns and we can add features to personalize it further to our liking via apps like for example tasker and of course others.

tasker is not better but you can do more with it. it's an app and not a rom, hence we can never compare the quality of an app with the quality of a rom. just look at these two things as totally different things which interact with each other. all is about what is good for you, for me or anyone else and there is no competition. it's not about who or what is better. needs and interests are far to different to make a "this is best/better statement.
[Nexus 6  Original Android Development] Formhault:
I was trying to figure out if there is something wrong with the way Smart Radio works, as opposed to Tasker (which just works). Thanks.
[Nexus 6  Original Android Development] flar2:
That's exactly it. I'll figure something out today

Battery life and stability are improved considerably. It's much smoother. And an annoying bug where the lockscreen would get stuck is completely gone. To me it's like a whole new phone.
[Nexus 6  Original Android Development] Formhault:
Wow, that's really not what I'm seeing :(

Battery life seems pretty much the same as on LP. Same for smoothness. Stability, as well - even worse, if I take into consideration an annoying bug that causes contacts to go haywire on edit / rarely...

The lockscreen bug... I think that's what I'm experiencing (more often than not) - although that might be related to the wake gestures (which I didn't use to use back on LP). Hope a clean flash will take care of that.
[Nexus 6  Original Android Development] flar2:
The lockscreen bug and gesture delay are definitely gone with marshmallow.

And battery life is improved significantly over lollipop, and this not due to my tweaks. You should be seeing this improvement even on a totally stock setup.
[Nexus 6  Original Android Development] flar2:
Update!!!

For Android 6.0 Marshmallow

-installer now does not touch /system partition at all. This means busybox is no longer automatically installed and the location of /etc/elementalx.conf is now /data/data/elementalx.conf. Also, init.d is no longer supported at all (you should have been using /system/su.d/ anyways)

-enforcing/permissive is now optional (yeah, I know, but it was causing me too much support trouble). Permissive.zip is no longer needed.

-no need to flash Chainfire's boot.img any more, the correct sepolicy for stock ROM is automatically installed and disabling the enforcing option will allow the kernel to run on permissive custom ROMs

-the tweak for key presses during suspend is now an option (used by Cataclysm), just in case it was causing instability

-went back to Google's toolchain and default build options

Stock ROM (rooted or unrooted):

-just flash EX, no need to flash Chainfire boot.img

Custom ROM:

-just flash EX, if it needs permissive, then make sure "Enforcing" is not checked in the installer options

NOTE: if you've previously flashed, and have wrong battery percentage, reflash the kernel that came with your ROM before flashing elementalx. The battery problems was caused by flashing Chainfire's boot.img, which gives you the incorrect ramdisk from an earlier release.

Download:

ElementalX-N6-3.06

Changes:

-massive installer update

-enforcing optional

-key press during suspend optional

-default toolchain and build options
[Nexus 6  Original Android Development] :
Too much coffee. O_o
[Nexus 6  Original Android Development] Formhault:
Can you please elaborate on this one?

---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------

No, I mean... The screen is very unresponsive at times, especially when trying to unlock after performing a wake gesture while the phone is flat on a surface. Usually turning the screen off and trying again does the trick. I'd try to get it on camera, but I can't camp for it to happen, lol.

Would a logcat show what the hell is going on?

Yeah... Not for me. Maybe my battery's dying? Too bad there's no way to know for sure how much capacity the battery has left in it...

I have some pretty interesting battery stats to show you guys. I'll do that later.
[Nexus 6  Original Android Development] daniel84cs:
[MENTION=4684315]flar2[/MENTION] Thanks for the update , this kernel is amazing , I love it......:)

Always an excellent work.......You are a great......;)
[Nexus 6  Original Android Development] jk8260:
On Pure and Chroma the

ElementalX-N6-3.00-sysrw.zip

Still works, all others fail, gives me DT2W and all other ElementalX features...

Wished the newer ones worked as I support all Flar2 work, but I have had no problems with this combo, on Pure 10.30
[Nexus 6  Original Android Development] metaphz:
Installed default settings and then without enforcing. Encounter issue on both setups. Cellular connection in status bar greyed out, also can not apply AdAway settings.
[Nexus 6  Original Android Development] farahzadfarahzad:
Daniel now its your turn ;)
[Nexus 6  Original Android Development] provolinoo:
Is chainfire's boot image still needed in case of systemless root or we don't need to flash it in that case either? :)
[Nexus 6  Original Android Development] flar2:
Installing a kernel doesn't affect that stuff

For systemless, yes you need chainfire's systemless root boot.img
[Nexus 6  Original Android Development] metaphz:
You sure? Because when I flashed 3.05 back my Cellular status bar logo went back to white instead of grayed out on 3.06.

AdAway doesn't like something now when flashing 3.06 either, what needs to be done to keep System R/W?
[Nexus 6  Original Android Development] flar2:
I don't understand how it could be related. I don't change anything that has anything to do with cell signal. And I have system r/w on all versions. Something on your system is messed up. Perhaps wipe your caches.
[Nexus 6  Original Android Development] suku_patel_22:
[MENTION=4684315]flar2[/MENTION] Hope you are still considering the option to choose from a very few color profiles in aroma.
[Nexus 6  Original Android Development] Mercado_Negro:
[MENTION=4684315]flar2[/MENTION]

Nice update. Good changes there on 3.06. Now, if you don't mind I'd like to ask you a question. It might sound a bit noobie but there are so many variables sometimes that I just want to make sure. I'm running stock 6.0 MRA58R with franco.kernel r34 and SuperSU 2.52. If I want to flash ElementalX 3.06 should I just flash the stock kernel back and then immediately your kernel or should I fastboot flash system.img as well? I see devs recommend to flash ROMs before flashing a new kernel but I never see them explaining the right procedure on stock Android/custom kernel. Sometimes devs make changes on /system partition with their kernels so I'm not sure what's the correct thing to do here.
[Nexus 6  Original Android Development] KonoeKyon:
You just don't have enough room on system, the 6.0 images use up more of the system space leaving very little left over. You can remove system apps you don't need or use such as the Google keyboards for other languages or other Google apps you can get from the play store.
[Nexus 6  Original Android Development] akshay961:
Bootloop on dirty flash over XtraSmooth 7/11 !
[Nexus 6  Original Android Development] arifqur:
Working well with latest Chroma with enforcing disabled.

Thanks for a super smooth experience
[Nexus 6  Original Android Development] ECrispy:
I just installed 3.06 on a new Nexus with Catacalysm rom, the only change I made in installer is to disable selinux enforcing. Now I see my phone is encrypted. Did I do something wrong or is this expected? I was hoping it wouldn't be since the OP says 'no forceencrypt'.

I also selected 'd2tw enabled' in Aroma installer and that doesn't work too.

I then installed WakeGestures 1.1 apk from the dev's site. I'm not sure if this is needed or not, or if installing kernel and choosing the option is enough? Inside the app everything is greyed out and I can't choose anything. When I turn the slider off it says 'Service stopped'. Turning it on, all options greyed out.
[Nexus 6  Original Android Development] Formhault:
That wallpaper and clock widget are awesoome!

Mind sharing them? :D
[Nexus 6  Original Android Development] nathanchance:
Did a fresh install of 3.06 over the latest release of Cataclysm, booted up with SELinux in Enforcing. Everything is working flawlessly so far.
[Nexus 6  Original Android Development] Georgiafan1969:
[MENTION=4684315]flar2[/MENTION] the new update is awesome man,running very smooth with no issues.:good: