Today I update to the 30O than immediately updated to 33R and now I am getting a constant system UI crashed pop-up. I have rebooted multiple times. Anyone else get this or know how to fix?
I'd clear the cache / fix permissions. Seems like you flashed something bad. Ultimately I'd recommend a clean install.
I think it might have had something to do with root. I flashed SU and removed a root app and all seems good.
Related
Does anyone know how I could manually go about removing the lag fix so I can receive OTA updates without any glitches?
This is the story...
Rooted with Z4 Root
installed Ryan's OCLF V1+
everything was working fine,
downloaded an app from the market (AR Satelitte) that caused my phone to start "black screen",
did a factory reset,
NOW, I've still got root and reinstalled Ryan's OCLF but it's showing that both the run lag fix and undo lag fix are unavailable, so now I technically have the lag fix installed but Ryan's OCLF isn't recognizing it's own lag fix.
I cannot undo it nor can I run it.
Does anyone know how I could manually go about removing the lag fix so I can receive OTA updates?
bludevil35 said:
Does anyone know how I could manually go about removing the lag fix so I can receive OTA updates without any glitches?
This is the story...
Rooted with Z4 Root
installed Ryan's OCLF V1+
everything was working fine,
downloaded an app from the market (AR Satelitte) that caused my phone to start "black screen",
did a factory reset,
NOW, I've still got root and reinstalled Ryan's OCLF but it's showing that both the run lag fix and undo lag fix are unavailable, so now I technically have the lag fix installed but Ryan's OCLF isn't recognizing it's own lag fix.
I cannot undo it nor can I run it.
Does anyone know how I could manually go about removing the lag fix so I can receive OTA updates?
Click to expand...
Click to collapse
I have the same problem. When I try to run OneClickLagFix V2.2+ a box pop's up which says "You already appear to have another lag fix installed! (/system/bin/playlogos2 less than 5KB)". This drives me mad since I have no idea what to do. The galaxy s just sucks without the lagfix. Can anybody help?
dumbledorrre said:
I have the same problem. When I try to run OneClickLagFix V2.2+ a box pop's up which says "You already appear to have another lag fix installed! (/system/bin/playlogos2 less than 5KB)". This drives me mad since I have no idea what to do. The galaxy s just sucks without the lagfix. Can anybody help?
Click to expand...
Click to collapse
I have the exact same problem... and there was me thinking I was the only one!
I had this problem too. Eventually I just used terminal emulator, ran as su and deleted the playlogos file (and one other similarly named file it complained about when I tried to apply a second time). I got it running again, but the lagfix in custom ROMs is so much better and more stable so I got rid of OCLF anyway.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have the same problem,"you have another lagfix....",couldn't remove ext2 tools,so i try to install the ext2 tool again,restore boot animation,and then i can removed the ext2 tools again...
Is anyone else experiencing market issues after updating firmware to 4.0.3? I can see my apps and search etc fine but when I try to download an app it says:
"... could not be downloaded because due to an error. (-101)"
I tried flashing the 4.0.1 firmware since market was working on it, but i still get the same issue.
I also tried clearing market cache and date, force closing it, and nothing works. I also tried reinstalling market and still same issue.
Anybody has an idea what the problem is and how to fix it?
Try clearing the cache and dalvik in recovery. also what i would do is go into cwm first reflash and then fix permissions then clear those things.
cameljockey1 said:
Try clearing the cache and dalvik in recovery. also what i would do is go into cwm first reflash and then fix permissions then clear those things.
Click to expand...
Click to collapse
Tried but it didnt fix it...
im having the same issue im running the newest elegancia rom everything is running fine except this issue with the market ..................NEED SOME HELP HERE
The problem went away for me last night but now all of sudden I'm getting the same error... then it went away again.
I can't really figure out how it went away... I did restore a nandroid backup yesterday before the problem went away, but I don't think that's what fixed it since I had tried that before...
Market Problems - Solution
I was having the exact same issues. I was running MIUI.us 1.12.23. I went online and found 1.12.30. Once I upgraded my problem was gone.
However, the new firmware is still eating up my battery!
David
I was having the same problems after 4.0.3 RUU install (rooted).
I cleared the market data and cache and UNINSTALLED MARKET UPDATE rebooted my device and everything was fine!
9020t running CM9 3.4 w/ stock kernal, has been running perfectly fine but all of a sudden this morning multiple apps give me the error "Unfortunately **** has stopped". Along with that I know at least 1 app disappeared, my launcher reset to default, and apps that had already been granted superuser are asking for it again. Chrome prompts "Critical Functionality required to run Chrome is missing; either your Chrome installation is incomplete, or not compatible with this version of Android".
Going to do a full fresh wipe, wondered if anyone else has had this happen recently.
system60 said:
9020t running CM9 3.4 w/ stock kernal, has been running perfectly fine but all of a sudden this morning multiple apps give me the error "Unfortunately **** has stopped". Along with that I know at least 1 app disappeared, my launcher reset to default, and apps that had already been granted superuser are asking for it again. Chrome prompts "Critical Functionality required to run Chrome is missing; either your Chrome installation is incomplete, or not compatible with this version of Android".
Going to do a full fresh wipe, wondered if anyone else has had this happen recently.
Click to expand...
Click to collapse
I had this happen with my old LG Optimus T, Booting into recovery and wiping the cache's did the trick to fix it without wiping the whole phone. But if that fails then a full wipe/re-flash would be required.
If you're going to do a full wipe anyway, I suggest you reflash CM9 as well, Just in case the flash image somehow became corrupt.
So I've been running the same setup since I updated to 4.4.4 about a month ago. Stock 4.4.4 rom with Xposed framework, rooted, custom kernel, custom DPI.
This morning I wake up and my phone will boot past the boot screen and just keep giving me the "Unfortunately, the process com.android.systemui has stopped.
Does anyone have stock 4.4.4 systemui file in case mine got corrupted somehow? Or should I flash the system.img? What does the system.img change if I flash it. Will if affect my apps/data/etc?
System.img replaces everything in /system. Your data and apps are in /data
Might be worth reading the sticky threads. This is pretty basic info that you should already know if you're messing with root.
Most likely the problem will be with /data anyway
Sent from my Nexus 5 using Tapatalk
I read somewhere that Xposed might be causing it. Is there a way to disable it as I can't get to it fast enough before the systemui crashes.
Isn't there an xposed removal flashable zip in the xposed thread? I think there is.
It won't be xposed itself but it could be a module or the settings of moduke causing it, which are stored in /data.
That said, removal of xposed would be the best course to take for elimination purposes.
Sent from my Nexus 5 using Tapatalk
impruv said:
I read somewhere that Xposed might be causing it. Is there a way to disable it as I can't get to it fast enough before the systemui crashes.
Click to expand...
Click to collapse
I had this problem after flashing a new nightly version of my ROM.
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401/post51306764
I went into safe mode, documented in the thread above. Uninstalled the xposed installer. Reinstalled the xposed installer apk. Updated Xblast tools to the latest version. Problem seems to have gone away. Will have to see what happens after I flash the next nightly, however. This might have something to do with the ROM overwriting /system
I came across this thread after Googling the issue I was having. I am also rooted, running 4.4.4 (CarbonROM on the Nexus 7 and stock on Moto X), and am running Xposed on both my Nexus 7, and on my Moto X. Suddenly last night I rebooted (first the N7, and then this morning the X), and lo and behold, System UI crashed on both.
I then restored my most recent nandroids on both (within a week), and all good again. Then updated all my apps that needed updating. Rebooted again because the Moto X froze, and again, System UI crash. That got me thinking that an app that was updated may be the culprit. So I updated each of my apps that had updates available one-by-one, and rebooted after each one. All good, until I came to Google+. When Google + updated, and then I rebooted, BOOM. System UI crash. Not sure if this is a conflict with Xposed or a coincidence, but Google + is definitely causing the issue for me. Hope this helps.
EDIT: I will try uninstalling Xposed then updating Google+, and report back.
UPDATE: After once again restoring my latest Nandroid, I uninstalled Xposed, rebooted, and updated all of my apps, including Google+. Rebooted, and all was good. I then went to re-install Xposed, and noticed that there were a few modules, XBlast, Gravity Box, and App Opps, that had updates available. I downloaded and installed the updates, then re-installed Xposed and rebooted. All is fine again.
sn2hotty said:
I came across this thread after Googling the issue I was having. I am also rooted, running 4.4.4 (CarbonROM on the Nexus 7 and stock on Moto X), and am running Xposed on both my Nexus 7, and on my Moto X. Suddenly last night I rebooted (first the N7, and then this morning the X), and lo and behold, System UI crashed on both.
I then restored my most recent nandroids on both (within a week), and all good again. Then updated all my apps that needed updating. Rebooted again because the Moto X froze, and again, System UI crash. That got me thinking that an app that was updated may be the culprit. So I updated each of my apps that had updates available one-by-one, and rebooted after each one. All good, until I came to Google+. When Google + updated, and then I rebooted, BOOM. System UI crash. Not sure if this is a conflict with Xposed or a coincidence, but Google + is definitely causing the issue for me. Hope this helps.
EDIT: I will try uninstalling Xposed then updating Google+, and report back.
UPDATE: After once again restoring my latest Nandroid, I uninstalled Xposed, rebooted, and updated all of my apps, including Google+. Rebooted, and all was good. I then went to re-install Xposed, and noticed that there were a few modules, XBlast, Gravity Box, and App Opps, that had updates available. I downloaded and installed the updates, then re-installed Xposed and rebooted. All is fine again.
Click to expand...
Click to collapse
Yea it was XBlast that caused the issue. I fixed it by disabling Xposed with the key taps, updating all the modules and then rebooting.
Since I upgraded to 8.1 touching anything in the notification drawer crashes System UI. Restarts with next screen on, but I can't do anything via the notification drawer, which is irritating.
I root (and usually theme) my phone (Pixel) - before upgrading I disabled and uninstalled the theme. Tried installing the OTA with flashfire, lost root, dirty flashed the full system image for 8.1 via fastboot. The system UI problem started immediately; I have since rooted the phone by flashing a Magisk created patched boot image, as you would expect the crashing system ui persisted, but it was definitely there before rooting.
I haven't themed since the upgrade and have tried everything suggested here:
http://www.blogtechtips.com/2017/02/28/fix-unfortunately-system-ui-stopped-working-android/
except factory reset. In summary that included reset app preferences, disable all non system apps that use the notification drawer, return to default pixel launcher, clear cache for system UI. The problem persists.
I don't want to wipe my phone atm because rl is busy, can anyone suggest another fix? It doesn't seem to be a widespread problem, but has anyone else encountered it?
TIA