Repository navigation
Conversation
MusicService posts a temporary foreground notification (ID 101) whenever the service is created or receives an external command. While playback is active the notification is intentionally left in place, assuming Media3 will replace it. Media3 does not always call startForeground(): when no foreground start is required it posts its notification with notify() and detaches the service via stopForeground(false). With a different notification ID the temporary notification was neither replaced nor removed, leaving an ongoing, non-dismissible "Processing playback action..." notification next to the working media notification. Use MusicService.NOTIFICATION_ID for the media notification as well, so every media update replaces the temporary notification and MediaNotificationManager.removeNotification() clears it.
This was referenced Oct 23, 2026
|
cool bro! Thanks |
|
Additional on-device verification for this fix (Samsung Galaxy S20 FE 5G, Android 13): started playback, backgrounded the app, then locked/unlocked the screen. Before the patch, an ongoing non-dismissible "Processing playback action…" notification remained alongside the media notification. With this change, the temporary notification (ID 101) is replaced by the media notification and cleared correctly — only the active media notification remains. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MusicService posts a temporary foreground notification (ID 101) whenever the service is created or receives an external command. While playback is active the notification is intentionally left in place, assuming Media3 will replace it.
Media3 does not always call startForeground(): when no foreground start is required it posts its notification with notify() and detaches the service via stopForeground(false). With a different notification ID the temporary notification was neither replaced nor removed, leaving an ongoing, non-dismissible "Processing playback action..." notification next to the working media notification.
Use MusicService.NOTIFICATION_ID for the media notification as well, so every media update replaces the temporary notification and MediaNotificationManager.removeNotification() clears it.
Prepared with AI assistance; reviewed and verified on-device by me.