Go offline when playback fails without a connection
A track that failed to load, or a station that couldn't fetch more, used to skip three times and stop, even with downloads on the phone. Now a failure checks for a connection, and with none the app goes offline: a queue skips to its downloaded tracks (trying each track once, so a fully missing queue stops with a notice), and a station, which has nothing more to give offline, gives way to all downloads, shuffled. Now Playing stays open through the switch and back. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
d085c169fb
commit
250e721fea
12 files changed
+115
-6
No files matched your search
@@ -180,6 +180,7 @@
|
||||
<string name="notice_station_dry">Couldn\'t load more of this station. Check your connection and try again.</string>
|
||||
<string name="notice_too_many">Several tracks in a row couldn\'t be played. Check your connection and try again.</string>
|
||||
<string name="notice_skipped">Couldn\'t play “%1$s”, so it was skipped.</string>
|
||||
<string name="notice_nothing_downloaded">None of the queued tracks are downloaded. Connect to the internet to play them.</string>
|
||||
<string name="menu_next_track">Next track</string>
|
||||
<string name="menu_play_next">Play next</string>
|
||||
<string name="menu_add_to_queue">Add to queue</string>
|
||||
|
||||
Reference in new issue
Block a user