yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Reechings:
Just flashed your kernel on Raven, so far so good but was just wondering if I should have vibration control showing up in EXKM or not? Thanks!
[Google Pixel 6] wolfeyes30:
Not yet implemented. I believe that's a feature in the works to come posted by eng.stk. Someone correct me if I'm wrong.
[Google Pixel 6] meljohnsony2k:
Got a bootloop on raven dec build. Is this just me?
[Google Pixel 6] vandyman:
Working good for me on my P6 Oriole.
[Google Pixel 6] wolfeyes30:
Did you have stock kernel prior or a different custom kernel?
[Google Pixel 6] meljohnsony2k:
Was stock. Sorry if I sound rude but are raven and oriole builds supposed to be the same?
[Google Pixel 6] wolfeyes30:
blu_spark works on both phones. I have the Raven as well and blu_spark works great.

What did you use to flash the kernel zip?
[Google Pixel 6] Vio281:
have to be on stock kernel or prior Blu_spark
[Google Pixel 6] wolfeyes30:
Also stock vendor_boot.img and vendor_dlkm.img.
[Google Pixel 6] meljohnsony2k:
FKM. Must be something on my end then sorry
[Google Pixel 6] Kenaz Rune:
Given all the glowing reviews from users of past devices, I'd love to install this.

Unfortunately, during installation, I receive a Busybox failure. I'm using SmartPack KM and I have the newest Magisk installed with systemless Busybox. Do I need to install Busybox through the Busybox installer for this to work?
[Google Pixel 6] ne0ns4l4m4nder:
Just wanted to inform everyone, this kernel is working great on ProtonAOSP
[Google Pixel 6] phaino00:
Not to hijack this thread. Did you install it on ProtonAOSP with exkm or FKM?
[Google Pixel 6] ne0ns4l4m4nder:
Fkm
[Google Pixel 6] Vio281:
wonder why proton didnt advertise his rom on XDA
[Google Pixel 6] dubt17:
Another ProtonAOSP and BluSpark user. It's the perfect combo. I've never experienced a phone this quick 🤠
[Google Pixel 6] misterk267:
I'm having the same problem as meljohnsony2k, except on oriole. Came from stock rooted with latest Magick canary, flashed through fkm. I've scoured the instructions and thread to see if I missed anything, but haven't seen anything. Guess I'll restore and see if there are any updates later on.

Edit: tried again from fresh restore and got it working!
[Google Pixel 6] phaino00:
I jumped on this bandwagon with blu_spark on ProtonAOSP, I couldn't be happier. Kudos! 😎
[Google Pixel 6] eng.stk:
@kdrag0n does an excelent job indeed 👍
[Google Pixel 6] norman00037:
Is the ProtonAOSP more stable than Stock rom sir?
[Google Pixel 6] phaino00:
It is very stable, at least from my experience.
[Google Pixel 6] dr460nf1r3:
Is there a chance to get DriveDroid patches in this kernel? Super convenient for running isos on the go :)
[Google Pixel 6] eng.stk:
Support for isos and luns with cdrom support should be already in kernel.

That stuff kinda fade away, development seems to be left in earlier kernel and android versions back.

Since quite some time I prefer stuff like ventoy in USB for my ISO needs
[Google Pixel 6] bench95:
@eng.stk - can you please advise how to build the project? are you compile it directly from makefile without build/build.sh?
[Google Pixel 6] Hecke92:
So glad to see @eng.stk here. I loved his work for my OnePlus 3.

Can somebody instruct me on how to install Magisk with this kernel? I think Magisk wants to be installed to a boot.img that i don't get here, i am confused 🤔 thanks :)
[Google Pixel 6] phaino00:
This is a great source:

https://xdaforums.com/t/guide-root-pixel-6-with-magisk.4356233/post-85877931
[Google Pixel 6] Kenaz Rune:
Is there nobody here who can help me out? I really don't want to resort to a paid application possibly only to find it doesn't work for me. Since TWRP does not exist for this yet, and the KM I am using fails with a busybox error right after extracting the archive, I'm at a loss here.

Can this be flashed from fastboot? Side-loaded?
[Google Pixel 6] docnok63:
What does "Tentative fix to external DAC use" mean? Are you talking about making DACs work in Exclusive Mode ala USB Audio Player Pro/Tidal/HiBy? Can you please link the specific commit that possibly fixes it?
[Google Pixel 6] eng.stk:
I already asked people to test and provide feedback. Did you?
[Google Pixel 6] docnok63:
I'd love to know what I'm testing BEFORE I install software on my device. DACs work on the 6 series as long as you don't put them in Exclusive Mode aka BitPerfect Mode aka bypassing Android's Sample Rate Conversion (SRC.) Do you think you've found a fix for this or not?
[Google Pixel 6] efel266:
Hello,

Like many people, I have problems with the battery on my Pixel 6.

10% lost in a night in airplane mode and about 20% if not in airplane !

Do you think flashing blu_spark kernel may improve things ?
[Google Pixel 6] phaino00:
It could. However, it seems there is something rogue going on. I rarely lose more than 3% overnight (approximately 9 hrs), whether stock or blu_spark.
[Google Pixel 6] efel266:
Thank you for your answer, I will test.

It seems this problem is known by Google :

Pixel 6 pro drains battery on standby. Roughly 15% over 8 hours - Google Pixel Community
[Google Pixel 6] Dillonjaf:
I would like to add that I have also just successfully installed this kernel on ProtonAOSP via FKM.

So far it is an immediate improvement, though I may have more to add after a while of use.

Also, how would I go about mounting CIFS or NFS shares under android?

Thanks for the great work

Cheers
[Google Pixel 6] bobby janow:
So you just used FKM to flash the zip and it worked? Are you rooted? I ask because I'm not rooted but I'm running ProtonAOSP latest. I tried CleanSlate and I bootlooped and don't want to go thru that again. Thanks.

edit: NVM, FKM requires root.
[Google Pixel 6] bobby janow:
He said he didn't have time to maintain a thread at XDA and to send people to his TG channel. Then the mods closed it.

@phaino00 Are you rooted with Proton? I'd love to install this but I don't root.
[Google Pixel 6] phaino00:
I am rooted. Changing font (probably the only person that uses ChinaCat font) and V4A are musts for me. I'm also liking the Repainter theming app. ProtonAOSP with blu_spark is rock steady for me. I'm thinking of flashing stock December to try out Renovate Ice tweaks, but my set up is pretty good right now. 😎
[Google Pixel 6] bobby janow:
Do you know if root is necessary? That's the big question for me. If it boots then I can mess with everything else.
[Google Pixel 6] phaino00:
I do not believe you need root. Just install with EXKM or FKM app.
[Google Pixel 6] bobby janow:
Both the kernel managers require root. Darn. I'd have to flash manually or root..
[Google Pixel 6] phaino00:
I forgot that. Hmmm...
[Google Pixel 6] nguyenson91hp:
I am rooted with Proton, LSposed (for an app to modify the default power menu), Repainter, Button Remapper, BBS, AppOps, AdAway, FKM (listed so anyone can discuss experience). I have tried blu_spark and it has been great so far (several days). Everything is up and running, including Gpay. Better battery life than stock for sure. For me AdAway root is a must.

How did you manage to change font? I have looked around but not sure any will work on Proton AOSP.

Another thing is maximum CPU frequency, how could it be managed/changed? I have not been on xda for awhile (years) and might missed something...

I have rooted on AOSP and it is quite fuss-free... I have considered non-root too, but then many things I want to change would be restricted. And for that I would buy an iPhone lol.
[Google Pixel 6] phaino00:
I use Font Manager magisk module from Androidacy.
[Google Pixel 6] sunnybwoy1:
Just flashed this on proton since I'm hearing all the good news & everything is working great so far & seems solid can't wait to see what the future brings
[Google Pixel 6] Dillonjaf:
Yes, that's how it usually goes. At least until TWRP becomes available for Pixel 6.

I would honestly recommend you just root your device with magisk. It's relatively straight forward and risk free.

I haven't rooted a device since 2015 but I definitely will be from now on.
[Google Pixel 6] bobby janow:
Thanks, I just might do that. Some reading to do tomorrow for sure. I don't know why it seems so convoluted to me, I've rooted multiple of times on multiple devices but.. big but here.. not since the 5X. Way different now. I'll look into it for sure.
[Google Pixel 6] nguyenson91hp:
It worked great. Thank you.
[Google Pixel 6] bobby janow:
@Dillonjaf @phaino00 @nguyenson91hp Ok, gonna call it a night but I installed magisk, patched the boot.img for the Proton rom and have it ready to fastboot for root (hopefully)

Then I can presumably use FKM to flash BlueSpark right on top of root? I see the roms have their own boot.img like CleanSlate so flashing those will not screw things up?
[Google Pixel 6] nguyenson91hp:
@bobby janow Yes. I have done exactly that and it worked. I could not say for CleanSlate, but for blu_spark its fine.

When you flash with FKM (importing the link to the json then choose "flash"), it will be like in the screenshot. I guess it patch the kernel file automatically for Magisk.
[Google Pixel 6] phaino00:
Question 1, yes.

Question 2, no. However, if you want to change from blu_spark to Clean slate, do not forget to go back to stock boot image before changing. You can do this by reflashing rom.
[Google Pixel 6] bobby janow:
Ok I'm rooted. Can't pass SafetyNet though. I must be missing something.
[Google Pixel 6] phaino00:
Do you have Universal Safety Net module installed and Zygisk enabled in magisk?
[Google Pixel 6] bobby janow:
No I don't. I set up a deny list but I can turn that off as you have. I downloaded the fix (it's a zip) do I just install the zip file from storage under modules?

edit: installed and now passed. Final question, I think, after I install this kernel do I need the fix again or will it hold?
[Google Pixel 6] phaino00:
You should be all good.👍
[Google Pixel 6] bobby janow:
I knew I'd have more questions.. can I turn off the deny list if I don't need it?

edit: It's not needed.
[Google Pixel 6] nguyenson91hp:
It got pretty interesting. But I thought Proton AOSP pass Safetynet by default? I didn't even have Safetynet fix module in Magisk and I passed YASNAC just fine. Am I missing smt?
[Google Pixel 6] phaino00:
I believe it passes SafetyNet until you patch the boot image to root, then you need SafetyNet fix.
[Google Pixel 6] bobby janow:
You guys have been great, thanks for walking me thru this process. Rooted now, passing SN, kernel installed.

Any tweaks to the kernel you made or just run as is? Thanks again.
[Google Pixel 6] phaino00:
Running as designed by @eng.stk.
[Google Pixel 6] bobby janow:
And now the be all and end all of final questions. (yeah right) Now that I have BS kernel installed, I'm rooted.. can I unroot? I'm having a dog awful time with GP and my banking app. With simple unlock it worked fine. If there is no way I'll have to unroot and reflash Proton which is no biggie either.
[Google Pixel 6] phaino00:
I'm not entirely certain about that to be completely honest. I don't use gp and chase bank app works to an extent, e.g., check balances, quick pay and transfer btwn accts, but cannot read secure messages. Wish I could be more help. 😎
[Google Pixel 6] nguyenson91hp:
You can simply unroot by using the Proton web flash tool. Do the very same process, but instead of "clean flash", choose "update", it will reflash the system file, keeping your data, but unroot.

What happen with your GP and bank app? Did you include them into the Magisk deny list? Mine is like this

Could you check Gpay's contactless payment option to see their check list?

Are all the boxes ticked? If yes, you could try clear all data of Google Pay and Google Play Services then try to set it up again. That worked for me.

In any case you think you messed the system up, just reflash the rom as I said, you will begin again with no root, but data and apps are all there
[Google Pixel 6] eng.stk:
blu_spark_r45 (A12)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.

You can use FKM download kernel feature, just import the link bellow in the app flash section.

FKM download config: HERE

Changelog:

Keep in mind: I will give no active support for custom ROMs (including stock based ones).

I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).

No mirrors please

Don't forget to hit thanks, it's free :)
[Google Pixel 6] sakerhetz:
Can I use the spark kernel op the January 2022 update or is it better to wait for an update??
[Google Pixel 6] Lughnasadh:
The changelog in the post you quoted states January has been merged, so yes, you can use it on the January update.
[Google Pixel 6] phaino00:
Thanks for quick update. Installed flawlessly. 😎
[Google Pixel 6] Vio281:
went from despair kernel back to this, I'm convinced I'll stay with this kernel for a bit! awesome update.
[Google Pixel 6] eng.stk:
Awesome, enjoy guys.

Seems like google also fixed most stuff on this OTA ROM wise 🥳
[Google Pixel 6] finshan:
Does this kernel allow screen color calibration?
[Google Pixel 6] c19932:
hey guys I really need some help here

I recently installed the Jan update on my pixel 6, rooted with magisk. I then installed this kernel through FKM. Now I can't get my pixel 6 to boot. When I restart, it tells me my device is corrupt. I press power to continue, and it still gets stuck at the "google" splashscreen. I can't even access recovery.

I really don't feel like wiping and reinstalling every app. If anyone has any idea how to boot again please let me know.

I tried reflashing a factory image, but when it gets to "system", it tells me system partition not found.

EDIT: it seems like flashing this kernel via FKM on Jan build will mess up the partitions.

On my active slot, system partition can't be find.

On my inactive slot, system partition is too small to "fastboot flash system"

I don't even know how to unbrick my pixel 6 at this point
[Google Pixel 6] bobbarker2:
Flashing the kernel did not mess up your system partitions, you must have done something out of order or wrong.

What are the step by step procedures you took? Are you on Magisk Canary?

To get your device booting again follow the instructions in OP about returning to stock.
[Google Pixel 6] Dillonjaf:
Are CIFS and NFS modules not yet included with the kernel?

Not sure how I would check

Cheers
[Google Pixel 6] eng.stk:
Nope not yet. Will try to remember for the next build :cool:
[Google Pixel 6] Hecke92:
Did you find a solution mate?
[Google Pixel 6] bobbarker2:
@nguyenson91hp Your attachment shows checking off Google Play Services components in the Zygisk denylist. However USNF removes Google Play Services from the denylist automatically.

magisk: Remove Play Services from DenyList earlier · kdrag0n/safetynet-fix@bc27f22

This ensures that GMS will never start before it's removed from the DenyList, even if another module's service.sh is blocking our script. Suggested-by: osm0sis <osm0sis@outlook.com>

github.com

You'll notice on reboot that GPS in the denylist if you have USNF installed.
[Google Pixel 6] bobbarker2:
Haptic Feedback control/strength? :D I was using my Pixel 4a for a bit and was really surprised by how much weaker the Haptic Feedback is on the 6 by default.

Btw I think its funny how everyone still says " hit Thanks on my post" but its "Like" now, since XDA changed their forums a while ago.

Edit: Weird, I flashed the kernel in FKKM and now it will only go to Fastboot with "Enter reason: boot failure". I saw FKKM patch vendor_boot and vendor_dklm. Now I have to "return to stock" and flash the magisk patched boot.img again.

I updated to January by downloading the entire update and doing a flash-all.bat without the -w flag.

I booted once into stock then rebooted to fastboot and did a fastboot flash boot magisk_patched_boot.img. Everything was working fine, root achieved and safetynet passing. Went into FKKM, downloaded the latest version of the kernel and flashed it/rebooted. Now I'm stuck in Fastboot mode.

Did I miss a step? I've always updated like this in the past.
[Google Pixel 6] eng.stk:
Eventually, I'm actually quite satisfied with the 3 levels provided by userspace, so it's not urgent for me.

I like the 4a a lot, hated the haptics. It's like an earthquake no matter what is signaling, absolute garbage.

Well most of us maybe don't care about the social networking crap every service try to inject on people.

Maybe that's why people leech on the goods but forget to hit the button nowadays...
[Google Pixel 6] bobbarker2:
Bah now I have that "your device is corrupt" crap. Trying to get into fastbootd to flash vendor_dlkm.img. Is there a way to do that from fastboot?

Edit: Nevermind, just did flash-all.bat again. But now everytime I reboot my phone I get the "your device is corrupt" message. I just hit the power button and it boots fine. Though its odd, why can't I flash the kernel? I'm on Magisk Canary, modules disabled, using the same tools as everyone else. And what is causing the "your device is corrupt" message, even though it isn't.. rooted and passing safetynet.
[Google Pixel 6] eng.stk:
Oriole or Raven?

That seems like messed up verify stuff, maybe something you flashed in between?

Did you always use canary 23016 to patch you stuff? Other zip namely if using anykernel3, must use the version that has magisk tools from 23016

Did you verify the kernel zip and does it indeed flash all the partitions (logs?)

Unless you solve that on stock rooted first, flashing this kernel will not make any difference.
[Google Pixel 6] cultofluna:
Run flash all bat again ...and add --disable-verity --disable verification to the fastboot update line.

Example:

fastboot --disable-verity --disable-verification update image-oriole -xxxxxxxxxxxx.zip
[Google Pixel 6] bobbarker2:
@cultofluna Oh I thought the new Magisk Canary allowed to skip those arguments. I'll give it a try now, thanks.

@eng.stk I'm on Oriole.

I was on November build rooted, safetynet passing with no corrupt device message prior to updating to January. I then updated to January and flashed stock rooted boot.img and no device corrupt message.

I only had a problem when I used FKKM to flash your kernel. I'm sure it's some weird quirk on my device. I do have FKKM logs if those are helpful.

Archive: /data/data/com.franco.kernel/files/blu_spark_r29-pxl6_eeba43b91.zip - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

And just fyi Magisk Canary updated.
[Google Pixel 6] eng.stk:
Skipping Dec build may have soemthing to do with that maybe, who knows.

There must be something particular triggering those verity issues some of you guys encountered.

I flash lot's and lot's of zips and never had anything similar. And most people are ok also.

Did you have any Magisk module installed previously, custom ROMs mods etc?
[Google Pixel 6] bobbarker2:
Stock rom, no mods, disabled all magisk modules prior to flashing. I don't think skipping Dec had anything to do with it since a lot of people skipped it due to the issues it caused. And I've had problems flashing the kernel prior to this.. when I was on the November version, I tried flashing the kernel with FKKM and EKM and my phone would only boot to fastboot. So I just ran stock rooted.

Haven't had any "corrupt" problems until now.

It's hard to keep up with what to do/what not to do when tinkering with this device since there are so many people with different results doing the same operations.
[Google Pixel 6] bobbarker2:
Edit: Nevermind, I must of had an extra space the cmdline didn't like.

Edit2: Now it won't boot. It goes into Android Recovery and gives me the options to Try Again or Factory Wipe. Great.
[Google Pixel 6] cultofluna:
Yea .

I forgot to mention that first time disabling verity will require wipe ..😁😁
[Google Pixel 6] Galaxea:
I had the same issue when flashing the DEC patch. I had to sideload the OTA to fix it then root again with Magisk by booting the rooted image.
[Google Pixel 6] bobbarker2:
So you did a sideload of the OTA and did a fastboot boot Magisk_boot.img and flashed the kernel then?

Thanks 😋. Fortunately it somehow flashed to the inactive slot so I was able to switch active slots and not factory reset.

But according to root guide (and Magisk git) since 23016 we no longer need to disable verity/verification.
[Google Pixel 6] cultofluna:
Only if you're using magisk..you should not have a problem..

If you try i flash a custom img ..you will....

Im disabling verity in every update...so i can mess around without any issue...
[Google Pixel 6] Gordietm:
Has anyone flashed this kernel on the 6 Pro?
[Google Pixel 6] Galaxea:
yes
[Google Pixel 6] bobbarker2:
@cultofluna ...Huh?
[Google Pixel 6] Hecke92:
Yes
[Google Pixel 6] ccsoccer23:
Anyone know if a custom kernel could potentially fix a software bug on the Pixel 6 devices? More specifically this bug:

https://www.reddit.com/r/GooglePixel/comments/qzymhd
-- And a little gif of it --

If anyone here who already has this kernel installed on their Pixel 6, see if they are able to reproduce this?

Or is it possible a custom kernel will not fix anything and I have to go with a custom ROM?
[Google Pixel 6] bobbarker2:
I reproduced the issue on stock. It's hard to notice unless you're specifically looking for it. And it is no where near 0.5s, more like 50ms.

A similar bug was found on Samsung devices when they updated to 12. It was caused by the frame rate switching between 120hz and 60hz when the user is touching/not touching the screen.

While the symptom of the bug is the same, the cause is different. If you enable Display Frame Rate you can see the refresh rate stays at 90Hz even when not touching the screen or while dragging. And the freeze is nowhere near 0.5s.

Considering the Tensor chipset is Exynos + some customization by Google, you'd think Google would have included the patch to fix the issue.

The kernel won't fix your issue unless the bug has a specific patch that can be merged into the kernel.
[Google Pixel 6] ccsoccer23:
It's very noticeable when playing a first person shooter like PUBG Mobile and you're slowly swiping back and forth trying to position your crosshairs on an enemy and the crosshairs just stop moving or they skip over the very spot you were trying to point at.

Thanks for the info. It's very unfortunate, I've reported this bug after every update, but nothing back from Google. And reaching out to Google support just leads to them trying to send me a replacement phone and ensuring me that it will fix the issue. Can't even return the phone now.
[Google Pixel 6] bobbarker2:
Do not get a replacement phone. You will be getting a refurbished device and it will be luck of the draw if that replacement has actual hardware issues.

Besides it's a software issue, not hardware.
[Google Pixel 6] Slim2none4u:
Is this kernel working with the february update?
[Google Pixel 6] c19932:
how did you manage to fix it from there? thanks for sharing
[Google Pixel 6] eng.stk:
blu_spark_r49 (A12)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.

You can use FKM download kernel feature, just import the link bellow in the app flash section.

FKM download config: HERE

Changelog:

Keep in mind: I will give no active support for custom ROMs (including stock based ones).

I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 6] krotin:
Hi @eng.stk,

Third device running your kernels never had a problem.

Thanks you very much.

Currently running r49 on feb update.
[Google Pixel 6] flyl0:
I don't think so, we need an update

Edit:nevermind we just got a new update lmao
[Google Pixel 6] Galaxea:
I made the mistake of flashing this kernel on the 12L BETA and it hangs after rebooting.

I don't suggest you do this until it is confirmed as compatible.

@eng.stk Are you able to give us a version for 12L please?
[Google Pixel 6] MattP410:
Nope.
[Google Pixel 6] a g bell:
Yes!!!just switched from op7t good to see this here😁👍sorry for OT😂
[Google Pixel 6] eng.stk:
I build for stable, not in my plans.