yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] flar2:
Update

For Android 6.0 Marshmallow

I removed the permissive hack, this kernel is back to selinux enforcing

You NEED SuperSU-2.50 for this one!

I'm not pushing it to EX Kernel Manager quite yet, because many people may be unaware they need to update SuperSU

Download:

ElementalX-N5-6.01 BETA

Changes:

-selinux enforcing

-sepolicy mod from Chainfire
[Nexus 5 Original Android Development] betodroid:
Flar,I install this kernel and superSU ,now my phone is on screenboot forever...in 6.00 boot normaly

Im on Xtrasmooth,what is the problem ?
[Nexus 5 Original Android Development] flar2:
No idea. Provide a log.
[Nexus 5 Original Android Development] nexttjme:
Battery life is good with stock and EX 6.0 (all default settings). 2,3 SOT and 60% battery left now ???
[Nexus 5 Original Android Development] yanleites:
Try Greenify "hibernate and sleep" widget :)

Afrer flashing su2.50 beta, is it safe flashing 6.01?
[Nexus 5 Original Android Development] roustabout:
very nice. Is per-app frequency control in the pipeline for this, or already present if I use something other than aduitor to control it with? Whenever i use the camera on my n5, cpu temp jumps 10 degrees C or more. I get that google wants to let the camera do all kinds of awesome stuff, but when the phone throttles down because the camera overheated it, it defeats the purpose. I'd be willing to clock the camera down to half open if it meant I could take pictures when I need to and not have the phone grind to a halt.

Just migrated to factory marshmallow to see if they'd done anything to improve that behavior. Looks like no, but then I wanted to see what kernels were ready to run.

And this one is very, very nice.
[Nexus 5 Original Android Development] Scartozzi:
so we have to flash first the kernel then the su 2.50 or the other way around?
[Nexus 5 Original Android Development] Wolfen38:
I've installed the 6.01 and supersu 2.50.

I've problem with power toggles. Now, I can't switch data on/off.

A solution ?
[Nexus 5 Original Android Development] BreckZeBoulay:
Now with EX kernel v6.01 we can have root access in secondary rom with MultiRom.

http://xdaforums.com/showpost.php?p=63193456&postcount=235

Many thanks [MENTION=4684315]flar2[/MENTION]
[Nexus 5 Original Android Development] Holer Togni:
For testing purposes, try setting SELinux to permissive. Open a terminal on the device, invoke "su" to become root followed by "setenforce 0". To go back to enforcing, type "setenforce 1" or simply reboot.

I'm suspecting SELinux policies to be the problem because I have some system settings trouble on my N9 with the latest ElX and permissive helps.

(Haven't gotten around to install Marshmallow on my N5 yet).
[Nexus 5 Original Android Development] rushilkr:
The kernel first, then SuperSu 2.50..
[Nexus 5 Original Android Development] Balino:
We are supposed to flash boot.img from chainfire before flashing SuperSU right?
[Nexus 5 Original Android Development] basti2909:
I dont think. Flash kernel then su 2.50

Boot.img Form chainfire is just if u want root on stock kernel
[Nexus 5 Original Android Development] Wolfen38:
It doesn't work, always same problem...
[Nexus 5 Original Android Development] xeraphael:
Mispost, sorry.
[Nexus 5 Original Android Development] Wolfen38:
How to uninstall the app ? I have only 'deactivate'
[Nexus 5 Original Android Development] NovaSlim:
The ElementalX app? The uninstall button is clearly visbile to me, though I'd never press it:p
[Nexus 5 Original Android Development] flar2:
No, just flash EX

If there are problems, send a log. Some custom roms seem to be deviating already and it's causing problems.
[Nexus 5 Original Android Development] Wolfen38:
Xeraphael said me to uninstall supersu but i just can 'deactivate', not uninstall....

he modified his post, it was a mistake....

So, i always have my problem.....
[Nexus 5 Original Android Development] flar2:
Wipe the app data
[Nexus 5 Original Android Development] Wolfen38:
It'll erase my phone ???? I'll have to install all my app after ?
[Nexus 5 Original Android Development] SketchyStunts:
no for gods sake..no
[Nexus 5 Original Android Development] xeraphael:
FWIW, eng.stk isn't implementing Chainfire's sepolicies into his kernel ramdisk. His approach requires flashing Chainfire's modified boot.img first for the ramdisk, and then flashing his kernel (for root on stock).

Which seems to make sense, if custom ROMs are messing with stuff already...

---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------

Yeah, I made a bad post. I'm using Power Toggles as well though, and "setenforce 0" seems to do the trick for me.

You can't uninstall Power Toggles because you installed it as a system app. You'll have to manually delete it from wherever you installed it to using a root-aware file manager, or from a rooted shell environment.
[Nexus 5 Original Android Development] Wolfen38:
I'm really bad... :(

I've written 'su setenforce 0' in a same line in terminal, so It didn't work.

Just with 'setenforce 0' it works.

Thanks.
[Nexus 5 Original Android Development] flar2:
That could introduce other incompatibilities and entirely defeats the purpose of reusing the ramdisk. Might as well just ship with Chainfire's boot.img.
[Nexus 5 Original Android Development] flar2:
You could also flash the permissive zip from the OP
[Nexus 5 Original Android Development] xeraphael:
I'm curious, but how? Flashing Chainfire's modified boot.img is required only if you're rooting on stock. For custom ROMs with their own ramdisk, you skip Chainfire's boot.img and just reuse the custom ROM's ramdisk. Custom ROMs most likely come with root, so their ramdisk would have the needed sepolicies already, along with what else they modified.

Looking to learn here, correct me if I'm wrong!
[Nexus 5 Original Android Development] flar2:
That will be an ongoing problem if root ends up requiring ramdisk changes

For now, I suspect these roms just don't work with an enforcing kernel. There were a bunch like that on lollipop, so people may have to flash the permissive zip.
[Nexus 5 Original Android Development] yanleites:
[MENTION=4684315]flar2[/MENTION], after flashing su2.50 the super user disappeared, I installed the APK from the ZIP common folder, and it's fine. Can I now flash 6.01?
[Nexus 5 Original Android Development] flar2:
You should be able to.

If it doesn't work, go back to 6.00
[Nexus 5 Original Android Development] menting:
I'm seeing something strange with 6.00 and 6.01. Cores 2,3,4 are pegged at 2265 MHz it seems, and it's heating up a lot when charging (as well as drawing a ton of power since the CPUs are pegged)

Installed xTraSmooth Rom (Android 6.0) => CPUs are fine, when charging the CPU gets to 54C.

Installed SuperSU 2.50 => CPUs are fine, 54C still

Installed 6.00 or 6.01, => Core 0 is fine, Cores 2,3,4 pegged at 2265, when charging it gets up to 59C and up

Installed permissive.zip => still same issue.

I installed ElementalX with the default settings, and turned off Sweep2Sleep

edit: Looks like xTraSmooth Rom is using Hells kernel. Makes me wonder if it's the switching between custom kernels that's causing it.
[Nexus 5 Original Android Development] yanleites:
Works...., As usual..., [MENTION=4684315]flar2[/MENTION], Small problem. On 6.01 "Greenify hibernate and sleep" widget doesn't work... Only hibernate.

What can be the problem?
[Nexus 5 Original Android Development] kojak1989:
Can i flash this kernel over the modified boot.img from Chainfire? because when i flash stock boot.img i have a bootloop.
[Nexus 5 Original Android Development] flar2:
6.00 is permissive, 6.01 is enforcing. There are still little things that won't work with enforcing kernel and latest SuperSU.

Remember, root on Marshmallow is still a work in progress.

If you need stuff to work, just use 6.00. The only kernel difference is permissive vs. enforcing.

Anyone who has a bit of know-how should be reporting relevant details of these issues to the app developer and possibly Chainfire.

Depending on what Chainfire comes up with, many root apps may have to be updated.

I predict that going forward, many root apps will have to make selinux changes themselves using the supolicy tool.
[Nexus 5 Original Android Development] yanleites:
Ok.

Back to 6.0!
[Nexus 5 Original Android Development] flar2:
EX 6.01 has the relevant parts of Chainfire's boot.img already.

Some users have reported bootloops with custom ROMs, which may still require permissive kernels. In that case, use 6.00 or the permissive zip.
[Nexus 5 Original Android Development] and313:
Good news! Nice to see it move ahead so quickly
[Nexus 5 Original Android Development] Balino:
Everything is OK here with supersu 2.50 and elementalx 6.01 version. All apps are working correctly and with superuser permission .. Thank you for the update
[Nexus 5 Original Android Development] mayurh:
With the amount of faulty nexus 5 power I'm wondering if it'll take long for volume rocker wake to be implemented? Sorry if it has been asked
[Nexus 5 Original Android Development] flar2:
Is this a feature that people want?
[Nexus 5 Original Android Development] mayurh:
Thanks for your response, yes most definitely from my side and a lot of users with power buttons acting up.
[Nexus 5 Original Android Development] RusherDude:
I'm not really interested in that, but if you don't mind, a question:

Considering your kernel implements DT2W and S2W (and implements them BRILLIANTLY, seriously, this is the first time in years that I get some kernel making 2W features work absolutely 100% of the time. Kudos for that! :good:), how hard it would be to implement something like permitting swipe/touches patterns to turn on the screen or even unlock the phone (like LG does, but LG implementation sucks with the only 4-grid tbh). I know you're not into lockscreens and such tho.. Imho this would be awesome and a very-distinctive feature for your module, worth even a new IAP only for it lol.

Also as a minor suggestion, instead of releasing versions with permissive/enforcing selinux, couldn't it be possible to ask for selinux status in the AROMA installer itself when flashing the kernel?

Keep up the excellent work :fingers-crossed:
[Nexus 5 Original Android Development] Koopa777:
Certainly! I got used to it on custom ROMs, and the number of times I've pressed the rocker expecting the screen to wake this week on 6.0 is frustrating, to say the least. :laugh:
[Nexus 5 Original Android Development] walpurgisnacht30:
I'd be really happy if you implement this since there are a lot of people out there who has broken power button issue like me on their Nexus 5 but still want to stick with stock rom.
[Nexus 5 Original Android Development] NovaSlim:
Useful on N5, but probably not needed for newer phones, 5X/6P probably don't even need DT2W/S2W as placing your finger on the FPscanner wakes and unlocks automatically.
[Nexus 5 Original Android Development] fajarlazuarding:
I vote one for this ?
[Nexus 5 Original Android Development] flar2:
It looks like there are already multiple apps on the Play Store that will turn the volume button into a power button.
[Nexus 5 Original Android Development] androcraze:
Sometimes it's better to leave something (that works well) alone....
[Nexus 5 Original Android Development] yanleites:
With SuperSU 2.51 and 6.01 Greenify screen off doesn't work too. [MENTION=4684315]flar2[/MENTION]
[Nexus 5 Original Android Development] xeraphael:
Guys, I don't know I might be wrong, but I think flar2's job is working on the EX kernel, not on Greenify or other root apps you guys might be using.

Pretty sure there are other threads on xda for that.
[Nexus 5 Original Android Development] yanleites:
I never said something about flar, he is great, I just thoughthe ccan help me with it.

With 6.0 everything works fine.
[Nexus 5 Original Android Development] Wout2426:
Volume wake is not yet in any m ROM. And that's why I didn't install it yet, it's what I'm waiting for. Would be great !
[Nexus 5 Original Android Development] Atok_fr:
Every thing works great with EX 6.0 on MM. All is perfectly smooth, no overheating and great great battery life. Thank you for your work !
[Nexus 5 Original Android Development] arboeh:
Boot hangs since CM 12.1 (20151006)

Since updating CyanogenMod to cm-12.1-20151006-NIGHTLY-hammerhead I have a serious problem with the latest 4.09 on my Nexus 5: It hangs at the boot screen.

After changing kernel to 3.4.0-blue_spark-5.1.1 (sorry for that) everything works fine...
[Nexus 5 Original Android Development] matze0611:
I got SuperSU 2.50 and Greenify 2.7.1, and screen off works fine.

Only Greenify doesn't work anymore :(

If I want to install the 6.00 kernel, is it OK just to overwrite the 6.01 kernel?
[Nexus 5 Original Android Development] yanleites:
Just flash 6.0.
[Nexus 5 Original Android Development] matze0611:
I flashed it but Greenify doesn't work neither, I think it doesn't has to do with the kernel, I wrote an email to support.
[Nexus 5 Original Android Development] Balino:
Greenify has been updated to work better with MM with the 2.7 beta 8 version. You can find it at his xda thread .

Anyway with 6.01 and SuperSU 2.50 root explorer couldn't recive root permission , on 6.0 it's working fine through

[MENTION=4684315]flar2[/MENTION] could I ask you if it's possible to modify powersave mode into your application to do not disable third and fourth core when we activate it while running custom hotplug?

Or maybe add a switch in the settings to disable core 3 and 4 when activating powersave mode?

Thank you for reading

An option like :with the option checked it will disable 2 core when activating powersave mode. If unchecked it will keep all 4 cores online
[Nexus 5 Original Android Development] matze0611:
No, I had SuperSU 2.50 and 6.01, and my root explorer worked fine :)
[Nexus 5 Original Android Development] Balino:
Maybe it needed a clean install to work again. Things are still too random on android 6.0 [emoji28]
[Nexus 5 Original Android Development] matze0611:
I have one more question about this kernel.

If an update of Android M will come, normally I flash it with fastboot.exe by flashing boot.img and system.img. I don't flash userdata.img cause I don't want to loose my apps.

Now that I am using this kernel, can I flash only system.img and not boot.img? Or should I flash boot.img and afterwards again this kernel here?

Maybe Google makes some changes in his kernel, that's why I am asking.

Thank you. :)
[Nexus 5 Original Android Development] flar2:
Flash stock boot.img and then flash this kernel in recovery
[Nexus 5 Original Android Development] flar2:
Reflash your ROM
[Nexus 5 Original Android Development] arboeh:
I always reflash my ROM on CM updates and after that I reflash the kernel. Problem exists since 20151006 version of CM..
[Nexus 5 Original Android Development] pr0xyw0rm:
Everything is fine so far with latest CM 12.1 nightly and EX 4.09. Reflash ROM and Kernel.
[Nexus 5 Original Android Development] yeiyei0891:
What i need for root my nexus with this and Android M? Flash EX kernel and superSU? What version?
[Nexus 5 Original Android Development] haseoxth:
Also want to say for some apps which need root permission. If they don't work normally remeber to check the SELinux status on your device and set it to permissive(some may also not work after this, then maybe they all need an update from their developers).
[Nexus 5 Original Android Development] yanleites:
EX kernel 6.0 and SuperSU 2.49,50,51... One of them.
[Nexus 5 Original Android Development] yeiyei0891:
What should I flash first?EX kernel or SuperSU?

Thanks.
[Nexus 5 Original Android Development] adnan.selimagic:
First EX kernel and then SuperSU
[Nexus 5 Original Android Development] dechronic:
In the last few posts on the SuperSU Beta thread someone posted a logcat of a problem with root explorer and Chainfire said the developer (s) need to update/modify the code.

Since this a new Android version there will be a lot of updates and testing for all app, kernel and ROM developers so report a problem in the relevant thread to help further development to help discover and resolve any problems.

If you find the problem today please don't expect it to be fixed the same day as we all live in different time zones.

Remember....developers are human beings not artificial intelligence....yet..lol

So they need enough sleep...
[Nexus 5 Original Android Development] flar2:
I've thought about the knock code or pattern, andI feel this is best implemented in userspace rather than the kernel so it can be integrated with the lockscreen. The kernel has no ability to influence the lockscreen so it needs to be an app or xposed module. A while ago, someone was working on an xposed module, I don't know what came of it, and I can't remember if I exposed the touch coordinates during screen off on this device or not (I did on at least one other device). Right now I'm extremely busy, but something like this might be a possibility down the road.

For selinux, I used to have this in aroma, but because of the huge trouble I got into with my app due to selinux, I removed the option. Now I suggest flashing the permissive zip in the OP if you need permissive. I want the kernel to be enforcing by default because that is Android's security model. There should be no reason to run permissive. Devs need to start using supolicy to make their apps and mods work with selinux enforcing. Rather than forcing users to run permissive, they could add one or two lines to their code to change the permissions as necessary.
[Nexus 5 Original Android Development] RusherDude:
AWESOME :good::good::good:, even if it came as a separate app or xposed module, I (and I bet a ton more ppl) wouldn't mind paying again for this (even if it wasn't into the elementalX app or separated into it into some new IAP section)!. Let's hope in the future you're less busy and somehow we motivate you for this, since I never saw something really coming out beating LG implementation... and it's sad, because it is awesome... :victory::victory:

Yeah I know the story, Google are so randoms banning for selinux change commands and such.. I agree that enforcing should be the way to go and if you wanna change that, then move for it, but the stock option should be enforcing.

Thanks a lot! :victory:
[Nexus 5 Original Android Development] ollidiemaus:
Oh man I wasn't reading carefully enough so thank you.

And flar good luck finding the proximity Sensor in the next year ;)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] zioxda:
Amazing Flar: 35511 stock rom ;)

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] DoesntPostAThing:
I'm getting anywhere between 28k to 32k on both 020 and 021, but it's really smooth on both so score doesn't really matter. Never gotten over 32k though, strange. Does using ART interfere with the dalvik tests?
[Nexus 5 Original Android Development] lethalboy:
0.21 running very well & smooth with Cataclysm here :D
[Nexus 5 Original Android Development] kmar22:
Hey guys are you undervolting (stock value 750 min) with the latest or keeping stock?
[Nexus 5 Original Android Development] 1337RYoN:
There is never a best kernel :)
[Nexus 5 Original Android Development] drawde40599:
I'm at 700 without issue ,one phone PVS 4 . other PVS 2 . I don't see a reason to go lower besides just to see if I can
[Nexus 5 Original Android Development] kmar22:
Thanks!

---------- Post added at 02:08 AM ---------- Previous post was at 02:08 AM ----------

Flashed and loaded all my crap and so far very smooth..
[Nexus 5 Original Android Development] Lancez:
been tethering for over 4 hours playing MW3 multiplayer game this afternoon, still got 80% juice left :good:

same ROM and kernel as flar's :victory:
[Nexus 5 Original Android Development] Sensamic:
Hi.

How can I get back to stock kernel after flashing the elementalX kernel? Do I need to flash the stock factory image or is there a more simple way?

Thanks.
[Nexus 5 Original Android Development] CRIME INC.:
http://xdaforums.com/showthread.php?t=2518816

[KERNEL] [4.4] [Stock]

sent from my Hammerhead Nexus
[Nexus 5 Original Android Development] Sensamic:
Great! Thanks!
[Nexus 5 Original Android Development] flar2:
I just noticed I forgot to update the exfat module in the latest installer. Oh well, not many people need this and the next version is coming soon enough.
[Nexus 5 Original Android Development] wantabe:
Restore "Boot" from your backup (nandroid).
[Nexus 5 Original Android Development] Johnny424:
hey flar..I had a random reboot on 21 a few minutes ago. my phone was sleeping on the desk for a few minutes..I woke and and tapped on an app to open and it rebooted. I pulled a last_kmsg right after boot so hopefully it helps some. I uploaded to paste.bin but not sure I did it right. here is the link if someone could take a look at it to see if it helps at all

running stock 4.4.2,2300max,400min,no UV,elemental gov

http://pastebin.com/hJEywEsZ
[Nexus 5 Original Android Development] zioxda:
Sorry you are right, I forgot bionic and Dalvik opt, I have them since they were published
[Nexus 5 Original Android Development] tommy.mann:
I undervolted to 700 by 300MHz

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] flar2:
That log looks fine, no errors
[Nexus 5 Original Android Development] blowtorch:
flar2, how about a non aroma version please? :)
[Nexus 5 Original Android Development] Johnny424:
I think I caught it to late then..thanks for taking a look at it anyway
[Nexus 5 Original Android Development] sherincal:
I don't know if it's of any help to anyone, but I was.... bored? And I ran some tests with the newest ElementalX kernel vs the stock comparing the storage performance while full stock, ElementalX with F2FS on data and cache and ElementalX with all ext4.

Here are the results:

I used Androbench and ran the Micro test to test the speeds. I guess the other benches would have yielded some good data as well, but writing it all down felt a little bit too much work for 2AM.

Cheers.
[Nexus 5 Original Android Development] fajarlazuarding:
So the results were not that much different, right ?
[Nexus 5 Original Android Development] alvintimothyjr:
It's not ART on my end. It must be one of my apps...seems I can manage it by using power saving mode when charging the device. Playing games are a no go for now however.
[Nexus 5 Original Android Development] Balino:
I know I was just reporting in case someone else had this problem.

Thank you anyway
[Nexus 5 Original Android Development] Sviborg2241:
Dunno about static tests, but in IRL testing I had second to none improvement in performance with F2FS back on Lollipop. I suppose it's the same for Marshmallow as well :)

F2FS does the trick only for devices which initially have issues with I/O performance like Nexus 7 and old Asus tablet line. On Nexus 5 it only gives you an extra hassle with reformatting, kernel modifications and reflashing roms, it's not worth it.
[Nexus 5 Original Android Development] Balino:
Not bad at all! Great kernel
[Nexus 5 Original Android Development] and313:
Btw how is the plan for n5 future updates?
[Nexus 5 Original Android Development] RusherDude:
Is that even a question? N5 got M and it's unsure if it will get N (if it takes another year for N to be released and Google keeps their policy, they may stop upgrading N5, even if N5 is equally powerfull for anyday uses than N5X/N6P.. it will be a bloody day on forums). Of course he will keep doing his great work on a supported device, and who knows later :laugh:
[Nexus 5 Original Android Development] flar2:
Netflix (and possibly other video stuff) is impossible to use since the Marshmallow update. Just letting everyone know this is not an elementalx issue, it happens on stock too, so the bug is either Netflix's or Google's. Nothing is showing up in the kernel log, so we may have to wait for Netflix or Google to fix it.
[Nexus 5 Original Android Development] janres155:
I see, so no "netflix and chill" for the weekend. [emoji20]
[Nexus 5 Original Android Development] yanleites:
With SuperSU 2.52 and ElementalX 6.01 everything works!