Database Info

"com.android.systemui has stopped"

Yesterday I rooted my phone and put on Xposed and gravity box. Since then I've been downloading various things and trying out different customisation options. The last thing I download was MotoXposed and I made my navigation bar completely transparent, when I tried to disable the effect my phone just came up with the message 'unfortunately the process com.android.systemui has stopped'. Now I can't use my phone and the message keeps coming up everytime I turn it on. How can I fix this? or get my phone working again?
Don't worry I've fixed my phone completely now.

how?
jamespat93 said:
Yesterday I rooted my phone and put on Xposed and gravity box. Since then I've been downloading various things and trying out different customisation options. The last thing I download was MotoXposed and I made my navigation bar completely transparent, when I tried to disable the effect my phone just came up with the message 'unfortunately the process com.android.systemui has stopped'. Now I can't use my phone and the message keeps coming up everytime I turn it on. How can I fix this? or get my phone working again?
Don't worry I've fixed my phone completely now.
Click to expand...
Click to collapse
Can you tell me how did you solve it w/o reseting your phone?

BlakeParker said:
Can you tell me how did you solve it w/o reseting your phone?
Click to expand...
Click to collapse
Boot into recovery and flash Xposed-Recovery-Framework located at /sdcard . This is assuming the problem was caused by an Xposed module in the first place. Not sure whether OP uses this
Sent from my XT1032 using XDA Premium 4 mobile app

thnx
thnxx got it!

BlakeParker said:
Can you tell me how did you solve it w/o reseting your phone?
Click to expand...
Click to collapse
All I had to do was reboot my phone and luckily (even though the message was still coming up) I could still use the touchscreen. This allowed me to go to the motoXposed module that caused the problems and undo the options I changed.

Unfortunately the process com android.systemui has stopped. Xposed Installer
Does anyone has any clue about this:
I have been having the same issue with my Galaxy S5.
I am using the rooted stock ROm with touchwhiz.
The issue started after I installed Xposed Installer with Wanam Xposed.
The "unfortunately the process com android.systemui has stopped" message does not come on until I received phone call while the phone is active. If I receive a call when the screen lock is on, the phone behaves normally.
The other issue I'm having with Xposed Installer are
1) a noticeable increase in lagging
2) apps takes close to 10 minutes to install
3) It takes a long time for the computer to see the phone after connecting them with USB....sometimes up to 15 minutes. thereafter it was not taking as long, but it was still being delayed.
I have flashed the phone three times with roughly the same observation after each flashing (i.e. issues cropping up only after installing Xposed Installer and some modules)
I'm going to try system tuner now...

Did you managed to fixed it? I have the same problem as well!
Sent from my GT-I9505 using XDA Free mobile app

edwardciasico said:
Did you managed to fixed it? I have the same problem as well!
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
No I did not. I factory-reset the phone. Did not install xposed installer again and It's been working well since then. However, I'm still going to try it one last time...I'll keep you posted

I resolved this by booting into recovery (TWM in my case) and then manually deleting the offending .apk file from /data/app.

jimnu said:
I resolved this by booting into recovery (TWM in my case) and then manually deleting the offending .apk file from /data/app.
Click to expand...
Click to collapse
Which offending apk please?

ekitiboy said:
Which offending apk please?
Click to expand...
Click to collapse
In my case it was motoxposed.apk but YMMV.

sry for doublepost

To fix the systemui-crash u need to disable the (new):
"Heads up notification" on Wanam !!!

Help
I recently rooted my phone with TWRP using Odin. I did a few small things in customizing (ie: font, rotate screen) and now I get this error message.I've tried to boot in recovery and it just constantly flashes the Teamwin logo screen and i get no where. Could really use some help here, cannot use my phone at the moment

i have this issue too
I have this with Orbot. Simply restarted the phone and made a speed-run to uninstall it. Works to me.
So, the main question is: why this happen?

marc_miranda said:
Boot into recovery and flash Xposed-Recovery-Framework located at /sdcard . This is assuming the problem was caused by an Xposed module in the first place. Not sure whether OP uses this
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm facing the same problem i'm unable to use my phone, kindly explain in details how to flash xposed recovery.
the problem appeared after installing an xposed mod.

[Q] Please help! "unfortunately the process com.android.systemui has stopped"

[Q] Please help! "unfortunately the process com.android.systemui has stopped"
I have a rooted nexus 5 running CM11. I kept getting this message before and I didn't know why so I posted here and someone told me to wipe my data so I did. That fixed the problem for about 2 weeks but it's back again. It happens so frequently now its very frustrating. It happens when I open an app, update an app or uninstall an app. Not every time but most frequently when updating. Why is this happening?! Please help and thanks in advance!

Just reflash your ROM or flash a different ROM and your problem should be fixed
Sent from my Nexus 5 using Tapatalk

Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.

CitizenLee said:
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
Click to expand...
Click to collapse
Ok I'll try reflashing. And yes I have xposed and around 10 mods.

lilfil3 said:
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
Click to expand...
Click to collapse
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again

CitizenLee said:
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
Click to expand...
Click to collapse
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.

lilfil3 said:
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
Click to expand...
Click to collapse
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.

CitizenLee said:
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
Click to expand...
Click to collapse
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?

lilfil3 said:
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
Click to expand...
Click to collapse
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?

CitizenLee said:
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
Click to expand...
Click to collapse
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.

lilfil3 said:
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
Click to expand...
Click to collapse
You can change all that stuff in GravityBox and XGEL so might be best to just use those instead

Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!

thank you. this helped me today.
woke up with the error. assuming its gravitybox and xblast causing an issue. will remove xblast.

i9o said:
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
Click to expand...
Click to collapse
Xposed does not actually "touch" or change SystemUI in any way. Xposed puts a couple of "files" in system which allows intercepted commands to be changed, without changing the actual code.
When you updated the ROM via a toolkit (PLEASE don't use toolkits by the way) you would have overwritten these Xposed files.
The simplest fix is to just remove the Xposed files
Sent from my Nexus 5 using Tapatalk

Random Parse Error

Hello,
Today, I am getting random prompts of 'Parse Error', I am using stock rom with xposed, root and haven't made any changes to make it to misbehave..
Anyone have any ideas, thanks?

Deeco7 said:
Hello,
Today, I am getting random prompts of 'Parse Error', I am using stock rom with xposed, root and haven't made any changes to make it to misbehave..
Anyone have any ideas, thanks?
Click to expand...
Click to collapse
You mean when trying to install an app** yes?
Edit : meant app, not ROM. My apologies.

TheLastSidekick said:
You mean when trying to install a ROM, yes?
Click to expand...
Click to collapse
no, I haven't flashed any rom on N5 since day 1, it just randomly popped up. I suspect it's caused by a misbehaving app, but can't figure out which...

Deeco7 said:
no, I haven't flashed any rom on N5 since day 1, it just randomly popped up. I suspect it's caused by a misbehaving app, but can't figure out which...
Click to expand...
Click to collapse
Sorry I meant app...
If any case..
1. There's a problem with the app
2. You should wipe dalvik and cache if possible.
3. If options 1 and 2 aren't viable try clearing data and cache of all applications and that should do it.

Caution, Nov update causes SystemUI FC if you use Substratum.

So after that latest update, I kept getting systemui force closes's and I couldn't figure out why.. Well I narrowed it down to the Substratum themes I was using to modify the systemui.. I was only using the standard Samsung ones that we get to center the clock and change the icons to AOSP, but those were apparently enough to make it do that.. I tried multiple times to fix it but each time resulted in a hard reset and had to start from scratch..
Hopefully this saves some who haven't done the update yet..
Side note: I think it has something to do with Samsung Backup literally saving every little detail and modification we do within certain app's, and the security update didn't like something about that perhaps..

Same thing happened to me. Even after I uninstalled all the themes and substratum I still got the FC.
Sent from my SM-N950U using Tapatalk

How did you reset the phone after the system ui crash?

chaztro1892 said:
How did you reset the phone after the system ui crash?
Click to expand...
Click to collapse
Through recovery
Sent from my SM-N950U using Tapatalk

Circlel05 said:
Through recovery
Click to expand...
Click to collapse
Cool. Thanks. So none of the substratum themes will work I assume.

You have to uninstall all of the Substratum theme stuff before you do the OTA. Says so in the thread and in the play store description. Just an FYI.

ShrekOpher said:
You have to uninstall all of the Substratum theme stuff before you do the OTA. Says so in the thread and in the play store description. Just an FYI.
Click to expand...
Click to collapse
Can the themes be reinstalled after the update?

chaztro1892 said:
Can the themes be reinstalled after the update?
Click to expand...
Click to collapse
Yeah I am running swift black with no issues right now.

ShrekOpher said:
Yeah I am running swift black with no issues right now.
Click to expand...
Click to collapse
I'm running swift dark right now and it's fine but I was told by the developer not to theme the system ui because it could restart the FC's. Can you confirm if that's the case for you?

newguy15 said:
I'm running swift dark right now and it's fine but I was told by the developer not to theme the system ui because it could restart the FC's. Can you confirm if that's the case for you?
Click to expand...
Click to collapse
I never used the system UI technically that is not supported on any Samsung devices with out root. It worked before, but was never officially support.

My father just updated his S8 with substratum installed and now hes getting FC all the time. Is there a way of recovering for this without losing everything? Thanks.

eXtremeDevil said:
My father just updated his S8 with substratum installed and now hes getting FC all the time. Is there a way of recovering for this without losing everything? Thanks.
Click to expand...
Click to collapse
Use adb to uninstall the Substratum overlay apks. I think the system ui overlay apk is the most important one to uninstall.
Then it should reboot fine

I dont have adb

eXtremeDevil said:
I dont have adb
Click to expand...
Click to collapse
You can set it up on a PC really easily.
You could try booting into "safe mode" and uninstall ingredients the overlay apks that way.

I meant on the phone, activated. I do have adb on my phone and my computer.
Safe mode didn't work eigther.
I ended up performing a factory reset.
Thanks anyway to all

This happened to me last week. I called AT&T and they ran through all their BS, they didn't have a clue what was causing it so they had me take my phone to a Samsung Experience Store AKA Best Buy. The tech there was useless I knew more about Samsung phones than he did so I ended up doing a factory reset. After getting my phone all set up and my apps downloaded I rebooted my phone and the same, thing so I called AT&T and they sent me a new phone priority which took 7 days ?. I got my new phone set it up download my apps did the update yesterday and boom same thing. My first mistake was not coming to this forum and not doing a search.

(This 'Should' be common knowledge when using substratum or any third party overlay that interacts with system files.)
But you should always uninstall any system overlay before performing a software update.
Otherwise you risk facing the SystemUI Force close issue.
If you are rooted you can recover via recovery (TWRP)
if you are not rooted the only way to recover without loosing your data is to try this:
How to recover?
You will have to boot up in Safe Mode (comes default on every device)
Reboot your device
Hold down the Volume Down key while booting up
You are now in Safe Mode
Go into Settings -> Apps, then find the overlay you think is messing up and uninstall!
How to recover if the above doesn't work? (Credits to Evozi)
You will have to boot up in Safe Mode (comes default on every device)
Turn on screen and press power button. It will show "Shutdown", "Restart", "Emergency Mode"
Turn on "Emergency Mode", keep spam the checkbox so you can tick the checkbox to proceed the agreement. (phone is super lagging)
While you are in emergency mode, you have very limited access. Open any system app and go to recent task list.
Long press the app task, press the info icon and app detail page will appear.
Hit the back button and it will show your whole app list.
Find your overlay and remove all its storage and phone permissions.
Deactivate Emergency Mode and now you are back to TouchWiz.
Uninstall the overlay app.
Click to expand...
Click to collapse
I was testing new and old system overlays when the Note 8 first came out to see what worked and what didn't, the ones that didnt gave me this problem.
You will most probably find the first one does not work and the second is a pain to get working, but personally i have had the Emergency mode method work for me after a few trys. I gave up at one point and started downloading firmware files to be honest but i gave it another shot while waiting and it worked.
Hope this helps - Hit thanks so this post gets shown to other users coming here looking for help

jdmsohc22 said:
So after that latest update, I kept getting systemui force closes's and I couldn't figure out why.. Well I narrowed it down to the Substratum themes I was using to modify the systemui.. I was only using the standard Samsung ones that we get to center the clock and change the icons to AOSP, but those were apparently enough to make it do that.. I tried multiple times to fix it but each time resulted in a hard reset and had to start from scratch..
Hopefully this saves some who haven't done the update yet..
Side note: I think it has something to do with Samsung Backup literally saving every little detail and modification we do within certain app's, and the security update didn't like something about that perhaps..
Click to expand...
Click to collapse
Awesome thanks for the heads up. Literally just got the substratum 2 days ago and am loving it so far.

I ended up factory reseting for this very reason
Sent from my [device_name] using XDA-Developers Legacy app

Has anyone on ATT but bought their phone unlocked from Samsung? On here

Please help!! S10 Plus touch sceen goes unresponsive!

Hello, as the title says, My touch screen goes unresponsive randomly, I've bought it used for 10 days now, and the problem started happening 3 days ago when I was trying to check my battery's use, nothing special.
I had a UV screen protector installed and I removed it, (slightly troublesome when removing the glue) when the problem started happening, tried factory resetting too, problem still here. please help

Africanstar said:
Hello, as the title says, My touch screen goes unresponsive randomly, I've bought it used for 10 days now, and the problem started happening 3 days ago when I was trying to check my battery's use, nothing special.
I had a UV screen protector installed and I removed it, (slightly troublesome when removing the glue) when the problem started happening, tried factory resetting too, problem still here. please help
Click to expand...
Click to collapse
bump :/

Africanstar said:
bump :/
Click to expand...
Click to collapse
What apps have you personally installed on the device in addition to the apps to the apps that were already on the device?
What settings have you changed?
Sent from my SM-S767VL using Tapatalk

Droidriven said:
What apps have you personally installed on the device in addition to the apps to the apps that were already on the device?
What settings have you changed?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi thanks for the reply, I have every application installed from the official playstore and spotify dogfood+google camera

Africanstar said:
Hi thanks for the reply, I have every application installed from the official playstore and spotify dogfood+google camera
Click to expand...
Click to collapse
I didn't ask about apps, I asked about your settings, as in, what have you changed or installed that is not default or was not already on the device when you bought it?
Ok, you've installed apps from the PlayStore, that doesn't tell me anything. What apps have you personally installed on the device that is not a stock app or stock app update?
Boot your device into safe mode, if the touch issue does not occur while in safe mode, that is a sure sign that the issue is caused by something that you installed or possibly a setting that you changed somewhere.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
I didn't ask about apps, I asked about your settings, as in, what have you changed or installed that is not default or was not already on the device when you bought it?
Ok, you've installed apps from the PlayStore, that doesn't tell me anything. What apps have you personally installed on the device that is not a stock app or stock app update?
Boot your device into safe mode, if the touch issue does not occur while in safe mode, that is a sure sign that the issue is caused by something that you installed or possibly a setting that you changed somewhere.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I just factory reset the phone through odin, and ran it on safe mode, still suffering from the issue