Getting wrong position value when using MediaSessionCompat.Callback.onSeekTo() with MediaSessionConnector
See original GitHub issueImplementing the MediaSession
and MediaSessionConnector
on the ExoPlayer Demo and dictating the fast-forward
command through Google Assistant, the returned value by MediaSessionCompat.Callback.onSeekTo()
does not seem to be correct, it looks like it includes extra time.
I’m using the latest ExoPlayer version(2.12.2) and following the MediaSessionExtension lab
Hope you can guide me if I need to set an extra setting or something and sorry if this is an already answered question but I could not find any info related.
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
MediaSessionCompat.Callback - Android Developers
The callback may be set using setCallback. Don't reuse the callback among the sessions. Callbacks keep internal reference to the session when it's...
Read more >onSkipToNext() and onSkipToPrevious() of ... - Stack Overflow
So far onPlay() and onPause() of MediaSessionCompact.Callback get triggered. However while debugging I noticed onSkipToNext() and ...
Read more >MediaSessionConnector (ExoPlayer library)
Handles queue navigation actions, and updates the media session queue by calling MediaSessionCompat.setQueue() . static interface, MediaSessionConnector.
Read more >Add Core Features to Your Android TV Receiver | Cast
Cast Android TV codelab tutorial - Learn step-by-step how to build a Cast-enabled Android TV Receiver app using the Google Cast SDK that...
Read more >The MediaSession extension for ExoPlayer | by Marc Bächinger
Callback when the flag MediaSessionCompat.FLAG_HANDLES_QUEUE_COMMAND is set. MediaSessionConnector.CustomActionProvider. Handles custom media actions specified ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The bug is filed internally and can be tracked internally only I’m afraid. We will update this issue if there is some news.
I think we can close this as fixed. However, please respond here if you still see the issue when using versions of the Google Search App that should have included the fix (i.e., >= 12.18.6).