OnePlus has not release source for Android 12
[KERNEL] [April 4] OnePlus 8 Pro ElementalX 2.06
- Thread starter flar2
- Start date
in my 8t, can't to fully charge the phone, just have 94%,then charge will stop,and charge is too slow
Because it's not for 8t?
Thanks for your work.
Because it's not for 8t?
Thanks for your work.
EX doesn't automatically back up your kernel before flashing a new one. You must back it up manually.
Gentlemen, I'm green. So far I have uploaded a custom rom via twrp. I currently have os 18.1 lineage and uploaded by adb. How do I make copies of the kernel of what I have so that I can come back in case I need to. And how to upload this one? Like rom by adb? Do i need magisk to work this kernel?
I'm afraid I have to abandon this great kernel after using it for more than 10 years (first HDC, later Pixel and now One+8
It doens't look like Oneplus makes it possible anymore to launch it so the kernel manager is unnecessary now.
So I don't receive any notifications if there's un update in the future. Sad!
Thanks flar2 for your good work all those years, your loyalty and all the efforts to keep the Kernel up to date.
It doens't look like Oneplus makes it possible anymore to launch it so the kernel manager is unnecessary now.
So I don't receive any notifications if there's un update in the future. Sad!
Thanks flar2 for your good work all those years, your loyalty and all the efforts to keep the Kernel up to date.
Last edited:
My op8 pro is going in for repair, then I will release the Android 12 kernel, assuming I don't have to pay too much for the RMA service
I would like to report one issue. Namely, the memory write speed is very slow. On stock kernel the write speed reaches over 700MB / s, on elementalx 2.06 it reaches max 250MB / s. I checked it several times. I even monitored the I / O using fkm. Is it possible to fix this? Elementalx is a very good kernel. It has a much smaller active drain and idle drain. It also has a wakelocks blocker. Also write and read speed is lower than stock.
Attachments
Bad news. It will cost $541 for repair, so that's the end of the line for this device.
I will never purchase or recommend a OnePlus device again.
I will never purchase or recommend a OnePlus device again.
Hey Flar2
That's too bad. I hope to "see" you later with another device.
Thanks for all your efforts
That's too bad. I hope to "see" you later with another device.
Thanks for all your efforts
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
41ElementalX Kernel
for OnePlus 8 Pro
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-038I 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.7Some 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.homebutton6
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.
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.
