mirror of
https://github.com/advplyr/audiobookshelf-app.git
synced 2026-07-26 14:38:39 +02:00
[Enhancement]: Android App Connectivity Enhancement #1183
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf-app#1183
Reference in New Issue
Block a user
Originally created by @LabLover on GitHub (Apr 8, 2025).
Type of Enhancement
None
Describe the Feature/Enhancement
Currently, when the app loses connection with the server (WIFI phasing null, momentary interference, etc.) the app displays an error notification but doesn't appear to try and reconnect automatically. I suggest that the app attempt to reconnect without limit when using WiFi.
Why would this be helpful?
I have a large piece of property and I listen to my books while I am out working the ranch. I have installed an outdoor access point on a raised mast and for the most part it works great and allows me to listen to my books on about 70% of the property. The rest of the area is spotty. When the WIFI signal drops off, the ABS app (android) puts out a red error message about not being able to access the server. This means I have to withdraw the phone from my holster, remove my gloves, dismiss the error and try and start playing the book.
I was wondering if the app can be be adjusted to keep trying to access the server instead of generating the error message which must be dismissed? Iw ill probably solve my issue by raising the AP antenna even higher but I can see where this could help others with WiFi dead-spots on their property.
Thanks for considering my request!
Future Implementation (Screenshot)
Not sure how to describe the appeance.
Audiobookshelf Server Version
2.20.0 Windows
Current Implementation (Screenshot)
No response
@advplyr commented on GitHub (Apr 9, 2025):
Are you referring to the red error icon over the cover in the audio player?
If so, the app is set up to continue trying to reach the server for every sync request. It should go away once it has a successful sync.
@advplyr commented on GitHub (Apr 9, 2025):
Please specify the app version
@LabLover commented on GitHub (Apr 9, 2025):
Version 0.9.79-beta (Android). The error I am talking about is a red rectangle that appears in the bottom 1/3 of the app when streaming a book from the server. When that appears, it seems that it stops trying to connect to the server. Of course this is happening when the WiFi drops out.
@advplyr commented on GitHub (Apr 9, 2025):
Can you take a screenshot?
@LabLover commented on GitHub (Apr 9, 2025):
I will do that, need to refresh my memory on how to do that.
@LabLover commented on GitHub (Apr 9, 2025):
Two screenshots each with different errors.
@nichwall commented on GitHub (Apr 9, 2025):
The first one means you need to enable streaming on cell data (in the settings)
For the second message, I assume that is because you are streaming and hit the end of the buffer. "Playback failed: source error" can mean multiple things, such as unsupported codec for a downloaded file, or the server did not provide a transcode in time for streaming, or a different problem with the file (the error does need to be more descriptive). From your use case, I assume you are getting a source error because you have hit the end of the buffer. You can also download the book for offline listening.
@LabLover commented on GitHub (Apr 11, 2025):
Thanks for the explanation, is there a way to force the app to continue trying to connect via WiFi when the end of the buffer is reached? Also, out of curiosity, how large is the buffer and could there be an option to increase the size of the buffer?
@advplyr commented on GitHub (May 22, 2025):
Connecting back to wifi is up to the device to handle. Abs is just checking if you're connecting to wifi or not. You can see it in the status icon in the app bar.
There is no way to increase the size of the buffer