NPE when connecting using a MediaController [142925848]

Fixed

Bug

Status Update

No update yet.

Description

jo...@gmail.com

created issue #1

Oct 18, 2019 11:19AM

Using androidx.media2:media2-session:1.0.1.

Code to connect:

if (sessionToken != null) {
mediaController = MediaController.Builder(activity)
.setSessionToken(sessionToken)
.setControllerCallback({ it.run() }, this)
.build()
}

Stacktrace:

java.lang.NullPointerException: Attempt to invoke virtual method 'boolean androidx.media2.session.SessionCommandGroup.equals(java.lang.Object)' on a null object reference
at androidx.media2.session.MediaControllerImplLegacy$ControllerCompatCallback.onPlaybackStateChanged(MediaControllerImplLegacy.java:1201)
at android.support.v4.media.session.MediaControllerCompat$Callback$MediaControllerCallbackApi21.onPlaybackStateChanged(MediaControllerCompat.java:917)
at android.media.session.MediaController$MessageHandler.handleMessage(MediaController.java:1174)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.HandlerThread.run(HandlerThread.java:67)

Comments

jo...@gmail.com <jo...@gmail.com> #2Oct 18, 2019 11:21AM

Update: I was able to downgrade to 32.1.10 and I can confirm it's smooth again. The issue is indeed in emulator version 33.1.1

gy...@google.com <gy...@google.com> Oct 21, 2019 02:07AM

Reassigned to gy...@google.com.

gy...@google.com <gy...@google.com> #3Oct 22, 2019 01:01AM

Reassigned to ja...@google.com.

It's happening to me too and I also confirm that reverting to 32.1.10 fixes the issue.

We should have an easier way of reverting versions. AS should allow picking the version similarly to how we already do for the other tools in SDK manager.

ap...@google.com <ap...@google.com> #4Dec 9, 2019 03:24AM

Hi,

would you try to turn on hardware GPU rendering (instead of auto GPU) and see if it fixes this issue?

ja...@google.com <ja...@google.com> Dec 9, 2019 05:24AM

Marked as fixed.

ja...@google.com <ja...@google.com> #5Jan 7, 2020 01:49AM

Hi,

I'm currently not able to change this option, it is greyed out.

ap...@google.com <ap...@google.com> #6Jan 9, 2020 06:55AM

Hi,

there are 2 ways to set it:

1. use a google_apis image (instead of google_apis_playstore). it will re-enable the option.
2. go to your avd folder (usually located in ~/.android/avd/your_avd_name.avd/), open config.ini and hardware-qemu.ini, then modify those lines:

hw.gpu.enabled=yes
hw.gpu.mode=host

an...@google.com <an...@google.com> #7Jan 22, 2020 03:27AM

Hi,

Yes, option 2 fixes the issue (which also persists on 33.1.2 btw). Even though I get a warning when I start the emulator (see attachments).

Will this option be enabled "out of the box" in a future version?

jo...@gmail.com <jo...@gmail.com> #8Jan 24, 2020 08:17AM

Hi,

we suspect a bug in gpu detection logic on Mac M1, and will try to address it in upcoming releases.

gy...@google.com <gy...@google.com> #9Jan 24, 2020 09:27AM

Hi Devki,

would you help to cp aosp/2451107 to next stable and canary releases? Thank you!

ma...@gmail.com <ma...@gmail.com> #10Oct 4, 2022 08:09PM

Hi Devki,

Could we cherry-pick it to canary release as well? Thanks!