Originally created by @LordNyrox on GitHub (Aug 17, 2024).
What was the Problem?
As you can see in the screenshot, listening sessions aren't being tracked correctly. I have checked past sessions, and it seems to have started about two weeks ago.
Steps to Reproduce the Issue
Listen to an audiobook
Let your phone go to sleep automatically
Listen for 20 min or so
And check if tracking is correct
What was Expected?
Listening session time tracking to be precise.
Phone Model
S21 FE
Phone OS
Android 14
Audiobookshelf App Version
Android App - 0.9.76
Installation Source
Google Play Store
Additional Notes
No response
Originally created by @LordNyrox on GitHub (Aug 17, 2024).
### What was the Problem?

As you can see in the screenshot, listening sessions aren't being tracked correctly. I have checked past sessions, and it seems to have started about two weeks ago.
### Steps to Reproduce the Issue
1. Listen to an audiobook
2. Let your phone go to sleep automatically
3. Listen for 20 min or so
4. And check if tracking is correct
### What was Expected?
Listening session time tracking to be precise.
### Phone Model
S21 FE
### Phone OS
Android 14
### Audiobookshelf App Version
Android App - 0.9.76
### Installation Source
Google Play Store
### Additional Notes
_No response_
adam
added the bugwaiting labels 2026-04-24 23:45:53 +02:00
Is the book downloaded on the device?
Can you confirm this happens when the screen is off and when you keep it on the listening time is correct?
@advplyr commented on GitHub (Aug 17, 2024):
Is the book downloaded on the device?
Can you confirm this happens when the screen is off and when you keep it on the listening time is correct?
No, it's on my PC, but I believe the issue is related to the screen timeout. As you can see in the first screenshot, it only tracked about 1 minute, even though I listened for 13 minutes. I had the screen timeout set to 1 minute, so it makes sense. The same thing happened with the 2-minute timeout setting on my phone—it only tracked for 1 minute and 47 seconds.
In the second screenshot, I set the screen timeout to 10 minutes and listened for 3 minutes, and it tracked the correct time. It only seems to not track or be inaccurate when the screen timeout is shorter.
@LordNyrox commented on GitHub (Aug 18, 2024):
No, it's on my PC, but I believe the issue is related to the screen timeout. As you can see in the first screenshot, it only tracked about 1 minute, even though I listened for 13 minutes. I had the screen timeout set to 1 minute, so it makes sense. The same thing happened with the 2-minute timeout setting on my phone—it only tracked for 1 minute and 47 seconds.

In the second screenshot, I set the screen timeout to 10 minutes and listened for 3 minutes, and it tracked the correct time. It only seems to not track or be inaccurate when the screen timeout is shorter.

I also tried version 0.9.72-beta, and the same issue occurred. I set the screen timeout to 30 seconds this time, listened for about 3 minutes, but it only tracked 28 seconds, as seen in the screenshot.
@LordNyrox commented on GitHub (Aug 18, 2024):
I also tried version 0.9.72-beta, and the same issue occurred. I set the screen timeout to 30 seconds this time, listened for about 3 minutes, but it only tracked 28 seconds, as seen in the screenshot.

Can you check the app settings on your device to see what is set for allowing background activities? This will be different per device and per android version. For pixel 6 on Android 14 the settings to look for are in battery usage and mobile data usage.
It used to be under battery optimization settings for the app. Let me know what you find for your device
@advplyr commented on GitHub (Aug 18, 2024):
Can you check the app settings on your device to see what is set for allowing background activities? This will be different per device and per android version. For pixel 6 on Android 14 the settings to look for are in battery usage and mobile data usage.


It used to be under battery optimization settings for the app. Let me know what you find for your device
It was set to Optimised, but I changed it to Unrestricted, and the issue persists. As you can see in the screenshot below, it still isn't tracking correctly.
@LordNyrox commented on GitHub (Aug 18, 2024):

It was set to Optimised, but I changed it to Unrestricted, and the issue persists. As you can see in the screenshot below, it still isn't tracking correctly.

Even with the screen on, the tracking seems to be off. I've been listening for 10 minutes, but it tracked it as 17 minutes.
@LordNyrox commented on GitHub (Aug 18, 2024):
Even with the screen on, the tracking seems to be off. I've been listening for 10 minutes, but it tracked it as 17 minutes.

I have no coding experience, so I don't know if it's even possible or if this makes sense, but in the next update, the app should subtract the Start Time from the Last Time to fix the issue. The problem seems to only be with "Time Listened," and the Last/Start Time is always tracked accurately.
@LordNyrox commented on GitHub (Aug 18, 2024):
I have no coding experience, so I don't know if it's even possible or if this makes sense, but in the next update, the app should subtract the Start Time from the Last Time to fix the issue. The problem seems to only be with "Time Listened," and the Last/Start Time is always tracked accurately.
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 @LordNyrox on GitHub (Aug 17, 2024).
What was the Problem?
As you can see in the screenshot, listening sessions aren't being tracked correctly. I have checked past sessions, and it seems to have started about two weeks ago.
Steps to Reproduce the Issue
What was Expected?
Listening session time tracking to be precise.
Phone Model
S21 FE
Phone OS
Android 14
Audiobookshelf App Version
Android App - 0.9.76
Installation Source
Google Play Store
Additional Notes
No response
@advplyr commented on GitHub (Aug 17, 2024):
Is the book downloaded on the device?
Can you confirm this happens when the screen is off and when you keep it on the listening time is correct?
@LordNyrox commented on GitHub (Aug 18, 2024):
No, it's on my PC, but I believe the issue is related to the screen timeout. As you can see in the first screenshot, it only tracked about 1 minute, even though I listened for 13 minutes. I had the screen timeout set to 1 minute, so it makes sense. The same thing happened with the 2-minute timeout setting on my phone—it only tracked for 1 minute and 47 seconds.


In the second screenshot, I set the screen timeout to 10 minutes and listened for 3 minutes, and it tracked the correct time. It only seems to not track or be inaccurate when the screen timeout is shorter.
@LordNyrox commented on GitHub (Aug 18, 2024):
I also tried version 0.9.72-beta, and the same issue occurred. I set the screen timeout to 30 seconds this time, listened for about 3 minutes, but it only tracked 28 seconds, as seen in the screenshot.

@advplyr commented on GitHub (Aug 18, 2024):
Can you check the app settings on your device to see what is set for allowing background activities? This will be different per device and per android version. For pixel 6 on Android 14 the settings to look for are in battery usage and mobile data usage.
It used to be under battery optimization settings for the app. Let me know what you find for your device
@LordNyrox commented on GitHub (Aug 18, 2024):
It was set to Optimised, but I changed it to Unrestricted, and the issue persists. As you can see in the screenshot below, it still isn't tracking correctly.
@LordNyrox commented on GitHub (Aug 18, 2024):
Even with the screen on, the tracking seems to be off. I've been listening for 10 minutes, but it tracked it as 17 minutes.

@LordNyrox commented on GitHub (Aug 18, 2024):
I have no coding experience, so I don't know if it's even possible or if this makes sense, but in the next update, the app should subtract the Start Time from the Last Time to fix the issue. The problem seems to only be with "Time Listened," and the Last/Start Time is always tracked accurately.