-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MediaButtonReceiver and KEYCODE_HEADSETHOOK #1581
Comments
@icbaker I was going to post in the previous issue, but thought this is perhaps unique enough for a new issue. |
Would you be able to clarify if this is a change/regression introduced in 1.4.0 (i.e. not present in 1.3.1, and maybe caused by c64dacf), or a longstanding inconsistency where we are not handling |
The code in question is quite old: This part exists over a year, so it is not a problem introduced in 1.4.0. The issue is here:
Whereby |
Issue: #1581 #cherrypick PiperOrigin-RevId: 662515428
Thanks for the extra info - this should be resolved by the commit linked above. |
Issue: androidx#1581 #cherrypick PiperOrigin-RevId: 662515428
Version
Media3 main branch
More version details
No response
Devices that reproduce the issue
SDK_INT >= 26
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Not tested
Reproduction steps
adb shell input keyevent 79
Expected result
The App should behave as if a play event was received.
Actual result
The App delivers
Related issue: #1493
The headset hook key event is not taken into account when only allowing a play command through the MediaButtonReceiver.
Media
n/a
Bug Report
adb bugreport
to [email protected] after filing this issue.The text was updated successfully, but these errors were encountered: