On Fri, May 29, 2009 at 1:15 AM, pavan savoy <[email protected]> wrote:
> 1 more observation -- > > 4. on a re-boot, when previously the headset was connection, it does > properly initiate an a2dp connection and succeeds however, after few seconds > it disconnects the a2dp connection but not the hsp/hfp one. This is not the intended behavior. I have also sometimes seen this, but not tracked down root cause. In some cases I think it is the fault of the A2DP headset. Many do not properly clean up L2CAP channel resources internally if L2CAP is not gracefully shut down (for example android hard reboot). So if you try to reconnect A2DP quickly afterwards it will fail. > > > somehow all these are so very consistent, like they were supposed to > happen. > > > On Fri, May 29, 2009 at 12:21 PM, pavan savoy <[email protected]>wrote: > >> Hi, >> >> I see some strange behavior whenever this intent happens >> SINK_STATE_CHANGED. >> >> 1. no song is playing, a2dp connection, play song -- in this case both h/w >> output stream and a2dp stream is opened by the audioflinger. >> >> 2. audio playing locally, a2dp connection -- in this player automatically >> starts playing on bt headset >> where is the a2dp stream opened in this case ? >> >> 3. audio is playing on bt headset, a2dp connection is disconnected -- the >> player pauses the local playback, only when i go back to the music player >> app, the audio is continued. >> where is the h/w output stream opened in this case ? >> >> where in code should i be looking for these things ? >> thanks, any help is appreciated .... >> -- >> --Pavan Savoy >> >> > > > -- > --Pavan Savoy > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
