-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
[Bug] Random crash after hitting home button from another application #480
Comments
If you haven't already, set the battery to Unrestricted for Olauncher and restart the device once. Let me know if it makes any difference. |
@tanujnotes When I go to Olauncher settings>App battery usage it says it is allowed for background usage and save battery is disabled. Is that what you mean? |
@rottenwheel could you post a screenshot? |
|
@rottenwheel Tap on the 'Allow background usage' text and set it to Unrestricted on the next page. Then restart the phone once. |
@tanujnotes sneaky, that setting. Olauncher has been working much more reliably since, no sudden force closes, nor have I lost functionality of the recents button again. However, every now and then I'll get a full black screen after hitting home button, just navigation buttons and status bar working. It looks like it hangs there. I can only get out of there via recents or pulling status bar down, going into settings, then hitting home button works again. It's odd because it doesn't crash, nor shows me an Olauncher has stopped working message, force close it. Maybe if I let it sit for longer in the black screen? Thanks for your fast responses. |
Got a crash log too. As a side note, from time to time, I notice the recents/apps in background button breaks: tapping on it doesn't trigger any action. The only solution I've found is to reboot my device, though I haven't tried force closing OLauncher to see if the causing agent is Olauncher or something else.
Regardless, that doesn't seem related to hitting home button and getting a black screen, then a force close message with the log...
The text was updated successfully, but these errors were encountered: