You will stuck at loading os. Install kernel via twrp. And Magisk.So, if I haven't backed up my partitions, can I just boot into twrp, flash 10.10 and boot into system without any issues? Someone tested?
Backing up and restoring is such pain in ...
Thnx in advance
So, I should flash arter kernel after flashing 10.10?You will stuck at loading os. Install kernel via twrp. And Magisk.
I think. At least it's what I've done.
So, if I haven't backed up my partitions, can I just boot into twrp, flash 10.10 and boot into system without any issues? Someone tested?
Backing up and restoring is such pain in ...
Thnx in advance
when you fastboot flashed the img's, did you specify a slot or simply flash without specifying a slot? just wonderingYeah, restoring via fastboot is reliable. And it's basically the same steps: Restore, then upgrade locally, then for root you can either patch the kernel or flash Magisk via TWRP.
I only went for the kernel patch option because I was too paranoid to flash TWRP and risk losing my data. Is it safe to flash it without wiping anything?
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 .when you fastboot flashed the img's, did you specify a slot or simply flash without specifying a slot? just wondering
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 slotI 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 .
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.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
I backed up and restored with dd, and wrote each image to both slots. The update went smoothly.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
well I have the images (partitions) ready to flash, is there any difference between using fastboot to flash vs dd?I backed up and restored with dd, and wrote each image to both slots. The update went smoothly.
I don't know what dd is, just used fastboot.well I have the images (partitions) ready to flash, is there any difference between using fastboot to flash vs dd?
yeah my bad was asking @tathagatab
I don't know. Didn't try fastboot flash. Just used dd from the twrp terminal, and it worked.well I have the images (partitions) ready to flash, is there any difference between using fastboot to flash vs dd?
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
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.”
It's unfortunate but I already switched over to DerpFest. They are both very fast ROMs and benchmark the exact same, but DerpFest I haven't had any issues and it just has more features.I had this Problem too. In my case the solution was to reset the CR-Droid Settings to default. The icon at the top right (see screenshot). After the reset i've never seen this bug again.
/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.”