yep, sometimes twice per day. returned to r1, and lets wait from arter update and fixes in r3

yep, sometimes twice per day. returned to r1, and lets wait from arter update and fixes in r3
It was the camera for me too. Hopefully it gets fixed!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
It won't work. You have to restore backup of partitions altered by this kernel.Just want to double check. If I would like to update to 11.2.10.10, the safest way woud be to do a local upgrade via a full installation file, re-root via magisk and flash back arter via FKM?
It won't work. You have to restore backup of partitions altered by this kernel.
You can also try other methods mentioned in comments above.
Thought so too, but it turned out differentlyAh ok, because if I read from the first post, installing a stock ROM with a full OTA restores the said partition. So that method doesn't work anymore huh.
/* Notice */
Only OxygenOS on Android 11 is supported.
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.
this is for anyone that was asking about the easiest way to do this process:It won't work. You have to restore backup of partitions altered by this kernel.
You can also try other methods mentioned in comments above.
I don't think that's the easiest way since you install twrp anyway.this is for anyone that was asking about the easiest way to do this process:
(if you don't have dtbo/vendor_boot/boot img's backed up): go to the telegram group for this kernel, find the user 'ileux' who posted 11.2.9.9AA img's, download all three (he posted an already magisk patched boot img), reboot to fastboot, run:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
reboot to oos
then local upgrade 11.2.10.10 (don't reboot when done)
flash twrp.zip from nebrassy's thread in magisk (if you use twrp) - don't reboot
flash magisk to inactive slot
- now reboot
profit
yeah I get that, but I don't use twrp to flash oos unless I absolutely have to, but that works too. with this method you take care of everything without having to reboot until it's doneI don't think that's the easiest way since you install twrp anyway.
You can install twrp, install the full OTA via twrp, than reflash Magisk and kernel via twrp. All works fine fore me.
What happened to yours?Reading other peoples experience with updating, now I know its not only me that got screwed.
Usually local update overwrites my kernel and root and i just flash magisk on the other side and reboot.
Ill stick with stock kernel for now
Usually i download the whole update (3gb) from oxygen updater and local update using the system and then flash magisk on the other slot (for ota) and then reboots.
Oh man sorry to hear that, I gotta do a proper backup then before attempting to restore back up and update hmm.Usually i download the whole update (3gb) from oxygen updater and local update using the system and then flash magisk on the other slot (for ota) and then reboots.
But with this kernel, i cant do that. Something prevented me and it keeps failing so i tried to restore my back ups dtbo, vendor, boot and it soft bricked my op9. Black screen at all. Thankfully msm tool saved me and now im just gonna run 10.10 rooted with stock kernel.
This kernel is pretty good but it kinda is a deal breakef for me since im always on the go and i rely on my phone a lot.Oh man sorry to hear that, I gotta do a proper backup then before attempting to restore back up and update hmm.
So I tried local upgrade straight and it failed like how everyone else mentioned.this is for anyone that was asking about the easiest way to do this process:
(if you don't have dtbo/vendor_boot/boot img's backed up): go to the telegram group for this kernel, find the user 'ileux' who posted 11.2.9.9AA img's, download all three (he posted an already magisk patched boot img), reboot to fastboot, run:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
reboot to oos
then local upgrade 11.2.10.10 (don't reboot when done)
flash twrp.zip from nebrassy's thread in magisk (if you use twrp) - don't reboot
flash magisk to inactive slot
- now reboot
profit
for dtbo and vendor_boot, you need to be in fastboot (or you run the risk of an unintended outcome), however, you can flash your boot img and restore that in twrp, simply bc that's technically the kernel.I am wondering if it is possible to restore partitions with twrp?
Well, don't know what did people expect when it was stated by the DEV that OOS12 is not supported and never will be.Does not work. Only fastboot mode after flashing r20b2, tried it myself.
I'm on OnePlus 9 Pro unlocked from OnePlus. I am running latest version of this kernel on top of Derpfest custom ROM. Derp is not being maintained any longer.Sorry but i don't know if i understood. Do you have a OnePlus 9 and are using a custom rom and kernel from XDA?
According to Google’s fleetwide profiling, multi-generational LRU yields an “overall 40% decrease in kswapd [the kernel daemon that manages virtual memory] CPU usage,” an “85% decrease in the number of low-memory kills at the 75th percentile,” and an “18% decrease in app launch times at the 50th percentile.”
/sys/module/lowmemorykiller/parameters/lmk_count
According to Google’s fleetwide profiling, multi-generational LRU yields an “overall 40% decrease in kswapd [the kernel daemon that manages virtual memory] CPU usage,” an “85% decrease in the number of low-memory kills at the 75th percentile,” and an “18% decrease in app launch times at the 50th percentile.”