Moto g6plus evert bootloop if fingerprint sensor not working

Moto g6plus evert bootloop if fingerprint sensor not working
none 0.0 0

卧梅又闻花,卧枝绘中天。鱼吻卧石水,卧石答春绿。
岸似绿,岸似透绿,岸似透黛绿,就似不岸格似发帖。

报告时请提供操作步骤当前版本,如果能附上屏幕截图录像错误日志将有利于我们的排查。

标准发帖格式:
问题描述: Lawnchair未翻译彻底
当前版本: MK71.2-oneplus3-201708232008-NIGHTLY
复现步骤: 桌面空白处长按 - 设置 - 行为 - Lock Desktop

如果您不能按照标准发帖格式提供基础信息,我们将会忽略删除您的报告。
因为信息不全很难定位并修复问题,甚至该问题可能是您自身操作不当导致的。

When posting a bug report, please mention the steps to replicate and affected version. Reports with screenshots, screen recordings or logcats will potentially be resolved faster.

Mandatory report format:
Bug description:
Bootloop if fingerprint sensor not working
Affected version:
MK100.0-evert-220723-RELEASE.zip MK110.1-evert-202209030726-NIGHTLY.zip
Steps to replicate:
just boot with the rom with mobile that is having fingerprint sensor not working.

logcat

--------- beginning of crash
09-05 06:03:21.337 1218 1218 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 1218 (android.hardwar), pid 1218 (android.hardwar)
09-05 06:03:21.368 1323 1323 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-05 06:03:21.368 1323 1323 F DEBUG : MoKee Version: ‘MK110.1-evert-202209030726-NIGHTLY’
09-05 06:03:21.368 1323 1323 F DEBUG : Build fingerprint: ‘motorola/evert/evert:8.0.0/OPW27.113-89/116:user/release-keys’
09-05 06:03:21.368 1323 1323 F DEBUG : Revision: ‘pvt1’
09-05 06:03:21.368 1323 1323 F DEBUG : ABI: ‘arm64’
09-05 06:03:21.368 1323 1323 F DEBUG : Timestamp: 2022-09-05 06:03:21+0000
09-05 06:03:21.368 1323 1323 F DEBUG : pid: 1218, tid: 1218, name: android.hardwar >>> /vendor/bin/hw/[email protected] <<<
09-05 06:03:21.368 1323 1323 F DEBUG : uid: 1000
09-05 06:03:21.368 1323 1323 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
09-05 06:03:21.368 1323 1323 F DEBUG : Abort message: ‘HIDL joinRpcThreadpool without calling configureRpcThreadPool.’
09-05 06:03:21.369 1323 1323 F DEBUG : x0 0000000000000000 x1 00000000000004c2 x2 0000000000000006 x3 0000007fe3d21fa0
09-05 06:03:21.369 1323 1323 F DEBUG : x4 feff2d6b6e6e4f63 x5 feff2d6b6e6e4f63 x6 feff2d6b6e6e4f63 x7 7f7f7f7f7f7f7f7f
09-05 06:03:21.369 1323 1323 F DEBUG : x8 00000000000000f0 x9 a485660f44e75caf x10 0000000000000000 x11 ffffffc0ffffffdf
09-05 06:03:21.369 1323 1323 F DEBUG : x12 0000000000000001 x13 000000000000003f x14 0013e35a8343b242 x15 0000000000001e22
09-05 06:03:21.369 1323 1323 F DEBUG : x16 00000071d2015c80 x17 00000071d1ff7c10 x18 00000071d29c8000 x19 00000000000004c2
09-05 06:03:21.369 1323 1323 F DEBUG : x20 00000000000004c2 x21 00000000ffffffff x22 0000000000000001 x23 0000000000000000
09-05 06:03:21.369 1323 1323 F DEBUG : x24 0000000000000000 x25 0000000000000000 x26 0000000000000000 x27 0000000000000000
09-05 06:03:21.369 1323 1323 F DEBUG : x28 0000000000000000 x29 0000007fe3d22020
09-05 06:03:21.369 1323 1323 F DEBUG : lr 00000071d1faa2a0 sp 0000007fe3d21f80 pc 00000071d1faa2cc pst 0000000000000000
09-05 06:03:21.378 1323 1323 F DEBUG : backtrace:
09-05 06:03:21.378 1323 1323 F DEBUG : #00 pc 000000000004e2cc /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: c7446781f0becbb013495ebcbb45d1ca)
09-05 06:03:21.378 1323 1323 F DEBUG : #01 pc 00000000000062b0 /system/lib64/liblog.so (__android_log_default_aborter+12) (BuildId: b5b2ed9d2859e7c956635d8bdb685c6f)
09-05 06:03:21.378 1323 1323 F DEBUG : #02 pc 0000000000006e18 /system/lib64/liblog.so (__android_log_assert+336) (BuildId: b5b2ed9d2859e7c956635d8bdb685c6f)
09-05 06:03:21.378 1323 1323 F DEBUG : #03 pc 0000000000056e9c /apex/com.android.vndk.v30/lib64/libhidlbase.so (android::hardware::joinBinderRpcThreadpool()+60) (BuildId: 408ba28f62bba357cea06ef12223a95f)
09-05 06:03:21.378 1323 1323 F DEBUG : #04 pc 00000000000048dc /vendor/bin/hw/[email protected] (main+232) (BuildId: 39dd754cb886fe56ce3cd468ae1dfbd1)
09-05 06:03:21.378 1323 1323 F DEBUG : #05 pc 000000000004988c /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: c7446781f0becbb013495ebcbb45d1ca)
--------- beginning of kernel

If you do not follow the format above when posting a bug report, it will delete or automatically be ignored. Without sufficient information, it is impossible for us to debug. Most probably the issue could be caused by your own inappropiate usage.