finamp icon indicating copy to clipboard operation
finamp copied to clipboard

Playback stops when finamp is not in the foreground

Open csaavedra opened this issue 1 year ago • 46 comments

This started happening to me several days ago. If I switch off the screen or just go to a different app, finamp will stop playback after less than a minute. Going back to the app will resume playback., but sometimes it will just go to the next song in the queue.

I have no battery optimisations enabled for finamp.

I have tried with Allow Low-Priority Status on Pause enabled and disabled, makes no difference.

This happens with both offline mode and streaming from my Jellyfin server.

I'm using a Pixel 7 with Android 15. Version is 0.6.24.

csaavedra avatar Nov 16 '24 08:11 csaavedra

Hey, could you please share some logs? Also, are you able to pinpoint if this started happening after updating to 0.6.24? That was released about a week ago.

Chaphasilor avatar Nov 16 '24 10:11 Chaphasilor

I have the exact same problem with a Pixel 9 Pro on Android 15. Another symptom is the player media control no longer shows up in notifications or lock screen.

shangyuj avatar Nov 16 '24 13:11 shangyuj

This may be because I switched main back to API 34, since the Play Store now requires it. redesign works fine, so maybe there's a dependency update or something that we need to carry over to main

jmshrv avatar Nov 16 '24 14:11 jmshrv

Also, are you able to pinpoint if this started happening after updating to 0.6.24? That was released about a week ago.

This is very likely. The app store app says finamp was updated 6 days ago. I started experiencing this 4 days ago but I wasn't using the app on the days before that, so that might definitely be it. I'll try going back to an older version.

csaavedra avatar Nov 16 '24 17:11 csaavedra

Hey, I’m encountering the same issue on iOS/iPadOS 18.1 using an iPad Pro M1. When Finamp is not in the foreground, playback stops. This happens both in offline mode and when streaming from my Jellyfin server.

•	OS Version: iPadOS 18.1
•	Device: iPad Pro M1
•	Finamp Version: Latest beta version (used to be just too good—now this bug makes it almost unusable)

I’d be happy to provide logs, but they contain too much sensitive information, like my server name and other details. If there’s a way to anonymize or filter the logs, let me know, and I’ll share them to help resolve this issue.

I hate to complain, but you guys have done a terrific job with this application. In fact, I don’t think it has anything to envy to Apple Music. Thanks for your hard work, and I hope this can be fixed soon!

martingagne avatar Nov 16 '24 19:11 martingagne

Interesting that you're seeing it happen on iOS too. I very occasionally have background playback not work (like twice ever) but if it's something that keeps happening that's bad.

As for logs, they're sanitised automatically when you copy/share them. Your server address and token should be censored :)

jmshrv avatar Nov 16 '24 19:11 jmshrv

Attached is the log. I manually censored a bit more since I could still see my fileserver URL and a couple of other things.

This bug is a real bummer because I typically use the app for about 12 hours a day - it’s been such a solid client for Jellyfin until now. Unfortunately, I might need to roll back to the previous version for the time being.

The issue is super consistent: as soon as the iPad or iPhone screen goes dark, or I switch apps, the music stops. Let me know if there’s anything else I can do to help troubleshoot this. You’ve done such an amazing job with this app - I really hope this gets sorted out soon!

sanitized_log.txt

martingagne avatar Nov 16 '24 20:11 martingagne

Same problem here. Playback stops when screen is off after 3-5 minutes. No media controls on notification screen. When I unlock the screen, finamp will start a random track from the album that was previously playing. Started happening in the last week, so likely when the app update occurred.

Pixel 7 pro Android 15 App version 0.6.24

bebopjp avatar Nov 18 '24 02:11 bebopjp

Just reproduced and the only errors right before the audio stop are this. No socket errors from other tasks.

[MusicPlayerBackgroundTask/SEVERE] 2024-11-17 21:13:07.222372: ClientException with SocketException: Failed host lookup: 'redacted' (OS Error: No address associated with hostname, errno = 7), uri=BASEURL/Sessions/Playing/Progress

null

bebopjp avatar Nov 18 '24 02:11 bebopjp

@martingagne thanks for the logs. You said that the previous beta version (0.9.11) workes fine for you, and the bug started appearing with this update?

The intereting thing in the logs is that while the app is paused by the OS multiple times (which is normal and wouldn't normally affect playback), it doesn't seem to have quit completely. In the whole log you shared, which spans almost three days, only one startup is logged.
That means it's probably not a crash.

The Android users reported playback stopping a short while after the app goes into the background, but in your case it's immediately. So it could be a different (perhaps related) issue.

Were you able to downgrade to a previous version?

Chaphasilor avatar Nov 19 '24 16:11 Chaphasilor

Yes, I downgraded to the previous version using the app for managing beta applications on iOS (I believe it’s called TestFlight), and now everything is back to normal. I can listen to music in the car or at work without needing to keep the phone and screen turned on all the time. However, in my case, with the updated version, the music stops immediately as soon as I press the power button to turn off the screen or switch to another app. I believe the downgraded version might expire sometime in December.

On Tue, Nov 19, 2024 at 10:47 AM Chaphasilor @.***> wrote:

@martingagne https://github.com/martingagne thanks for the logs. You said that the previous beta version (0.9.11) workes fine for you, and the bug started appearing with this update?

The intereting thing in the logs is that while the app is paused by the OS multiple times (which is normal and wouldn't normally affect playback), it doesn't seem to have quit completely. In the whole log you shared, which spans almost three days, only one startup is logged. That means it's probably not a crash.

The Android users reported playback stopping a short while after the app goes into the background, but in your case it's immediately. So it could be a different (perhaps related) issue.

Were you able to downgrade to a previous version?

— Reply to this email directly, view it on GitHub https://github.com/jmshrv/finamp/issues/956#issuecomment-2486233688, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEGWKMHPC57SHCZADJAAKND2BNTSFAVCNFSM6AAAAABR4S5WBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWGIZTGNRYHA . You are receiving this because you were mentioned.Message ID: @.***>

martingagne avatar Nov 19 '24 17:11 martingagne

@jmshrv can you look up which dependency versions were used during your build? Pubspec allowed for the latest versions of everything related to just_audio, but maybe you hadn't pulled them yet?
I also couldn't find any significant differences in the pubspec and gradle files between main and redesign, aside from some SDK versions (notably dart 2 vs dart 3).

Chaphasilor avatar Nov 19 '24 17:11 Chaphasilor

Updated dependencies, pushing a new build now. Just tested and it looks good :)

jmshrv avatar Nov 20 '24 16:11 jmshrv

The problem persists for me unfortunately. I'm on Pixel 9 Pro running Android 15 and I've updated the app to the newest 0.6.25 version. There is still no audio control in the notification center, and audio stops playing shortly after leaving the app but resumes after returning to the app. Here are the last two logs copied after returning to the app after audio stopped:

[Chopper/INFO] 2024-11-22 03:27:56.063932: --> POST BASEURL/Sessions/Playing/Progress Content-Type: application/json; charset=utf-8 Authorization: MediaBrowser UserId="cbca3f987e664ea7a945e76ea9610536", Token="TOKEN", Client="Finamp", Device="Pixel 9 Pro", DeviceId="b8e3f517ed788367", Version="0.6.25" content-length: 445

{"CanSeek":true,"Item":null,"ItemId":"2dd616d778fda3eefb0c4f783c5aaef1","SessionId":null,"MediaSourceId":null,"AudioStreamIndex":null,"SubtitleStreamIndex":null,"IsPaused":false,"IsMuted":false,"PositionTicks":2111270000,"PlaybackStartTimeTicks":null,"VolumeLevel":null,"Brightness":null,"AspectRatio":null,"PlayMethod":"DirectPlay","LiveStreamId":null,"PlaySessionId":null,"RepeatMode":"RepeatNone","NowPlayingQueue":null,"PlaylistItemId":null} --> END POST

null

[Chopper/INFO] 2024-11-22 03:27:56.099415: <-- 204 No Content POST BASEURL/Sessions/Playing/Progress x-response-time-ms: 3.9925 date: Fri, 22 Nov 2024 09:27:56 GMT server: Kestrel content-length: 0 <-- END HTTP

null

shangyuj avatar Nov 22 '24 09:11 shangyuj

Thanks for letting me know, I'll keep looking into it. For now, I'd recommend you switch to the beta, which isn't affected by this

jmshrv avatar Nov 22 '24 09:11 jmshrv

@shangyuj were those two logs the only logs that were shown? Or did you just leave out the other logs?
Because it those really are the only logs then the app is definitely getting killed in the background and not just paused.

Chaphasilor avatar Nov 22 '24 19:11 Chaphasilor

I've got the same issue. version 0.6.25. pixel 7a. android 15

DickChang avatar Nov 30 '24 06:11 DickChang

0.6.25 on Pixel 6 with Android 14 has this same issue. It plays for maybe a minute and the just stops. As soon as I unlock the phone and push play it resumes.

rawkhopper avatar Nov 30 '24 22:11 rawkhopper

@DickChang @rawkhopper give the beta a try. You can switch to it through the Play Store at the bottom of Finamp's store page

Chaphasilor avatar Dec 11 '24 22:12 Chaphasilor

I had the same problem on a pixel 9 with Android 15. After switching to the beta provided through google playstore, finamp is working fine again. The media control is also appearing again 👍

@Chaphasilor fyi

Thecrafterja avatar Dec 17 '24 09:12 Thecrafterja

Just to clock in and say "here also - exact same issue".

Recently (I think like...yesterday?) f-droid updated to 0.6.25, and today I'm seeing everything reported here.

I'll try the beta I guess, see what happens.

UPDATE: indeed, the beta seems to be working perfectly :) ALso, thank your for not killing support for older jellyfin like 10.8.13!

demaniak avatar Dec 19 '24 10:12 demaniak

Got a few questions for you:

  1. Playback just pauses and you can just hit play again to resume, yes?
  2. Could it be that the pausing happens right after you receive a notification? Maybe you could try this out with a friend :)
  3. Does the playback progress slider in the media notification keep moving?
  4. To those of you that observed skipped tracks, like @bebopjp and @csaavedra, could you check if Finamp the skipped tracks were reported in the Activity tab of your Jellyfin server's admin dashboard?

Combined with your mentions of missing media notifications (also in #977), I'm now suspecting something being wrong with audio_session or audio_service, which handle audio ducking (reducing volume for notifications, pausing and resuming for calls) and the media notification, respectively.

PS @demaniak we'll try not to enforce a minimum version, but also don't guarantee compatibility for older (minor) versions. So you should try to upgrade as soon as you can!

Chaphasilor avatar Dec 19 '24 12:12 Chaphasilor

Got a few questions for you:

1. Playback just _pauses_ and you can just hit play again to resume, yes?

2. Could it be that the pausing happens right after you receive a notification? Maybe you could try this out with a friend :)

3. Does the playback progress slider in the media notification keep moving?

4. To those of you that observed skipped tracks, like @bebopjp and @csaavedra, could you check if Finamp the skipped tracks were reported in the Activity tab of your Jellyfin server's admin dashboard?

Combined with your mentions of missing media notifications (also in #977), I'm now suspecting something being wrong with audio_session or audio_service, which handle audio ducking (reducing volume for notifications, pausing and resuming for calls) and the media notification, respectively.

PS @demaniak we'll try not to enforce a minimum version, but also don't guarantee compatibility for older (minor) versions. So you should try to upgrade as soon as you can!

  1. Not..exactly. It's weird. When in this state, Just hitting play does nothing. Hitting next, does nothing (where "nothing" is defined as "seems to move to next song but does not play" .BUT, hitting the "play random songs from all songs" - that gets music flowing again. For approx 2 songs, then...back to square one. Mostly. Sometimes I get to 3 or 4 songs.

  2. no notifications (yeah I'm a friendless hermit :p )

  3. No, for me, the slider is stuck at 0 in these cases

  4. Um, just a data point on that from my side - I have in this period also noticed "shortened" tracks - the track would end prematurely and then go on to the next track (or, just stop as explained above).

FWIW, the beta is working very nicely, control widget back in business etc

Regarding upgrade: yeah... the 10.9+ releases has some wonky memory use issues (in some cases/platforms), but I know I'll have to give it a try again sometime in near future :(

demaniak avatar Dec 19 '24 14:12 demaniak

Good news everyone!
Seems like there are some new permissions required for Android 14+ that are requested in the beta but not on stable:
https://github.com/ryanheise/just_audio/issues/1363#issuecomment-2562409290

We'll add the missing permissions and push an update ASAP!

Chaphasilor avatar Dec 26 '24 12:12 Chaphasilor

I'll investigate adding those permissions when I get home later today 🫡

jmshrv avatar Dec 29 '24 09:12 jmshrv

@jmshrv I've already committed the changes ^^

Chaphasilor avatar Dec 29 '24 15:12 Chaphasilor

Okay, we've pushed an update for this now. Should become available on the Play store in a few hours.

Please try it out and let me know if it's fixed!

Chaphasilor avatar Jan 08 '25 21:01 Chaphasilor

Is the latest 0.6.26? Because it's still happening with that version.

erahhal avatar Jan 08 '25 23:01 erahhal

Sorry new user here so I can't speak to prior issues but both 0.6.25 and 0.6.26 do not have the lockscreen / media playback persistent notification, at least on Lineage 22 / Android 15.

But finamp does NOT stop playing when the screen is off.

Other issue reports on the lockscreen were linked here, so I am not sure if the issue is the same or not.

rik-shaw avatar Jan 09 '25 23:01 rik-shaw

Just here to +1 on the issue; no playback notification or permission request on 0.6.24-26, and it doesn't show up in the media drawer, either.

Playback works while the phone is locked, as long as you didn't close the app before locking your phone.

Playback stops a few seconds after switching apps, but the progress bar keeps going in FinAmp while the playback is paused, which also leads to a desync in the progress bar until the song changes; this can lead to funny shenanigans like a song being at 9:08/6:14, but is no real cause for concern.

Tested on Android 14.

EDIT: I noticed I could enable the "Notifications" permission manually via system settings and have done so now. This hasn't affected the issue, as a notification never appears.

EDIT 2: Just wanted to say it seems to be resolved in 0.9.13-beta, so whatever was done there regarding permissions and playback notification must've resolved it 🙂

EmilHeilbo avatar Jan 10 '25 12:01 EmilHeilbo