search

Omeya / a2dpvolume

Automatically exported from code.google.com/p/a2dpvolume
0 stars 0 forks source link

Use Bluetooth device friendly name for ICS #98

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Ice Cream Sandwich implemented the ability to rename Bluetooth devices 
(finally!).  A2DP volume should use this device name when available instead of 
the default name that comes across Bluetooth.

Original issue reported on code.google.com by JimR...@gmail.com on 31 Mar 2012 at 1:23

GoogleCodeExporter commented 9 years ago 
Found this:
http://grepcode.com/file_/repository.grepcode.com/java/ext/com.google.android/an
droid/4.0.1_r1/android/bluetooth/BluetoothDevice.java/?v=diff&id2=2.3.7_r1
ICS added a getAlias() function but I can't access it in the normal way like 
getName().  May need an interface.  Its a public function like getName() but 
does not work the same way for some reason.

Original comment by JimR...@gmail.com on 29 Apr 2012 at 1:01

GoogleCodeExporter commented 9 years ago 
actually I need getAliasName().

Original comment by JimR...@gmail.com on 29 Apr 2012 at 1:04

GoogleCodeExporter commented 9 years ago 
Fixed in 2.8.3 and up.  Added another AIDL file to access getRemoteAlias() 
function.  Checks for Android API >= 11.

Original comment by JimR...@gmail.com on 29 Apr 2012 at 1:52

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision cbc1a4179046.

Original comment by JimR...@gmail.com on 29 Apr 2012 at 1:54

GoogleCodeExporter commented 9 years ago 
We could make this do more.  A2DP Volume could set the device alias name as 
well.  I implemented this in the interface but don't use it yet.  Need to think 
through all the use cases.  In most cases the user will pair the device and 
rename it then before finding that new device in A2DP Volume.  That case works 
fine with the fix implemented in 2.8.3 and up.  

If they instead rename it in Android after finding it with A2DP Volume, then 
the device name is not updated.  Here is where we could sync it back with the 
alias name in Android but that would overwrite any name they had in A2DP 
Volume.  Is this a good thing?

I could add a check in edit device screen.  If you have ICS and up, and the 
alias name is different than the current device name in A2DP Volume, then a 
button would be enabled.  Clicking this mutton would give the user 2 options: 
copy the name from A2DP Volume to Android alias name or copy the Android alias 
name to A2DP Volume.  This gives the user the most flexibility.  However, is it 
really worth all that work?  Great question.  Probably not.  It also adds noise 
to the already very busy edit device screen.

Original comment by JimR...@gmail.com on 29 Apr 2012 at 4:55