yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] DespairFactor:
I had to pull it, I am updating now. Looks like the patch causes bootloops on 12.1 unfortunately
[Google Pixel 6 Pro] RetroTech07:
I would love to try a new kernel, but every time I do my idle drain just goes sky high and I can never understand why.
[Google Pixel 6 Pro] reaper000:
I flashed your initial 2.04, it wouldn't boot. Tried reflashing the entire 12.1 stock rom to get a bootable device.

No dice.

Unfortunately, it looks like I'm gonna have to do a full internal storage wipe and clean install...
[Google Pixel 6 Pro] RetroTech07:
You just need to flash back dtbo, boot, and the two vendor files. Have you tried that?
[Google Pixel 6 Pro] reaper000:
Yeah, the dirty flash would have included all that... still bootlooped.

Only a totally clean flash has gotten me booting.

Not blaming anyone -- that's the acknowledged risk we all take when flashing stuff
[Google Pixel 6 Pro] RetroTech07:
I know you did a dirty flash, but was hoping doing it with just the 4 files would work.

I'm overly cautious now, making sure I backup before I do any sort of mod because I've lost out on some small things before.

Sorry you had to do a wipe, though. 😣
[Google Pixel 6 Pro] DespairFactor:
you flashed a file that I never said was good to flash. Also, the initial 2.04 was from several hours ago and it is running on my device right now.
[Google Pixel 6 Pro] reaper000:
Look, I already said (post #325) I'm not blaming anybody -- including you, @DespairFactor -- for my troubles. I appreciate your work and will continue to use it because you put out damn good product. I've used your kernels/ROMs for years.

However, I have every right to post my experience with flashing that product. Which is all I did. Perhaps it was a bad download, a bad flash, whatever. As a dev, I would think you need to know it didn't go for me. But then you accused me of "flashing a file that I never said was good to flash"?!?

@DespairFactor: See your own post -- #319 -- on this thread.

To me, that post "New 2.04 released with DAC support fixed" , is you saying 2.04 was good to flash. I'm not sure how anybody can read that differently. Heck, I even tapped "Like" on it.
[Google Pixel 6 Pro] DespairFactor:
Android 13 Beta 1 kernel is up, you may flash using the zip
[Google Pixel 6 Pro] DespairFactor:
Android 13 Beta 2 kernel is up on drive. Also have been making some changes to A12 kernels
[Google Pixel 6 Pro] DespairFactor:
heard some people are hiding out in here https://t.me/despairkernelnew
[Google Pixel 6 Pro] jericho246:
Hey mate, is it safe to flash the latest version on July update? :)

i gotta say, after trying numerous kernels and ROMs, I find that the best combo (temperature-wise), is stock with Despair kernel. Could be placebo of course.

I do zero gaming, and on other ROMs with different kernels, the temperature climbs up to 39 degrees in a matter of like 4 minutes. With Despair on stock, I can actually browse the web, use Instagram, Telegram, Reddit and Spotify and the temperature will still reach around 39 degrees but noticeably slower, so that's good. 👍
[Google Pixel 6 Pro] DespairFactor:
yeah it will work, I also have updated for July, it's not much of a difference from June. I also have raised the max brightness of the display.

Download: https://drive.google.com/drive/folders/17VzhffFNH0iyzruH_49L8-f0hB2-NvMF
[Google Pixel 6 Pro] NLQuantumFluxx:
This folders empty, sorry if i'm being blind but where can I download the kernel for July build? thanks
[Google Pixel 6 Pro] DespairFactor:
Yeah here, back to original location in the QPR3 folder https://drive.google.com/drive/folders/1taqEh8jXJ9v2NA1AJvgysyNafG1NPRhs
[Google Pixel 6 Pro] HollywoodHogan:
Telegram says this chat doesn't exist? Is there anywhere else to discuss the kernel?

I see two new A13 kernels in the Drive folder, including one under 'LTO' which I flashed but unsure what this is or what to compare it to? Phone has also been running a bit warm and I'm not sure if the kernel could be causing it or if others are experiencing the same?

Thanks.
[Google Pixel 6 Pro] DespairFactor:
That is very odd, the link should work. https://t.me/despairkernelnew alternatively DM me with the link in my signature
[Google Pixel 6 Pro] HollywoodHogan:
All good now, I had set things up incorrectly, weird.
[Google Pixel 6 Pro] cosy6ay:
any one can share the link to telegram despair kernel group? cannot seen to find the group.

thanks in advance.
[Google Pixel 6 Pro] DespairFactor:
New build up for QPR3 and March.

Telegram: https://t.me/despairchat
[Google Pixel 6 Pro] jploco:
i this moment, can i flash this kernel on update march of 2023?
[Google Pixel 6 Pro] DespairFactor:
yes you can
[Google Pixel 6 Pro] jploco:
With which apk do you recommend installing it?
[Google Pixel 6 Pro] aimsjahan:
Hi dev! It's been a long since your last build, hell I even thought the kernel is dead!

AFAIK, this kernel is the only one out there which supports beta builds of official F/W. So having this updated is a big deal.

Really happy to see this thread alive again. Keep this on pls. Thank you for your works.

PS: Can we get a changelog or something?
[Google Pixel 6 Pro] DespairFactor:
EXKM
[Google Pixel 6 Pro] w_tapper:
WOAH i wanna try this kernel, would it work on feb update?
[Google Pixel 6 Pro] DespairFactor:
You can try it, but I cannot guarantee it will work.
[Google Pixel 6 Pro] kpirnie:
Sweet! So far, this is the only kernel I've been able to flash on Evo. Used KF this time, don't know if that is what made the difference or not, but still cool :)
[Google Pixel 6 Pro] DespairFactor:
Awesome! It could be dependencies other kernels have on other files, I try not to stray ridiculously far from stock.
[Google Pixel 6 Pro] DespairFactor:
New 3.00 is up!
[Google Pixel 6 Pro] rayraycarter4:
Did you try it
[Google Pixel 6 Pro] w_tapper:
no
[Google Pixel 6 Pro] w_tapper:
works on latest lineageos
[Google Pixel 6 Pro] DespairFactor:
Good to know!

3.01 has been uploaded
[Google Pixel 6 Pro] DespairFactor:
new version of 3.01 up with changes from QPR3 beta 3
[Google Pixel 6 Pro] ultraklew:
new version of 3.01 works perfect on latest lineageos/ thanks boss for your job!
[Google Pixel 6 Pro] DespairFactor:
new build up for May

Telegram link updated in OP
[Google Pixel 6 Pro] w_tapper:
is it 3.0.4?
[Google Pixel 6 Pro] DespairFactor:
doesn't support may officially, that build is for june
[Google Pixel 6 Pro] w_tapper:
oh ok, i flashed 3.0.3 on my risingos build and it didnt work, i was using only lineageos trees so its kinda weird
[Google Pixel 6 Pro] jlokos:
The update for July said 3.07, but there is also a 3.08. Can you use either one for the July image?
[Google Pixel 6 Pro] DespairFactor:
yes
[Google Pixel 6 Pro] Alxoom33:
Any work on Android 14 beta 4? Has source been released?
[Google Pixel 6 Pro] cantthinkofagoodusername:
Would i be able to flash the newest version of this kernel on A13 TQ1A?
[Google Pixel 6 Pro] Zilla0617:
Has the Telegram channel returned?
[Google Pixel 6 Pro] dark2099:
@DespairFactor Tried using the 4.00 kernel on the drive with the stable A14, had some reboots, attached everything from /sys/fs/pstore.
[Google Pixel 6 Pro] DespairFactor:
yeah it will work fine
[Google Pixel 6 Pro] Az Biker:
@DespairFactor

Want to verify this before I do it :p

Patch your kernel.img in Magisk

Flash/install it with a kernel manager like Franco or EXKM?

That's it?

Thanks in advance!
[Google Pixel 6 Pro] bs3pro:
Kernal have color control??
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm pretty sure the kernel is the same on both the universal and Verizon versions of the firmware, as well as both the Pixel 6 and Pixel 6 Pro. Yes you can flash over the Verizon version of the OTA.

Yes.
[Google Pixel 6 Pro] CrashTestDroid:
That's a big change from previous Verizon phones. The 6 Pro escaped their locked bootloader policy?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I have no idea / I haven't been keeping close track if anyone with Verizon variants of the P6P has been able to unlock their bootloader and root, such as several or many folks have with their AT&T and T-Mobile variants. However, just because someone has the Verizon firmware on their phone doesn't mean they're on a Verizon variant. We have several (at minimum) folks on here with the unlocked P6P being used on the Verizon network, and just being on the Verizon network has no effect on whether you can unlock the bootloader or not.

Since the question was simply "can Despair be flashed over the Verizon versions of the OTAs?" without any qualifier remarks as to whether they're on a Verizon variant or another variant just running on the Verizon network, I was just answering the question directly.

When I used Verizon, there were a couple of unlocked phones I used on their network, one or both of which required Verizon-specific elements for the unlocked phones to work on their network, but that didn't keep me from being able to unlock the bootloader - in fact it was completely necessary in order to use those phones on Verizon, in order to install their proprietary radio firmware.
[Google Pixel 6 Pro] reaper000:
I bought an unlocked P6P from Google Store and am using VZW Prepaid. When I ran the flash-all.bat of the new factory image 037. a1 in fastboot mode, the Verizon-specific radio was flashed.

I'm not sure I've noticed any difference in reception. But the FPS is indeed faster. Must be "less secure", huh, Google? LOL
[Google Pixel 6 Pro] DespairFactor:
Yes sir! Feel free to join the Telegram for quicker responses.
[Google Pixel 6 Pro] Az Biker:
No. All VZW devices have locked bootloaders.

The Verizon factory image is for those, like me, who have a bootloader unlockable device that works on any carrier.

If I wanted a VZW specific features I'd use the VZW factory image because it's made to work better with VZW's network (I suppose).

But I prefer to flash the universal factory images, not sure why :D
[Google Pixel 6 Pro] DespairFactor:
We are currently testing a vnedor_dlkm with 10hz idle mode re-enabled. I am not 100% sure if it is working correctly, but it will not break anything on device. Also, current two builds that are being seen as the best are 1.042 and 1.06, feel free to flash either one with the vendor_dlkm and provide feedback:)
[Google Pixel 6 Pro] Az Biker:
Neither of the builds you mention are listed in the OP 'links".
[Google Pixel 6 Pro] DespairFactor:
All builds are posted in the shared Google drive link, we are now currently using V1.05 as stable. I am awaiting the new update from Google prior to releasing a new build.
[Google Pixel 6 Pro] Az Biker:
Okay, I guess I confused "current two builds that are being seen as the best" with stable builds , got it(y)(y)(y)
[Google Pixel 6 Pro] DespairFactor:
I have since removed those builds and replaced them, I don't keep this thread too up to date compared to telegram
[Google Pixel 6 Pro] DespairFactor:
If anyone is curious, there are a couple builds in the test folder on Google Drive.
[Google Pixel 6 Pro] DespairFactor:
Despair-V1.07 is out, includes December update!
[Google Pixel 6 Pro] cd993:
Great, thanks!

I don't suppose your custom kernel helps/could help the loss of root situation? Guess we'll most likely need to wait for magisk to be updated
[Google Pixel 6 Pro] DespairFactor:
I may be able to add in kernel root, but it wouldn't bypass safetynet
[Google Pixel 6 Pro] cd993:
Thanks for the quick reply! That'd be cool, though indeed perhaps Magisk will be promptly updated.

We can see, great to have custom kernel options too!

:)
[Google Pixel 6 Pro] DespairFactor:
I don't think it is a good idea though for me to ship that without a way of properly disabling. Magisk should be able to get past this, I am thinking within the next few days
[Google Pixel 6 Pro] cd993:
Agreed. A fix will be with us soon 😊
[Google Pixel 6 Pro] freddienuxx:
glad to have you back @DespairFactor
[Google Pixel 6 Pro] DespairFactor:
Thank you:) I am constantly building test builds to see what works best
[Google Pixel 6 Pro] reaper000:
Patched December update-based Despair v1.07 with new Magisk. Updated stock ROM using fsctory image, flashed patched v1. 07 and running smooth and rooted.
[Google Pixel 6 Pro] shag_on_e:
Hmm this didn't work for me. I'm running the newest Magisk and patched 1.07 and lost root. The update was clean, kept verity and verification disabled but root didn't stick. I've also re patched and re flashed 1.07 and the stock patched boot but none worked.
[Google Pixel 6 Pro] yyz71:
It's working here.his zip and boot img👍
[Google Pixel 6 Pro] reaper000:
Your Magisk is likely not the latest unofficial Magisk that was patched AFTER the December update. You can get it from other threads here on XDA. Some users also provided it on Despair's Telegram support thread
[Google Pixel 6 Pro] Lughnasadh:
FYI: Canary 23016 is now out with all the fixings 👍
[Google Pixel 6 Pro] DespairFactor:
what zip?
[Google Pixel 6 Pro] yyz71:
There's a 1.07 zip there as well
[Google Pixel 6 Pro] yyz71:
The zip is gone 😔
[Google Pixel 6 Pro] DespairFactor:
that worked on your phone?

EDIT: Can you join telegram?
[Google Pixel 6 Pro] yyz71:
Yes it worked 😊
[Google Pixel 6 Pro] DespairFactor:
We are now using flashable zips:) for those of you without EXKM or FKM, I have uploaded the boot.img and you will need to take the dtbo.img, vendor_boot.img and vendor_dlkmg.img from the zip and flash them all manually.
[Google Pixel 6 Pro] Az Biker:
Those with a kernel manager can still patch the Despair v108.img and flash that directly from the kernel manager, right?
[Google Pixel 6 Pro] DespairFactor:
Of course but that isn't all of the images
[Google Pixel 6 Pro] Az Biker:
@DespairFactor

Last time I just patched your v103.img and flashed it via EXKM., no issues.

This time I did the same thing with v107, bootlooped at GOOGLE logo.

Got back into bootloader, fastbooted the patched Magsik boot.img and all is well.

Tried it several times, no go.

Are there additional steps needed with the new magisk?
[Google Pixel 6 Pro] DespairFactor:
It depends on your phone setup, if you have Verity enabled you need to use new magisk to patch the boot.img or the zip method. You also need to flash all 4 images I mentioned in the post about the flashable zips(boot.img, vendor_boot.img, vendor_dlkm.img and dtbo.img) if you're using fastboot. If you are on the November build, 1.07+ will not work.
[Google Pixel 6 Pro] Az Biker:
I'm on Dec update, 23016 magisk, flashed factory image with out any verity commands, neither 107 or 108 worked after patching with new Magisk and flashing with EXKM

Edit: after rereading your comment "We are now using flashable zips:) for those of you without EXKM or FKM, I have uploaded the boot.img and you will need to take the dtbo.img, vendor_boot.img and vendor_dlkmg.img from the zip and flash them all manually."

I think I see where I misread your instructions. I thought the manual flashing of the extra images were for those NOT using a kernel manager.

I'll add flashing the additional imgs you mentioned to the patched v107 img.
[Google Pixel 6 Pro] DespairFactor:
Yeah sorry about the confusion! I am on 1.09 and I believe I may be getting the best battery I have so far.
[Google Pixel 6 Pro] Az Biker:
I'll check for 109 before I get started in a bit! Thanks for your hard work, time, and support in xda!
[Google Pixel 6 Pro] shooterlgk:
So can I just flash the zip without having to do the whole dtbo img or vendor img? Im rooted as well
[Google Pixel 6 Pro] DespairFactor:
Yes sir!
[Google Pixel 6 Pro] mac796:
I flashed 1.09 with ex manager no problem. Thanks
[Google Pixel 6 Pro] mac796:
I flashed 1.11 and now my wireless charging works again. That quit since November. Maybe it's something Google did I don't know, but I'm thankful to somebody.
[Google Pixel 6 Pro] DespairFactor:
V1.14 is out.

Changelog: https://github.com/DespairFactor/raviole/commits/dec
[Google Pixel 6 Pro] DespairFactor:
Back to 1.13 and 1.12 testing.
[Google Pixel 6 Pro] DespairFactor:
V1.14 and 1.15 are testing now.
[Google Pixel 6 Pro] Vio281:
got boot loop coming from Pixel 6 magisk patch, cant even get back to stock flashing stock image.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Try this?

Official Google Android Flash Tool
[Google Pixel 6 Pro] Vio281:
yep thats what I did, would preffer not to do this every time.

how are people flashing this kernel on November update?

does 1.15 work with November update? only asking because other kernel stated certain version work with November or december update.
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's a good point. I looked at the Google Drive link for the downloads and selected "Last modifed" instead of the default "Last modified by me". I see the oldest version is from December, so I would fully expect that none of them would work with the November firmware.

Sometimes there are just too many changes from one month to the next for the kernel to work with an older firmware. All the kernels will have been at least partially based on the same source code provided by Google for the month in question, so they'd all likely share that limitation.
[Google Pixel 6 Pro] DespairFactor:
won't work on November build
[Google Pixel 6 Pro] Tulsadiver:
Question, I don't know anything about kernels but it seems I can't access developer settings now. It crashes when selected. I'm on December update and flashed V1.14

Seems like I had the same issue when I tried a different kernel. Anyone know what I'm doing wrong?
[Google Pixel 6 Pro] DespairFactor:
The problem is magisk for some reason causes this, you can either use Safetynet Fix, which sets ro.debuggable to 0, I can also include a tweak that does this in my zip. Sorry for the inconvenience.
[Google Pixel 6 Pro] Tulsadiver:
Thank you sir!!
[Google Pixel 6 Pro] Zilla0617:
It may be one of your modules, I had this issue unable to access Google preferences within settings. It turned out that it was a module causing it to crash.
[Google Pixel 6 Pro] DespairFactor:
I thought I had the prop in there, I will update my zips to support it:) I am also working on making a similar build of 1.14 for November image for all of you who are not on the December update. I am also mirroring the December update on Google Drive for raven.
[Google Pixel 6 Pro] DespairFactor:
New zip for V1.14 is being uploaded with the fix and will be up shortly!:)
[Google Pixel 6 Pro] DespairFactor:
December Image mirror for Raven: https://drive.google.com/file/d/1it7rb7QjHwo9U9mL-YWD3-aUqk8gVI3X/view?usp=sharing

November Images: https://drive.google.com/drive/folders/1dJOl20F9tR--DiUC3yzI6gScbGnjeZrs?usp=sharing
[Google Pixel 6 Pro] freddienuxx:
which module because im having same issue. thx advance
[Google Pixel 6 Pro] roirraW "edor" ehT:
Wow, that's awesome of you!
[Google Pixel 6 Pro] DespairFactor:
I figured that I should make a proper November build since Google has taken away the ability to install December update on both Pixel 6 devices.
[Google Pixel 6 Pro] Zilla0617:
It was a font module, don't remember which because I deleted it a while ago.
[Google Pixel 6 Pro] freddienuxx:
Thx that was the culprit Google Sense text system magisk mod. Now it works thx again
[Google Pixel 6 Pro] Tulsadiver:
That worked!!....Thanks!
[Google Pixel 6 Pro] Vio281:
not being an asshole but you could have save me a lot of time with a disclaimer. I literally try this 4-5 times on november build and was wondering why it is not working.
[Google Pixel 6 Pro] DespairFactor:
well, I think it's safe to assume that a build on a branch called Dec would be meant for the December update
[Google Pixel 6 Pro] roirraW "edor" ehT:
Please don't take this the wrong way. I'm not joining in or advocating any kind of pile-on for your suggestion. I'd like to point out why your suggestion isn't realistic:

Some developers don't even have the phone they're developing for.

Developers rely on testers, which is time-consuming enough.

Sometimes a kernel that was made for month Y will work on the previous firmware from month X - but I'd never do so except for unusual circumstances.

You have learned a valuable lesson from your adventure. This isn't the developer's fault or anyone else's. You didn't know that running a kernel from the wrong month might temporarily brick your phone, but now you do. I'm reasonably sure you won't make the same assumption about kernels anymore. This has been a basic truth about kernels for as long as kernels have existed.

Don't turn the lesson you learned into something it's not.

The only disclaimer any developer really needs is in the OP (also below). You are the only one responsible for making sure that what you think will work, will work.

It's inevitable that for whatever disclaimer(s) an OP has, someone will not read or notice them, and then some of them will complain that they should be made more obvious.

These developers don't owe us anything, we owe them.
[Google Pixel 6 Pro] DespairFactor:
V1.15 is now up! I would like to hear feedback between V1.14 and V1.15.

EDIT: December build is up, November is in progress
[Google Pixel 6 Pro] DespairFactor:
V1.15 is now up for November!
[Google Pixel 6 Pro] Lycidias:
Is there a change log i could read through the kernel builds?

Thanks
[Google Pixel 6 Pro] DespairFactor:
yes, it is on github
[Google Pixel 6 Pro] Vio281:
fair enough, how do I know which version is December build and November build?
[Google Pixel 6 Pro] wolfeyes30:
See attachment. Folder named November and the file names end with nov as well
[Google Pixel 6 Pro] Vio281:
V 1.15 for november build is still broken, would nto get pass the "G" screen with loading bar
[Google Pixel 6 Pro] kheltek:
Thanks as always, appreciate you sharing your work
[Google Pixel 6 Pro] DespairFactor:
stop spreading misinformation, if you rebooted your device it would work...
[Google Pixel 6 Pro] kheltek:
Will take a day or two for full feedback, but so far everything is smooth. One thing I noticed off the bat is the finger print sensor is working significantly better than it did on 1.14. Not sure if it's kernel related, but definitely better performance. I'll share more on TG.
[Google Pixel 6 Pro] Vio281:
What would I gain from that....if it doesn't work then I tell you it doesn't work..1.14 work
[Google Pixel 6 Pro] DespairFactor:
k, it does work though, so enjoy
[Google Pixel 6 Pro] DespairFactor:
The current December builds will work on the January update. I will update as soon as sources are released.
[Google Pixel 6 Pro] DespairFactor:
January build up now, I have removed December and November builds! Build is Despair-V1.15
[Google Pixel 6 Pro] shag_on_e:
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
[Google Pixel 6 Pro] Kris Chen:
Does it mean that Despair-V1.15 can be used in Jan updated ?
[Google Pixel 6 Pro] DespairFactor:
Yeah, 1.14 and 1.15 are updated for January. I am also working on 1.16
[Google Pixel 6 Pro] DespairFactor:
Awesome! I appreciate any feedback
[Google Pixel 6 Pro] nummer:
will you make a features list for the op?
[Google Pixel 6 Pro] DespairFactor:
Haven't really thought about it
[Google Pixel 6 Pro] freddienuxx:
Your the man been the man since them nexus days
[Google Pixel 6 Pro] DespairFactor:
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.
[Google Pixel 6 Pro] Attinderkahlon:
Telegram invite link is not working. It's expired.
[Google Pixel 6 Pro] EthanG_1988:
It looks like the group disappeared recently. I was reading posts earlier this morning, and now it is gone
[Google Pixel 6 Pro] DespairFactor:
Too much drama occurred from it, sorry!
[Google Pixel 6 Pro] EthanG_1988:
Okay, thanks for all your work. The kernel is awesome!
[Google Pixel 6 Pro] DespairFactor:
Thank you, I appreciate it! I will try to be more active on here
[Google Pixel 6 Pro] freddienuxx:
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
[Google Pixel 6 Pro] wanttotree:
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.