Development [r12] arter97 kernel for OnePlus 9 series
- Thread starter arter97
- Start date
You will stuck at loading os. Install kernel via twrp. And Magisk.
I think. At least it's what I've done.
That's what I did. I don't think it is recommended way to update, but it worked for me. You can always reflash arter's using FKM - just to be sure it's done correctly 
so has anyone attempted to update to 11.2.10 10 via latest twrp and has success? I'll fastboot reflash the partitions if I have to but if others have success with twrp I'll go that route
I booted into twrp (not flash), then flashed 10.10 in twrp, rebooted into system (choose the correct slot), and my system booted up fine. If it stalls on boot, choose the other slot. Also make sure you remove your screen lock BEFORE using TWRP.
I re-rooted the new firmware using the pre-patched boot method. Then rebooted. Then used FK Kernel to re-install the kernel. No need to wipe data, thankfully.
RheinPirat
Senior Member
Why so complicated? https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-11-2-10-10.4252373/
Check: Keep Root and OTA updates -> Option 1: With full OTA Access (BA/DA) :
Check: Keep Root and OTA updates -> Option 1: With full OTA Access (BA/DA) :
when you fastboot flashed the img's, did you specify a slot or simply flash without specifying a slot? just wondering
I had 2 dtbo and vendor_boot images for each slot, the backup had them named dtbo_a and dtbo_b. So I did fastboot getvar current-slot first to confirm the slot, then just fastboot flash dtbo dtbo_a.img .
thanks for the response. yeah I only have a backup of the images from the telegram group, but I can flash each one to both slot a and b, but I was just wondering if it was necessary to get the update to take, bc the basic command 'fastboot flash boot boot.img' or whatever is being flashed will auto flash to the current active slot
Sorry mate, I don't have a clear answer to that, this whole slots thing is confusing and risky. Hopefully you will get better support on Telegram.
I backed up and restored with dd, and wrote each image to both slots. The update went smoothly.
well I have the images (partitions) ready to flash, is there any difference between using fastboot to flash vs dd?
I don't know. Didn't try fastboot flash. Just used dd from the twrp terminal, and it worked.
yep, although it took a while to get one (others were getting random reboots sooner than I was) -- in short, when I open my camera, I have about a 1 in 4 chance of getting a reboot, don't know why, but that is the only time I get them. went back to stock bc having my phone reboot when trying to take a video on xmas is something I don't feel like dealing with unfortunately. thing is this kernel is awesome in every way and I wish I could continue using, but that's the deal breaker for me
Last edited:
Similar threads
- Locked
Top Liked Posts
-
1
-
18A major new testing release is up.
Changes made in this round is big enough that I've decided to name it r20.
While the build has been stable for me, I'm marking this an alpha as a lot changed.
r20a1 marks the first Linux v5.4 based kernel to have MGLRU backported.
MGLRU is a big deal in everything Linux related, especially for Android.
Esper have a great article on what is MGLRU in a nutshell: https://blog.esper.io/android-dessert-bites-22-linux-memory-management-38419756/
TL;DR:
Personally, I've noticed a sharp decrease in swap usage and improvements in general performance.
Besides MGLRU, there are other numerous patches that are worth noting.
I've brought back updated arm64 routines that were once tried in a beta release but removed later due to random kernel panics (mostly notable from Netflix). The mainline Linux kernel have gotten new updates since then, so r20a1 includes that.
Also, some memory patches made by Sultan are also picked, and I've confirmed that those also help improving responsiveness.
With all these memory stuffs going on, I've also changed swap/zram's parameters. You'll notice a difference in how many apps you can keep open, etc.
The excessive RMNET_DFC wakelock that annoyed some users are now also gone by incorporating a fix from Snapdragon 8 Gen 1.
All in all, this is indeed a pretty big release.
I'm expecting mixed feedback, so please let me know how the new kernel behaves.
/* Full changelog */
Backported MGLRU
Fixed full system crash on some custom ROMs (by LibXZR)
Added a few memory patches to improve responsiveness (by Sultan)
Tuned swap/zram configurations
Backported updated arm64 memory functions for better performance
Fixed excessive RMNET_DFC wakelock
Fixed OnePlus charging code to handle worker failure
Backported more BFQ commits from mainline
Backported mm/mremap fix from mainline
Latest WireGuard merged
LA.UM.9.14.r1-19400-LAHAINA.QSSI13.0 merged
Linux v5.4.190 merged
Wi-Fi drivers updated to 2.0.8.28K
2022-04-05 security patch merged
Latest f2fs from Linux v5.18 merged
Now built with the latest Clang 14.0.5
Device-tree updated to LA.UM.9.14.r1-19300-LAHAINA.QSSI13.07New alpha build r20a2 is up.
Due to some memory issues causing major lags, I've decided to revert MGLRU for now and take r20 alpha rounds to debug more memory-related issues.
Simple LMK by Sultan (kerneltoast) is back to speed up memory debugging.
Please consider joining the Telegram group and sending feedback/logs.
Thanks.2Is it just me, or does anyone get this weird bug when sometimes I turn off Wi-Fi and make use of mobile data, a process/script(?) calledclatd-rmnet_data1 -i rmnet_data1 -m 0xf0075etc. (it's longer but I omitted it) runs in the background at full CPU speed when checkingtop -m 10, making the phone heat up super fast and drain the battery? It happens sometimes when turning off Wi-Fi, but always happens everytime after going to bed and waking up seeing my phone at 1%, or when charging overnight I see it super hot and phone threw the overheating notice at one point. I'm on latest OOS11 if that matters.2So after a few days with the new release I have found another issue. Around once a day I will get System UI stopped responding. The phone becomes very slow during this and also becomes very hot, I'm assuming in an attempt to recover itself. Sadly it never seems to recover and requires a manual restart. -
54
arter97 kernel for OnePlus 9 series running OxygenOS
/* Features */
Supports OnePlus 9 series
Fully rebased kernel without unnecessary OnePlus code
Latest CAF msm-5.4 kernel fully merged
Latest Linux v5.4 subversion merged
Latest Google’s security fix merged
BBR as the default TCP network congestion control
Features the latest WireGuard
Modules support disabled for lighter kernel
Latest Wi-Fi drivers from Qualcomm with customized config
Built with Clang 13 and ThinLTO
Power optimizations
Memory management optimizations
Latest SELinux subsystem backported from mainline
Latest f2fs backported from mainline
Latest BFQ I/O scheduler backported from mainline
mmap/mremap backported from mainline for a major performance boost
Touchscreen optimizations for lower latency
Uses LRNG for better performance
/* Details */
- Fully rebased kernel without unnecessary OnePlus code -
- Power optimizations -
- Memory management optimizations -
- Latest subsystems -
- LRNG -
/* Notice */
OxygenOS 12 is unsupported.
Non-OxygenOS custom ROMs are supported, but your mileage may vary wildly. Most notably, gesture orientations on some ROMs may be inverted.
This kernel touches vendor_boot and dtbo partitions, meaning you'd need to restore said partitions whenever you're switching to another kernel or stock.
Please make a back-up of these partitions. The installer doesn’t do this automatically for you. Installing the stock ROM with a full OTA restores said partitions as well.
/* Disclaimer */
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this kernel
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Thanks to */
Vishalcj17
kristofpetho
kdrag0n
kerneltoast (SultanXDA)
/* Instructions */
1. Read the above. Please.
2. Flash the zip file from FK Kernel Manager. Any other installation methods are untested.
/* Downloads and links */
arter97.com
Kernel source
Telegram chat link18A major new testing release is up.
Changes made in this round is big enough that I've decided to name it r20.
While the build has been stable for me, I'm marking this an alpha as a lot changed.
r20a1 marks the first Linux v5.4 based kernel to have MGLRU backported.
MGLRU is a big deal in everything Linux related, especially for Android.
Esper have a great article on what is MGLRU in a nutshell: https://blog.esper.io/android-dessert-bites-22-linux-memory-management-38419756/
TL;DR:
Personally, I've noticed a sharp decrease in swap usage and improvements in general performance.
Besides MGLRU, there are other numerous patches that are worth noting.
I've brought back updated arm64 routines that were once tried in a beta release but removed later due to random kernel panics (mostly notable from Netflix). The mainline Linux kernel have gotten new updates since then, so r20a1 includes that.
Also, some memory patches made by Sultan are also picked, and I've confirmed that those also help improving responsiveness.
With all these memory stuffs going on, I've also changed swap/zram's parameters. You'll notice a difference in how many apps you can keep open, etc.
The excessive RMNET_DFC wakelock that annoyed some users are now also gone by incorporating a fix from Snapdragon 8 Gen 1.
All in all, this is indeed a pretty big release.
I'm expecting mixed feedback, so please let me know how the new kernel behaves.
/* Full changelog */
Backported MGLRU
Fixed full system crash on some custom ROMs (by LibXZR)
Added a few memory patches to improve responsiveness (by Sultan)
Tuned swap/zram configurations
Backported updated arm64 memory functions for better performance
Fixed excessive RMNET_DFC wakelock
Fixed OnePlus charging code to handle worker failure
Backported more BFQ commits from mainline
Backported mm/mremap fix from mainline
Latest WireGuard merged
LA.UM.9.14.r1-19400-LAHAINA.QSSI13.0 merged
Linux v5.4.190 merged
Wi-Fi drivers updated to 2.0.8.28K
2022-04-05 security patch merged
Latest f2fs from Linux v5.18 merged
Now built with the latest Clang 14.0.5
Device-tree updated to LA.UM.9.14.r1-19300-LAHAINA.QSSI13.018r2 is up, and it's a big release.
Changelog is quite self-explanatory.
r2
Display-related processes are now allowed to use the middle cores as well for better smoothness
Enabled more mremap() performance improvement that was missing from r1
LA.UM.9.14.r1-18400-LAHAINA.0 merged
LA.UM.9.16.r1-08100-MANNAR.0 merged
LA.UM.10.9.1.r1-00300-QCS610.0 merged (contains a lot of new improvements including power optimizations)
Linux v5.4.159 merged
Wi-Fi drivers updated to 2.0.8.25M
2021-11-06 security patch merged
Watermark boosting disabled to fix aggressive app killings (by Sultan)
Workaround added to fix unwanted doubles presses from the power button1515After months of tests, r3 is up and it's a major release that should fixes all major bugs from previous versions and improve performance.
It turned out that using SimpleLMK causes random soft reboots due to page allocation failures.
This kernel reverts back to using the stock lmkd until this issue is sorted out.
You may experience a slight decrease in how many apps you can leave in the background.
Also, random app crashes and freezes are fixed too.
This was specific to OxygenOS, which freezes apps with cgroup and expects the kernel to un-freeze them, but with my kernel lacking that feature from OnePlus, using my kernel led to app crashes and freezes.
This was fixed by forcefully disabling that feature from the kernel.
Some Bluetooth and USB stuffs were also fixed with this release.
Bug fixes alone make this a noteworthy release, but it also comes with nice performance improvements.
With the Qualcomm HDK, I've managed to debug why using Clang 13 leads to boot failures.
r3 has that issue sorted out and now the kernel uses the latest Clang 13.0.2 instead of 12.
Read-write semaphore backported from Linux v5.16 will also give some nice latency improvements under heavy I/O.
These patches are actively being talked in the f2fs mailing list for backporting to older Android devices.
From Sultan (kerneltoast), r3 also has SLUB per-CPU partial caches disabled for better latency.
r3
SimpleLMK disabled for now to fix random soft reboots
Fixed random app crashes and freezes due to op_cgroup
Bluetooth drivers re-worked to fix Bluetooth-related issues
USB malfunctions fixed (dwc3)
LA.UM.9.14.r1-18900-LAHAINA.0 merged
LA.UM.10.9.1.r1-00800-QCS610.0 merged
Linux v5.4.174 merged
Wi-Fi drivers updated to 2.0.8.26T
2022-01-05 security patch merged
Latest WireGuard merged
Latest f2fs from Linux v5.17 merged
Latest LRNG v43 merged
Read-write semaphore backported from Linux v5.16 to improve smoothness under heavy I/O
Now built with the latest Clang 13.0.2
Disabled SLUB per-CPU partial caches for better latency (by Sultan)
