Listening progress skipping backwards #1

Closed
opened 2026-04-24 23:01:37 +02:00 by adam · 3 comments
Owner

Originally created by @scorpio862 on GitHub (Sep 12, 2021).

This app is great but I can see one problem with it.
When I'm listening to audiobook on my mobile phone this application is working in the background and I use the media notification to play and pause the book. But then, when I open this app, the progress of the currently listened book is skipping backwards a lot and I have to manually search the timeline to adjust the progress of the audiobook. This happens quite often.

I'm guessing this happens because when I open the app, it takes the listening progress of the book from the server which is not up to date.
Is it possible to store the progress in the android app so it doesn't download out of date data from the server?

I only listen to audiobooks using this app and never with web browser so I don't really need the listening progress to be downloaded from the server.

Originally created by @scorpio862 on GitHub (Sep 12, 2021). This app is great but I can see one problem with it. When I'm listening to audiobook on my mobile phone this application is working in the background and I use the media notification to play and pause the book. But then, when I open this app, the progress of the currently listened book is skipping backwards a lot and I have to manually search the timeline to adjust the progress of the audiobook. This happens quite often. I'm guessing this happens because when I open the app, it takes the listening progress of the book from the server which is not up to date. Is it possible to store the progress in the android app so it doesn't download out of date data from the server? I only listen to audiobooks using this app and never with web browser so I don't really need the listening progress to be downloaded from the server.
adam closed this issue 2026-04-24 23:01:37 +02:00
Author
Owner

@advplyr commented on GitHub (Sep 13, 2021):

You are correct, it was not storing progress locally. I think this is resolved in v0.8.0-beta that just went live. I went over some details about the offline support here.

When a connection with the server is established all of your local audiobook progress will be synced with the server based on the last update timestamp.

@advplyr commented on GitHub (Sep 13, 2021): You are correct, it was not storing progress locally. I think this is resolved in `v0.8.0-beta` that just went live. I went over some details about the offline support [here](https://github.com/advplyr/audiobookshelf/issues/14#issuecomment-917744526). > When a connection with the server is established all of your local audiobook progress will be synced with the server based on the last update timestamp.
Author
Owner

@Budlyte commented on GitHub (Sep 20, 2021):

This is still happening in the app. I've noticed it more when listening in the car, the player runs on the notification screen but when I open the app it continues to display another time (Maybe what it thinks the server time is).

Example 1
Screenshot_20210917-082530
Screenshot_20210917-082537

Example 2
Screenshot_20210918-094901
Screenshot_20210918-094908

It seems like it may have to do with the connection, notice the disconnected status in my examples. I noticed that when the connection is available and I open the app the time displays the old value for a second and then updates. So the disconnect appears to be that the app running in the background isn't getting the updated timestamps from the player.

@Budlyte commented on GitHub (Sep 20, 2021): This is still happening in the app. I've noticed it more when listening in the car, the player runs on the notification screen but when I open the app it continues to display another time (Maybe what it thinks the server time is). Example 1 ![Screenshot_20210917-082530](https://user-images.githubusercontent.com/4451365/134044838-93acb197-0198-47fa-bc21-ee6ee3d2e6c2.png) ![Screenshot_20210917-082537](https://user-images.githubusercontent.com/4451365/134044862-017d0f9c-d249-4489-9377-3a65300707fd.png) Example 2 ![Screenshot_20210918-094901](https://user-images.githubusercontent.com/4451365/134044898-cdae1757-dda4-4df3-822c-ac261477edc9.png) ![Screenshot_20210918-094908](https://user-images.githubusercontent.com/4451365/134044912-9f0e165f-fdc4-49e4-bf23-11b5eb723355.png) It seems like it may have to do with the connection, notice the disconnected status in my examples. I noticed that when the connection is available and I open the app the time displays the old value for a second and then updates. So the disconnect appears to be that the app running in the background isn't getting the updated timestamps from the player.
Author
Owner

@advplyr commented on GitHub (Sep 20, 2021):

I had this issue also on the old version, but I can't reproduce it on the newest version.

Can you make sure you are running v0.9.0-beta and provide a few steps on how I can reproduce it?

While testing it I noticed a bug when listening offline, then connecting to the server, it does not sync your currently playing audiobook correctly.

@advplyr commented on GitHub (Sep 20, 2021): I had this issue also on the old version, but I can't reproduce it on the newest version. Can you make sure you are running `v0.9.0-beta` and provide a few steps on how I can reproduce it? While testing it I noticed a bug when listening offline, then connecting to the server, it does not sync your currently playing audiobook correctly.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf-app#1