yesSo 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.
Development [KERNEL] [blu_spark r65] [A12L]
- Thread starter eng.stk
- Start date
Anyone know if a custom kernel could potentially fix a software bug on the Pixel 6 devices? More specifically this bug:
-- 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?
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?
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.
Last edited:
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.
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.
rhewins2268
Senior Member
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
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
I don't think so, we need an update
Edit:nevermind we just got a new update lmao
Good to see you here mate, welcomeYes!!!just switched from op7t good to see this heresorry for OT
Am I the only one who have noticed the improvement of the fingerprint reader after installing this Kernel?
I am using Pixel 6 with a tempered glass screen protector installed.
Previously my Fingerprint reader always made me insane, it never succeeded more than 5 out of 10. I have used stock kernel and several third-party Kernels as well.
Now after installing this Kernel, it seems that the FPR now works almost 90% for me, just like the naked screen.
This is incredible.
Huge thanks to @eng.stk
I will keep watching the response of the fingerprint reader and revert back.
I am using Pixel 6 with a tempered glass screen protector installed.
Previously my Fingerprint reader always made me insane, it never succeeded more than 5 out of 10. I have used stock kernel and several third-party Kernels as well.
Now after installing this Kernel, it seems that the FPR now works almost 90% for me, just like the naked screen.
This is incredible.
Huge thanks to @eng.stk
I will keep watching the response of the fingerprint reader and revert back.
Yeah a bit, but still slow compared to my other optical FoD devices.
I got used to it, just left the finger a bit more on place laying flat and unlocks fine in my case.
But it is a slow sensor, I really doubt Google can make it any better via sw.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
11blu_spark_r65 (A12L)
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 free32
Coolblu_spark_r65 (A12L)
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
11
Yes. Just flash through FKM and all modules will be retained.I'm on A12 May Stock and Magisk stable root. I flash blu_spark with FKM script and that's all I need to do? Will Magisk and modules be kept?
Tyvm
-
49
Kernel features: (WIP)
- Build with custom upstream LLVM 14.x (Clang 14.0.3 + LLD linker + IAS)
- Full -O2 Thin LTO build with device and target flags enhanced, build improvements and compiler fixes, etc
- Less is more: stockish kernel+modules+dtb builds based on Google latest sourcedrop for max stability (android-gs-raviole-5.10-android12L)
- Full kernel tree with OEM integrated drivers, for minimal build overhead and fast deploy
- Systemless installer (doesn't touch system/vendor partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
- Removed some debug and logging options
- Misc ARM performance and battery patches
- CVE security patches, general upstream and fixes for important subsystems when applicable
- No OC, use 250HZ base timer frequency
- Enhanced TCP methods (westwood is default, BBR and others available)
- Some I/O control tweaks, advanced filesystems enabled (NTFS3 5.15 backport, ExFAT upstreamed, , CIFS & NFS)
- ZRAM set at 4G (default lz77eh with lzo-rle, zstd, etc available)
- Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
- Gamepad support enabled (xbox, ps4, switch)
- USB2 Fast Charge (force USB CDP mode up to 1500mA with MTP on)
- Wakelock blockers available
- TWRP Support(LZMA/LZ4 Ramdisk)
- Wireguard updates
- Compatible with EXKM, FKM , Kernel Adiutor and others
Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
If you come from other kernel or have any issues, you should restore your stock setup or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
If you are upgrading between blu_spark versions, just flash the kernel zip.
About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
If you're using custom ROMs (including stock based ones) you're much on your own. I'm mostly interested on debugging stuff in stock and stable ROM.
Also try not to spam the thread with OT. There's threads for all kind of stuff, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img/vendor_boot.img/vendor_dlkm.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock. You can also flash boot.img/vendor_boot.img in fastboot and vendor_dlkm.img in fastbootd from you stock ROM. Or just dirty flash your full OTA ROM zip.
Source Code: https://github.com/engstk/pxl6
Don't forget to hit thanks, it's free28blu_spark_r29 (A12)
So here's blu_spark for the oriole (and probably raven ;p)
Been cracking around on this since I got the device a couple weeks ago.
The new GKI kernel stuff(which imo will kill custom kerneling in the future) and the "let's use 10GB of garbage device tree to build a kernel" is not really for me.
So I decided to put on an full tree with all the vendor stuff on it, with less that 5% of what Google proposes we can play with the device just fine.
My primary objective was also to make a full builtin kernel, but seems like init expects modules and other stuff to be in place so it's a no go, at least for now (maybe with some further init stages crack it's possible, idk)
So kernel output is splitted across boot.img, vendor_boot.img and vendor_dlkm.img.
I also take the time to make AK3 basic hdr v4 compliant (big shouts to @osm0sis for being the best wingman, as always). Because fastboot is tedious and since it's 2021 there's no room for that in my builds.
You can flash the AK3 kernel zip in your favorite kernel app with autoflash functions or with TWRP when/if available. If you want/need to go stock again, instructions are on OP.
Besides Pixel 6, this should work on Pro also, but I can only test on Oriole, let me know how it goes on Raven if you're brave enough.
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 free14blu_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 free12blu_spark_r42 (A12)
New build is up! Merry
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 free12blu_spark_r35 (A12)
New build is up!
Added USB fast charge (forces CDP mode for wonky usb controllers that don't advertise modes properly or at all).
I normally find it useful for mainboards that have ports capable of 900/1200mA/1500mA and fail to advertise CDP compliance (1500mA per spec).
Keep in mind that, despite some protections that should be in place, like everything else that uses electricity, damage can happen.
It's disabled by default, use with caution. If your cat get's on fire, you're on your own.
Build is unified for raviole, should work both on Pixel 6 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
