Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Listening session isn't tracking correctly #1290

Open
LordNyrox opened this issue Aug 17, 2024 · 7 comments
Open

[Bug]: Listening session isn't tracking correctly #1290

LordNyrox opened this issue Aug 17, 2024 · 7 comments
Labels
bug Something isn't working waiting Waiting for OP

Comments

@LordNyrox
Copy link

What was the Problem?

Screenshot_20240817_175603_Samsung Internet
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

@LordNyrox LordNyrox added the bug Something isn't working label Aug 17, 2024
@advplyr
Copy link
Owner

advplyr commented 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?

@advplyr advplyr added the waiting Waiting for OP label Aug 17, 2024
@LordNyrox
Copy link
Author

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.
Screenshot_20240818_002914_Samsung Internet
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.
Screenshot_20240818_003208_Samsung Internet

@LordNyrox
Copy link
Author

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.
Screenshot_20240818_010517_Samsung Internet

@advplyr
Copy link
Owner

advplyr commented 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.

image

image

It used to be under battery optimization settings for the app. Let me know what you find for your device

@LordNyrox
Copy link
Author

Screenshot_20240818_162745_Settings
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.
Screenshot_20240818_165942_Samsung Internet

@LordNyrox
Copy link
Author

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.
Screenshot_20240818_173919_Samsung Internet

@LordNyrox
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working waiting Waiting for OP
Projects
None yet
Development

No branches or pull requests

2 participants