#Mplayerx threads update#
#Mplayerx threads android#

In your application does the same thread interact with ExoPlayer as run the SurfaceView's window?

They thus need to correctly synchronize with any state that is also touched by the drawing thread.

All SurfaceView and SurfaceHolder.Callback methods will be called from the thread running the SurfaceView's window (typically the main thread of the application).

If you are going to use it this way, you need to be aware of some threading semantics: One of the purposes of this class is to provide a surface in which a secondary thread can render into the screen. Assuming the concrete implementation of SurfaceHolder is SurfaceView then this part of the javadoc seems possibly relevant (emphasis mine): The stack trace looks to me like it's coming via a SurfaceHolder.Callback.

#Mplayerx threads update#

Please also update this issue to indicate you’ve done this.Įrror stack traces doesnt show that my app is involved in it, only androidtv+exoplayer

#Mplayerx threads android#

This could be an Android Studio project on GitHub, or zipped up and sent to using a subject in the format 'Issue #1234', where ' #1234' should be replaced with your issue number.

Can you reproduce this with the demo app, or only with your application? If it's only with your app, please provide a minimal reproducible example that demonstrates the problem in a way that we can build locally. Check the configuration settings in mplayer itself by right clicking the mplayer screen and selecting preferences or use the icon on the player. I followed your repro steps using the demo app and an Android TV emulator running Q but I didn't see any such exception in logcat. Depending on where you got your packages from, make sure you have installed all the dependent packages, codecs, skins, etc. When calling player methods I always do it in this way: See Īt 2.SimpleExoPlayer.verifyApplicationThread(SimpleExoPlayer.java:1953)Īt 2.SimpleExoPlayer.getCurrentTimeline(SimpleExoPlayer.java:1640)Īt 2.(AnalyticsCollector.java:816)Īt 2.(AnalyticsCollector.java:865)Īt 2.(AnalyticsCollector.java:873)Īt 2.(AnalyticsCollector.java:471)Īt 2.SimpleExoPlayer.maybeNotifySurfaceSizeChanged(SimpleExoPlayer.java:1897)Īt 2.SimpleExoPlayer.access$3600(SimpleExoPlayer.java:79)Īt 2.SimpleExoPlayer$ComponentListener.surfaceDestroyed(SimpleExoPlayer.java:2188)Īt (SurfaceView.java:715)Īt (SurfaceView.java:242)Īt (ViewRootImpl.java:1549)Īt (WindowManagerGlobal.java:647)Īt (Activity.java:8027)Īt (ActivityThread.java:4616)Īt (ActivityThread.java:4753)Īt $2500(ActivityThread.java:219)Īt $H.handleMessage(ActivityThread.java:1957)Īt android.os.Handler.dispatchMessage(Handler.java:107)Īt android.os.Looper.loop(Looper.java:214)Īt (ActivityThread.java:7356)Īt .invoke(Native Method)Īt .RuntimeInit$n(RuntimeInit.java:492)Īt .ZygoteInit.main(ZygoteInit.java:930) : Player is accessed on the wrong thread.