[Pixel C Android Development] szescxz:
Found some issues:

- Cannot unlock (I've tested pattern and PIN) after a long screen off setting SELinux to enforced (it says "Wrong pattern/PIN"). Reboot fixes it, but "setenforce 0" via adb shell does not. This only happened once, I'll try to determine whether it's a temporary issue or a permanent one.

When it unlocks:

03-31 09:12:02.519 1155 2011 D LockSettingsService: spBasedDoVerifyCredential: user=0 challengeType=0 hasEnrolledBiometrics=false
03-31 09:12:02.562 215 215 D TlkGateKeeper: Received tlk_call, cmd: 1, in_buf 0x7ff849fc68, in_size: 146, out_buf: 0x7ff849dc68, out_size: 8192
03-31 09:12:02.640 215 215 D TlkGateKeeper: tlk returned 82

When it does not unlock:

03-31 09:26:11.204 1177 1308 D LockSettingsService: spBasedDoVerifyCredential: user=0 challengeType=0 hasEnrolledBiometrics=false
03-31 09:26:11.250 215 215 D TlkGateKeeper: Received tlk_call, cmd: 1, in_buf 0x7ffb8ede28, in_size: 146, out_buf: 0x7ffb8ebe28, out_size: 8192
03-31 09:26:11.252 215 215 D TlkGateKeeper: tlk returned 8

- App incompatibility (I don't think it's an app-side issue though): Cytus II still fails to save the progress. This is probably related to the first issue. Also occurs on Pie, but not on Oreo (LineageOS 15.1):

04-03 13:44:53.091 186 186 I TLKKeymaster: Sending 1441 byte request
04-03 13:44:53.091 186 186 D TLKKeymaster: Received tlk_call, cmd: 15, in_buf 0x7fc1960ae8, in_size: 1441, out_buf: 0x7fc195eae8, out_size: 8192
04-03 13:44:53.091 186 186 D TLKKeymaster: TLK returned 197
04-03 13:44:53.091 186 186 I TLKKeymaster: Received 197 byte response
04-03 13:44:53.092 186 186 I TLKKeymaster: Sending 1445 byte request
04-03 13:44:53.092 186 186 D TLKKeymaster: Received tlk_call, cmd: 6, in_buf 0x7fc19609b8, in_size: 1445, out_buf: 0x7fc195e9b8, out_size: 8192
04-03 13:44:53.092 186 186 D TLKKeymaster: TLK returned 302
04-03 13:44:53.092 186 186 I TLKKeymaster: Received 302 byte response
04-03 13:44:53.097 186 186 I TLKKeymaster: Sending 1441 byte request
04-03 13:44:53.097 186 186 D TLKKeymaster: Received tlk_call, cmd: 15, in_buf 0x7fc1960a08, in_size: 1441, out_buf: 0x7fc195ea08, out_size: 8192
04-03 13:44:53.097 186 186 D TLKKeymaster: TLK returned 197
04-03 13:44:53.097 186 186 I TLKKeymaster: Received 197 byte response
04-03 13:44:53.097 186 186 I TLKKeymaster: Sending 1445 byte request
04-03 13:44:53.097 186 186 D TLKKeymaster: Received tlk_call, cmd: 6, in_buf 0x7fc19608d8, in_size: 1445, out_buf: 0x7fc195e8d8, out_size: 8192
04-03 13:44:53.097 186 186 D TLKKeymaster: TLK returned 302
04-03 13:44:53.098 186 186 I TLKKeymaster: Received 302 byte response
04-03 13:44:53.098 186 186 I TLKKeymaster: Sending 1550 byte request
04-03 13:44:53.098 186 186 D TLKKeymaster: Received tlk_call, cmd: 1, in_buf 0x7fc1960c18, in_size: 1550, out_buf: 0x7fc195ec18, out_size: 8192
04-03 13:44:53.098 186 186 D TLKKeymaster: TLK returned 24
04-03 13:44:53.098 186 186 I TLKKeymaster: Received 24 byte response
04-03 13:44:53.099 186 186 E TLKKeymaster: Error -41 sending update
04-03 13:44:53.157 18409 18491 E Unity : Cannot write PlayerRecord to the local storage: java.util.concurrent.ExecutionException: java.security.SignatureException: android.security.KeyStoreException: Memory allocation failed
04-03 13:44:53.157 18409 18491 E Unity : java.util.concurrent.ExecutionException: java.security.SignatureException: android.security.KeyStoreException: Memory allocation failed
04-03 13:44:53.157 18409 18491 E Unity : at java.util.concurrent.FutureTask.report(FutureTask.java:123)
04-03 13:44:53.157 18409 18491 E Unity : at java.util.concurrent.FutureTask.get(FutureTask.java:193)
04-03 13:44:53.157 18409 18491 E Unity : at com.unity3d.player.UnityPlayer.nativeRender(Native Method)
04-03 13:44:53.157 18409 18491 E Unity : at com.unity3d.player.UnityPlayer.c(Unknown Source:0)
04-03 13:44:53.157 18409 18491 E Unity : at com.unity3d.player.UnityPlayer$e$2.queueIdle(Unknown Source:72)
04-03 13:44:53.157 18409 18491 E Unity : at android.os.MessageQueue.next(MessageQueue.java:405)
04-03 13:44:53.157 18409 18491 E Unity : at android.os.Looper.loop(Looper.java:174)
04-03 13:44:53.157 18409 18491 E Unity : at com.unity3d.player.UnityPlayer$e.run(Unknown Source:32)
04-03 13:44:53.157 18409 18491 E Unity : Caused by: java.security.SignatureException: android.security.KeyStoreException: Memory allocation failed
04-03 13:44:53.157 18409 18491 E Unity : at android.security.keystore.AndroidKeyStoreSignatureSpiBase.engineUpdate(AndroidKeyStoreSignatureSpiBase.java:273)
04-03 13:44:53.157 18409 18491 E Unity : at java.

I assume these two issues require something released from NVIDIA (like Android 10 for Shield TV)? Correct me if I'm wrong.

- Rotate button on navigation bar does not show up on 270° (which is reasonable on mobile phones, but Pixel C is a tablet). Auto-rotate works, of course.

- 2-button navigation's swipe up and swipe right does not work on 90° and 270°, making it impossible to switch apps. (EDIT: It still works on 90° but at a wrong position, I have to swipe from the left side of the screen (like it's on 0°). It does not work on 270° at all)

- There seems to be issues with /vendor/lib/hw/memtrack.dragon.so, my current workaround is setting SELinux to enforced (so I'm not pasting a logcat right now). It works fine on another Android 10 device I have with permissive SELinux though.

- Possible memory leak: On LineageOS 17.1, the maximum memory usage of "Android OS" can go up to 1GB, while on LineageOS 15.1 it never goes more than 700MB. This causes some RAM-consuming games laggy sometimes. Doesn't seem to be a kernel issue though, as I have tested with the unified kernel on both versions.