leak in the notification

Duplicate Check

• I confirm I searched for existing reports and found no duplicates.

Describe the Bug

SimpMusic's SimpleMediaService enters a notification retry loop that causes a Binder proxy leak, eventually crashing the system after extended background playback.

Steps to Reproduce

1. Start playback
2. Leave app in background overnight (or several hours with screen off)
3. System becomes sluggish / low memory warning triggers

Expected Behavior

SimpleMediaService should either successfully reclaim foreground status or exit cleanly instead of retrying notification posting indefinitely.

App Version

1.2.1

Android Version

EvolutionX / Android 16 (SDK 36)

Device Model

Poco f5

Custom ROM

• I am using a custom ROM

Custom ROM Name (if applicable)

evolution x 11.7

Screenshots (optional)

No response

Log / Error Details

E NotificationService: Package enqueue rate is 6.3. Shedding 0|com.maxrave.simpmusic|2026|null|10297. package=com.maxrave.simpmusic
E ActivityManager: FGS logic changed: [WIU changed] Orig WIU:PROC_STATE_PERSISTENT_UI New WIU:DENIED Orig BFSL:SYSTEM_ALLOW_LISTED New BFSL:SYSTEM_ALLOW_LISTED cmp: {com.maxrave.simpmusic/com.maxrave.media3.service.SimpleMediaService} sdk: 36
E libbinder.BpBinder: Too many binder proxy objects sent to uid 1000 from uid 10229 (6000 proxies held)
E ActivityManager: Uid 10229 sent too many Binders to uid 1000
E AppHost.Android: Low memory. Level : 40. App part of LRU list. Likely to be killed anytime

error_logs_only.txt

Start with SimpleMediaService and the attached error_logs_only.txt, focusing on the notification retry and foreground-service messages. Reproduce extended background playback if possible and trace whether repeated notification posting retains Binder proxies. Done means the service no longer loops indefinitely, avoids the Binder proxy leak, and exits or reclaims foreground status cleanly.