I haven't even noticed that But yeah, I can confirm this, too.
Flashing kernels only works on EXKM when on Android R right now. FYI. It's been this way through the betas.
Happened to me before also.I'm on android 11. I had the kernel installed but switched back to stock and now face unlock doesn't work. it just says "Can't verify face. Try again."
Happened to me before also.
Reflashing the stock image did the trick for me.
I'm on android 11. I had the kernel installed but switched back to stock and now face unlock doesn't work. it just says "Can't verify face. Try again."
I'm on android 11. I had the kernel installed but switched back to stock and now face unlock doesn't work. it just says "Can't verify face. Try again."
Happened to me before also.
Reflashing the stock image did the trick for me.
I had the exact same issue as well and coincidentally also yesterday! Rebooted a few times but no change. But Kirisakura V6 had been working fine for me for a few days so I don't think it's that. I narrowed it down to the Viper 4 Android beta for 11 that I had recently flashed. Uninstalled that module, rebooted and my Face Unlock was functional again.
I'm also having some issues with alarms but that's unrelated.
+1 don't happen all the time but it does and I doubt it has anything to do with this kernel because I too was on stock kernel before switching to kiri and same thing would happenDoes anyone experience animation and scrolling lag right after unlocking the phone on 11?
Same on both stock and this kernel.
Restart can help for awhile but it's really annoying.
Never happened before on Android 10.
Already tried clean install with factory image.
I'm going back to android 10+1 don't happen all the time but it does and I doubt it has anything to do with this kernel because I too was on stock kernel before switching to kiri and same thing would happen
Not using clean slate features ATM so that's why I ruled out the kerneli am not sure if this is the right place to write this issue. Cleanslate gamma settings sometimes deactivates itself and stop working and then a bit later it funktions again. Sometimes it works after reboot so maybe it os kernel related do not know.
Are you using Magisk canary? You'll need to.New root user (post 11 update).
Magisk patched boot image wont boot (no valid slot to boot) after going to google logo and going back to bootloader on its own.
Works fine with stock boot.img from r/11 but wont boot with latest magisk patch. Do i need to use the old magisk apk or what?
It seems Google flipped their switch again. Try the MagiskHide Props Module and set it to basic.Probably not the right forum to ask.
Everything has been working fine since updating to android 11 and 6.0
My device just randomly attestation failed eval type hardware. Can't get google pay to work or fix the false CTS
It seems Google flipped their switch again. Try the MagiskHide Props Module and set it to basic.
EDIT: It may break NGA though.
Probably not the right forum to ask.
Everything has been working fine since updating to android 11 and 6.0
My device just randomly attestation failed eval type hardware. Can't get google pay to work or fix the false CTS
Why don't we wait until the device is actually released, bub.have a questio. regarding the upcoming pixel 5. Will this kernel with all its featurrs ported for the pixel 5??