-
-
Notifications
You must be signed in to change notification settings - Fork 249
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; navigation recents button stops working #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. |
Yeah, unfortunately can confirm the random black screen problem with home button is still occurring, sometimes accompanied by the Olauncher isn't responding, force close or wait popup and I also noticed default launcher gets reset, as I'm asked which launcher I want to use after force closing the application. |
@rottenwheel Would you try these 2 things separately and report if it makes any difference -
|
Noted, on it. I am turning auto keyboard off first. For what it is worth what I've been getting the most of is, hit home screen from an application, screen turns fully black, nothing comes through. Either pull down notification bar, go to system settings by tapping on gear icon and then do home button again, this time it'd work ok, or press recents button, then home button would work. Not sure what's up. I am very used to my daily driver keyboard application, but I'll see what I can do for 2 if 1 doesn't improve the situation the next few days. Will report back. Thanks. Edit: black screen just happened again about 5-10 minutes after I turned auto keyboard setting off. Err... |
OK, turnin off auto keyboard did not help at all, if anything, I think it made it worse. I am currently testing with a different keyboard application, will give it a day or two, if I can... It's tedious, too many mistakes. Used to daily driver. |
Can confirm it happens in both tested scenarios, much less often with a different keyboard application though. Main is Swiftkey, alternative is FUTO. |
Any hints on this yet? Upgraded to v4.3.3 hoping for some improvement. 😅 |
@tanujnotes GrapheneOS people are saying it might be outdated SDK target versions for applications and recommended reaching out to developers; especially for those running Android 14 or 15. Thoughts? Forum comment. |
@rottenwheel We are targeting Android 14 so that shouldn't cause any issue with Olauncher. |
@tanujnotes I have been running Android 15 for a couple weeks and likely most GOS users as well, FWIW. |
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: