Database Info

Gestures not working after OTA

I did the OTA by flashing the stock recovery, then twrp. Also had to flash super su again since I lost root. Now none of the gestures are working. Also noticed the terminal (or data usage) icon pops up in the top left every once in a while. Kinda annoying
Sent from my HTC6525LVW using Tapatalk

It's not an xposed module as I uninstalled xposed but the gestures still are not working. Anyone?
Sent from my HTC6525LVW using Tapatalk

Bump
I've ran into this same issue- updated via OTA this morning and gestures stopped working
Rooted with Titanium Installed as well- anybody have suggestions on this?

I tried reverting back to stock everything with s off and took the OTA. Gestures still didn't work.
Sent from my HTC6525LVW using Tapatalk

I had this happen too. Uncheck the box (to turn them off) and see if they work. If they do, check the box (to turn them on) and reboot.

Antny6 said:
I had this happen too. Uncheck the box (to turn them off) and see if they work. If they do, check the box (to turn them on) and reboot.
Click to expand...
Click to collapse
I actually had the same issue and just unchecked to disable. rebooted. once the phone came back up, i enabled again and it seems to be working..

That hasn't worked for me.
Sent from my HTC6525LVW using Tapatalk

I'm having the same issue. I tried everything but I can't get the gestures to work in the latest software release.

Factory reset fixed it for me.

z-man79 said:
Factory reset fixed it for me.
Click to expand...
Click to collapse
Yup. Tried this yesterday and worked.
Sent from my HTC6525LVW using Tapatalk

Offtopic, but where'd you find the stock recovery image? I tried using the one here:AIO VZW M8 Developer Resource Thread but it's not working to install.
Just wondering if you got it from someplace else.

Factory reset did the trick for me as well...
I was running weak sauce so so my ROM was untouched and was able to run a reset from settings menu

[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

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

Settings keeps stopping

Hello fellows
Sorry for my poor English in advance,
Since I installed the new system update I'm having a problem that whenever I go in display settings exactly I instantly get kicked out to the home page with the "settings keeps stopping" popping up. You should know that I installed the update while my phone is rooted and I used to have rooted themes as well. My phone was unrooted after the update but I got it rooted again now.

W4LUIZ said:
Hello fellows
Sorry for my poor English in advance,
Since I installed the new system update I'm having a problem that whenever I go in display settings exactly I instantly get kicked out to the home page with the "settings keeps stopping" popping up. You should know that I installed the update while my phone is rooted and I used to have rooted themes as well. My phone was unrooted after the update but I got it rooted again now.
Click to expand...
Click to collapse
Disabling the theme might fix the issue.

adizz4 said:
Disabling the theme might fix the issue.
Click to expand...
Click to collapse
Can you please explain to me how to do that?

W4LUIZ said:
Can you please explain to me how to do that?
Click to expand...
Click to collapse
I'm assuming you are using substratum for theming. The applied theme might be causing settings to crash.

adizz4 said:
I'm assuming you are using substratum for theming. The applied theme might be causing settings to crash.
Click to expand...
Click to collapse
No actually I flashed the theme with TWRP and then it appeared in the settings. I wanna uninstall it but I'm not sure how

W4LUIZ said:
No actually I flashed the theme with TWRP and then it appeared in the settings. I wanna uninstall it but I'm not sure how
Click to expand...
Click to collapse
Can't be 100% sure the theme's causing it to crash. Process of elimination is probably the way to go IMO.

Question Pixel Launcher broken after March update

I updated to March firmware the same way I always do. After the phone restarted pixel launcher crashes when using the Google search bar at the bottom of main page. I can manually add the search bar widget on another page and it works. The most frustrating thing though is recent apps no longer functions when swiping up. I've reinstalled March firmware without wiping and it doesn't fix it. I've also cleared data from the pixel launcher to no avail. I am rooted stock and the same problem persists with all magisk modules deactivated and after reinstalling firmware before Magisk is installed. I'm hoping someone has an idea of how to fix this without wiping my phone and starting over. I've attached a short screen recording of the issue. Any help would be appreciated.

Uninstall Pixel Launcher updates from Play Store and install it back
had the same problem and thanks to
@nomfway i fixed it see post 2103 here https://forum.xda-developers.com/t/march-13-2023-tq2a-230305-008-c1-global-a3-windtre-canada-unlock-bootloader-root-pixel-7-pro-cheetah-safetynet.4502805/solved mypage-106​

boontje3 said:
Uninstall Pixel Launcher updates from Play Store and install it back
had the same problem and thanks to
@nomfway i fixed it see post 2103 here https://forum.xda-developers.com/t/march-13-2023-tq2a-230305-008-c1-global-a3-windtre-canada-unlock-bootloader-root-pixel-7-pro-cheetah-safetynet.4502805/solved mypage-106​
Click to expand...
Click to collapse
Thanks, that worked perfectly!