Hi,
I have come across a scenario related to Media Interface meant for AVRCP 1.3
features.
Kindly please provide your opinions on this.
If the Media Interface "RegisterPlayer" is called before the headset
connection, then player gets registered successfully and all the
Vendor dependent commands are handled properly. And in case of any change in
the track, through the "TrackChanged" Dbus signal
shall be sent with information about "Change of track" and "Start of track".
This scenario will work because we have registered for the
callback "state_changed"(audio/avrcp.c) through "avrcp_register_player"
(audio/avrcp.c) API. When connection is ongoing "state_changed"
callback shall be invoked with state as "AVCTP_STATE_CONNECTING" where in
"player->session" will be initialized.
However if the "RegisterPlayer" is called after the headset connection, then
we will not be able to send the "TrackChanged" signal with
information of "Change of track" and "Start of track". Since the headset is
already connected,"state_changed" callback will not be
invoked, hence in the avrcp_player_event" API "player->session" is NULL.
Is it not necessary to handle the above the mentioned scenario?
Thanks and Regards
Jaganath
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
