Volume Adjusts when Bluetooth Device is in Range, not Connected

[GoogleCodeExporter]

Device (phone) brand: HTC
Device (phone) model: Incredible
Android OS version: 2.3.5 (CyanogenMod 7)
App version: main

When I turn my bluetooth headphones on, they do not automatically connect to my 
phone; I have to press play on the device for it to connect. As soon as I turn 
the headphones on, A2DPVolume adjusts the media volume to max.

Expected results are: only change volume levels when connected, not just in 
range.

Original issue reported on code.google.com by mwcarr...@gmail.com on 27 Jan 2012 at 5:29

[GoogleCodeExporter]

What profiles do your headphones support?  Just A2DP or hands free as well?  
Some devices connect as multiple profiles.  Prior to API 11 (Honeycomb) it was 
very difficult to know the nature of the connected device.  You could easily 
tell what profiles it supported (and A2DP Volume shows these if you long press 
on the device in the list) but the nature of the current connection was not 
exposed in the API until 11.  I could make an enhancement for API 11 and up to 
support adjusting media volume only on A2DP connection but I don't think it 
will work for API 10 and older.  

Can you look in the bluetooth menu in Android when this happens and see what it 
says about the connection?  It should show if the device is connected and what 
profiles are active. 

Original comment by JimR...@gmail.com on 28 Jan 2012 at 3:23

[GoogleCodeExporter]

My headphones, Motorola MOTOROKR S9-HD, support both A2DP and handsfree. When I 
turn them on, they do not automatically connect; I have to press the play 
button on them for them to connect. Before they connect, A2DPVolume changes the 
media volume to the specified setting.

Original comment by mwcarr...@gmail.com on 29 Jan 2012 at 7:23

[GoogleCodeExporter]

I suspect it does auto-connect to the hands free profile but then leaves the 
A2DP profile not connected until you press play.  Today my app just looks for 
the device level connection and does not query the currently active profiles.  
Prior to API 11 (Android 3) I could not find a way to determine the currently 
active profiles on a device so I kept it simple.  For API 11 and up I could 
support checking to see of A2DP was active before setting the volume.  I don't 
know of a way to do it for API 10 and older though.  You can see the API levels 
here: http://developer.android.com/guide/appendix/api-levels.html.

I looked at the manual for that device you have. 
http://www.motorola.com/staticfiles/Support/Mobile%20Phones%20Accessories/S9-HD/
US-EN/_Documents/Static%20Files/S9_User_Guide.pdf It states that it 
automatically connects to your phone: "If connected when turned off, when your 
S9 is turned on, it automatically connects with the last hands free device 
(such as a mobile phone) and the last streaming music source it was connected 
to."  This is similar to the Motorola T605 units I have.  Later in the manual 
it also says this: "When turned on, the S9 automatically establishes handsfree 
phone and streaming music connections with the last connected Bluetooth devices 
(phone and/or music devices)." on page 23.

Original comment by JimR...@gmail.com on 30 Jan 2012 at 1:20

[GoogleCodeExporter]

Is this still a problem or should this issue be closed?

Original comment by JimR...@gmail.com on 4 Feb 2012 at 1:06

[GoogleCodeExporter]

I will confirm on Monday, when I'm back at work and have my headphones again.

Thanks!

Original comment by mwcarr...@gmail.com on 5 Feb 2012 at 4:42

[GoogleCodeExporter]

The issue still persists.

Original comment by mwcarr...@gmail.com on 6 Feb 2012 at 1:14

[GoogleCodeExporter]

The fact your units automatically connects per the manual is not something I 
can fix with this app.  Did you read comment number 3 above?  I posted details 
about your device including a link to the manual and references in the manual 
where it states that your device does automatically connect.  A2DP Volume sees 
that connection and responds accordingly. 

Original comment by JimR...@gmail.com on 7 Feb 2012 at 11:39

• Changed state: CanNotFix