Development [KERNEL]Despair Kernel
- Thread starter DespairFactor
- Start date
The current December builds will work on the January update. I will update as soon as sources are released.
January build up now, I have removed December and November builds! Build is Despair-V1.15
Yayah let's get it. I've been rocking every Despair kernel so far and haven't had any problems. I'm about to rock that Jan unit
Yeah, 1.14 and 1.15 are updated for January. I am also working on 1.16
Awesome! I appreciate any feedback
I've decided to hold off on 1.16, so far 1.14 is the best in my opinion. I am currently testing powerhint module from freak07 with my kernel to see how it performs compared to my kernel without it.
Also, appreciate the compliment.
It looks like the group disappeared recently. I was reading posts earlier this morning, and now it is gone
Okay, thanks for all your work. The kernel is awesome!
Thank you, I appreciate it! I will try to be more active on here
Smh why do people gotta be kooks. Causing drama and your giving us free development stupid. Sorry @DespairFactor and thank you for your great work
Will stay on here for this good work of yours, been following the group since the p6/pro release. Thanks again for the hard work matt.
Upon a bit of testing, I have decided to re-release 1.12 but based on January source. I am seeing a lot smoother/faster UX/UI on this build than 1.14 and 1.15
Top Liked Posts
-
There are no posts matching your filters.
-
45Mission:
The purpose of this project is to increase efficiency of the Pixel 6 series devices by merging functional patches with minimal bloat.
If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Installation:
To install kernel on a rooted device with EXKM/FKM
- Download ZIP and flash using the manual flasher in the app
To manually flash kernel updates
-Download ZIP for kernel and the current boot.img
-Use the below commands to flash from bootloader/fastboot
-fastboot reboot fastboot
-fastboot flash vendor_dlkm vendor_dlkm.img
-fastboot reboot bootloader
-fastboot flash dtbo dtbo.img
-fastboot flash boot boot.img
-fastboot flash vendor_boot vendor_boot.img
Links:
Telegram:
Downloads:
raviole - Google Drive
drive.google.com
Source:
https://github.com/DespairFactor/raviole
Credits:
Google191716
actually @RetroTech07 is right here. You should restore stock images via fastboot/fastbootd to avoid issues.
In the case of boot.img, dtbo.img and vendor_boot.img you probably can flash the kernel.zips over the other without running into any issue.
But since vendor_dlkm.img gets flashed on this device as well and sits on the super partition, you want to flash back the stock vendor_dlkm.img via fastbootd (not via any kernel manager while the phone is running!). The reason for that: While flashing vendor_dlkm in fastbootd, the vendor_dlkm partition actually gets resized to their original size inside the super partition.
While the device is running and either a kernel.zip containing a vendor_dlkm.img is flashed or a vendor_dlkm.img is restored via the option in EXKM/FKM app, vendor_dlkm.img is only dd´ed to the partition, essentially cutting a bit of the original size off, as the resizing part that´s happening when flashing via fastbootd is not happening there.
It´s not a problem in itself, as all vendor_dlkm.img´s shipped by the custom kernels available are smaller than the vendor_dlkm from stock firmware is.
However when hopping between kernels, I´d always restore the stock images via fastboot/fastbootd.15
