[KERNEL] [April 4] OnePlus 8 Pro ElementalX 2.06
- Thread starter flar2
- Start date
I don't see any source code from OnePlus and the latest update for my device is Android 11
I just tried it with three different chargers (samsung, google and unknown) and they all worked fine. Try a different usb cable, some of them are wired incorrectly.
Thanks for the Kernel, its the best i tried on my op8 so far.
Is there a way to activate battery saver mode in your kernel manager if we lock the device?
Edit: Do you suggest turning zram on or off? I cant turn it off in FKM and EXKM anyway...
Is there a way to activate battery saver mode in your kernel manager if we lock the device?
Edit: Do you suggest turning zram on or off? I cant turn it off in FKM and EXKM anyway...
well anyway, even if they released the source i guess it would be janky due to cos base, even now playing with boot on oos causes crashdump and boot destroyed warning on cos.
Anothey thing is when i was using cos, something tripped. Got boot destroyed. flashed stock boot didnt fix. I tried to go edl with adb, sent me to fastboot and it was constantly cycling the menu by itself then it sent me on a bootloop. Managed to boot into cos, tried button combinations, didnt do. I had to switch to other slot (it had h2os) and used EDL in there. Switching to h2os slot caused corrupt data/partitions but at least i could msm.
Worst experience i ever had after redmi note 8 pro hardbricking case. OOS12/COS12 is dangerous :C
if it was working before, it should now though, i had my 5t 18w brick and it's cable. it was charging fine with dash(when i was on oos11 with previous kernel versions.). I could say maybe cable got damaged somehow? but i really dont know. if you are using oos, maybe try stock oos kernel or try an older elemental kernel version which was working for you?
Even so, dash-warp or not charging should work just fine, maybe port got dust or gunk, port board maybe got damaged(would check usb pc connection), try different cables or even try charging with same bricks/cables in a different place? maybe your place got electricity issues who knows?
Last edited:
imo i would keep it off if my ram was 12gb, dunno about 8 ones. one thing i could do is give 1-2 days for both on and off. compare it and see which suits best.
also try to use a single kernel manager, if you use more than 1, they could both have inflict over eachother. (also someone once told me that fkm locks userspace. dont know what it means but i like elemental manager more.) I use my own custom made gpu table and voltages, fkm doesnt work well with custom gpu freqs but elemental does.
if i was him, I would try my luck with a cable which supports power delivery like PD100. I know people with 8t using other branded PD100 cables and get 60W charging normally.
Even now i use a 2meters magnetic PD100 cable but im limited to 10W max cause my 30W brick got Type A as you now, my cable got type c on both ends. have to use an adapter and it drops the support of PD100...
Commits · flar2/OnePlus8
ElementalX for the OnePlus 8 series. Contribute to flar2/OnePlus8 development by creating an account on GitHub.
github.com
Are you willing to share your gpu table? Is it meant for gaming or battery?
@flar2 Have you updated gpu drivers to v530 in the kernel? Would you be able to upgrade to v614 or v615?
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.
