yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
the updated zip, works on device with disabled vbmeta as well, I just flashed it on my own device.

yes, I´ll upload them shortly and try to update the OP accordingly so nobody gets confused.

first give terminal emulator su privileges by typing "su".

afterwards type "top" and rotate the phone to landscape. alternatively you can do it via adb shell on your pc, which might be more convenient. don´t forgot to give adb shell, su privileges as well.

If it´s generally less snappy, then no I can´t think of anything as I should be affected as well then.
[Google Pixel 6 Pro] Freak07:
double post
[Google Pixel 6 Pro] wolfeyes30:
@kirisakura is this command correct in post #4

fastboot flash vendor_boot vendor_boot boot.img

or is it

fastboot flash vendor_boot vendor_boot.img

thank you
[Google Pixel 6 Pro] Freak07:
Typo

fastboot flash vendor_boot vendor_boot.img

Thanks for catching it! :)
[Google Pixel 6 Pro] jac0b:
With the AK3 module do we still have to have the powerhint module installed also?
[Google Pixel 6 Pro] Freak07:
If you flash the zip follow the instructions in the OP :)

(Flashing the kernel.zip will automatically create the magisk module for the kernel upon flashing (y))
[Google Pixel 6 Pro] bjevers:
No
[Google Pixel 6 Pro] Texan1:
Yikes, I've somehow got myself into a bootloop situation I can't get out of :eek:

Quick summary..

6 Pro, December update (A1), was rooted and running Kirisakura 1.4, all ok.

Australian firmware version A5 was released so I wanted to flash that. Was happy to wipe and start fresh so I performed a factory reset from within Settings and was then going to use Android Flash Tool.

After doing factory reset and getting back into the phone, I went to enable developer options again but Settings would crash every time I tried to click on developer options.

From here I can't recall now the exact steps I took but I did go into Fastboot Mode and tried using ADB commands to flash the A5 factory image, also patched the boot image and flashed with Magisk in case there was an issue there.

Now stuck in bootloop, I can get into Fastboot Mode but not Recovery.

Trying "adb devices" comes up blank.

I've tried running flash-all.bat (both as is and also using the --disable verity etc commands) to flash the factory image but get this:

fastboot update image-raven-sq1d.211205.016.a5.zip
target reported max download size of 261095424 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: slider-1.0-7892371
Baseband Version.....: g5123b-93368-211209-B-7985098
Serial Number........: 1A141FDEE000YX
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (65536 KB)...
OKAY [ 1.417s]
writing 'boot'...
FAILED (remote: partition (boot) not found)
finished. total time: 1.464s

Any and all help appreciated please! 🤞
[Google Pixel 6 Pro] old_fart:
Um, if <vol up><pwr> get you into fastboot, then <vol up> a couple more to see 'recovery' and press <pwr> to select.

.

plz read by most recent struggle with a happy ending . . .

https://xdaforums.com/t/pixel-6-pro-easy-step-by-step-unlock-root.4361847/post-86099355
[Google Pixel 6 Pro] Texan1:
Sorry didn't make that clear, yes I can choose recovery as an option to boot to but it doesn't work, it's just bootloops again 🤬
[Google Pixel 6 Pro] nguyenson91hp:
A quick search come up with this

https://xdaforums.com/t/cant-flash-boot-because-boot-partitions-not-found.4215613/

and this

https://xdaforums.com/t/system-partition-not-found.4221411/

Do you happen to have an older version of adb platform?
[Google Pixel 6 Pro] bason230:
Hello, I've just installed this kernel and it is working fantastically, but I was wondering if there was a recommendation list as to what wakelocks are worth blocking? I see that that was added as a feature to this kernel, but I don't really know what I can or cannot block as far as wakelocks go.
[Google Pixel 6 Pro] nguyenson91hp:
You should have an understanding of what wakelock you want to suppress. It could affect your experience of using the phone (missing notification, tasks unfinished). You could look at, for example, BetterBatteryStats to first see what wakelock is impacting your battery (e.g., keeping your phone awake)...
[Google Pixel 6 Pro] Texan1:
No, I've got the very latest version, downloaded from the Google site.
[Google Pixel 6 Pro] Freak07:
2./3. Don´t to a factory reset when running my kernel. The magisk module is now tied to the kernel. If you factory reset the phone the magisk module will be gone, but my kernel still on the phone. This will cause issues like developer options force closing.

If you flashed the update via android flash tool and afterwards the dev options were force closing, that means the update was not flashed correctly.

4.-7. adb commands do not work in bootloader/fastboot. only fastboot commands.

so "fastboot devices" is the correct command.

From the look of it, it seems you either have outdated platform tools/fastboot binaries or are you maybe in fastbootd when you run the script?

When running the flash-all script you need to be in fastboot/bootloader not fastbootd.

none are worth blocking. I did describe the reason why it´s included in the release post. there´s also an article linked.

from the perspective you´re asking the question, you probably don´t want to block any wakelock :)
[Google Pixel 6 Pro] felek73:
So to get this right: I got this device yesterday so did fresh update with A4 firmware. I disabled verity/verification (I think so , cause after flash it asked me to wipe data because od corrupted data) ,rooted pjone and started to search for custom kernel. I knew Krisakura from previous devices so my choice was obvious :) I downloaded latest zip and flashed using FKM then got in bootloop - google logo appears and then back to fastboot etc. I restored stock img's but I'd like to knon what I did wrong ?
[Google Pixel 6 Pro] cultofluna:
These are worth blocking

EDIT: sorry for wronq quote
[Google Pixel 6 Pro] Texan1:
Yes I did notice after the factory reset that your kernel was still there. The dev options were force closing after the factory reset, I haven't been able to flash a fresh rom since then.

I've definitely been in fastboot mode, not fastbootd, using the power volume down key combo to break the bootloop. From there I'm not sure what to do because when I tried the flash-all.bat command I got that error message I posted previously.

If I have messed up Magisk or the patched boot image or something is there something I can do about that in fastboot to try and progress further?
[Google Pixel 6 Pro] Freak07:
I would not recommend anyone on this kernel blocking the first two or any other wakelocks with the wakelock blocker, except for the situation that´s described in the release post in spoiler tags and the OP.

The wakelock blocker was included solely for this purpose. If there´s a discussion started or recommendations given on what wakelocks to block the function will be removed in the next update as I won´t deal with random issues that are introduced by this.

If you decide to ignore this warning and block wakelocks for any other purpose please don´t report any issues here and understand that I can´t give support.

Thanks for the understanding everybody.

The other two wakelocks (wlan) shown on the screenshot do not exist on this kernel.
[Google Pixel 6 Pro] Freak07:
Restore boot, dtbo, vendor_boot and vendor_dlkm from the firmware you´re currently running. If that gets you back up and running patch boot.img again with latest magisk canary.

The first three images need to be flashed via fastboot, the vendor_dlkm via fastbootd.

I don´t know why flashing the factory image does not work for you, there are only those two possibilities I can think of. Other than that I have no experience with using windows to flash and issues that can occur there.
[Google Pixel 6 Pro] cultofluna:
Blocking first two for at least one month now..

Without any issue
[Google Pixel 6 Pro] Freak07:
That´s fine with me, but please respect what I asked for above.

Just because you don´t notice any issue, doesn´t mean it´s fine to block them for everybody or there won´t be an issue.

spi11 is touchscreen related. there´s no reason to block any of those as they don´t keep the phone awake more than they need to.

blocking both of those wakelocks will not improve idle drain, as they don´t keep the phone awake.
[Google Pixel 6 Pro] felek73:
OK , so I decided to try again. Dirty flashed A4 update from fastboot without setting any verity flags , so I assume these are enabled (don't know how to check it) . Downloaded from github newest magisk 92546e8a(23016) and patched boot.img. Gained root and tried to flash kernel via FKM, flasjed without erroes. And then bootloop again...ROM starts , G logo apperas and goes to boot again .. What maybe the reason ? Logs would be helpful ?
[Google Pixel 6 Pro] DanielF50:
Did you try downloading the kernel zip again, the download might be corrupt?

You could also try extracting the zip and flashing the images manually (make sure to also download boot.img / powerhint module from AFH link in OP) after restoring the original files.
[Google Pixel 6 Pro] felek73:
I downloaded it at least 3 times.. Flashing manully seems like good idea , thanks.. will try this later today ..

EDIT: didn't help. I have flashed powerhint magisk module and rebooted.

Went to fastboot and flashed 3 partition in bootloader and 1 in fastbootd.. It didn't get into bootloop but instead hangs on G logo .. restored stock partition .. I'm cursed ;)
[Google Pixel 6 Pro] Texan1:
@Freak07 you legend, thank you, that worked, I'm out of bootloop and back up and running! 🙏 🙏

Enjoy the couple of beers/coffees I sent your way 🍻 :coffee: (y)
[Google Pixel 6 Pro] DanielF50:
Sounds it 🤣

I had a similar issue. Dirty flashing December build allowed me to get into recovery mode (but not boot), so I used recovery mode to sideload the December build again, then I reset the phone completely, flashed magisk, booted, flashed kernel and it worked, maybe you can try that?

Also, when flashing manually, did you patch the kernel boot.img with Magisk before flashing it? Obviously it isn't pre-patched when you download 👍

edit: also, if you're stuck on the "G" logo, try holding down "vol down" when it appears, it should boot to safe mode?
[Google Pixel 6 Pro] felek73:
Thanks for hint , will try if I another kernel well also pain with my current setup

Edit : so it's the same with another kernel so my config must be a culprit.

Btw.. Instruction in OP says:

2a. Don´t forget to flash the provided boot.img in magisk manager prior to flashing it via fastboot

What does it mean "flash boot.img in magisk manager"?
[Google Pixel 6 Pro] roirraW "edor" ehT:
It means:

In the Magisk app, beside "Magisk", click "Install".

Then click "Select and Patch a File".

Find and click the particular boot.img (or other filename for a kernel) that you have a copy of on your internal phone storage which you want to have provide root access.

Click "Let's Go"

This "roots" the kernel you selected (CleanSlate, in this example). When you flash the kernel, flash this new rooted copy. I always rename the Magisk'ed kernels to reflect what they're a Magisk'ed version of.
[Google Pixel 6 Pro] ajent:
Thank you for creating this.

I was having a hell of a time getting my Sprint (T-mobile TNX) esim Pixel 6 pro to hotspot properly.

Finally got it working. Rooted & flashed your magnificent kernel. Added "Dun" to Tmobile APN. This allows the hotspot to enable but anything that connects has no internet. The fix was to change the TTL. I added this to the script section of EX Kernel Manager:

iptables -t mangle -I POSTROUTING -j TTL --ttl-set 64
ip6tables -t mangle -I POSTROUTING -j HL --hl-set 64

The key for me was the ip6 tables since Tmo 5g uses only ipv6 and I'm in a 5G area.

Hope it helps
[Google Pixel 6 Pro] Vio281:
interesting, how the hell did you even figure that out...
[Google Pixel 6 Pro] ajent:
it has been a hell of a process, between multiple phones and apps :ROFLMAO:
[Google Pixel 6 Pro] foobar66:
I'm trying the custom kernels. One thing I noticed, also with this kernel, using "adb shell dumpsys battery"

Google kernel:

Max charging current: 500000

Kirisakura kernel:

Max charging current: 100000

As a result, I can barely get any charging when phone is connected to USB/PC.

Any clue where this difference is coming from?

This is the sysfs entry:

/sys/devices/platform/10d50000.hsi2c/i2c-6/i2c-max77759tcpc/power_supply/usb/current_max

I'm guessing there's a kernel config variable/setting for it? But I'm not sure.
[Google Pixel 6 Pro] Freak07:
charging driver is stock, so no idea why there´s a difference. Didn´t modify anything there.

I just plugged into my usb with normal usb connection and got

Max charging current: 100000

while on stock it´s indeed

Max charging current: 500000

so the same as you.

No idea where the difference is coming from. I suppose maybe a linux-stable update, changed how the PC is detected upon connection, unrelated to the charging driver. If I find enough time I´ll try to see if I can pin anything down.

Which other kernels show this behaviour as well?

Then I plugged into Google charger and got:

Max charging current: 2200000

So it seems the charger works fine. :)
[Google Pixel 6 Pro] foobar66:
I tried the RadioActiver kernel yesterday and posted same in that thread.

It don't have a Google charger, tried with a OnePlus and I get (obviously) a higher value there:

Max charging current: 1200000

Anyway, on the USB/PC port, when the value is only 100000, the phone barely charges ...

It is possible to write to /sys/devices/platform/10d50000.hsi2c/i2c-6/i2c-max77759tcpc/power_supply/usb/current_max (after chmod +w), so I'll try that on your kernel with the Google value of 500000.
[Google Pixel 6 Pro] Freak07:
Hm radioactive kernel is very close to stock, modifying nothing I can see changing behaviour there. Since the same issue happens there, i currently have no idea what could cause it.

I'll think about it a bit more and maybe I'll get to the bottom of this.

You should be able to write to this sysfs node yes.
[Google Pixel 6 Pro] foobar66:
Just for info. If I increase:

echo 500000 > /sys/devices/platform/10d50000.hsi2c/i2c-6/i2c-max77759tcpc/power_supply/usb/current_max

Then - obviously - charging happens faster (voltage also increases).

However, when unplugging and replugging on USB port then the value is RESET to 100000.
[Google Pixel 6 Pro] Maverick Jester:
KCAL only works on Snapdragon devices.
[Google Pixel 6 Pro] Ghisy:
Oh I didn't know that. So I guess there's no way to control the display colors on the Tensor chip so far?
[Google Pixel 6 Pro] Freak07:
So far not. But I'm very pleased with the display so there's little to no reason or motivation for me to look into it. I'd also recommend to take a look at this post:

https://xdaforums.com/t/kernel-16-1...pixel-6-pro-aka-raviole.4358435/post-85906969

Also at this post:

https://xdaforums.com/t/kernel-16-1...pixel-6-pro-aka-raviole.4358435/post-85917565

Maybe it helps :)
[Google Pixel 6 Pro] Ghisy:
Alright, thanks.

I always like being able to tinker with my display, just in case. So hopefully, down the road, we'll be able to do that. Don't know if that Color Changer app works on Android 12 and/or Tensor. I'll check it out eventually.
[Google Pixel 6 Pro] DanielF50:
Me too, this is the first Google phone I've bought that is actually colour correct.

My Nexus 5, 6P & 3A XL were all badly binned screens, all had weird colour tints & needed to be corrected (not very successfully, unfortunately) with kcal, but the 6 Pro's screen actually matches my calibrated monitor near enough perfectly. I even compared my phone to a few friends 6 Pros & all the screens seem to be consistent in terms of accuracy, which I love.
[Google Pixel 6 Pro] Freak07:
Check the thread from cf lumen if you like to tinker, it offers more options than kcal. It's mentioned by @Chainfire that cf lumen is superior to kcal, also how the content of the display is processed.

Once you have a nice setup adjusted to your likings, sundown and sleep mode specifically, it's pretty awesome.

Used that on several phones, but on the p6 pro I'm also very content with stock night mode and extra dim QS tile.

In cf lumen if you set RGB levels all lower than 1, you can make your display dimmer than it is on lowest possible stock setting, if that's something you like to do.
[Google Pixel 6 Pro] Ghisy:
Thanks, I didn't know about cf lumen, its options look interesting!
[Google Pixel 6 Pro] Reechings:
So I just got my phone yesterday and was able to use the updated magisk so I didn't have to disable verity or anything. Now that I'm up and running and rooted and everything I can use FKM to flash the updated kernel zip obviously and should be good to go? But it sounds like if I want to change kernels or go back to stock, I still have to restore all four of those image files and can't just do a backup using FKM right? Also does this kernel support high brightness mod?
[Google Pixel 6 Pro] Freak07:
Correct, to get back to stock flash all four images from the matching factory image as mentioned in the faq. Fkm only backs up boot if I'm not mistaken.

High brightness mode has nothing to do with the kernel. If rooted you'll see it in exkm as an option. But if in sunlight it will be triggered automatically if adaptive brightness is used.
[Google Pixel 6 Pro] Reechings:
Oh good to know, HBM does work through EXKM app manually but it seems that FKM quick setting tile does not.
[Google Pixel 6 Pro] Freak07:
Then it's up to fkm to update the sysfs path for hbm. (y)
[Google Pixel 6 Pro] Lughnasadh:
High Brightness Mode app by flar2 has a HBM QS tile that works.

Sorry for the off topic. Just wanted to let them know that.
[Google Pixel 6 Pro] Reechings:
Forgot about that app. Worked perfectly, thanks!
[Google Pixel 6 Pro] Reechings:
Does this kernel support dt2w?
[Google Pixel 6 Pro] Lughnasadh:
https://xdaforums.com/t/kernel-16-1...-pro-aka-raviole.4358435/page-9#post-85976045
[Google Pixel 6 Pro] Reechings:
Sorry should have searched first. This single tap and always on FOD is a little bit of a pain but not this kernels fault.
[Google Pixel 6 Pro] Reechings:
Sorry for another question, but I was wondering if there's any way to add finer controls for vibration through EXKM, etc. Thanks!
[Google Pixel 6 Pro] Freak07:
That's available in the CleanSlate config app. Check the CleanSlate thread for a download link
[Google Pixel 6 Pro] felek73:
I had also a problem with charging using powerbank. I connected phone to powerbank at 30% of battery and wake up with 30%of battery. It seemed in battery history like phone was trying to hold the same level of battery. In battery settings it showed : conected ,not charging. Returned to stock kernel and all is good
[Google Pixel 6 Pro] Freak07:
Thanks for the report. I don't use power-banks so I wouldn't notice.

As previously mentioned the charging driver is stock, so no idea what's going wrong there. If I find time I'll look into it.
[Google Pixel 6 Pro] Israafil:
Do you know if there will be an option in the near future to enable hbm mode in cleanslate with pixel 6/pro devices??
[Google Pixel 6 Pro] roirraW "edor" ehT:
You already can https://play.google.com/store/apps/details?id=flar2.hbmwidget
[Google Pixel 6 Pro] jal3223:
Yeah, the 6 Pro's display is great. Unfortunately, the regular six does have tint issues that would benefit from tweaking. I'll definitely check out the app you linked, but hopefully you can figure out an alternative to kcal.
[Google Pixel 6 Pro] swieder711:
I am trying to get more Charging current delivered to my P6P via my wireless car charger. I am using ACC/AccA to set the Max_Voltage to an arbitrarily high number.

The readme file for ACC states the following:

Custom Max Charging Voltage And Current Limits​

Unfortunately, not all kernels support these features. While custom current limits are supported by most (at least to some degree), voltage tweaking support is exceptionally rare.

That said, the existence of potential voltage/current control file doesn't necessarily mean these are writable* or the features, supported.

* Root is not enough. Kernel level permissions forbid write access to certain interfaces.

Sometimes, restoring the default current may not work without a system reboot. A workaround is setting the default max current value or any arbitrary high number (e.g., 9000 mA). Don't worry about frying things. The phone will only draw the max it can take.

Is there anything in the Kirisakura kernel that would hinder or help getting high charging rates?

ACC worked on my Pixel 3XL, but does not seem to work on my Pixel 6P.
[Google Pixel 6 Pro] TotallyAnxious:
You should also ask in the TG group for ACC, it's very active.

Me doing so is how the 1+ 7 Pro Kiri kernel got support of disabling charging and running off external power. Because someone there responded. I can't remember the actual name of the feature.
[Google Pixel 6 Pro] Tomatot-:
With Proton 12.2 (based on December update), I can report kiri 1.4 works great!
[Google Pixel 6 Pro] cd993:
Could you please provide a link or details to this?

I've donated via patron before but can only see the November release....

It's ok sorry, I found it....
[Google Pixel 6 Pro] Tomatot-:
This is not the place to ask but here you go: https://kdrag0n.dev/patreon

You need to donate every month and then you can log in and get the files.
[Google Pixel 6 Pro] DanielF50:
Unsure if this is Kernel related or not so sorry if OT, but I should be able to switch active slots & boot, no?

I just noticed that my B partition is unbootable - set B to active & dirty flashed December build to just that slot and still can't boot (reboots at Google logo, before G logo).

Edit: it's genuinely absolutely gone, no way to boot from partition B - even after multiple full wipes, flashing both Nov/Dec builds, sideloading Nov/Dec build & even dd'ing the "A” partitions to "B" partitions just incase they're corrupt, it still loops.

Unsure where to go from here, is there a way to reformat the partitions using fastboot? Fastboot <format:filesystem> <partition> doesn't seem to work at all on the P6 Pro 🙄
[Google Pixel 6 Pro] foobar66:
Actually I realize that my original post was incorrect. There are 2 cases:

a) boot phone with phone connected to USB/PC

google: max current: 500000

kirisakura: max current: 100000

b) unplug USB and replug

now both kernels have the same value: max current: 1500000

I was confused in my original post, since I was running google kernel (current: 1500000), flashed kirisakura from EX, checked again (current: 100000) - hence the very big difference.

However then unplugging and replugging USB -> current: 1500000

So it is scenario (a) which has a small difference.
[Google Pixel 6 Pro] yujinloh:
In android flash tool , there's an option to "force flash all partitions" that may help.

Backup your data before doing any flashing though.
[Google Pixel 6 Pro] manueltimz:
My screen time out is set to 15 seconds however it is not turning off after the 15 sec.

Screen attention feature has been turned OFF

Is this a kernel issue?

P6P
[Google Pixel 6 Pro] DanielF50:
Thanks - I thought it had, but upon further inspection it's just moved the issue to partiton A. I'll try to use the force command manually and flash both partitions at the same time.
[Google Pixel 6 Pro] Utini:
Reboot fixed it for me. Encountered the same issue today.
[Google Pixel 6 Pro] Freak07:
It's not kernel related. Generally switching slots manually is a bad idea as it might cause issues.

I guess successfully flashing factory image with -w should fix whatever slot is unbootable.

Works fine on my end. Don't think the kernel would have an impact there. That's Framework related, not kernel.

Thanks for the report. that might prove helpful when I find time to debug and look closer at this issue. Appreciate the report! :)