Closed GoogleCodeExporter closed 9 years ago
I commented on the android issue with play/pause not working with apps in ICS.
The keycodes that get sent for play/pause changed in ICS for some reason.
This shouldn't be related to the issue of Audible not showing up in media
button router. That's probably something else. I haven't had a chance to look
into it yet, but my first guess is that Audible doesn't list its media button
broadcast receiver in its AndroidManifest.xml.
Original comment by harleens...@gmail.com
on 10 Jan 2012 at 4:12
I raised this as an issue on Audible's beta users forum, and Adam Vollmer (on
the Audible dev team) offered this:
"I'd love for the Media Button Router team to try to enable a workaround for
us/our users. It should be a simple matter of them registering for all media
button events and properly dispatching them explicitly to us. I'd be happy to
answer questions from them to help them get this working in the interim."
Sounds like they'd be willing to make this a reality if you guys have the time.
Adam can be reached via http://groups.google.com/group/audible-for-android-beta
Original comment by steven.g...@gmail.com
on 20 Feb 2012 at 6:35
Just saw MBR dev's prior comment above mine - they do admit that these are the
current issues:
- We register our broadcast receiver programmatically, rather than via the
manifest. ICS doesn't handle this correctly at present.
- We aren't calling registerMediaButtonEventReceiver
For whatever reason, there are other issues on their radar taking precedence,
which obviously is not your problem. Me - I'm just looking for a way to get
AVRCP working with their app, such as it is, until they fix it.
Original comment by steven.g...@gmail.com
on 20 Feb 2012 at 6:38
Hi Steven,
Thanks for confirming that Audible's app is indeed culprit. Unfortunately, all
the changes that need to be made are on their end. There is nothing else I can
do. Several other apps have no problem working with mbr because they follow the
standard procedures for registering for listening to media button intents.
Here's the API they need to use, and more importantly the information on
needing to declare your receiver in the manifest.
http://developer.android.com/reference/android/media/AudioManager.html :
public void registerMediaButtonEventReceiver (ComponentName eventReceiver)
Since: API Level 8
Register a component to be the sole receiver of MEDIA_BUTTON intents.
Parameters
eventReceiver identifier of a BroadcastReceiver that will receive the media
button intent. This broadcast receiver must be declared in the application
manifest. The package of the component must match that of the context you're
registering from.
Original comment by harleens...@gmail.com
on 4 Mar 2012 at 6:24
Original issue reported on code.google.com by
andrew.m...@gmail.com
on 10 Jan 2012 at 3:31