[KERNEL] [January 29] ElementalX-N9 5.17 (Nougat) 7.03 (Oreo)

[Kubens1pl]

Hi, that's great kernel. Thanks for that.
I have got one question. How can I disable fast charging? I have enabled it during installation process. I tried to disable that feature via ElementalX app from play store, but i don't know how i can check that fast charging is actually disabled.
I used Ampere app, but it still indicates charging current above 1100mA :/
I have also tried type in terminal: su echo 0 > /sys/kernel/fast_charge/force_fast_charge, but it also didn't changed anything in Ampere measurements.
Thanks in advance for your help

 

[flar2]

Hi, that's great kernel. Thanks for that.
I have got one question. How can I disable fast charging? I have enabled it during installation process. I tried to disable that feature via ElementalX app from play store, but i don't know how i can check that fast charging is actually disabled.
I used Ampere app, but it still indicates charging current above 1100mA :/
I have also tried type in terminal: su echo 0 > /sys/kernel/fast_charge/force_fast_charge, but it also didn't changed anything in Ampere measurements.
Thanks in advance for your help

Fastcharge is only while charging from a usb port, it doesn't affect charging from an ac adapter.

If you change fastcharge setting while it's plugged in, you have to unplug and replug for it to take effect.

 

[Kubens1pl]

@flar2 thanks for answer. I have got one more question. What does actually do 'Apply on boot' option in ElementalX app?
When i should use it?
Can i enable/disable features on the fly, or should i reboot device every time?

 

[flar2]

@flar2 thanks for answer. I have got one more question. What does actually do 'Apply on boot' option in ElementalX app?
When i should use it?
Can i enable/disable features on the fly, or should i reboot device every time?

Settings are changed on the fly, click the apply on boot button to apply them every time the device boots.

 

[Holer Togni]

My N9 won't accept the PIN to unlock the screen with 4.01 Beta and SELinux set to enforcing. However if I set SELinux to permissive (via adb while the screen is locked), the PIN is accepted.

I'm on the factory image (clean install) with SuperSU 2.50. Also flashed Chainfire's most recent boot image before ElX in order to remove the triangle warning message.

Obviously, if I flash back 4.00-sysrw the PIN is accepted and vice versa.

For what it's worth, after upgrading SuperSU to 2.52, I still couldn't pin-unlock the screen after the first boot up with ElX 4.01 and selinux enforcing. So I switched to permissive, disabled the lock screen, went back to enforcing and enabled lock screen again. Now it works.

 

[corkiejp]

New to using a Custom Kernel!!

New to using a Custom Kernel!!

Got introduced to this kernel when I was rooting my Nexus 9 on Marshmallow.

So I thought I would try it out!

Can anyone link me to guides for using it?

Or recommend some settings I should be using, pretty much went with the default settings when installing it! What settings are others finding useful etc?

I got the "EX Kernel Manager" : - https://play.google.com/store/apps/details?id=flar2.exkernelmanager

Thanks in advance for assistance.

Regards
John

 

[capt730]

The combo of marshmallow and this kernel is very nice. I bought the ex kernel mgr a while back and glad I did. Very nice work.

 

[flar2]

Update

For Android 6.0 Marshmallow

-no changes to the actual kernel
-if you are stock and not rooted, you must flash Chainfire's boot.img and use SuperSU 2.52 or later
-if you are stock rooted or on a custom ROM, just flash
-recommended to reflash your ROM before flashing this




Download:
ElementalX-N9-4.02


Changes:
-better compatibility for custom ROMs

 

[corkiejp]

Download:
ElementalX-N9-4.02

Changes:
-better compatibility for custom ROMs

Is this just for custom ROMs?

If I'm on stock ElementalX 4.01, is there any need to flash this version?

 

[flar2]

Is this just for custom ROMs?

If I'm on stock ElementalX 4.01, is there any need to flash this version?

No need to update if you're on stock

And users of custom ROMs should reflash the ROM and then flash the update

 

[chrmica]

Hi are there any sixaxis issues with this kernel trying to use ps4 controller with it and its not detected with 5.1.1 on nexus 9 had no issues

Sent from my Nexus 9 using XDA Free mobile app

 

[jolinnard]

No need to update if you're on stock

And users of custom ROMs should reflash the ROM and then flash the update

Hi flar2,

I flashed 4.02 over 4.01, I'm running MelloShmallow by @bshiznit but new kernel cause some weird issue applying iptables (it says that some rule already exist), and it doesn't finish boot (these iptables messages appears in logcat over and over again):

10-17 15:44:07.270  5912  5912 I Netd    : Netd 1.0 starting
10-17 15:44:07.270  5912  5912 D TetherController: Setting IP forward enable = 0
10-17 15:44:09.137  5912  5912 V NatController: runCmd(/system/bin/iptables -w -F natctrl_FORWARD) res=0
10-17 15:44:09.147  5912  5912 V NatController: runCmd(/system/bin/iptables -w -A natctrl_FORWARD -j DROP) res=0
10-17 15:44:09.158  5912  5912 V NatController: runCmd(/system/bin/iptables -w -t nat -F natctrl_nat_POSTROUTING) res=0
10-17 15:44:09.167  5912  5912 V NatController: runCmd(/system/bin/iptables -w -F natctrl_tether_counters) res=0
10-17 15:44:09.177  5912  5912 V NatController: runCmd(/system/bin/iptables -w -X natctrl_tether_counters) res=0
10-17 15:44:09.186  5912  5912 V NatController: runCmd(/system/bin/iptables -w -N natctrl_tether_counters) res=0
10-17 15:44:09.196  5912  5912 V NatController: runCmd(/system/bin/iptables -w -t mangle -A natctrl_mangle_FORWARD -p tcp --tcp-flags SYN SYN -j TCPMSS --clamp-mss-to-pmtu) res=0
10-17 15:44:09.826  5912  5912 E Netd    : netlink response contains error (File exists)
10-17 15:44:09.827  5912  5912 E Netd    : Can't add IPv4 default route to dummy0: File exists
10-17 15:44:09.828  5912  5912 D MDnsDS  : MDnsSdListener::Hander starting up
10-17 15:44:09.828  5912  6164 D MDnsDS  : MDnsSdListener starting to monitor
10-17 15:44:09.828  5912  6164 D MDnsDS  : Going to poll with pollCount 1
10-17 15:44:12.239  6169  6169 W init    : type=1400 audit(0.0:31): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p29" ino=1573 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0

Back to 4.01 and all is working. Flashed ROM+Gapps, also I tried to wipe system... Still it doesn't boot.

 

[flar2]

Hi flar2,

I flashed 4.02 over 4.01, I'm running MelloShmallow by @bshiznit but new kernel cause some weird issue applying iptables (it says that some rule already exist), and it doesn't finish boot (these iptables messages appears in logcat over and over again):

10-17 15:44:07.270  5912  5912 I Netd    : Netd 1.0 starting
10-17 15:44:07.270  5912  5912 D TetherController: Setting IP forward enable = 0
10-17 15:44:09.137  5912  5912 V NatController: runCmd(/system/bin/iptables -w -F natctrl_FORWARD) res=0
10-17 15:44:09.147  5912  5912 V NatController: runCmd(/system/bin/iptables -w -A natctrl_FORWARD -j DROP) res=0
10-17 15:44:09.158  5912  5912 V NatController: runCmd(/system/bin/iptables -w -t nat -F natctrl_nat_POSTROUTING) res=0
10-17 15:44:09.167  5912  5912 V NatController: runCmd(/system/bin/iptables -w -F natctrl_tether_counters) res=0
10-17 15:44:09.177  5912  5912 V NatController: runCmd(/system/bin/iptables -w -X natctrl_tether_counters) res=0
10-17 15:44:09.186  5912  5912 V NatController: runCmd(/system/bin/iptables -w -N natctrl_tether_counters) res=0
10-17 15:44:09.196  5912  5912 V NatController: runCmd(/system/bin/iptables -w -t mangle -A natctrl_mangle_FORWARD -p tcp --tcp-flags SYN SYN -j TCPMSS --clamp-mss-to-pmtu) res=0
10-17 15:44:09.826  5912  5912 E Netd    : netlink response contains error (File exists)
10-17 15:44:09.827  5912  5912 E Netd    : Can't add IPv4 default route to dummy0: File exists
10-17 15:44:09.828  5912  5912 D MDnsDS  : MDnsSdListener::Hander starting up
10-17 15:44:09.828  5912  6164 D MDnsDS  : MDnsSdListener starting to monitor
10-17 15:44:09.828  5912  6164 D MDnsDS  : Going to poll with pollCount 1
10-17 15:44:12.239  6169  6169 W init    : type=1400 audit(0.0:31): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p29" ino=1573 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0

Back to 4.01 and all is working. Flashed ROM+Gapps, also I tried to wipe system... Still it doesn't boot.

There is absolutely no difference between 4.01 and 4.02 on the kernel side

On the ramdisk side, there is also no difference installing 4.02 over 4.01. Each and every file will be identical.

Did you try wiping caches?

 

[jolinnard]

There is absolutely no difference between 4.01 and 4.02 on the kernel side

On the ramdisk side, there is also no difference installing 4.02 over 4.01. Each and every file will be identical.

Did you try wiping caches?

Just forget my words... I'm feel like a noob

 

[BigJPNut]

Do we stick to su 2.50?

Sent from my Nexus 9 using Tapatalk

 

[flar2]

Do we stick to su 2.50?

Sent from my Nexus 9 using Tapatalk

Use the latest, which is 2.52

 

[flar2]

Hi are there any sixaxis issues with this kernel trying to use ps4 controller with it and its not detected with 5.1.1 on nexus 9 had no issues

Sent from my Nexus 9 using XDA Free mobile app

I'll look in the config and see if I enabled it.

Edit: looks like it's enabled, it should work. Anyone else try it?

 

[dan04103]

I'll look in the config and see if I enabled it.

Edit: looks like it's enabled, it should work. Anyone else try it?

Ps4 controller works fine out of the box here.

 

[chrmica]

With sixaxis ? because I have been trying for a few days now and on another rooted phone it works perfectly with 5.1.1, if so is there anything I need to check on Nexus 9 Marshmallow\elementalx to get sixaxis working. Thanks

Sent from my Nexus 5 using XDA Free mobile app

 

[flar2]

Update

For Android 6.0 Marshmallow

No changes to the actual kernel, therefore no need to update. This will make clean installs easier


Stock ROM, already rooted:
-just flash EX


Stock ROM, not rooted:
-just flash EX, but make sure you install SuperSU 2.52 if you want root. Chainfire's boot.img is not necessary


Custom ROM:
-just flash EX
-if it bootloops or you want selinux permissive, flash this permissive zip

Sorry, I am not adding a permissive option to the installer due to the problems I had with Google a few months ago






Download:
ElementalX-N9-4.03


Changes:
-autodetect proper sepolicy for stock