[
https://issues.apache.org/jira/browse/CB-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836135#comment-13836135
]
Tommy-Carlos Williams commented on CB-5504:
-------------------------------------------
I think the best situation would be to fix both this and CB-5505.
1. Inline the phone state listener in Media and stop listening to the one from
Device.
2.
a. Fix the one in device so that it actually works by adding the correct
permissions as per CB-5505 and having it trigger an event that could be
listened for in JS...
b. or maybe even move it out to the core Events.
I think the second step is important as it's a very useful feature that users
should be able to respond to these events in their code if they want.
Does that make sense?
> Telephone events are handled by the Device plugin, but Media needs them to
> know to pause on incoming calls, etc
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CB-5504
> URL: https://issues.apache.org/jira/browse/CB-5504
> Project: Apache Cordova
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Tommy-Carlos Williams
>
> There is a telephony receiver in the Device plugin that sends a message to
> all plugins so that they can handle incoming calls etc.
> Currently the only core plugin that listens for those messages is the Media
> plugin so that it can pause playback when a call comes in.
> There is no documentation for this (before the great plugin break out, there
> didn't need to be) so if you just add the Media plugin, audio playback does
> not pause on an incoming or outgoing phone call.
> I am not advocating moving this into Media as there might be third party
> plugins listening for this. However, I do think that at the least this needs
> to be documented in the docs for the Media plugin/api and possibly even have
> Device as a dependancy for Media.
> There's another bug that is related involving android permissions but I will
> lodge that separately. (See:
> [CB-5505|https://issues.apache.org/jira/browse/CB-5505])
--
This message was sent by Atlassian JIRA
(v6.1#6144)
