Issues after booting the system when shut down using the power menu (?)

[RandomTypek]

(I have no idea how to title this, sorry)

I'm experiencing this weird issue with the latest LineageOS 16 build you provided (20190417), where the system sometimes boots up in a broken state (WiFi doesn't work, Settings app doesn't work at all - freezes instantly, I'm unable to shut down the system properly via the power menu - it gets stuck at the shutting down screen, etc.). After shutting down the system forcefully (by holding down the power button) while in this state and turning it back on, everything works. After shutting it down properly and booting immediately after shutting it down, everything works. But if I shut it down properly and turn it on 10 minutes later for example, it breaks again.
Attaching a logcat for now, will provide more logs if needed.
2019-04-21-17-15-15.txt

[lambdadroid]

Is ADB still working via USB when your system freezes? Or how/when did you get the log?

[RandomTypek]

It's not that the system freezes when this happens, it runs relatively fine, but I can't access the internet (since WiFi doesn't work), can't open settings etc. until I forcefully shut the tablet down and turn it on once again

I got the log using MatLog when it was happening, before shutting it down of course, will test whether ADB works when/if it happens again (seems to be a bit random, it seems to boot correctly every time now... I really don't know at this point)

[lambdadroid]

Would be useful to have both logcat (adb logcat) and kernel log (adb shell dmesg). Not sure if MatLog can get kernel log too.

[RandomTypek]

Alright, it happened again - ADB does not work in this state. The tablet is detected in adb devices but doesn't respond to any commands. Haven't found any way to get kernel log in MatLog; is there any other way to get the logs? (Terminal Emulator comes to mind but I don't have it installed currently, will have to wait until it happens again then)

[RandomTypek]

Okay nevermind, managed to get an .apk of Terminal Emulator and send it over via Bluetooth.. here are the logs I got using T.E.

logcat.txt
dmesg.txt

[lambdadroid]

Will need to try to reproduce this. The logs don't really contain something useful. There are some binder related errors, but I don't see how they would be related to anything I work on (more likely a problem with some apps).

[RandomTypek]

It almost seemed like this was fixed in the latest build, but I ran into this again just now... seems to be related to either Bluetooth or the system crashing unexpectedly:

1. I shut down the system with WiFi being off and Bluetooth being on
2. Booted normally a day later, everything still worked fine
3. Turned WiFi back on
4. Left the tablet idle
5. Went to check the tablet a few minutes later, found out that the system had crashed (tablet had turned itself off..)
6. Booted (presumably normally), the issue started again (no WiFi, no Settings, can't shut down normally)

Might have been just something random but I thought I'd share in case it helps...