If you're on Windows:
Follow these steps closely:
The best way to report bugs is by sending a message in the
Telegram Channel.
If you want to report a bug:
Use the following command:
adb logcat -b all -d > logcat.log
And send the file saved "logcat.log" to the Telegram group
Or use inbuilt MatlogX app if you can't use adb right now.
For MatlogX logs will be saved in a matlogx folder under the directory you choose at startup.
If you experience a CrashDump, please send us logs by doing the following...
Troubleshooting
During CrashDump screen, Device Manager should list device as Qualcomm HS-USB Diagnostics 900E.
If it does not, right click > Uninstall Device > Delete the driver software for this device
Reboot and install above driver set
Blackscreen issue has been a thing since 12. Here's what happens:
When you unlock with fingerprint, under rare circumstances, the high brightness mode
(which gets triggered for the period you press the finger) does not get turned off after unlocking (usually it does).
So if you lock your screen at this point then it'll not turn on without a reboot.
There is a workaround:
No one has been able to reproduce the said issue reliably so don't expect any fixes. Cheers.
You can view changelogs for each device here.
No, face unlock will never be a thing unless google implements it.
Enrollment can give you various accuracy results, and everyone's experience with fp is therefore different. The workaround is to enroll the same finger multiple times (3-4). Basically keep enrolling the same finger until you literally can't enroll it anymore
You can find lots of different Google Camera ports at GCam Hub.
This is easy to fix, just execute the following ADB command in a terminal:
adb shell settings delete secure theme_customization_overlay_packages
Note: you only need to do this once