[KERNEL] [April 4] OnePlus 8 Pro ElementalX 2.06

Search This thread

flar2

Recognized Developer
Jun 11, 2012
18,853
87,843
Southwestern Ontario
elementalx.org
Significant update to EX Kernel Manager version 5.70. Now you can choose a directory for kernel downloads and backups. This will make it a lot easier to access your kernel backups and kernel downloads.

This required a lot of refactoring and new code, so let me know if there are problems.

Also, please check out my new app, it's the ultimate apk tool, app manager and backup solution. You can tag and backup your apps, including data. It can install, analyze and extract split APKs, XAPK, APKM, etc. It will show you the most detailed info about any app or apk, including the full manifest.
 

XDAMaxe

Senior Member
Oct 15, 2012
1,179
880
OnePlus 5
OnePlus 8 Pro
I have no idea what ROMs it will or won't work with, there are too many. For many years now, my kernels are made to work with stock ROMs.
true :)
Last Kernel for OP8T (ElementalX-OP8-2.04-express) for Oxygen11 (11.0.8.14.KB05BA) works fine but has a weird behaviour regarding charging with other than the warp charger coming with the device (warp65).
1. Common charger (no warp /dash feature):
In no third party battery monitoring app the charging progress is shown/recognized by the app (i.e. 3c Battery Monitor Widget - https://is.gd/3PzTmvor - or Battery Widget Reborn - https://is.gd/r3RqgZPro).

2. Plugged with the warp charger (65W) coming with the phone:
All works fine and could be monitored via all battery apps.

3. Plugged with other warp/dash charger (i.e. 30w or dash charger for older OP devices):
Same as described for common charger, no monitoring of charging progress possible.

As written charging works but no monitoring except with plugged 65W warp charger.

Checked with stock kernel: Charging progress shown with any charger, dash, warp, common in any monitoring app.
Checked with bluspark kernel: like stock.

So maybe you can have a look or if I can do anything to help let me know because ElementalX is my very really very favorite kernel.
 
Last edited:

dangtoi1993

Senior Member
Feb 26, 2016
181
25
LG V60 ThinQ
OP8 pro Androi 10 10.5.12, i flashed ElementX 1.08, kernel working fine but when watching facebook video the phone getting hot, CPU about 42 cel ( enviroment 20cel), never meet with stock.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 41
    ElementalX Kernel
    for OnePlus 8 Pro
    p3890301369-11.jpg


    ElementalX is designed for maximum stability. It is made for people who depend on their phone every day.


    Features:
    -Optimized for performance and battery life
    -Advanced color control (RGB, hue, saturation, contrast, value, K-Lapse)
    -Adjust vibration
    -Wake gestures (S2W & DT2W)
    -Sweep2sleep
    -Block wakelocks
    -CFQ, noop, BFQ, deadline, FIOPS, SIO, maple and zen i/o schedulers
    -Adrenoboost option
    -Option to disable fsync
    -Option to disable touchboost
    -WireGuard support


    Installation
    1. Flash directly in EX Kernel Manager (root is required to flash in the app)

    Notes

    Stay up to date with EX Kernel Manager. The latest updates are always available through the app. EXKM can be used to configure settings, backup and flash zips and img files, run scripts and install kernel updates quickly and easily. EXKM is compatible with all devices and kernels and is the best supported and most complete kernel manager available.

    Thanks to @tbalden for getting this running on the 8 Pro

    Downloads

    Android 10
    ElementalX-OP8-1.08



    Source code:
    https://github.com/flar2/OnePlus8







    .


    XDA:DevDB Information
    ElementalX OnePlus 8, Kernel for the OnePlus 8 Pro

    Contributors
    flar2
    Source Code: https://github.com/flar2/OnePlus8

    Kernel Special Features:

    Version Information
    Status:
    Beta

    Created 2020-05-11
    Last Updated 2020-08-03
    8
    I might be able to shed a bit of light.

    The QCom CrashDump Mode seems to be due to a kernel or dtbo mismatch, for example @mauronofrio and I noticed it when the kernel was updated between OOS versions but not in TWRP's .img. The solution was to always use the latest prebuilt stock kernel and use the one from India, IIRC.

    So, if I had to guess why restoring a kernel backup might cause this issue, I'd probably think perhaps the user made that backup before getting an OTA or something, so once they went to restore it it wasn't for the correct OOS version anymore.

    So none of that would be flar2 or EXKM's fault, but more on the end user for not understanding how their device behaves or updating their backups.
    7
    Some of you may remember a few years ago I had an app called Wake Gestures. It stopped working and I never got around to fixing it, but I left the wake gestures function in most of my kernels. Good news for those who liked that app, I've added support for Wake Gestures to Button Mapper and it is supported on the OnePlus 8 series as well as almost every other phone with sweep2wake built into the kernel (root is required)

    Wake Gestures allows you to set an action for a swipe in any direction or a double tap, while the screen is off. OnePlus has basically the same feature, but Button Mapper lets you assign basically any action. From basic stuff like toggling the flashlight or wifi, to broadcasting custom intents or executing root commands. Lots of possibilities.

    You need version 1.45 of Button Mapper, which is only on XDA Labs for now:
    https://labs.xda-developers.com/store/app/flar2.homebutton
    6
    I might be able to shed a bit of light.

    The QCom CrashDump Mode seems to be due to a kernel or dtbo mismatch, for example @mauronofrio and I noticed it when the kernel was updated between OOS versions but not in TWRP's .img. The solution was to always use the latest prebuilt stock kernel and use the one from India, IIRC.

    So, if I had to guess why restoring a kernel backup might cause this issue, I'd probably think perhaps the user made that backup before getting an OTA or something, so once they went to restore it it wasn't for the correct OOS version anymore.

    So none of that would be flar2 or EXKM's fault, but more on the end user for not understanding how their device behaves or updating their backups.

    It's either that or also could be the audio modules. I seem to recall ending up in download mode once while fooling around with the audio modules.

    @czerdrill, @old_fart can you please report exactly steps how you backup and restore through the exkm app ( before getting crashdump)
    Are you sure you didn't try to restore a backup from a previous oos ?

    ---------- Post added at 09:14 AM ---------- Previous post was at 08:42 AM ----------



    That's i believe the issue...
    Most custom kernels are using custom dtbo
    So users when they restoring stock kernel through your app the stock dtbo it doesn't be restored...
    It will be very useful to add a dtbo.img backup ..

    No kernel on the OP8 Pro Forums is flashing a custom dtbo.img as far as I can see. Feel free to double check.

    Most kernels include custom dtb in their AK installers. Some kernels might flash them to the wrong place (appended dtb), instead of the new separate dtb section introduced in Android 10.
    Restoring the correct stock boot.img will overwrite these changes however, as the dtb is still part of the boot.img unlike a custom dtbo.img. So I don´t see this problem being caused by restoring a boot.img.

    What can cause problems indeed like @osm0sis mentioned is restoring a boot.img that doesn´t match either the firmware variant (ba, aa, etc) or that is not matching the correct firmware version such as flashing 10.5.6 vs 10.5.9 and having a mismatch there.
    Using the dtb from 10.5.6 on a device running 10.5.9 will result in a crashdump screen as described by users. I tested this myself since it took OnePlus a week to update the source. Once I removed the dtb from my AK3 zip, I was able to boot a 10.5.6 source built kernel Image with 10.5.9 dtb.

    I saw quite a few posts where people uploaded a boot.img for other users without detailing the variant specifically for example.
    I advise everybody to take their own backups of their boot.img´s and not rely on others. It´s good practice and can help you to recover your device.

    Another thing to keep in mind that maybe not everybody is aware of when taking their own backups, which can result in mismatching boot.imgs:
    If you flash an OTA via OnePlus Updater and backup the boot.img without doing a complete reboot after the OTA, you will end up with a boot.img from the OLD firmware not the updated one if I´m not mistaken. @flar2 can gladly correct me here, but I think EXKM always backs up the active slot.
    So if you´re on slot a, flash OTA via OnePlus Updater (this is flashed to slot b), go to EXKM to backup the boot.img you will end up with a backup of the outdated firmware, since slot a is still the active one. The OS switches slots on the reboot following the OTA Update.


    I go to kernel backup, click the saved backup i have and say yes to restore. I want to be clear i don't think it's ekxms fault either, it's something i did I'm sure. It's possible i restored from an earlier version although i make it a habit to backup after each update.

    In another instance i restored the stock kernel and lost wifi and lte. Was only able to get them back after flashing elemental again.

    I don't know what I'm doing wrong but was just sharing my experience.

    Sent from my IN2025 using Tapatalk

    You´re probably restoring a mismatching boot.img. This results in modmagic for kernel modules failing (stock kernels have modmagic enabled) and the WLAN driver cannot be loaded.
    EX-Kernel disables this modmagic check for kernel modules, hence WiFi works fine for you again.
    You need to flash exactly the same boot.img from the firmware you´re running to get back to stock.
    6
    If the problem is flashing alternate dtbo.img from other kernels, perhaps I will add a dtbo partition backup to EXKM as well, that way you can save the stock dtbo.img before flashing other kernels. You would need that for compatibility with ElementalX as well.