yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] DespairFactor:
Mission:

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:

Despair Chat

Temp holder

t.me

Downloads:

raviole - Google Drive

drive.google.com

Source:

https://github.com/DespairFactor/raviole

Credits:

Google
[Google Pixel 6 Pro] DespairFactor:
I will update OP when I am back at a PC on the weekend
[Google Pixel 6 Pro] ne0ns4l4m4nder:
Kir is working on pixel 6, is this also working on pixel 6?
[Google Pixel 6 Pro] DespairFactor:
Should be
[Google Pixel 6 Pro] freddienuxx:
yeah know i have to go back to p6pro
[Google Pixel 6 Pro] DespairFactor:
What do you mean?

Also, I have updated the top post with a telegram link for chat
[Google Pixel 6 Pro] AlkaliV2:
Flashed this last night because DespairFactor's work is awesome and I had some suspicion about the stock kernel. Stock kernel loss the previous night was 1.4%/hr and last night's result with Despair was 0.8%/hr. Doing a screen on test comparison through my workday today so I'll have more to share later but this paired with EXKM is excellent so far!
[Google Pixel 6 Pro] Nekromantik:
do you need to flash anything else apart from the kernel img?
[Google Pixel 6 Pro] DespairFactor:
For now it is just the boot.img
[Google Pixel 6 Pro] AlkaliV2:
Also, don't make the mistake I did and forget to root the image via the app first. Flashing the boot by itself will unroot you so just use magisk to root the image before flashing. If you're already rooted this can be flashed via EXKM without issue.
[Google Pixel 6 Pro] reaper000:
Damn, it's been a while. I think I flashed Despair's ROM on the Nexus 5..?

Anyways, running rooted (Magisk 23013) Despair kernel now atop the 036 update.

Smooth and hopefully less power hungry.
[Google Pixel 6 Pro] DespairFactor:
Build V1.01 is out now and source has been pushed
[Google Pixel 6 Pro] DespairFactor:
Just pushed build V1.02 this morning with some changes from Google's Android 13 branch
[Google Pixel 6 Pro] Nekromantik:
working great so far
[Google Pixel 6 Pro] foobar66:
Testing this kernel as well (rooted) ... will post findings ...
[Google Pixel 6 Pro] DespairFactor:
1.03 and 1.04 are released, source on github
[Google Pixel 6 Pro] AlkaliV2:
There's a lot of activity in the telegram channel for those interested including tips for Wakelock blocking and other tips for battery life improvement. Feel free to join in and report your results using the kernel!

We find that we can only do Wakelock blocking on Franco Kernel Manager. EXKM doesn't work for Wakelock blocking so just wanted to mention that as well even though it is included in the kernel.
[Google Pixel 6 Pro] flar2:
The latest version of EXKM has the updated paths for wakelock blocking
[Google Pixel 6 Pro] DespairFactor:
Tested it already, working great. Thank you for updating it
[Google Pixel 6 Pro] reaper000:
Note that 037 OTA just dropped. Don't know if there's kernel changes.

BTW, can Despair be flashed over the Verizon versions of the OTAs..?
[Google Pixel 6 Pro] bigdog1459:
I have a 1.14 build from Jan 28th still on my phone but don't want to step on any toes. @DespairFactor is it ok to share it?
[Google Pixel 6 Pro] kheltek:
I appreciate you both. That build was the best for me by far, no heat, idle and active drain was amazing and phone felt real smooth.
[Google Pixel 6 Pro] DespairFactor:
I am making a new build with the changes added.
[Google Pixel 6 Pro] bigdog1459:
Amazing! The kernels have been great. Thanks for all the hard work.
[Google Pixel 6 Pro] DespairFactor:
new build is up as V1.15
[Google Pixel 6 Pro] Texan1:
Seems to be working well, thanks 👍
[Google Pixel 6 Pro] kheltek:
Thanks again for everything @DespairFactor 1.15 is holding up much better.
[Google Pixel 6 Pro] RetroTech07:
Does anyone apply any special parameters in either FKM or EXKM to improve battery performance?

Before installing a custom kernel I somehow managed over 48hrs of standby on a mobile network and I'm trying to find ways to replicate that as much as possible.
[Google Pixel 6 Pro] Gordietm:
Just flashed v1.16. Running well so far, thanks.
[Google Pixel 6 Pro] DespairFactor:
I didn't even tell anyone this was released yet haha, you must have hax
[Google Pixel 6 Pro] Gordietm:
I saw it in the file directory.🙂
[Google Pixel 6 Pro] Gytole:
Gordietm's of the mostedst feared and well nowen Ultmit Hax an root cracks guy in alf time. Your serves are NOW his. THast how.

Yes, I wrecked it on purpose. 🥸
[Google Pixel 6 Pro] DespairFactor:
V1.17 is being built and uploaded to support February patch
[Google Pixel 6 Pro] avid_droid:
Where's the Telegram link?
[Google Pixel 6 Pro] Lughnasadh:
https://xdaforums.com/t/kernel-feb-despair-kernel-v1-17.4359945/page-6#post-86273939
[Google Pixel 6 Pro] avid_droid:
Thank you. I'll be rooting and flashing this kernel tonight
[Google Pixel 6 Pro] crixxuscenturion:
Thank you! Just flashed the Kernel :cool:
[Google Pixel 6 Pro] avid_droid:
Does this kernel support double tap to wake? I need to go back and read
[Google Pixel 6 Pro] ram4ufriends:
No kernel supports double to wake at the moment.
[Google Pixel 6 Pro] DespairFactor:
New update coming, I have removed older builds
[Google Pixel 6 Pro] Nekromantik:
does the kernel include the fix to not needing to disable verity?
[Google Pixel 6 Pro] DespairFactor:
yes, in the zip, this is actually not provided by the kernel, but by magisk
[Google Pixel 6 Pro] Sui77:
Can't download 1.18, is it up?
[Google Pixel 6 Pro] DespairFactor:
yeah it is now, I had to make a new update to it because the first build had an issue.
[Google Pixel 6 Pro] Tulsadiver:
You are just too fast.
[Google Pixel 6 Pro] bigdog1459:
Just got the Feb Update and 1.18 Despair installed. Will let it settle in but I am sure it's awesome as always.
[Google Pixel 6 Pro] Nekromantik:
i now have to do full wipe as after flashing 1.18 after booting with patched stock kernel on Feb update and flashing the kernel in EKM I get your device is corrupt message and android does not boot :(
[Google Pixel 6 Pro] reaper000:
Updated to Feb using factory image, rooted stock boot.img with Magisk 24.1, and then flashed 1.18 with EKM.

Great as usual, dev.
[Google Pixel 6 Pro] Nekromantik:
hmm strange how it worked for you and not me

now I re flashed full image without wipe and I can boot into adroid and root and flash other kernel.

so worried about flashing this again. I cant get rid of the device is corrupt message on boot though.

I am on latest canary magisk and not 24.1
[Google Pixel 6 Pro] Lughnasadh:
You'll likely have to factory reset or wipe to get rid of that corrupt message.
[Google Pixel 6 Pro] Nekromantik:
thought so :(
[Google Pixel 6 Pro] avid_droid:
Test driving 1.18
[Google Pixel 6 Pro] avid_droid:
So far so good. .7%/hr and that's with Bluetooth watch connected. Looking forward to see what deep sleep and idle drain per/hr is tonight
[Google Pixel 6 Pro] RetroTech07:
I wish .7%hr using the screen was possible lol
[Google Pixel 6 Pro] DespairFactor:
This seems good for using a watch too.

don't we all
[Google Pixel 6 Pro] avid_droid:
Haha. Right. Mine is currently at 3.4%. with watch it was at .7,but went to 1.3 shortly after. Things are looking good here with this kernel so far.
[Google Pixel 6 Pro] shag_on_e:
So I was in the process of flashing the Feb factory build after modifying the flash-all.bat to avoid wiping and to keep root so I could flash Despair 1.17 and got in a nice boot loop from copy pasting too many "update"s in the updater script. Once I found this it was an easy fix, but remember watch those details lol. On to 1.18
[Google Pixel 6 Pro] RetroTech07:
3.4hr for active drain with screen on? Mine is usually 7ish. This is about as good as I can get.
[Google Pixel 6 Pro] jcp2:
Can this be flashed over top of Kirisakura kernel, or does factory boot image need to be restored first?
[Google Pixel 6 Pro] RetroTech07:
I'd take the safest approach and just flash back the stock images, and then flash the new kernel to avoid any potential mishaps.
[Google Pixel 6 Pro] cultofluna:
Yes..you can if you want..

No need to restore stock images
[Google Pixel 6 Pro] :
It works, because it will overwrite the same files which comes with Kiri. I went back to Kiri from despair without restoring stock files.
[Google Pixel 6 Pro] RetroTech07:
That's fine, but I'm saying for me I'd rather go the safer route just in case something happens. I'd also make sure to back up my data before doing such things as I've experienced random reboots and loss of data back when the November build was out.

I'd rather avoid such headaches again, even though I know things will be OK.
[Google Pixel 6 Pro] Freak07:
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.
[Google Pixel 6 Pro] phaino00:
I can't thank you enough for that explanation. 👍😎👏
[Google Pixel 6 Pro] jcp2:
Thanks for the detailed explanation. I'll flash stock first:)
[Google Pixel 6 Pro] DespairFactor:
Build for Android 12L beta is coming out shortly. I am unsure if it works on the stock February A12 image as of yet.
[Google Pixel 6 Pro] Gordietm:
I flashed v2.0 on Android 12L. It flashed ok and booted up, however my phone kept freezing up and was unresponsive. I had to bo back to the stock kernel.
[Google Pixel 6 Pro] DespairFactor:
I am debugging this right now, don't flash anything until I give the go ahead
[Google Pixel 6 Pro] DespairFactor:
new build is up and working perfectly! Despair-V2.0
[Google Pixel 6 Pro] Gordietm:
As you said, V2.0 is working perfectly now. Thanks 👍
[Google Pixel 6 Pro] DespairFactor:
I am in the process of cleaning up the A12 build as well, please stay tuned for a rebase
[Google Pixel 6 Pro] Attinderkahlon:
If I want 12 L, do I need to clean wipe or i can update keeping the root the way i update every month?
[Google Pixel 6 Pro] DespairFactor:
Same as every month:)
[Google Pixel 6 Pro] Gordietm:
You don't need to wipe. Update the same way you've done previously. I used the android flash tool without wiping, then flashed the patched boot image.
[Google Pixel 6 Pro] DespairFactor:
I flashed it using the factory images and modified the script as I usually do. I honestly wasn't planning on flashing this. I had a report of the build not working properly, which made me flash it to start debugging it myself to ensure it was fully functional.
[Google Pixel 6 Pro] DespairFactor:
V1.20 is up for A12, this is a rebase. I am hoping to keep it closer in line to what the A12L build has
[Google Pixel 6 Pro] DespairFactor:
1.21 is out for A12 and 2.01 is out for A12L, I am done updating for the day
[Google Pixel 6 Pro] sunnybwoy1:
Using 1.21 with proton Jan update or should I use another version thank you.
[Google Pixel 6 Pro] DespairFactor:
It should work perfectly fine
[Google Pixel 6 Pro] Gordietm:
@DespairFactor Since you were so quick with the 12L kernel update, any possibility of a kernel for Android 13 DP1? I'm already on it and rooted.🙂
[Google Pixel 6 Pro] Alekos:
Let the guy rest lol how about we give him 24 hours? these devs are friggin heroes
[Google Pixel 6 Pro] Ivixmax:
mate,dont try A13 dp1,the modem is terrible.i only have 4 mbps on 4g.On A12 L i have 40 mbps in the same site
[Google Pixel 6 Pro] Alekos:
edit-- just rebooted and its better but who knows what's going on. transition from wifi to lte/5g is a lot better than January/Feb build (for me at least) but I'll have to give it a few days - don't want to jump to conclusions...

edit#2 - it's all good, LTE modem is fine on 12L.
[Google Pixel 6 Pro] Ivixmax:
the best modem at the moment is on A12L i think,or A12 febraury
[Google Pixel 6 Pro] DespairFactor:
I actually was ready to do it, a couple of the modules are not updated yet. Looking at edgetpu and wifi. I could build with the old modules maybe to have a booting build, but not sure how this will work.
[Google Pixel 6 Pro] Gordietm:
You mean Google hasn't updated the modules yet? When does that usually happen?
[Google Pixel 6 Pro] DespairFactor:
Are you on telegram? If so, shoot me a message, link is in my signature
[Google Pixel 6 Pro] DespairFactor:
Android 13 build is up and confirmed working by @Gordietm. Thank you for testing! https://drive.google.com/drive/u/0/folders/1uU-mDh-qmCJ6fp2T529p1mFkclDzOY3G
[Google Pixel 6 Pro] Texan1:
Well done and thanks for pushing a 12L kernel out so quickly mate, brilliant work! 👏

So are you happy with 2.01 as it stands? I've just flashed so will take it for a run.
[Google Pixel 6 Pro] DespairFactor:
I think it is pretty solid for now. We have to always remember these are not final products that Google has released. I think that A12 was "faster", but the animations on 12L are smoother. Also, just pushed out the A13 build, I have not tested for myself yet, but it has the changes that the A12L kernel has from me.
[Google Pixel 6 Pro] RetroTech07:
I hope I'm not asking a silly question as I've been looking all over for it, but is there a change log by chance?
[Google Pixel 6 Pro] DespairFactor:
on github
[Google Pixel 6 Pro] RetroTech07:
Is the change log known as commits? I always get lost trying to find things on GitHub because the layout can be confusing at times.
[Google Pixel 6 Pro] DespairFactor:
Yeah, that is correct
[Google Pixel 6 Pro] Texan1:
You're not the only one, I'm not great at reading/understanding commits at all, much prefer the old changelog in plain English!
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
2.01 works like a charm on 12L. Thank you @DespairFactor

Regards
[Google Pixel 6 Pro] DespairFactor:
For A13, I have uploaded a pro specific build to fix some touchscreen issues. You will notice these issues if you try to hold down the backspace key, it won't register your touch. Use the files ending in -Pro if you have this issue.
[Google Pixel 6 Pro] b0uNz:
v3.0pro installed and runs great. Also no more problems with Gboard, thank you
[Google Pixel 6 Pro] DespairFactor:
it wasn't gboard, it was the touch drivers;) and you are welcome!
[Google Pixel 6 Pro] RetroTech07:
@DespairFactor do you know what could cause a high idle drain while using the phone? The last few days I've gotten over 3% idle drain while just texting and browsing the web, and then active drain with screen on is high in the 15%. I'm curious if there's any kernel tweaks / settings I should be applying in a kernel manager or if I'm just unlucky?
[Google Pixel 6 Pro] DespairFactor:
I find the way drain is calculated is not true to your usage. For example, if you use your screen for 10 minutes and then turn it off, when it drops the percentage it counts against idle and not active. That is the first part of your question, the second part is the active drain being pretty high, I am not sure why it would be so high. It could be due to apps you run or some of the options on the device itself such as NFC, bluetooth, scanning, location services, etc.
[Google Pixel 6 Pro] Psych0t1c20:
I'm on January update still and using 1.13. Is it safe to update the kernel? I know it's based on February update.
[Google Pixel 6 Pro] DespairFactor:
Yeah it is fine to update, should still work!
[Google Pixel 6 Pro] Alxoom33:
@DespairFactor, are the boot.img files that you provide the stock boot images for that rom, or boot images that include your kernel? Thanks, it's been a long time since we chatted on your Pixel 2 and 2 XL threads.
[Google Pixel 6 Pro] DespairFactor:
It is my kernel, it is for people who are not using EXKM/FKM to flash
[Google Pixel 6 Pro] Divine Bicycle:
Can I flash this over the Kirisakura kernel using FKM directly?
[Google Pixel 6 Pro] bush911:
If you ask me, you better restore to the stock kernel before proceeding.

I have flash several third-party Kernels over each other, it turned out the phone started to show the "corrupt" message after booting.

I had to disable the flags to remove that annoying message, ended up wiping the whole device.
[Google Pixel 6 Pro] Divine Bicycle:
Hmm, ok. I will do that thanks
[Google Pixel 6 Pro] Texan1:
I got into two different bootloops trying to restore stock kernel yesterday, managed to get my way out of it but would prefer for that to not happen again!

If you are rooted with Magisk, what's the best way to return to stock?
[Google Pixel 6 Pro] indian84:
I will flash factory images without wipe.

Open flash-all.bat file and edit it to remove -w from fastboot -w command.

And flash all the images.
[Google Pixel 6 Pro] jac0b:
1.21 working pretty good. Not a lot of heavy use today.
[Google Pixel 6 Pro] Texan1:
@DespairFactor ...is the newer 'Test' kernel in your 12L folder ok to use?

Any major changes? Thanks.
[Google Pixel 6 Pro] DespairFactor:
It has vibration control but only lets you reduce the level
[Google Pixel 6 Pro] rafik25:
deleted
[Google Pixel 6 Pro] bigdog1459:
Just was able to install the newest FEB (004) update and despair 1.21. No issues thus far. Not that I expected there to be any, but I just wanted to report in that things went well incase anyone is on the fence.
[Google Pixel 6 Pro] g.shaunus:
Gents, I'm new to this so a little out of my depth here however I'm running A13 DP1 on a Pixel 6 Pro.. My device isn't rooted and I plan to keep it that way. I was wondering if anybody could give me some guidance/instructions on how to install this kernel? The touch driver issue is really bothering me.

Many thanks in advance chaps.
[Google Pixel 6 Pro] DespairFactor:
It's on my thread, you'd need to download the zip and the img file and flash the partitions manuallym make sure verity is disabled though or it will not boot
[Google Pixel 6 Pro] smurfmeat:
How do you adjust the vibration level? I'm using FKM, is there a particular setting?
[Google Pixel 6 Pro] g.shaunus:
Ah ok man, thanks for your response but I don't even know where to begin so I'll wait until March to see if Google address it
[Google Pixel 6 Pro] RetroTech07:
I know you can control vibration and haptic feedback in your regular settings.

Settings > sound & vibration > vibration and haptics

From there you can adjust settings, but idk if you're referring to something else.
[Google Pixel 6 Pro] smurfmeat:
I was referring to a response from the developer who said the main difference in the newer test kernel was vibration level control, which sounds like they're referring to something beyond the stock vibration settings. I think the "lowest" vibration levels on stock are still to high for my taste and it would be a plus if I could lower them even further with Despair kernel.
[Google Pixel 6 Pro] RetroTech07:
Yes, I understand you were referring to what the dev said about the new update, but posted what I did just in case if that's what you were looking for.
[Google Pixel 6 Pro] DespairFactor:
It's done via EXKM, I am unsure if FKM supports it at this time.
[Google Pixel 6 Pro] smurfmeat:
I now have EXKM but do not see a setting to modify vibrations.
[Google Pixel 6 Pro] DespairFactor:
2.02 for 12L is up
[Google Pixel 6 Pro] Zilla0617:
Is 2.02 similar to 2.0 or 2.01?
[Google Pixel 6 Pro] smurfmeat:
Vibration intensity settings now show up in EXKM, thank you.
[Google Pixel 6 Pro] Texan1:
@DespairFactor Was that the only change in 2.02?
[Google Pixel 6 Pro] DespairFactor:
This wasn't a change for 2.02 really
[Google Pixel 6 Pro] Texan1:
Ok... where can I find the commits for your A12L kernel?
[Google Pixel 6 Pro] DespairFactor:
Now to mess you all up, A12 build is rebased and back to 1.00. Trying to clean things up and get this running the best I can, as always
[Google Pixel 6 Pro] Texan1:
I see the 2.02 12L kernel is no longer in your Google Drive folder, is that kernel being rejigged as well? (I installed 2.02 yesterday).
[Google Pixel 6 Pro] DespairFactor:
yeah, in the process right now, making 2.00;)
[Google Pixel 6 Pro] Texan1:
Thanks, installed 👌

Edit... could you have possibly done anything in this build that might affect benchmark scores? One of my tests has significantly dipped lower after running it on the new 2.0 kernel.
[Google Pixel 6 Pro] Gytole:
At least you TELL us, so we're not all confused. I agree with yuh, clean it up so it make senses to you AND us! Appreciate the hard work!
[Google Pixel 6 Pro] DespairFactor:
Don't trust benchmarks

EDIT: some stuff may make a return
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
@DespairFactor hello there! Thank you as always for sharing your kernel builds with us. Quick question, I am on 2.02 as was released earlier. Based on your recent cleanup, does the current 2.0 correspond to the erstwhile 2.02 and the current 2.01 correspond to the latest build for 12L? My apologies for the inconvenience.
[Google Pixel 6 Pro] DespairFactor:
2.0 is for 12L, I am going to clean the folders so they only have the most recent release:)
[Google Pixel 6 Pro] DespairFactor:
1.01 up for A12, 2.01 up for A12L and 13 builds are being rebuilt as 3.0 with vibration control added in
[Google Pixel 6 Pro] DespairFactor:
Anyone interested in a support telegram group?
[Google Pixel 6 Pro] Texan1:
Count me in 👍
[Google Pixel 6 Pro] DespairFactor:
https://t.me/despairkernel created, added link to OP
[Google Pixel 6 Pro] Gytole:
Ready to nuke my phone at will, my frand!

I FIGHT FOR THE USERS!
[Google Pixel 6 Pro] Gytole:
How the Despair Kernel bar looks as the kernel progresses.
[Google Pixel 6 Pro] DespairFactor:
You missed the final stage, where there is no name and the development tag is gone.
[Google Pixel 6 Pro] cosy6ay:
can 2.01_a12 works on 12l?
[Google Pixel 6 Pro] Sui77:
Why don't you use the 12L?

12L - Google Drive
[Google Pixel 6 Pro] cosy6ay:
hi as per the naming convention.

i thought it would work on 12l.

post #300

1.01 up for A12, 2.01 up for A12L and 13 builds are being rebuilt as 3.0 with vibration control added in
[Google Pixel 6 Pro] Golf c:
If an old man can figure it out. So can you. Keep up youngblood
[Google Pixel 6 Pro] DespairFactor:
Redacted
[Google Pixel 6 Pro] rhetorician:
Hi, does this work with March update?
[Google Pixel 6 Pro] Golf c:
It's broken it doesn't work. Try kriskura
[Google Pixel 6 Pro] avid_droid:
Edit
[Google Pixel 6 Pro] rhetorician:
Thanks!
[Google Pixel 6 Pro] Lughnasadh:
The answer lies in the post right above yours.
[Google Pixel 6 Pro] Lughnasadh:
You know very well it's not broken.
[Google Pixel 6 Pro] DespairFactor:
New 2.04 released with DAC support fixed
[Google Pixel 6 Pro] jcp2:
All I'm seeing is 2.02 in the first post download link for A12L