yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] dimine:
LineageOS is still on Nougat, had to give up on your kernel, too :(
[Nexus 5X Original Android Development] SlimSnoopOS:
Flar2 does not update Nougat Ex. He was referring to Oreo Ex since it was recently updated. Anyone running Nougat roms (myself included) with security changes backported into the rom will miss out on any kernel based security updates if they flash the last Nougat EX kernel.
[Nexus 5X Original Android Development] kridster:
That was the answer, I was looking for. Thanks. So there are kernel and ROM related security issues, which have to be patched separately. Is that correct?

Hopefully, LineageOS will update to Oreo soon.
[Nexus 5X Original Android Development] SlimSnoopOS:
Not always but generally speaking yes. You can always read about what's specifically been updated in the latest Android or Nexus/Pixel specific security bulletin. This is updated on the first Monday of the month that is not a US holiday:

https://source.android.com/security/bulletin/

If you're strict about maintaining security patches, stick to the stock Lineage OS 7.1.2 kernel since this includes security patches.

Coincidentally, I'm in the same situation as you. My daily driver is Dirty Unicorns and I'm also patiently waiting (lol) for them to update to Oreo. So I stick to Nougat Ex until Oreo DU officially arrives.
[Nexus 5X Original Android Development] BS86:
Well, i WAS in the same situation (waiting for PureNexus to update to Oreo) - But I gave AICP a shot as they already build nightlies based on LOS15 - and will not go back to PN. AICP basically offers the same slim/basic stock Android features with Pixel-optics AND is rock solid. ElementalX works without issues there.
[Nexus 5X Original Android Development] marcelojudoka:
Hi guys, I have a question.

How to enable LED charger on stock ROM? In EX Kernel Manager? I'm using latest Oreo version, with ElementalX 5.0.6.

Thanks
[Nexus 5X Original Android Development] OhioYJ:
Yes. And the guy you responded to was referring to Nougat as well. Lineage is still on Nougat for this device. Even when Lineage makes the leap to Oreo, I probably generally won't switch for quite some time just as when they first switch they are missing a lot of features.
[Nexus 5X Original Android Development] flar2:
I don't want to downplay security too much, but even without the last two or three months of security patches, using EX 4.x with LineageOS is still more secure than about 99% of Android users in the world. You'll be fine.
[Nexus 5X Original Android Development] gorilla p:
Is anyone else losing Magisk Root after flashing latest EX?
[Nexus 5X Original Android Development] yochananmarqos:
Nope. I would flash your stock boot.img, Magisk then EX.

/OT You made the Nexus 4 modem flasher, right?
[Nexus 5X Original Android Development] gorilla p:
I am. I'm having some issues and trying some different things. Just uninstalled magisk, reinstalled 14.0 and now everything is working normally.

Originally started having a lot of issues with a couple new Oreo builds (ABC and Validus). Everything appears to be in order now.

/OT No, I didn't make them but helped keep track of them and made the makostuff repository to host all kinds of nexus-related stuff
[Nexus 5X Original Android Development] Lossyx:
Flash kernel first then magisk.
[Nexus 5X Original Android Development] elmagio:
Since the app struggles with root permissions with CM's default root, would it be possible to include the possibly to disable touchboost (arguably the best feature of this kernel) directly from the Aroma installer? Or is that something that needs to be done in app?
[Nexus 5X Original Android Development] flar2:
I will add it to aroma soon. There are some selinux complications with that setting.
[Nexus 5X Original Android Development] HeinousJ:
I'm missing something obvious.. Please help. Every time I try to install the backlight dimmer option I get a bootloop. I let it spin for 20 minutes last time just to make sure I wasn't impatient. I re-read all related posts but I must be blind. I have to re install the entire system to fix it. I'm running pure nexus on a nexus 5X, always clean flash.
[Nexus 5X Original Android Development] flar2:
You mean if you check backlight dimmer in AROMA it bootloops, if you don't check it, it boots?

Could be a problem with the installer, but I need confirmation.

This is the kind of stuff I need people to carefully troubleshoot for me, as it is fairly easy to do and I am extremely busy (literally, every minute of every day is spent).
[Nexus 5X Original Android Development] dfryer1193:
I just tested this by flashing 1.02 on top of 1.02 express.

No bootloop.

I'll give it a try by going back to stock and let you guys know what happens.
[Nexus 5X Original Android Development] SlimSnoopOS:
I doubt it's the installer. I went full stock last night just to make an EFS backup then reinstalled systemless SuperSU and Elemental. I selected backlight dimmer, disabled touchboost, and Sw2S which booted just fine.
[Nexus 5X Original Android Development] dfryer1193:
After going back to stock I successfully installed ElementalX 1.02 with the backlight dimmer checked, and booted without bootlooping (though the boot did take a long time compared to a normal boot).
[Nexus 5X Original Android Development] HeinousJ:
I'll try again. I'm probably just getting impatient. How long did it take to get past the boot animation?
[Nexus 5X Original Android Development] dfryer1193:
I don't remember exactly, but it was maybe 2-5 minutes.
[Nexus 5X Original Android Development] flar2:
That couldn't be caused by enabling the backlight dimmer, sounds like it was re-optimizing ART.
[Nexus 5X Original Android Development] dfryer1193:
I figured - it does that every time I install ElementalX over stock. Not bothered by it, just mentioning it so people don't worry!

Thanks for all your hard work by the way! Greatly appreciated! Something I only just noticed is that the home button doesn't seem to work when sweep to sleep is disabled from the AROMA installer. Could've been something else though. Fixed by reflashing ElementalX with sweep to sleep left enabled. No idea if that's possible, but it was the only reason I could think of for the home button not working across reboots.
[Nexus 5X Original Android Development] HeinousJ:
Installation woes..* I retried the installation and here is how it went:

Nexus 5X

- wipe cache and dalvik

-- Install EX 1.02 via aroma

--- only changed selection for backlight dimmer

- reboot system

Phone sat on boot animation for 30 minutes

Force boot to recovery

- wipe cache and dalvik

- Re-install EX via aroma

-- selected all default settings

- reboot system

Phone sat on boot animation for 30 minutes

Force boot to recovery

- wipe cache and dalvik

-- flash Pure Nexus 20151209

-- Pure Nexus Gapps 20151208

-- Bullhead vendor img MMB29K

-- google dialer for fi support 1209

-- EX via aroma

--- kept all default values

Phone took two minutes to boot.

I do not know what is wrong but, the backlight dimmer is not working for me.* I can select the dimmer option within EXKM however I do not know if it does anything.* Other than this, everything is great! I will try again on the next update.
[Nexus 5X Original Android Development] flar2:
Update!!!

Download

ElementalX-N5X-1.03

Changes:

-update LED to work with Cataclysm

-a few optimizations
[Nexus 5X Original Android Development] flar2:
Update!!!

The previous update for LED control in Cataclysm didn't work completely right, so I've went with the original patch from atl4ntis.

Download

ElementalX-N5X-1.04

Changes:

-update LED to work with Cataclysm (part II)
[Nexus 5X Original Android Development] randman2011:
Updating to 1.04 fixed all of my LED problems and I am not even on Cataclysm. I was coming from 1.01 which was working perfectly. Didn't really try to troubleshoot because updating the kernel was the first thing that I tried. Thanks for keeping those updates coming, flar2!
[Nexus 5X Original Android Development] gpvecchi:
Sorry, do I have to flash kernel before or after superSU? Thanks!
[Nexus 5X Original Android Development] Smultie:
Before
[Nexus 5X Original Android Development] till22:
That's because [MENTION=3913401]atl4ntis[/MENTION] is a universal problem fixer :laugh::laugh::laugh:
[Nexus 5X Original Android Development] leAndroid91:
Is there a list of upcomming features?

I would like to have undervolting for the cpu.

Had good experiences with franco on hammerhead.
[Nexus 5X Original Android Development] andresee:
Delete
[Nexus 5X Original Android Development] 23icaro:
When will the kernel be updated to DP1 of Oreo 8.1.0 ? At now i'm using franco + Ex Manager, but touchboost remains ON, and this combination isnt to good like ExManager + Elemental X Kernel... If there's how install Elemntal Kernel on the DP1 8.1 please someone tell me!!
[Nexus 5X Original Android Development] joetheshmo:
8.1 source isn't released so it's impossible to build for it atm
[Nexus 5X Original Android Development] 23icaro:
Aaaaa, thats explains a bunch of things... Thanks for the info bro!! :)
[Nexus 5X Original Android Development] androidalexm:
Hi everyone. I just switched to android O with the AICP rom and I'm not able anymore to switch color profile. As soon as I lock the phone it reset the profile to stock...

With android N I didn't have such problems...

Is it a common problem on oreo or is it just me and this rom?

Thanks in advance
[Nexus 5X Original Android Development] 0xcafebabe:
Check settings>display>live display

It interferes with the colour profile
[Nexus 5X Original Android Development] akilanmc:
Hi all,

I'm new to this thread, yesterday I flashed this Oreo kernal. Now I'm wondering whether I can able to install lineage os 14.1 or I need to wait for lineage 15. Please advise.

Thanks
[Nexus 5X Original Android Development] 23icaro:
Thats better you re-do a clean instalation of stock, then install the custom rom (LineageOS in this case) and then put the kernel. The kernel works with every 8.0.0 or minor android system's version, soo if you're using lineage 14 or 15 I guess that will work to both. If you want to try, just flash the ROM now or for better results re-flash the boot.img of your actual rom or the entire rom and then put the kernel.

Attention to a fact: when you install a custom ROM sometimes the ROM can flash a boot.img, if a new boot.img be flashed, your kernel will be replaced, soo install the rom and then the kernel. Always will be this sequence!

Best whises bro!!! :))
[Nexus 5X Original Android Development] SlimSnoopOS:
You quoted the wrong person.
[Nexus 5X Original Android Development] androidalexm:
Thanks for your answer.

After disabling it, nothing changes. After locking the screen it returns to the stock profile. Anyway I noticed that saturation and brightness remain to the values set by me and don't reset like the colors.

Any other idea?

Thanks in advance
[Nexus 5X Original Android Development] 23icaro:
AW sorry broo haahaha
[Nexus 5X Original Android Development] flar2:
Update!!!

Android 8.1.0 update

Download

ElementalX-N5X-6.0.0

Changes:

-update for Android 8.1.0

-December security patches
[Nexus 5X Original Android Development] snacdaws:
The app doesn't show the changelog

Had to look both on XDA and g+ before I thought to look here for it

Thought you should know incase it's a bug or something like that

Edit:

Of course as soon as I said that it shows up fine
[Nexus 5X Original Android Development] harib12:
you are fast bro
[Nexus 5X Original Android Development] Bonez1802:
I was waiting for your update to switch to 8.1 .. thank you.. fast & furious.. ?
[Nexus 5X Original Android Development] srnoth:
Working great so far :good:.

One thing I've noticed over the last couple releases, even though FIOPS is selected by default in the Aroma installer, the NOOP scheduler is what the phone actually boots with. To get FIOPS I have to set it through your app.

Not a big issue - hopefully an easy fix!
[Nexus 5X Original Android Development] batman368:
Works flawlessly on stock 8.1 release. I can confirm then little issue with the fiops and noop, but apart from it works perfect!

Thanks for your great work!
[Nexus 5X Original Android Development] flar2:
That has nothing at all to do with the kernel.
[Nexus 5X Original Android Development] CazeW:
Don't know why but it's still caused by flashing the kernel. I've tried it four separate times now with a re-downloaded zip and with the normal version instead of express. Going back to stock always fixes it.
[Nexus 5X Original Android Development] dechronic:
What he means is that a logcat has nothing to do with the kernel. There are different logs for the kernel. Specifically last_kmsg and dmesg.

Edit; Additionally how are you flashing the kernel on your N5X? Do you flash your su solution of choice first and then the EX kernel?

With SuperSU there is one boot loop that must occur before the changes are applied.
[Nexus 5X Original Android Development] CazeW:
Couldn't find last_kmsg anywhere (none to be found in /proc/last_kmsg). Only thing I managed to get is the attached dmesg.

I think this where the crash happened:

[32m[ 61.119042] [33m12-07 14:45:24.874 E/keymaster1_device( 772)[0m: Begin send cmd failed
[32m[ 61.119066] [33m12-07 14:45:24.874 E/keymaster1_device( 772)[0m: ret: 0
[32m[ 61.119088] [33m12-07 14:45:24.874 E/keymaster1_device( 772)[0m: resp->status: -30
[32m[ 61.119111] [33m12-07 14:45:24.876 E/keymaster1_device( 772)[0m: Abort send cmd failed
[32m[ 61.119135] [33m12-07 14:45:24.876 E/keymaster1_device( 772)[0m: ret: 0
[32m[ 61.119158] [33m12-07 14:45:24.876 E/keymaster1_device( 772)[0m: resp->status: -28

And like I mentioned in the previous post, I flashed SuperSU first, then ElementalX. I'm not having issues with boot loops, I'm having a problem getting past the lock screen.
[Nexus 5X Original Android Development] flar2:
It has absolutely nothing to do with the kernel.

Lockscreen and kernel are simply not related in any way.
[Nexus 5X Original Android Development] CazeW:
As much as you're saying that they are not related, something is definetily going amiss after installing the kernel. I'm just guessing here but could it be something that it fails to decrypt data which causes it to "restart"? But it doesn't seem to be caused by this kernel specifically, happens with the new Franco as well so it's something with my phone. Really weird though...
[Nexus 5X Original Android Development] SlimSnoopOS:
Flash the 8.1 system and boot image then flash Ex 6.0 or Franco. Make sure you also have the 8.1 bootloader and radio installed before flashing 8.1 kernels.
[Nexus 5X Original Android Development] CazeW:
Already done that. I'm not trying to install a 8.1 kernel on 8.0.
[Nexus 5X Original Android Development] zurik:
I am not facing any issue like yours on my 5X
[Nexus 5X Original Android Development] stifmaster81:
Do not have an excess battery with elementalx and android 8.1?

Enviado desde mi Nexus 5X mediante Tapatalk
[Nexus 5X Original Android Development] ywy9876:
Stayed in reboot stage (circle are spinning) after flashed the kernel 6.0...
[Nexus 5X Original Android Development] dechronic:
You flashed it and you are using Android 8.1?
[Nexus 5X Original Android Development] bland.life:
So kernel 6.0 is strictly for 8.1 ROMs?
[Nexus 5X Original Android Development] Lughnasadh:
I am using it on an 8.0 rom and have had no problems. Anecdotal comment here... :)
[Nexus 5X Original Android Development] CazeW:
The issue I'm having is just weird. I've tried without SuperSU, I've tried reinstalling the OTA and doing a factory reset but none helped. I can get past the lockscreen by removing the PIN before flashing ElementalX, but when I go to settings to enable it again and after typing (and retyping) my PIN, it asks for it a third time but now keeps telling me it's wrong.

EDIT: Even Googles Find My Device fails to lock the phone with the error that it failed to decrypt the blob. By going back to stock kernel and locking the phone with find my device I can replace the unworking PIN.
[Nexus 5X Original Android Development] Clae:
Maybe try following the instructions if you restore a backup with fingerprint / pin enabled? (after flashing Ex) It is a very strange bug, so I'm taking stabs in the dark here...
[Nexus 5X Original Android Development] CazeW:
What instructions? But anyhow that wouldn't help as the issue is not being able decrypt the blob which keeps the password. I've come to the conclusion though that it's an issue with my phone and Oreo 8.1, as I decided to try with both ElementalX 5.06 and Franco r48 which both worked fine in 8.0. ElementalX 5.06 ended up in a bootloop but Franco r48 booted and had the same issue with the PIN.
[Nexus 5X Original Android Development] yochananmarqos:
Can you reproduce the issue in Safe Mode?
[Nexus 5X Original Android Development] flar2:
The best thing to do when you have a weird unexplained problem is a full wipe and reinstall of factory images. You will waste more time on a fruitless toubleshooting mission than you will backing up your stuff and starting from scratch. These days almost everything is saved in the cloud and it takes very little time to get your device back up and running.
[Nexus 5X Original Android Development] CazeW:
I don't mind the troubleshooting, you learn more stuff that way, but I've come to the conclusion that a full wipe with the factory images is probably the only way I'm going to fix this. As the stock kernel still works, I might as well wait until we get Oreo based TWRP with FBE support before wiping.
[Nexus 5X Original Android Development] flatpedals:
Ok so I have a little trouble with mounting /system as RW. I'm not sure where to ask, sorry if I'm off here. I read it could be a kernel issue (dm-verity?), even tough it was exactly the same on the stock kernel.

I'm running the fresh 8.1.0 factory, clean flash, with latest ElementalX and Magisk 14.5.

Titanium Backup WON'T uninstall any system app, even if I get the ok notification.

I CAN delete /system files in TWRP File Manager after mounting /system. (used it to replace the thermal engine - Magisk module didn't work).

Solid Explorer shows /system as 755. When I try to change it to 777, it gives me "Unable to remount the file system under /system". I CAN'T delete anything from /system using Solid Explorer.

Both Titanium Backup and Solid Explorer have all the permissions enabled and "modify system settings" checked in settings, if that counts.

AdAway DOESN'T work, even though I have the systemless hosts checked in Magisk Manager.

AppSystemizer Magisk Module IS able to make system apps and installs itself as a system app.

***FX File Explorer gives me "Protected filesystems remounted with write access: {/system}".

I have tried mounting in terminal emulator, adb shell - nothing works.

What's the deal with all the inconsistency?
[Nexus 5X Original Android Development] AndroidDeveloperLB:
Good job on giving us 8.1 so soon after stable version of the OS!
[Nexus 5X Original Android Development] notstevek:
So just to confirm, this will work on 8.1 (OPM1) with Magisk 14.5 beta?
[Nexus 5X Original Android Development] flar2:
You shouldn't mount /system these days. Use Magisk to do whatever you need systemlessly
[Nexus 5X Original Android Development] flatpedals:
Yep, would be ideal.

The thing is I can't change the thermal engine systemless-ly and Titanium Backup is also handicapped.

Coming from 7.1.2 where I didn't have these problems. Did the oreo kernel changed to protected file system? Can it be removed?
[Nexus 5X Original Android Development] SlimSnoopOS:
Thanks for this post. I bumped up to 8.0 stable yesterday and Ex 6.0 works well for me too.
[Nexus 5X Original Android Development] stifmaster81:
It consumes me a lot of elementary battery 6.0 with android 8.1, someone else happens?

Enviado desde mi Nexus 5X mediante Tapatalk
[Nexus 5X Original Android Development] Maerk-051:
Does this Kernel work with AICP?
[Nexus 5X Original Android Development] Lughnasadh:
Yes
[Nexus 5X Original Android Development] Aman301582:
Request: Please add night mode feature in your app. Or a tile to toggle color profiles.
[Nexus 5X Original Android Development] yochananmarqos:
I'm guessing if he was going to, he would have by now. I use Night Light which does exactly the same thing as the Night Shift feature in Kernel Manager for Franco Kernel.
[Nexus 5X Original Android Development] Aman301582:
Thanks, didn't know about this app. Very useful.
[Nexus 5X Original Android Development] Vipauer:
Hi friend,

What's the difference between that app and this app?

Thanks your help :good:
[Nexus 5X Original Android Development] gerstlauer:
I can't remember exactly why, but I preferred, and still use the one you mentioned.
[Nexus 5X Original Android Development] yochananmarqos:
Try them both and see which you like better. The one I mentioned has more options and has a Quick Settings tile.
[Nexus 5X Original Android Development] tyroneballz:
version 6 helps with the wifi problem on 8.1 december?? thanks
[Nexus 5X Original Android Development] Addicted2Bass:
hello, for safety i did first a full backup and then installed the 4core EX kernel, after booting phone is stuck in the famous loop,

i have a modified 4core img on my N5X did i installed the kernel wrong? i needed to set the speed of the big clusters which are causing the whole problem
[Nexus 5X Original Android Development] dechronic:
First thing. Use the official Ex Kernel for the version of Android you are using. There is no need to have a "modified 4 core img" because once you have it installed, you can modify the speeds of the cores and a whole lot more and to make it even easier flar2 has made an ex kernel app to manage all of that and in case you don't want to modify any of the values because you don't want the hassle of it just use a profile. You can use any of the profiles that flar2 has already included or try one of the profiles from https://xdaforums.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557

EDIT: Make sure you are using a stock boot image (if you are using the stock ROM) flash your SU solution of choice and then flash the EX kernel
[Nexus 5X Original Android Development] Addicted2Bass:
so if i set speed of the big cores lower it isnt gonna back in loop?
[Nexus 5X Original Android Development] flar2:
Depending on your situation, you may need to use the modified version. Some devices will not boot at all unless the big cores are shut down from the very start.
[Nexus 5X Original Android Development] Addicted2Bass:
ok i thought i needed to install the 4core img for 8.1 and after that 4core ex kernel version 6

---------- Post added at 06:06 PM ---------- Previous post was at 05:22 PM ----------

sorry i thought i had read it here, but im booting in twrp recovery.. that is the bug that needs to be fixed?
[Nexus 5X Original Android Development] SlimSnoopOS:
That's correct, you do need 4 cores to boot. However, Flar2 isn't providing 4 core versions of his kernel. Users have been creating modified versions of Ex kernel that only use 4 cores. Flashing the Ex kernel from this thread is not the same as flashing the 4 core versions of Ex that users have provided.
[Nexus 5X Original Android Development] gorilla p:
If you're in the US, I suggest contacting LG to send it in for repair. They have extended the warranty period to 2yrs and will probably fix it anyways if you push for it.

If not, I suggest you joint he current class action lawsuit.

---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------

Has anyone had any issues with crash/stuck at boot animation screen?

It started happening regularly with phone plugged in at night on multiple custom roms and stock.

I stopped using Greenify, removed magisk and it continued.

I did a clean wipe and started from scratch with stock 8.1 and EX kernel and it continued.

I just did another clean wipe, flashed Magisk and using Greenify (EX kernel was the only remaining factor) and no EX kernel and it appears fine.

I'm going to give it a couple more days before flashing EX again. Maybe it was a fluke/coincidence but I just wanted to check.

I tried grabbing logs but when I tried, nothing before the most recent boot was available.

Will update later.