Com.android.systemui has stopped working unexpectedly
how can I bypass this error?
Ist dies eine gute Frage?
Die dritte Generation des HTC One Smartphones, das zum ersten Mal im März 2015 auf den Markt kam. Die größten Änderungen zum Vorgängermodell sind ein Snapdragon 810-Prozessor und eine 20 Megapixel Hauptkamera auf der Rückseite des Smartphones.
how can I bypass this error?
I just ran into this problem yesterday at the shop and I was able to resolve the issue by going to Settings - Application Manager - Google App - Uninstall updates.
(Posted to another question and she said this helped her resolve the issue)
Let me know if that helps your problem!
Sounds like an ART incompatibility. You probably installed an app recently that doesn't work properly with ART. Presumably it added itself to the start-up apps. That's why your UI crashes when booting up. You will have to find a way to either remove the app in question or go back to the Dalvik runtime.
I went through the same ordeal a month ago when I opted to try out ART. Of the various solutions I found on the internet only this one by androidcentral user sajidr worked. I'll quote it here in case the forum post goes down:
I managed to switch my runtime back to Dalvik. It was painfully slow but in the end I didn't have to do a factory reset.
There's a fraction of a second after unlocking when the screen responds to a touch or swipe. This happens only right after you see the error message popup - "Unfortunately, the process com.android.systemui has stopped". If you do not see this message after unlock then open up the camera from the lock screen & close it.
Next, follow these steps to open up the app drawer - 1. Unlock the phone 2. Once you see the popup "Unfortunately, the process com.android.systemui has stopped", keep tapping on the area where you think the app drawer icon is. At the same time, using another finger click on the OK button of the systemui message box. 3. If your timing's good then once the message box is closed, the app drawer should open. 4. The phone would go back to lock screen but the app drawer would be open. You can validate this by unlocking the phone.
Repeat the above steps to swipe over to your Settings app. Instead of tapping, do short swipes & then click on the message box OK button. Each time the phone would go back to the lock screen but you should be able to slowly navigate over to change your runtime.
Once I got the hang of it, it took me about 15 minutes to go to Settings & change the runtime.
Don't bother trying to uninsintall flipboard from your play store this way. I tried it twice & both times the phone rebooted itself after i clicked the uninstall button.
If your screen layout shifts vertically after the unlock then tap on the area where you first see the icon & not where it moves to after the shift.
Other users have had varying success with booting to safe mode and disabling ART / ART-incompatible apps from there.
You will find more discussion on this issue and possible solutions in these threads:
I just installed ZenUI launcher and somehow it fixed the problem in my Galaxy S3 Neo.
Edit: My phone was able to start but whenever I tried to clear all the open apps by pressing the home button for 2 seconds, it showed this error message ['com.android.systemui has stopped working, unfortunately'].
So first I factory reset the phone, the error was gone. Then when google play store was restoring all my apps, the error message came back. After lots of hit and trial, I installed a Launcher and then just by installing (not even using it), the error was gone.
For my old school galaxy s4, I accept updates on some of my apps. Google was my issue. Go to play store and uninstall updates be sure your google settings are set to not automatically allow updates
I've been battling this problem for days now. The first phone I ever successfully rooted so I'm very reluctant to let it go. Master reset, cleared cached partition, safe mode start up, nothing so far. I think I might have deleted an important app or process by mistake. Anyone know what I could have deleted that would cause this error?
Letzte 24 Stunden: 32
Letzte 7 Tage: 119
Letzte 30 Tage: 591