yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] HolyAngel:
I was just looking at this myself and it's gonna be rough. KCAL was made for MSM display manager, basically qualcomm only, and we're not using that on this device. I also haven't seen Savoca here in over a year..

Yeah thats an interesting one. It's built in to the kernel but not enabled by default. I enabled it but still getting 'userspace' in wireguard app. I seem to remember root being a thing tho for the kernel module and i'm not rooted 🤔
[Google Pixel 7 Pro] bs3pro:
Ugh, that's rough. Hopefully something will come. I know in custom roms on p6/p6pro rgb was available in the display settings. So maybe its just SW related? Thanks for your hard work!
[Google Pixel 7 Pro] DespairFactor:
I'll take a look at the wire guard stuff during the week
[Google Pixel 7 Pro] HolyAngel:
oh my bad, I was looking at the wrong tree lol wireguard does get built-in by default with nothing extra necessary needing done. The app userspace still stands though. I still think I remember it being a root issue or permissive kernel maybe. I can't remember.
[Google Pixel 7 Pro] xChickens:
So if I understand this correctly, you don't need to wipe when you disable verification? You can just boot with the modified magisk init_boot.img?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You do have to wipe when you disable Verification. Next month, if you update your Pixel firmware, as long as you re-disable Verity and Verification when you update, then you won't have to wipe again to install next month's kernel update.

If you update and forget to disable them, then if you re-disable them after, you'll have to wipe yet again.
[Google Pixel 7 Pro] xChickens:
What was this referring to then?
[Google Pixel 7 Pro] jac0b:
What did you undervolt on 1.08?
[Google Pixel 7 Pro] DespairFactor:
it's the same panel undervolt
[Google Pixel 7 Pro] Nekromantik:
@DespairFactor

See this post https://xdaforums.com/t/kernel-24-1...-pixel-7-pro-aka-pantah.4509795/post-87630491

Might be good idea to stop people forgetting to disable verity from flashing it and causing wipe without having backup etc
[Google Pixel 7 Pro] DespairFactor:
Yeah, capntrips sent me a message about it too, I will include it in future zips. I don't want to repack all of the existing ones.

I do appreciate the heads up though :)
[Google Pixel 7 Pro] Nekromantik:
no worries
[Google Pixel 7 Pro] jac0b:
@DespairFactor

Was the lower voltage mod causing issues?
[Google Pixel 7 Pro] DespairFactor:
nope, not at all, just don't think it truly ever reached that voltage. The voltage that was being lowered was the max for the display, not the minimum
[Google Pixel 7 Pro] jac0b:
Gotcha, will test out the new version.
[Google Pixel 7 Pro] lassetth:
The QPR version of the kernel is missing in GDrive Pantha QPR?
[Google Pixel 7 Pro] s3axel:
Hmm, I can see V1.09
[Google Pixel 7 Pro] lassetth:
Stange, because I still can`t se the QPR kernel file!? For Android 13 stock the kernels files are there. But I have one saved on my Pc. I was also looking for if there where any upgrade. Thanks!
[Google Pixel 7 Pro] DespairFactor:
the 1.09 is definitely there
[Google Pixel 7 Pro] lassetth:
Ok, thanks!
[Google Pixel 7 Pro] exocetdj:
this must be why my update experience was as follows:

- patched init_boot and added to image.zip - amended flash_all.bat to "fastboot update --skip-reboot image....zip"

- rebooted to fastboot and installed the image zip to both sets of partitions (fastboot set_active other then flash_all.bat)

- rebooted fastboot and flashed vbmeta to both sets of partitions (fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification)

- rebooted device (fastboot reboot) - my device rebooted a couple of times then finally booted to system on the other set of partitions

- i then rebooted and flashed patched init_boot.img to root and then Despair kernel 1.09 via kernel flasher

Pretty cool :)
[Google Pixel 7 Pro] Pixel86:
Just flashed v1.15. It's running great 👍.

Question, was WireGuard support ever implemented?
[Google Pixel 7 Pro] jac0b:
@DespairFactor

Did you take a break?

Thanks for the new QPR kernel. They are running very solid.
[Google Pixel 7 Pro] theimpulson:
THREAD CLOSED DUE TO MULTIPLE GPL VIOLATIONS | XDA DEVELOPERS AND GPL
[Google Pixel 7 Pro] karandpr:
Thread Re-ropened.

@DespairFactor

-XDA Staff
[Google Pixel 7 Pro] Texan1:
Nice to see this thread back open. Kernel is excellent.

Assuming it's ok to provide the download link again: https://drive.google.com/drive/folders/1cfjl2hZkBJbNlKdlZ7dK-4cVb8u76Pgc

Kernels in the main folder are for stock eg. Despair V2.03.zip

Kernels in A14 and QPR folders are self-explanatory.
[Google Pixel 7 Pro] DespairFactor:
Yeah, I will add it to the main post. Also QPR kernels also work on stable for anyone wanting to do that

EDIT: Link added, also telegram link added to OP
[Google Pixel 7 Pro] DespairFactor:
New builds are up
[Google Pixel 7 Pro] DespairFactor:
2.01 and 2.01-Q3 builds are up now
[Google Pixel 7 Pro] DespairFactor:
new builds up now for QPR3 beta 3 and stable V2.01, V2.01-Q3
[Google Pixel 7 Pro] Sui77:
Can i just flash over Radioactive using kernel flasher?
[Google Pixel 7 Pro] Pixel86:
My guess is no, but YMMV if you try.
[Google Pixel 7 Pro] DespairFactor:
yes
[Google Pixel 7 Pro] Sui77:
Worked flawlessly using Franco
[Google Pixel 7 Pro] Curiousn00b:
Any chance anyone has the builds for February/March?

Some roms aren't updated to the newest ones yet, but would like to pair it with an older build.

Thanks 🙏
[Google Pixel 7 Pro] DespairFactor:
The newest should still work on those iirc
[Google Pixel 7 Pro] Curiousn00b:
Just gave it a shot, for me it didn't workout, but it didn't bootloop, just stayed on the boot animation.
[Google Pixel 7 Pro] Sui77:
Did you manage to overcome that?
[Google Pixel 7 Pro] DespairFactor:
May be a rom issue actually
[Google Pixel 7 Pro] Curiousn00b:
I thought it was because March was another rebase, so all things March and up no longer work on previous stuff like how December and onward didn't work on previous stuff.

But I guess it's time to move on and wait for an older build to be updated, lol.
[Google Pixel 7 Pro] DespairFactor:
2.02 up for May, should work on April builds too
[Google Pixel 7 Pro] scott45333:
I see 2.02 and 2.03. Which should be used for may?
[Google Pixel 7 Pro] DespairFactor:
Use 2.03
[Google Pixel 7 Pro] speakeasy2:
Would I be able to use 2.03 on the most recent 13 beta
[Google Pixel 7 Pro] DespairFactor:
No, there is a build for each beta
[Google Pixel 7 Pro] DarkLinuxz:
Is there maybe a way for the end user to experiment with the display undervolt? It's totally fair for you not to include a heavy undervolt which works on your device, of course the lowest it will go depends on the device, but I imagine it could be further lowered on a device-to-device basis. Thank you for your work!
[Google Pixel 7 Pro] roblav96:
@DespairFactor is there WireGuard love in this kernel?
[Google Pixel 7 Pro] Pixel86:
There is 👍
[Google Pixel 7 Pro] speakeasy2:
Will this kernel work for Android 14 beta 3? Thank you for the help.
[Google Pixel 7 Pro] cultofluna:
Yes, if you flash the kernel build that's for a14
[Google Pixel 7 Pro] aleksgiab:
Pixel 7 pro Android 14 (UPB3.230519.014) Can we put the kernel here?
[Google Pixel 7 Pro] 5.1:
Hi,

The answer is literally one post above your question 😅

Cheers,

Sébastien.
[Google Pixel 7 Pro] aleksgiab:
Ugh, it's not worth anything...it hangs and breaks the mobile completely...stay away from here....
[Google Pixel 7 Pro] 5.1:
Hi,

Are you sure you downloaded the proper version for A14 beta?

There are 2 folders, one for A13 and one for A14. 🤔

Good luck,

Sébastien.
[Google Pixel 7 Pro] DespairFactor:
yes @aleksgiab, please stay away
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Ive been looking for a custom kernel to try out and this one seems like my taste.

Im looking for a permissive kernel that allows gpu configuration.

All my kernel apps wont display the gpu settings on the stock kernel. Will this kernel allow gpu changes? ex. change gpu frequencies..etc..

Edit: installed and I guess pixel devices can't access the GPU settings but other than that the kernel runs pretty good while on beta 4.

Thanks for your work..
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Took over 25 minutes to drop from 100 to 99 on battery with Bluetooth on..

Give the o.p credit for keeping performance and less battery drain symotanously..
[Google Pixel 7 Pro] JohnTheFarm3r:
FYI: 100 > 99% takes much longer than 99 > 98%. Certain phones "overcharge" the battery slightly from 99 to 100%. Common among Xiaomi phones. So, don't measure the battery from 100% but rather from 99%.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
very interesting thanks
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Had to return to stock.

when processing pictures the system just hangs..
[Google Pixel 7 Pro] Pixel86:
No issues here on latest Android 14 Beta 4 and v3.03 👍
[Google Pixel 7 Pro] jhjhjhjhjhjh:
i see your on 3.03 i was using 3.02 ..

All in all this is a smooth kernel but the stock kernel has a little bit more performance..

Battery life is the best feature of this kernel..
[Google Pixel 7 Pro] DespairFactor:
stock wouldn't have more performance, there is nothing here to implement further battery savings that would impact performance at all
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Thanks for the clarification.

I saw you updated to 3.04 and I must say thank you for the update as performance is more stable now that my kernel app is sticking on boot..

I finally feel the gpu gain using the gpu policy set to always on.. again appreciate your work..
[Google Pixel 7 Pro] cantthinkofagoodusername:
I recently downgraded my phones Android version to A13 TQ1A. Will the newest version of the kernel work for me, or do i need to get an older version?
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Again O.P appreciate the update..

running version 3.05 on android 14 beta 4.2

smooth kernel:)

This version feels like im running a custom kernel. Whatever you did to this version 3.05 keep doing it.. 😉
[Google Pixel 7 Pro] Pixel86:
Agreed. @DespairFactor , v3.05 is so much smoother and quicker than v3.04 was.
[Google Pixel 7 Pro] pro_granade:
oops
[Google Pixel 7 Pro] DespairFactor:
will work
[Google Pixel 7 Pro] bigknowz:
It's alive! Welcome back.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Kernel running Excellent on August update 3.05..

Ive seen @DespairFactor giving Pixels love since the Nexus days..

Give the O.P his Props...:)
[Google Pixel 7 Pro] IdrisMC:
There is a issue with volume when using Apple USB c to aux. Could you please add this patch to fix it https://github.com/polkaulfield/and...mmit/fd86681a040119610bd54b02c7e152e03f8cff7c
[Google Pixel 7 Pro] doomwithdon:
Where is the 3.05 kernel version for A14? All i see is 3.03 in the A14 folder for pantah
[Google Pixel 7 Pro] Texan1:
3.03 is the latest. You'll need to get used to Despairs awful use of version numbers! 🤪
[Google Pixel 7 Pro] DespairFactor:
Will do with next build
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Thanks for the August update version 3.04 running like butter on A14 Beta 5.1 ..0005

edit

My favorite kernel build so far is v3.05.

I love the fast charge feature. Version 3.04 doesn't have that feature.

So i flashed back version 3.05.. thanks again for this version..
[Google Pixel 7 Pro] Pixel86:
Agreed. The old v3.05 A14 version was the smoothest and best battery life yet.
[Google Pixel 7 Pro] i42o:
So I can flash this on latest LOS android 13 ? 3.05 that is.. thanks in advanced
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
For Android 13, please use one of the files that are outside the folders. For example, if you have a Pixel 7/Pixel 7 Pro Pro then 2.02 and 3.01 which are in pantah root directory are the ones to use.

If you have a Pixel 6/Pixel 6 Pro, for A13, you can use any of the files from 3.05 to 3.11 which are in the raviole root directory.

These files correspond to the current/last month's security update at best. It's any ones best guess if they would work on earlier month's updates. Please don't use the files in the A14 folder for A13. The ones in the A14 folder are specifically for A14.
[Google Pixel 7 Pro] DespairFactor:
feel free to join the telegram channel :) I monitor that more closely, curious which 3.05 this is so I can maybe recreate it :)
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Im not on telegram but i can upload the kernel if u want..
[Google Pixel 7 Pro] DespairFactor:
ah, it won't help, unfortunately. Keep an eye on the folder ;)
[Google Pixel 7 Pro] Pixel86:
It was the v3.05 from like late July.
[Google Pixel 7 Pro] bbender716:
Back in DespairKernel after no custom kernels for like 2 years. Damn it's good to be back. What's the TG channel again?
[Google Pixel 7 Pro] Lughnasadh:
Link is in the OP.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Version 3.03 is the one similar to the july 3.05 version.. Running good as usual..

You rock Despair!!
[Google Pixel 7 Pro] fuzzgruble:
Did the Telegram chat disappear for anyone else too? I saw some messages come through and the notification didn't open the chat.
[Google Pixel 7 Pro] ltth:
Yes!!!
[Google Pixel 7 Pro] cultofluna:
Yep..TG channel disapeard
[Google Pixel 7 Pro] bbender716:
Yeah looks like it says I'm banned lol Rose gone rogue.
[Google Pixel 7 Pro] DespairFactor:
PM and I can add you
[Google Pixel 7 Pro] Fishawy:
Looks like the Telegram group is not open, I never joined so I don't think I'm banned.

Just wanted to ask, now that Sultan figured out a way to flash kernels on our phones without disabling verity and verification, are there plans to implement that on this kernel (if not already)?

I want to test the kernel, and I searched the thread, but OP post still states that disabling them is required.
[Google Pixel 7 Pro] DespairFactor:
no plans to add that
[Google Pixel 7 Pro] fk4mil:
Pixel 7 / a14 qpr1 bootlop with kernel 4.01 :/
[Google Pixel 7 Pro] xflowy:
@DespairFactor Will the kernel be further updated for Android 14 or are you moving to the pixel 8? :/

Also: is there still a telegram group? Somehow I am not a part of it anymore.
[Google Pixel 7 Pro] DespairFactor:
yes there is still a private chat and I will be updating still, I am also working on Pixel 8
[Google Pixel 7 Pro] Octaviastikos:
Hello from Greece how can I put the kernel on the pixel 7 pro?
[Google Pixel 7 Pro] USHERROB:
Read post #1 ?
[Google Pixel 7 Pro] Nekromantik:
Ah ok

if thats the case then will flash over next few days. :)
[Google Pixel 7 Pro] capntrips:
Yes, though I have only managed to get it working with verity AND verification disabled.

I removed all the bits about the ramdisk, dump_boot, and write_boot and added the following in anykernel.sh:

flash_generic boot;
flash_generic vendor_kernel_boot;
flash_generic vendor_dlkm;
flash_generic dtbo;

I have not successfully patched vbmeta to get it working without verity and verification disabled.

Yes and no. Yes, you can flash vbmeta with verity disabled on stock without a wipe, but so far I haven't been able to avoid the wipe when installing the kernel with only verity disabled.
[Google Pixel 7 Pro] DespairFactor:
Let me know when you push your changes and I will update my zips to use the updated AnyKernel
[Google Pixel 7 Pro] Ghisy:
Ditto here! I knew it would come in handy to tinker when both are disabled! We learned from the 6 Pro in that case :)
[Google Pixel 7 Pro] capntrips:
It didn't require any changes to the core of AK3, just anykernel.sh, which already needs to be customized for the specific kernel/device. Attached is the one I used.

Note AK3 prints out the block for init_boot at the beginning, but it is not actually flashing anything to it.
[Google Pixel 7 Pro] Nekromantik:
saw the PR on AK3 Github @DespairFactor posted

is this different then making it work without verification disabled?
[Google Pixel 7 Pro] DespairFactor:
Yeah it's not even needed apparently, what capntrips has done removes any need for what I was attempting to do.

Thanks for the script @capntrips

I have uploaded AK3 versions of 1.02 and 1.03
[Google Pixel 7 Pro] JakeDHS07:
AK3 version of 1.03 results in corruption and unable to boot
[Google Pixel 7 Pro] kkjb:
Yep same thing here. Goes back to recovery loop and need to factory reset. Will disable I guess. Reminds me of pixel 6 early days.

Thank you for the developers efforts.
[Google Pixel 7 Pro] JakeDHS07:
Instead of factory reset I rebooted into bootloader and simply reflashed the magisk'd init_boot and bam back up and running 🤘
[Google Pixel 7 Pro] Gordietm:
That's smart. 👍
[Google Pixel 7 Pro] kkjb:
Excellent news.. was lazy and didn't think to use two hands and buttons for the return to Bootloader. Early morning coffee hadn't kicked in yet.
[Google Pixel 7 Pro] capntrips:
I had the same thing when I tested without disabling verity and verification, though I did trip the eio screen a few times while testing both the AK3 and fastboot methods after disabling them, but it would successfully boot after dismissing it. In the latter case, I was able to clear it with the method below.

Good tip. I was also able to fastboot boot boot.img to clear it.
[Google Pixel 7 Pro] kkjb:
Yeppy, gotter done....flashed fine, coincidence on last cup of coffee? Disable of verity was the ticket...nice working with the safety net module too.

Thank you again all the pioneers and devs.
[Google Pixel 7 Pro] DespairFactor:
Hopefully we can stop this soon for future builds.
[Google Pixel 7 Pro] dmbardal:
Without knowing how to check - does Pixel 7 and Pixel 7 Pro use the same kernel, so it can be flashed or any of the devices?

If not; any chance to see this on the P7 as well?

Love how fast development began on the new Pixel series. Keep it up! :)
[Google Pixel 7 Pro] capntrips:
This works on Pixel 7.
[Google Pixel 7 Pro] JakeDHS07:
As with most pixels yes they use the same kernel. That's why the codenames are merged
[Google Pixel 7 Pro] dmbardal:
Glad to hear it!

Thank you.

Will follow cross forums then.

Edit: Thats why its 'Pantah'. I feel stupid now.
[Google Pixel 7 Pro] Lughnasadh:
I still think Cheeter would have been better 🙃
[Google Pixel 7 Pro] DespairFactor:
I like pantah, it is like Mike Tyson chose the name
[Google Pixel 7 Pro] Lughnasadh:
Haha
[Google Pixel 7 Pro] jac0b:
Is there no telegram chat anymore and I can flash just disabling verity?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Correct, just disable Verity if you flash the AK3 Zip version of the kernel - preferably before, but you can do so after, too.
[Google Pixel 7 Pro] Samuel Holland:
So I can flash AK3 version just disabling verity, w/o wiping? Thank u sincerely.
[Google Pixel 7 Pro] capntrips:
This did not work for me, but ymmv. I was able to flash vbmeta with verity disabled on stock without a wipe, but I wasn't able to avoid the wipe when installing the kernel with only verity disabled.

On a somewhat related note, I was able to pull the ramoops after flashing the kernel without vendor_dlkm (which requires fastbootd, which wipes ramoops) with verity and verification both enabled, and I found the following in the log:

Oddly, the stock kernel does not print this to dmesg despite the same conditions.

I'm going to see about modifying the hash descriptor for init_boot in vbmeta to see if that leads to any further progress.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks, and interesting! Sorry to all who I gave misinformation to.
[Google Pixel 7 Pro] DespairFactor:
This is because vbmeta is used for chained boot between init_boot and boot
[Google Pixel 7 Pro] jac0b:
Didn't work on mine, booted into recovery.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I apologize I gave misinformation. Disabling Verity doesn't normally require a factory reset, butt did far, in combination with this kennel, it does. I don't know if flashing the stock partitions that this kernel replaces and/or re-enabling Verity is enough to get you running again.
[Google Pixel 7 Pro] jac0b:
No problem, now I will have verification and verity disabled. I tried everything before factory resetting.
[Google Pixel 7 Pro] capntrips:
Right, which is why I'm working on patching the hash descriptor for init_boot. What I don't understand is why the stock kernel boots with a modified init_boot with verity enabled, but the custom kernel does not (assuming that line in ramoops is an indicator of the root problem).
[Google Pixel 7 Pro] DespairFactor:
I don't think magisk messes with the init_boots hash, which is why it may work.
[Google Pixel 7 Pro] capntrips:
It doesn't mess with the hash in the vbmeta footer of the init_boot partition, but it does modify the contents of the partition, which will cause its hash to no longer match the one stored in the descriptor, which is why avb prints that message.

You can test this by dumping the partition to a file and running avbtool verify_image on it.
[Google Pixel 7 Pro] feligoni:
Quick question as I come from P 4XL and we didn´t have all this verity stuff. Do I have to disable verity on every OS update or it remains after OTA/flashing firmware zip? Just checking for the future as I'm flashing Despair right now on my just arrive pantah
[Google Pixel 7 Pro] cultofluna:
On every update you have to flash the OS with the verity/verification flags disabled ...

( Installing factory images or via Android flash tool)

No need to wipe...( only the first time that you're disabling verification requires wipe)

Also disabling only verity , it doesn't requires wipe at all..
[Google Pixel 7 Pro] DespairFactor:
I actually just flashed an AK3 zip for the first time this morning, worked flawlessly with no issues. I have verification and verity disabled. I was reading some people got corruption after doing this, but I am not sure if they have the same setup I had.
[Google Pixel 7 Pro] JakeDHS07:
I'm not familiar with the disabling process for those. My previous device I used Freak07 kernel and that wasn't a requirement that I ever dealt with. Just flashed through EXKM and booted. If it ends up that this process is a requirement going forward it's something I'll have to learn and look into.
[Google Pixel 7 Pro] DespairFactor:
It was a requirement at first, @capntrips was able to fix it for all of us on the Pixel 6 devices using hashtree patcher.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, there are two schools of thought on this. I'm in the camp of waiting until hopefully disabling neither Verity or Verification is necessary, since it necessitates a factory reset, plus you have to always remember to disable it/them in the flash-all.bat whenever you use one. Not disabling it doesn't make you do a factory reset, but then disabling it again will.

The other idea is to just always keep disabling both from the get go and forever as a habit, and therefore never running into known problems, and some suspected problems. It is believed, and I can't refute, that not having them disabled may occasionally/randomly cause a corruption issue after flashing a custom kernel.

I only once had a corruption issue on the Pixel 6 Pro, but mine was a mild case. I didn't have to factory reset, but every time I rebooted, the phone would initially halt on a screen saying that something was corrupted, etc, and it wouldn't continue booting until I pressed the power button. I don't remember what all I had tried to fix the problem - I believe I had tried a dirty flash of the factory image including stock unrooted kernel.

When the next month's update came out, I updated and flashed the newest custom kernel, and the issue was gone.

If I remember correctly, later it was discovered that flashing an old boot.img (or new one when there's a new update out) solved the issue. Anyone, please correct me if my memory is faulty.

I don't plan on disabling Verity and/or Verification unless I have to, although it's possible I would if there hasn't been any solution for a few months.

Edit: Freak07's kernel for the Pixel 6/Pro also initially required those to be disabled, until the AK3 process was created and refined.