From 2815ff1b024ee75a4f56a7ab99deb780466320b0 Mon Sep 17 00:00:00 2001 From: jdong Date: Thu, 2 Aug 2018 10:36:36 -0700 Subject: [PATCH] Tiny cleanup: remove an extra "thread" in the comment for ExoPlayer interface. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=207124509 --- .../src/main/java/com/google/android/exoplayer2/ExoPlayer.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java b/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java index 0a0e2b0147..5780f7b418 100644 --- a/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java +++ b/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java @@ -93,7 +93,7 @@ import com.google.android.exoplayer2.video.MediaCodecVideoRenderer; * #getApplicationLooper()}. This Looper can be specified when creating the player, or this is * the Looper of the thread the player is created on, or the Looper of the application's main * thread if the player is created on a thread without Looper. - *
  • Registered listeners are called on the thread thread associated with {@link + *
  • Registered listeners are called on the thread associated with {@link * #getApplicationLooper()}. Note that this means registered listeners are called on the same * thread which must be used to access the player. *
  • An internal playback thread is responsible for playback. Injected player components such as