Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System framework not responding. Exiting #2141

Open
LucasBS1 opened this issue Jul 4, 2022 · 2 comments
Open

System framework not responding. Exiting #2141

LucasBS1 opened this issue Jul 4, 2022 · 2 comments

Comments

@LucasBS1
Copy link

LucasBS1 commented Jul 4, 2022

System framework not responding. Exiting

This message shows up when I attempt to open GravityBox

I can only find old threads for this message on google, but the problem is there.
Apparently every android version has it...

All of them tell me to install on the internal memory (does anyone still install on SD ?), or to reboot, or to nuke dalvik and cache (done and done. Lost all my lucky patched apps). Other asks me to install from the APK instead from the module repository (the repository doesn't even exist anymore)...

GravityBox [P] 9.2.1
LSPosed 1.8.3 (API 93)
MotoG6 XT-1925-5
PPS 29.55-37

The system interface... Phone... Clock... Gboard... All of those were already selected when I opened LSPosed

@Arrowpuppet
Copy link

I was having the same issue, so I checked the logs on LSPosed. It told me that I had the wrong version of GravityBox downloaded. I guess I misread the page for the [R] version and thought it was compatible with Android 10.

I downloaded the correct version, which worked fine after a reboot.

Would you be able to check your logs to see if LSPosed shows a similar error?

@LucasBS1
Copy link
Author

Thank you for the support

But this thing fixed itself

I deleted the log to let LSPosed generate a clean one, AND I uninstalled GravityBox.

Upon reinstalling, it fixed itself.
But I have done this many times before, always rebooting, but never making any difference

This thing fixed itself, but it doesn't mean the problem won't happen again to other users

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants