audiobookshelf-app
audiobookshelf-app copied to clipboard
advplyr
[Bug]: Play status sync issue if 2 books have been played on Android Auto
What happened?
On Android Auto I have started playing book A and listened until 1:30 then started playing book B from 5:00 to 5:30. Paused, and then turned off car On next start of car and Android Auto, open ABS Book A can be continued from 5:30, book B can be continued from 5:00 So second books status is not saved, first books progress is dropped and instead second book's playtime is saved to it. Same play status can be seen in the app as well. Note: I am playing in offline mode so no server status sync happened, issue in app itself not server
What did you expect to happen?
Both books' status would be saved where I left it off
Steps to reproduce the issue
- As mentioned in What happened section
Audiobookshelf version
v2.13.3
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
No response
Additional Notes
No response
Are you using android app or web browser. If android app, then +1 from me, but I guess its more like feature request that the app keeps some data offline in local e.g. sqlite database and then sync it with the server. I will write some comments further but if you are playing through web browser, I will raise different FR topic.
My setup is:
- Synology, docker container,
- Android app,
- Wireless android auto connection
The problem in my case is, that wireless android auto connection is unable to work, when connected to VPN, so I think, that it should have local database which would be synced, when I connect back to server. Maybee with timestamp, so if I e.g. 9.9.2024 play half of podcast and on 10.9.2024 I play it directly from server, that the status from 10.9.2024 won't get overwriten, when I sync app on 11.9.2024.
I am using the Android app as well. There seems to be some local status DB, since the app remembers the play states in general and if I just play them on my phone the states are saved correctly. There might be a different behavior when using Android Auto. Maybe it needs a syncs back to the app when playing over AAuto at certain intervals and at pause.
I must try the app without android auto and without connection to server, because I am using it only in combination with android auto and it doesn't remember anything. I stop car, e.g. at fueling station, do the stuff there and return, the podcast I am listening to starts from begining, no state saved (I download files before the trip to the phone). So at the end of journey when I stop the car I just disconnect from car, remembering position and connecting to VPN, sync the time and leave.
Same thing. I even have the issue that if play on Android Auto and the continue on the app on the same device after AA disconnects, it won't have picked up the progress from AA. Same thing when I listen through the browser and then continue in the car. It won't pick up the browser progress.
BTW I can confirm, that without AA and server connection it seems to be saving the state. How can I provide some logs?
By the way, I had remembered that most of my audio players (Apple Music, poweramp) wanted to lift restriction on background use. So I had tried to set unrestricted background run for audiobookshelf and the status seems to be synchronizing between android auto and android app correctly. The only thing that is not working at this moment is, when I get home, connect to wifi, the played podcast episodes won't mark as complete on the server, but I guess thats different topic.
I have tested it with Unrestricted battery settings, but the result is still the same where the second books progress is save onto the first book only. It was worth a try.
I have tested it with Unrestricted battery settings, but the result is still the same where the second books progress is save onto the first book only. It was worth a try.
Ok sorry, I had tried it it worked "two car ways" and then it sometimes works sometimes wont. :-( And I was too happy about it. TBH, this is really great piece of software, but still needs a little polishing. Thanks authors for their work.
I'm pretty sure this has been reported in this repo already if anyone is able to find it
