Rob. S. 1,660 Posted September 19, 2022 Share Posted September 19, 2022 (edited) Lately, the Android 11 System UI starts to crash now and then, after the device has been in use for some time (at least a few days). Once it has started behaving like that, one thing that reliably triggers the crash is opening or closing the hardware keyboard. Drove me nuts today when I was in one of my banking apps which should give me a code to authenticate a transaction in my laptop's browser, I opened out the keyboard to enter that app's password, just to see everything disappear behind the lock screen that the crashed System UI had brought up. Logged in to the phone again, the banking app had of course closed and requested its password again... At next try, it happened again! I just cannot seem to be able to not open the keyboard when there's use for it! 😀 (Oh, and by the way I have a fingerprint reader problem that I already used to have on my Pro1, once, very early in my first steps with the original Pro1 and LineageOS 16.1. If I only could remember how I made it go away... I'll be reporting more when I have looked into it a bit more.) Good thing is, with a full shutdown and reboot of the device, the crashes stop happening, for the time being. Edited September 19, 2022 by Rob. S. 1 Quote Link to post Share on other sites
Hook 3,020 Posted September 19, 2022 Share Posted September 19, 2022 The first question would be were you bin tbe past able to use the phone for long periods without this happening? Is this recent? If so, whatt have you added to or changed on the phone in recent history, I would look for the culprit there. Quote Link to post Share on other sites
Rob. S. 1,660 Posted September 19, 2022 Author Share Posted September 19, 2022 Yes, this is recent, and I rarely ever shut down or reboot the phone, as I, luckily, haven't experienced the "not charging" issue with it yet... I surely did add a few apps recently and also probably removed one or two. (Problem is, I tend to remove fewer apps than I install.) Quote Link to post Share on other sites
EskeRahn 5,460 Posted September 20, 2022 Share Posted September 20, 2022 It is really hard to guess what it could be, and you already know the standard suggestion: Factory reset and no apps installed, to see if that is stable, but not a very useful suggestion IRL, so as @Hook suggests, have a look at what have happened at the time the behaviour started, and peel off any new apps. There is absolutely no guarantee that an app is the culprit and even if it is, that this will find it. If an app it also could be an Android-market triggered update that have caused the problems. At the least you found a consistent way of making it crash, so I would suggest starting to peel off apps, starting with those with limited/no setup and/or ways to backup&restore settings. So IF an app is the culprit you can narrow it down. Though less likely you also might want to try killing some apps marked as system.... Quote Link to post Share on other sites
Dirk 4 Posted September 22, 2022 Share Posted September 22, 2022 I'm having the same issue, and it looks like a bug in the firmware. I had already reported it, let's hope someone is taking care of it. Here's a sample stack trace from logcat, that nicely shows how a filed mUiMode is not properly initialized when a new DisplayLayout-Object is created: 09-13 21:27:20.823 2872 2872 E AndroidRuntime: FATAL EXCEPTION: main 09-13 21:27:20.823 2872 2872 E AndroidRuntime: Process: com.android.systemui, PID: 2872 09-13 21:27:20.823 2872 2872 E AndroidRuntime: java.lang.NullPointerException: Attempt to read from field 'int com.android.systemui.wm.DisplayLayout.mUiMode' on a null object reference 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.systemui.wm.DisplayLayout.set(DisplayLayout.java:118) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.systemui.wm.DisplayLayout.<init>(DisplayLayout.java:113) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.systemui.stackdivider.Divider.lambda$new$0(Divider.java:116) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.systemui.stackdivider.Divider.lambda$new$0$Divider(Unknown Source:0) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.systemui.stackdivider.-$$Lambda$Divider$0WHTGcDpweqOnqzkpJAQb7brKYs.onRotateDisplay(Unknown Source:2) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.systemui.wm.DisplayChangeController$1.lambda$onRotateDisplay$0(DisplayChangeController.java:56) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.systemui.wm.DisplayChangeController$1.lambda$onRotateDisplay$0$DisplayChangeController$1(Unknown Source:0) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.systemui.wm.-$$Lambda$DisplayChangeController$1$cr2NyoFjnt2r0DMHwy9cOe5oGO4.run(Unknown Source:10) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7705) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) 09-13 21:27:20.823 2872 2872 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:952) 2 Quote Link to post Share on other sites
Rob. S. 1,660 Posted November 4, 2022 Author Share Posted November 4, 2022 Just for the record, the issue has stopped appearing here soon after my report, without me changing anything... 2 Quote Link to post Share on other sites
Dirk 4 Posted November 5, 2022 Share Posted November 5, 2022 After Beta 2.1.5/6 the issue is happening less often for me, but still happens -- especially when opening/closing the keyboard 1 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.