Playback should resume after network connection loss

MartinSt commented

2023-01-27 09:16:00 +00:00

When I listen to a radio station while moving around the internet connection of my phone sometimes gets interrupted.
Sometimes transistor does not to resume the playback when the connection get working again. The play state changes from Playing (arrow to the right) to Stopped (square symbol) without any user interaction.

Transistor should never change its play state unless the user wants it.
When "Play" was selected, transistor should resume the playback if the connection comes back, no matter how long the interruption lasted.

When I listen to a radio station while moving around the internet connection of my phone sometimes gets interrupted. Sometimes transistor does not to resume the playback when the connection get working again. The play state changes from Playing (arrow to the right) to Stopped (square symbol) without any user interaction. - Transistor should never change its play state unless the user wants it. - When "Play" was selected, transistor should resume the playback if the connection comes back, no matter how long the interruption lasted.

👍 1

MartinSt added the

bug

label 2023-01-27 09:16:00 +00:00

serrq commented

2023-01-27 19:23:20 +00:00

Same issue. When internet connection is lost for a long time (> 5 seconds) Transistor is unable to regain playing.

y20k self-assigned this 2023-02-23 08:36:06 +00:00

y20k referenced this issue

2023-02-23 08:40:29 +00:00

Cache Setting #447

y20k commented

2023-02-23 08:40:53 +00:00

Owner

I will look into it.

Note to self: I will probably have to look into LoadErrorHandlingPolicy / DefaultLoadErrorHandlingPolicy.

https://exoplayer.dev/customization.html#customizing-error-handling

https://medium.com/google-exoplayer/load-error-handling-in-exoplayer-488ab6908137

I will look into it. Note to self: I will probably have to look into [LoadErrorHandlingPolicy](https://developer.android.com/reference/kotlin/androidx/media3/exoplayer/upstream/LoadErrorHandlingPolicy) / [DefaultLoadErrorHandlingPolicy](https://developer.android.com/reference/kotlin/androidx/media3/exoplayer/upstream/DefaultLoadErrorHandlingPolicy). https://exoplayer.dev/customization.html#customizing-error-handling https://medium.com/google-exoplayer/load-error-handling-in-exoplayer-488ab6908137

y20k referenced this issue from a commit

2023-02-27 16:35:13 +00:00

changes the reconnection policy (see #446) + replace NotificationHelper with DefaultMediaNotificationProvider

y20k referenced this issue

2023-03-01 14:55:07 +00:00

Cache Setting #447

y20k commented

2023-03-02 16:40:48 +00:00

Owner

a new re-connection mechanism is implemented in the v4.1.4 release
fda691e761

a new re-connection mechanism is implemented in the v4.1.4 release https://codeberg.org/y20k/transistor/commit/fda691e761b2e9f8baf01f2bd6bc16bb5d8aceb4

y20k closed this issue

2023-03-02 16:40:49 +00:00

rckt commented

2023-03-22 15:47:19 +00:00

@y20k I started using the app today and faced this issue. The stream was constantly stopping when I was on mobile network. On wi-fi everything works fine, I guess because of the good uninterrupted connection.

MartinSt commented

2023-05-11 08:44:20 +00:00

Poster

Thank you very much for the improvement.
The behaviour is now much better but I still get issues with connection losses:

Sometimes the playback is not resumed after a recover of the internet connection
The play symbol (triangle) does not always react to user interactions. A user should always be able to instantly change the state of this icon.

Thank you very much for the improvement. The behaviour is now much better but I still get issues with connection losses: - Sometimes the playback is not resumed after a recover of the internet connection - The play symbol (triangle) does not always react to user interactions. A user should always be able to instantly change the state of this icon.

MartinSt reopened this issue

2023-05-11 08:44:21 +00:00

Playback should resume after network connection loss #446