[KERNEL] [February 5] ElementalX-OP6 4.00 (Android 10)

[carlos67]

@flar2

Check this out. It seems that we can finally kiss goodbye to the internal error message appearing on lockscreen pin screen on custom kernels.

Credits to @Sultanxda

https://github.com/sultanxda/androi...mmit/0a737ab6ec5267e8e4414cb7c58cb17e7b9ecebc

Can you implement this on next update?

 

[magnamentis]

Wel, i think so but where can i check this ? For info, i'm rooted and do have Twrp (official version), Magisk 16 and SuperSU. Thanks for your help !

Magisk AND SuperSU

either language problem or not possible, you cannot have both at the same time and if you really attempted that it might be the reason that you don't have root at all.

don't forget to report back once you solved that, this should be two way, not only ask and consume but provide feedback for others as well.

---------- Post added at 12:58 PM ---------- Previous post was at 12:52 PM ----------

@flar2 Can you add underclock and overclock please?

two things:

flasr2 already posted his take on the matter. this question shows that you don't search/read the thread before asking questions

further if this device would be 10 times faster than it already is, some guys would still ask for more, just for the sake of it and because they
understand the main purpose of having a custom kernel wrong.

once you'd be able to overclock a device with last generation CPUs you wouldn't recognize much or any difference because a split second will remain a split second and you won't be able to see or feel the difference between 0.001 and 0.002 seconds in execution.

but what you will recognize is excessive battery consumption, hence you'd trade in nothing for a lot

that said, should OC ever be available it will of course be personal choice but i'd not be surprised if the dev wouldn't go very far to
find a way to overclock. all this is an opinion to consider, ultimately personal preference as already mentioned.

---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------

I have a question about kernel flashing (Ex kernel exactly) using the app. So far, I've made every update for 1 + 3 using the app which threw the kernel through my twrp. Now I've learned that every update deletes the root. So I understand that after each update of the kernel you will have to throw magisk through twrp anyway?

Regards

Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka

the answer is yes, always flash root method last thing after rom and kernel updates.

the term BTW is flash not throw. while it's not an issue there could result misunderstandings due to using un-common terminology.

 

[Arly77]

Thanks for the answer

 

[novo123]

You can go to Magisk Manager -> Tap 3 bar on the top left corner -> #Superuser, and you will see apps with root permission granted. :good:

Thanks ! I've checked out and i confirm that i do have the permission for Ex Kernel. Any other idea ? It's very strange, it seem that i'm the only guy with this issue.

---------- Post added at 01:30 PM ---------- Previous post was at 01:25 PM ----------

Magisk AND SuperSU

either language problem or not possible, you cannot have both at the same time and if you really attempted that it might be the reason that you don't have root at all.

don't forget to report back once you solved that, this should be two way, not only ask and consume but provide feedback for others as well.

---------- Post added at 12:58 PM ---------- Previous post was at 12:52 PM ----------

Al right i will unsinstall SuperSU and let you know if it works. Thanks u !

---------- Post added at 01:42 PM ---------- Previous post was at 01:30 PM ----------

@ magnamentis : Regarding my issue (sound tab is missing on the dashboard of Ex kernel manager), i uninstalled SuperSU & Ex Kernel, rebooted my OP6, checked if still do have the root with root checker (it's OK), installed once again Ex Kernel but the sound tab is still missing. Any other idea ? Thanks.

 

[Flying Fox]

Anybody knows why i don't have the sound tab on the Dashboard of Ex Kernel ? Tried several time to reinstall but no changes. Thanks.

This normally happens when the kernel doesn´t support this feature. So maybe your issue is not app- but kernel related. The kernel itself works well. So my question: did you change the kernel sometime? If yes, without flashing original boot.img between? If so, you could try following steps for a "clean kernel flash":
flash boot.img via twrp (the original boot.img, which belongs to your rom)
then flash twrp-installer again, magisk and reboot. Then back to recovery and flash ElementalX and magisk once more. The kernel should be installed "clean" now.
Always backup first.

 

[novo123]

This normally happens when the kernel doesn´t support this feature. So maybe your issue is not app- but kernel related. The kernel itself works well. So my question: did you change the kernel sometime? If yes, without flashing original boot.img between? If so, you could try following steps for a "clean kernel flash":
flash boot.img via twrp (the original boot.img, which belongs to your rom)
then flash twrp-installer again, magisk and reboot. Then back to recovery and flash ElementalX and magisk once more. The kernel should be installed "clean" now.
Always backup first.

As far as i know (but i'm a noob), I did not change the Kernel on my Op6 so do you really thnk i must try the steps you've mentionned ? It's a hard work :crying: Thanks.

 

[Flying Fox]

As far as i know (but i'm a noob), I did not change the Kernel on my Op6 so do you really thnk i must try the steps you've mentionned ? It's a hard work :crying: Thanks.

If you didn´t change the kernel then I don´t know. You could try anyway, it´s not hard work.. not more than 5 minutes unless the data is deleted for some unknown reason. So always backup first!! (nandroid and copy to pc). But this is recommended either way.
You can also PM me. I´m sitting in the sun, watching the nature and have time now.

 

[novo123]

If you didn´t change the kernel then I don´t know. You could try anyway, it´s not hard work.. not more than 5 minutes unless the data is deleted for some unknown reason. So always backup first!! (nandroid and copy to pc). But this is recommended either way.
You can also PM me. I´m sitting in the sun, watching the nature and have time now.

Again thanks for your help and time. I'll probably try this later, when i'm back to home. Sure, i'll PM you if any problem, thanks for this Enjoy the sun ! :good:

 

[MBurns2]

Guys if i nandroid restore stock boot.img will i return to stock kernel? Ty

 

[magnamentis]

Guys if i nandroid restore stock boot.img will i return to stock kernel? Ty

boot image is the kernel, even though it now contains the recovery as well but yes, of course, what else, if you flash stock kernel you're on stock kernel.

 

[MBurns2]

boot image is the kernel, even though it now contains the recovery as well but yes, of course, what else, if you flash stock kernel you're on stock kernel.

Beacuse i'm on stock rom..can i only extract the kernel or i have ti reflash the whole rom?
Otherwise the solutions is to restore stock boot.img from twrp

 

[Astrubale]

Your seriously needing to overclock this device?

Why not? You can get extrapower

 

[magnamentis]

Beacuse i'm on stock rom..can i only extract the kernel or i have ti reflash the whole rom?
Otherwise the solutions is to restore stock boot.img from twrp

dirty flash the rom or extract boot.img from stock rom BUT:

due the A/B thingy I recommend to only flash the boot.img, why?

because if you flash the boot.img alone everything will remain on current slot, you flash to current and boot from current slot.

oposed to that, if you flash the entire stock rom, it will switch slots after flashing the stock rom which means you will have to deal with
extra steps to make it boot from newly installed rom and at the same time keep root and kernel should you have that custom.

either way it's no bit deal but still, if you want to make things easy, risk and hassle free, just boot the stock kernel (boot.img) and don't forget
to reflash twrp if you flash the kernel via fastboot, i recommend to flash boot.img from within TWRP.

so, as you can see depending on the method you have to keep a few things in mind. advantage to avoid the easiest way would be to get a feel for how this works and how to get back on track once having forgotten to execute one of the extras

 

[flar2]

@flar2

Check this out. It seems that we can finally kiss goodbye to the internal error message appearing on lockscreen pin screen on custom kernels.

Credits to @Sultanxda

https://github.com/sultanxda/androi...mmit/0a737ab6ec5267e8e4414cb7c58cb17e7b9ecebc

Can you implement this on next update?

Thanks, it works.

 

[flar2]

Update!!!


I've been experimenting with dynamic stune boost from @joshuous with good results. Seems to be some improvement in battery. If you want to try it, I've put all the necessary settings into one place in the latest version of EX Kernel Manager (3.56).

Go to the CPU screen and select "Boost Settings" to open the Boost Settings screen
-Disable MSM Touchboost
-Change Dynamic stune boost to 15 (or somewhere between 10 and 20)
-Set all Input boost frequencies to 0 MHz (i.e. disabled)
-Change Input boost milliseconds to 1500 (might be unecessary, feel free to experiment)



This version also allows separate settings for vibration for notifications and taps. I prefer the tap vibration to be very low so it's not so noisy when typing, but I still want notifications to vibrate strongly. Also requires latest EXKM



Latest EX Kernel Manager: https://play.google.com/store/apps/details?id=flar2.exkernelmanager




Download (OxygenOS Android 8.1.0):
ElementalX-1.04.zip


Changes:
-remove annoying warning on device start
-add separate tunables for tap and notification vibration
-add Dynamic Stune Boost

 

[MBurns2]

dirty flash the rom or extract boot.img from stock rom BUT:

due the A/B thingy I recommend to only flash the boot.img, why?

because if you flash the boot.img alone everything will remain on current slot, you flash to current and boot from current slot.

oposed to that, if you flash the entire stock rom, it will switch slots after flashing the stock rom which means you will have to deal with
extra steps to make it boot from newly installed rom and at the same time keep root and kernel should you have that custom.

either way it's no bit deal but still, if you want to make things easy, risk and hassle free, just boot the stock kernel (boot.img) and don't forget
to reflash twrp if you flash the kernel via fastboot, i recommend to flash boot.img from within TWRP.

so, as you can see depending on the method you have to keep a few things in mind. advantage to avoid the easiest way would be to get a feel for how this works and how to get back on track once having forgotten to execute one of the extras

Mate can i simply restore nandroid boot.img?

 

[tbalden]

Nice update. You're fast now I can cherry pick the alert annoying fix. Thanks
So is the eas vs hmp bag of mixture being exorcised here?
I'll look out for results.

 

[flar2]

Nice update. You're fast now I can cherry pick the alert annoying fix. Thanks
So is the eas vs hmp bag of mixture being exorcised here?
I'll look out for results.

I barely have any time to work on this right now, I'm just picking away at the little stuff.

The stune boost is all eas, it increases utilisation in the scheduler by x% for the top app whenever the user touches the screen, this makes the governor choose a higher frequency.

 

[detritu5]

I barely have any time to work on this right now, I'm just picking away at the little stuff.

The stune boost is all eas, it increases utilisation in the scheduler by x% for the top app whenever the user touches the screen, this makes the governor choose a higher frequency.

The button mapper app is not compatible with alert slider right?

 

[flar2]

The button mapper app is not compatible with alert slider right?

Nope