-
Notifications
You must be signed in to change notification settings - Fork 6
Remove 'Focus Launcher is running' notification #24
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
Comments
You understood me in a wrong way. It's just impossible to have a background task without such notifications on new Android's versions. Here is some info about such restriction https://developer.android.com/about/versions/oreo/background. |
But how do other launchers get setup without displaying that notification (Before Launcher, for example)? |
It's quite interesting actually. I've looked at Before launcher screen shots at Google Play. Looks like they use special workaround for this NotificationListenerService. To work without notification it should be properly configured. I've never worked with NotificationListenerService. There is such class in our codebase. And it has appropriate config in AndroidManifest. Why previous developers have decided to make it foreground - I don't know. Never the less, there are two additional services wich are run as foreground service:
|
Interesting. OK, so it sounds like it's possible, but would take some more investigation and work. I say we put this on hold until after the 1.0.0 launch and let the initial user feedback decide when to prioritize this |
As a user, I want to install & use Focus Launcher without seeing any unnecessary notifications, so that I can focus more on using my phone mindfully.
This persistent notification was introduced in #20 (#19). As I understand, the more recent version of Android SDK enforced stricter notifications. It is possible to avoid this notification (by turning Focus Launcher back into a background service, I think).
When @zed13 tried that initially, the app started crashing.
Fgure out how to avoid that notification while maintaining the app's stability.
The text was updated successfully, but these errors were encountered: