Audio Books are not resuming from last position played

[stephen_hill 35]

@LukeDefinitely not. I tend to just swipe the playback notification in android to make it go away. (I assume this does not trigger stop event?)

I want to give you a little more information that might be helpful, but obviously complicates the investigation matter...

1. I tend to just switch my car off at the end of the journey, therefore (from the phones point of view), suddenly removing the bluetooth device. I might not look at my phone again for a while.
2. Both places where a finish my commute, home and work, my phone will be switching from 4G to wifi - so changing networks.
3. My emby server is accessed through an nginx reverse proxy.
4. I just noticed that my emby server's time was set to UTC instead of BST (British Summer Time), which is UTC + 1 right now.

Cheers
Stephen

 

[stephen_hill 35]

@LukeI also just wanted to post this morning's logs because, on the surface it looks like everything went ok, but if you look carefully, there are some odd things happening. (Times are in UTC).

2023-07-13 07:34:25.560 Info SessionManager: Playback stopped reported by app Emby for Android 3.3.07 playing Lecture 01. Stopped at 0 ms
2023-07-13 07:34:25.563 Info SessionManager: Playback start reported by app Emby for Android 3.3.07 playing Lecture 08. Started at 1699975 ms
2023-07-13 07:34:26.077 Info SessionManager: Playback start reported by app Emby for Android 3.3.07 playing Lecture 08. Started at 0 ms
2023-07-13 07:35:06.729 Info SessionManager: Playback stopped reported by app Emby for Android 3.3.07 playing Lecture 08. Stopped at 1701248 ms
2023-07-13 07:35:06.908 Info SessionManager: Playback stopped reported by app Emby for Android 3.3.07 playing Lecture 08. Stopped at 1701248 ms
2023-07-13 07:35:07.290 Info SessionManager: Playback stopped reported by app Emby for Android 3.3.07 playing Lecture 08. Stopped at 1701248 ms
2023-07-13 07:35:07.326 Info SessionManager: Playback start reported by app Emby for Android 3.3.07 playing Lecture 01. Started at 0 ms
2023-07-13 07:35:07.358 Info SessionManager: Playback stopped reported by app Emby for Android 3.3.07 playing Lecture 01. Stopped at 1701248 ms
2023-07-13 07:35:07.359 Info SessionManager: Playback start reported by app Emby for Android 3.3.07 playing Lecture 08. Started at 1696248 ms
2023-07-13 07:35:08.851 Info SessionManager: Playback start reported by app Emby for Android 3.3.07 playing Lecture 08. Started at 1701248 ms
2023-07-13 08:00:50.743 Info SessionManager: Playback stopped reported by app Emby for Android 3.3.07 playing Lecture 08. Stopped at 2604218 ms
2023-07-13 08:00:50.803 Info SessionManager: Playback stopped reported by app Emby for Android 3.3.07 playing Lecture 08. Stopped at 2604218 ms

As you can see, playback begins with Stopped at 0 ms and Started at 1699975 ms on the same second - 3ms between them.

Then, 500ms later, there is a Started at 0 ms event.

Then I noticed that my bluetooth was not connected, so I:
  - Paused playback
  - Turned on bluetooth on my phone
  - Pressed play when it had connected
  - Locked my phone and started driving.

So this will explain the stop event at 07:35:06.729 until the final start event at 07:35:08.851.

However, in that time there is a Started at 0 ms event, and then two start events with different timestamps, Started at 1696248 ms and Started at 1701248 ms.

The last 4 lines look normal.

So I have two questions:

1. Why are the random Stopped at 0 ms and Started at 0 ms event?
2. Why does the android client appear to be sending multiple HTTP playback events?

Cheers
Stephen

 

logs.log

[Luke 37254]

On 7/13/2023 at 4:18 AM, stephen_hill said:

@LukeDefinitely not. I tend to just swipe the playback notification in android to make it go away. (I assume this does not trigger stop event?)

I want to give you a little more information that might be helpful, but obviously complicates the investigation matter...

1. I tend to just switch my car off at the end of the journey, therefore (from the phones point of view), suddenly removing the bluetooth device. I might not look at my phone again for a while.
2. Both places where a finish my commute, home and work, my phone will be switching from 4G to wifi - so changing networks.
3. My emby server is accessed through an nginx reverse proxy.
4. I just noticed that my emby server's time was set to UTC instead of BST (British Summer Time), which is UTC + 1 right now.

Cheers
Stephen

 

OK try doing a full stop in the emby user interface and see how that compares. Thanks.