Originally created by @deadchimis on GitHub (Jan 28, 2024).
Steps to reproduce
This is going to be a rough guess of what I did to cause this issue (I think)
Download two books.
Listen using Android Auto to finish book 1
Select Book 2 after Book 1 finishes using Android Auto interface.
Listen to Book 2, and wait.
Attempt to come back to listen later.
Expected behaviour
Correct progress should be saved on different audiobooks. (first audiobook should show finished, second should have correct progress saved/sync'd)
Actual behaviour
Downloaded Book 1 and Book 2 to Audiobookshelf Android App. Listened no issue, progress sync'd.
Drove 2.5 hours morning 1/27, book sync'd fine listening through Android Auto.
Waited 4-5 hours walking around, back into car, progress picked up where left off again using Android Auto.
About 1 hour into 2.5 hour drive home Book 1 finishes. Select Book 2 from android auto (not using the phone directly) listen perfectly without issue 1.5 hours.
Get home, disconnect phone, phone attaches to home wifi, and attempt to listen on phone a few hours later, Book 1 shows halfway completed, Book 2 does not show up as having been listened to at all.
When looking at history of Book1, it looks as though when Book2 was selected, the "progress" may have been applied to Book1 and not Book2. Timing in the history of Book#1 makes sense to when I was listening to Book#2.
Environment data
Audiobookshelf Version: v2.7.2 docker (unraid)
Externally accessible using SWAG reverse proxy docker.
Android App? 0.9.71-beta
iOS App?
Android Issue
Android version: 14 (kernel 6.1.25-android14)
Device model: Samsung Galaxy S24 Ultra
Stock or customized system: Stock
Originally created by @deadchimis on GitHub (Jan 28, 2024).
### Steps to reproduce
This is going to be a rough guess of what I did to cause this issue (I think)
1. Download two books.
2. Listen using Android Auto to finish book 1
3. Select Book 2 after Book 1 finishes using Android Auto interface.
4. Listen to Book 2, and wait.
5. Attempt to come back to listen later.
### Expected behaviour
Correct progress should be saved on different audiobooks. (first audiobook should show finished, second should have correct progress saved/sync'd)
### Actual behaviour
1. Downloaded Book 1 and Book 2 to Audiobookshelf Android App. Listened no issue, progress sync'd.
6. Drove 2.5 hours morning 1/27, book sync'd fine listening through Android Auto.
7. Waited 4-5 hours walking around, back into car, progress picked up where left off again using Android Auto.
8. About 1 hour into 2.5 hour drive home Book 1 finishes. Select Book 2 from android auto (not using the phone directly) listen perfectly without issue 1.5 hours.
9. Get home, disconnect phone, phone attaches to home wifi, and attempt to listen on phone a few hours later, Book 1 shows halfway completed, Book 2 does not show up as having been listened to at all.
When looking at history of Book1, it looks as though when Book2 was selected, the "progress" may have been applied to Book1 and not Book2. Timing in the history of Book#1 makes sense to when I was listening to Book#2.
### Environment data
Audiobookshelf Version: v2.7.2 docker (unraid)
Externally accessible using SWAG reverse proxy docker.
- [x] Android App? 0.9.71-beta
- [ ] iOS App?
#### Android Issue
Android version: 14 (kernel 6.1.25-android14)
Device model: Samsung Galaxy S24 Ultra
Stock or customized system: Stock
this is the screenshot that shows where i would have "restarted" book 1 but I 100% didn't restart the book, i started listening to book 2.
14:49 shows the pause and sync at 07:16:26
@deadchimis commented on GitHub (Jan 28, 2024):

this is the screenshot that shows where i would have "restarted" book 1 but I 100% didn't restart the book, i started listening to book 2.
14:49 shows the pause and sync at 07:16:26
I am also seeing this type of behavior. I am currently on a second pass through a book, and the issue did not happen the first time, so my assumption is that this is a bug that has been introduced in the last year or so.
My process is similar to OP's:
Open Book 1 via Android Auto and listen for 1.5 hours starting at beginning.
Before turning off the car, open ABS app and verify that it is syncing.
Turn off car while looking at ABS app. Still shows it is syncing.
Force close and reopen ABS app. Book 1 starts playing at 1.5 hours.
Listen for 30 minutes via ABS app. Close ABS app with progress at 2 hours.
Next day, turn on car. ABS Android Auto opens automatically and Book 1 starts playing at previous timestamp (2 hours).
After 10 seconds or so, pause Book 1.
Using Android Auto, switch to Book 2. Playback resumes at Book 2's previous location, listen for 30 minutes.
Pause Book 2 via Android Auto
Use Android Auto to switch to Book 1. Playback begins at beginning of book. ABS app on phone also shows 0 progress.
It seems that the listening sessions are not getting logged. Here are the listening sessions that were logged during all of that activity above:
Server: v2.17.5 App: v0.9.77-beta
@gamendorf commented on GitHub (Dec 20, 2024):
I am also seeing this type of behavior. I am currently on a second pass through a book, and the issue did not happen the first time, so my assumption is that this is a bug that has been introduced in the last year or so.
My process is similar to OP's:
1. Open Book 1 via Android Auto and listen for 1.5 hours starting at beginning.
2. Before turning off the car, open ABS app and verify that it is syncing.
3. Turn off car while looking at ABS app. Still shows it is syncing.
4. Force close and reopen ABS app. Book 1 starts playing at 1.5 hours.
5. Listen for 30 minutes via ABS app. Close ABS app with progress at 2 hours.
6. Next day, turn on car. ABS Android Auto opens automatically and Book 1 starts playing at previous timestamp (2 hours).
7. After 10 seconds or so, pause Book 1.
8. Using Android Auto, switch to Book 2. Playback resumes at Book 2's previous location, listen for 30 minutes.
9. Pause Book 2 via Android Auto
10. Use Android Auto to switch to Book 1. Playback begins at beginning of book. ABS app on phone also shows 0 progress.
It seems that the listening sessions are not getting logged. Here are the listening sessions that were logged during all of that activity above:

**Server:** v2.17.5
**App:** v0.9.77-beta
I see similar issues (using android auto, and with auto media play on connection) even when one book is streaming and the other is downloaded. I'm going to try:
only streamed books (none local/downloaded)
disable auto play media on android auto start
@lessthanjoey commented on GitHub (Sep 4, 2025):
I see similar issues (using android auto, and with auto media play on connection) even when one book is streaming and the other is downloaded. I'm going to try:
- only streamed books (none local/downloaded)
- disable auto play media on android auto start
I see similar issues (using android auto, and with auto media play on connection) even when one book is streaming and the other is downloaded. I'm going to try:
Just jumping onto your test plan
only streamed books (none local/downloaded)
I can try streaming the books to see if that makes a difference. But I don't know if streaming would be reliable during my commutes.
disable auto play media on android auto start
Did this help?
@jjcf89 commented on GitHub (Oct 6, 2025):
> I see similar issues (using android auto, and with auto media play on connection) even when one book is streaming and the other is downloaded. I'm going to try:
Just jumping onto your test plan
>
> * only streamed books (none local/downloaded)
> *
I can try streaming the books to see if that makes a difference. But I don't know if streaming would be reliable during my commutes.
> * disable auto play media on android auto start
Did this help?
I see similar issues (using android auto, and with auto media play on connection) even when one book is streaming and the other is downloaded. I'm going to try:
Just jumping onto your test plan
only streamed books (none local/downloaded)
I can try streaming the books to see if that makes a difference. But I don't know if streaming would be reliable during my commutes.
disable auto play media on android auto start
Did this help?
It did not, although perhaps it ties into it.
What I've found is that without closing the player on the phone (menu close player option from within the expanded view of a particular book that's playing), swapping to a different book in android auto will cause it to send updates to the wrong book. I captured some logs of this:
This log started from getting in the car in the morning:
then we listened to How to Fight a Dragon's Fury until dropping my first kid off at 7:48, which all appears correctly synced
minutes later at 8:08 I went to start my audiobook (Eyes of the Void), but you can see from that point it is still trying to sync How to Fight a Dragon's Fury (and now failing each time)
@lessthanjoey commented on GitHub (Oct 7, 2025):
> > I see similar issues (using android auto, and with auto media play on connection) even when one book is streaming and the other is downloaded. I'm going to try:
>
> Just jumping onto your test plan
>
> > * only streamed books (none local/downloaded)
>
> I can try streaming the books to see if that makes a difference. But I don't know if streaming would be reliable during my commutes.
>
> > * disable auto play media on android auto start
>
> Did this help?
It did not, although perhaps it ties into it.
What I've found is that without closing the player on the phone (menu close player option from within the expanded view of a particular book that's playing), swapping to a different book in android auto will cause it to send updates to the wrong book. I captured some logs of this:
[abs_logs_android_0.10.1-beta.txt](https://github.com/user-attachments/files/22733685/abs_logs_android_0.10.1-beta.txt)
This log started from getting in the car in the morning:
- then we listened to How to Fight a Dragon's Fury until dropping my first kid off at 7:48, which all appears correctly synced
- minutes later at 8:08 I went to start my audiobook (Eyes of the Void), but you can see from that point it is still trying to sync How to Fight a Dragon's Fury (and now failing each time)
Just jumping in to say I'm having the same problem and am happy to help try to troubleshoot.
I'm using my android phone with Android Auto and the play history seems to get synced to the wrong book when you switch between books. My son and I swap books during our commute. Right now I don't have any workaround and have to manually seek to the correct location for each book back again each evening.
Both of my books are downloaded locally.
@nm3210 commented on GitHub (Jan 7, 2026):
Just jumping in to say I'm having the same problem and am happy to help try to troubleshoot.
I'm using my android phone with Android Auto and the play history seems to get synced to the wrong book when you switch between books. My son and I swap books during our commute. Right now I don't have any workaround and have to manually seek to the correct location for each book back again each evening.
Both of my books are downloaded locally.
Just jumping in to say I'm having the same problem and am happy to help try to troubleshoot.
I'm using my android phone with Android Auto and the play history seems to get synced to the wrong book when you switch between books. My son and I swap books during our commute. Right now I don't have any workaround and have to manually seek to the correct location for each book back again each evening.
Both of my books are downloaded locally.
I found that if I open the app on my phone, then expand the player if open, then "close player" (assuming it was open), it'll sync properly when swapping to a new book.
@lessthanjoey commented on GitHub (Jan 7, 2026):
> Just jumping in to say I'm having the same problem and am happy to help try to troubleshoot.
>
> I'm using my android phone with Android Auto and the play history seems to get synced to the wrong book when you switch between books. My son and I swap books during our commute. Right now I don't have any workaround and have to manually seek to the correct location for each book back again each evening.
>
> Both of my books are downloaded locally.
I found that if I open the app on my phone, then expand the player if open, then "close player" (assuming it was open), it'll sync properly when swapping to a new book.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @deadchimis on GitHub (Jan 28, 2024).
Steps to reproduce
This is going to be a rough guess of what I did to cause this issue (I think)
Expected behaviour
Correct progress should be saved on different audiobooks. (first audiobook should show finished, second should have correct progress saved/sync'd)
Actual behaviour
When looking at history of Book1, it looks as though when Book2 was selected, the "progress" may have been applied to Book1 and not Book2. Timing in the history of Book#1 makes sense to when I was listening to Book#2.
Environment data
Audiobookshelf Version: v2.7.2 docker (unraid)
Externally accessible using SWAG reverse proxy docker.
Android Issue
Android version: 14 (kernel 6.1.25-android14)
Device model: Samsung Galaxy S24 Ultra
Stock or customized system: Stock
@deadchimis commented on GitHub (Jan 28, 2024):
this is the screenshot that shows where i would have "restarted" book 1 but I 100% didn't restart the book, i started listening to book 2.
14:49 shows the pause and sync at 07:16:26
@gamendorf commented on GitHub (Dec 20, 2024):
I am also seeing this type of behavior. I am currently on a second pass through a book, and the issue did not happen the first time, so my assumption is that this is a bug that has been introduced in the last year or so.
My process is similar to OP's:
It seems that the listening sessions are not getting logged. Here are the listening sessions that were logged during all of that activity above:

Server: v2.17.5
App: v0.9.77-beta
@lessthanjoey commented on GitHub (Sep 4, 2025):
I see similar issues (using android auto, and with auto media play on connection) even when one book is streaming and the other is downloaded. I'm going to try:
@jjcf89 commented on GitHub (Oct 6, 2025):
Just jumping onto your test plan
I can try streaming the books to see if that makes a difference. But I don't know if streaming would be reliable during my commutes.
Did this help?
@lessthanjoey commented on GitHub (Oct 7, 2025):
It did not, although perhaps it ties into it.
What I've found is that without closing the player on the phone (menu close player option from within the expanded view of a particular book that's playing), swapping to a different book in android auto will cause it to send updates to the wrong book. I captured some logs of this:
abs_logs_android_0.10.1-beta.txt
This log started from getting in the car in the morning:
@nm3210 commented on GitHub (Jan 7, 2026):
Just jumping in to say I'm having the same problem and am happy to help try to troubleshoot.
I'm using my android phone with Android Auto and the play history seems to get synced to the wrong book when you switch between books. My son and I swap books during our commute. Right now I don't have any workaround and have to manually seek to the correct location for each book back again each evening.
Both of my books are downloaded locally.
@lessthanjoey commented on GitHub (Jan 7, 2026):
I found that if I open the app on my phone, then expand the player if open, then "close player" (assuming it was open), it'll sync properly when swapping to a new book.