mirror of
https://github.com/advplyr/audiobookshelf-app.git
synced 2026-07-31 08:58:48 +02:00
Progress percentage not shown correctly / only updated on app restart #685
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#685
Reference in New Issue
Block a user
Originally created by @0verEngineer on GitHub (Sep 3, 2023).
Steps to reproduce
Expected behaviour
Actual behaviour
Environment data
Audiobookshelf Version:
Android Issue
Android version: 13
Device model: Google Pixel 7 Pro
Stock or customized system: CalyxOS 4.12.0
@nichwall commented on GitHub (Sep 4, 2023):
Are you referring to the progress percentage here? (There's a few places you could be referring to)
The percentage and time remaining both update in this view without requiring an app restart, but it may only update if you are listening to the book or refresh the page (such as from restarting the app)
Did you resume playing the book after seeking an hour, or only seek? Did the time remaining change but the percentage didn't, or did neither change?
@0verEngineer commented on GitHub (Sep 4, 2023):
Yea i mean this one, both time and percentage are not updating if i randomly select (and of course play) chapters in a book.
@nichwall commented on GitHub (Sep 4, 2023):
I just tested and yes you're correct, it doesn't update until the first sync event to the server (about 30 seconds).
I'm not sure if this is by design, but the long initial sync time is intentional so you have some time to realize you didn't mean to start it or don't want to listen to the book (so it doesn't automatically show up on Continue Listening)
@advplyr commented on GitHub (Nov 18, 2023):
This is intentional as it updates when the progress sync happens
@0verEngineer commented on GitHub (Nov 18, 2023):
@advplyr i pressed play and pause multiple times and it did not update, this is intentional?!? :D lol
@0verEngineer commented on GitHub (Nov 18, 2023):
And even if intentional, wrong information is shown to the user, so this is a bug, why do you close this? It affects multiple users as well.
@advplyr commented on GitHub (Nov 18, 2023):
Have you pressed play and listened for at least 15 seconds?
If you are on a metered network you would need to listen for 60 seconds since it syncs less on metered connections.
@0verEngineer commented on GitHub (Nov 18, 2023):
I can't remember, but i think i listened long enough because i wanted to continue with the book.
But imho this is irrelevant, wrong data should never be shown.
How does this happen, is this the old timestamp that is saved locally on the phone bcs then it would make sense to me.
@advplyr commented on GitHub (Nov 18, 2023):
It's relevant because that progress represents where you will pick up at if you force closed the app before the next sync happens. We don't save progress every second to prevent making many requests to the server. Progress is saved every 15 seconds for unmetered connections.
@0verEngineer commented on GitHub (Nov 18, 2023):
Ok, as i said i think i played longer then 60 seconds because i found this bug/problem as i started to listen to an audiobook.
I understand the reasoning behind this, but when we start playing, we already hit the server for the audio stream (idk how this is implemented). But why does the app/web interface not load the progress after starting the stream?
And the app/web could also query the audiobook info when i click on it to show the details/play page. I think this way wrong info is never shown.
Btw: does a way to sponsor the project exist? I use it almost daily and i love it...