search

austgl / a2dpvolume

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

Jelly Bean Bluetooth is a mess #146

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Not sure I can fix this as it appears Jelly Bean is riddled with Bluetooth 
integration issues.  I wanted to post this issue for others to see and I will 
look into what I can do to better deal with it.  Some issues include:

Sound pool is a mess.  It gets mixed up on what stream goes where and appears 
to rapidly toggle between them.  When sending a TTS to a stream it will switch 
streams late and then hold the new stream sometimes.
http://code.google.com/p/android/issues/detail?id=27333

Bluetooth toggle connection.  Sometimes devices will quickly connect, 
disconnect, reconnect.  Sometimes this happens multiple times.  Causes problems 
for A2DP Volume as it sees this and tries to respond.

Bad sound stutter when playing music on Bluetooth.  For the first minute or so 
of the A2DP connection the music playback stutters badly.  
http://code.google.com/p/android/issues/detail?id=39633
http://code.google.com/p/android/issues/detail?id=40802

Hopefully they fix these issues soon in Android.  Most of them are posted to 
their issues list already.

Original issue reported on code.google.com by JimR...@gmail.com on 30 Dec 2012 at 2:53

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 29 Mar 2013 at 3:03

GoogleCodeExporter commented 9 years ago 
Found some issues that should give a path to fixing this.  I am using some 
methods that are deprecated in Jelly Bean.  I was basing the app on Android 
2.3.3 for a build target.  When I switched to 4.1.2 the deprecated methods 
showed up.  Now I can probably get this all working right again.  Stay tuned...

Original comment by JimR...@gmail.com on 18 Apr 2013 at 1:29

GoogleCodeExporter commented 9 years ago 
Tested with Android 4.2 and it seems pretty good.  4.1 is the issue.

Original comment by JimR...@gmail.com on 19 Apr 2013 at 1:33

GoogleCodeExporter commented 9 years ago 
I have been working with 4.2 and 4.2 devices now.  4.2 works pretty well 
actually.  Seems the sound pool issues are resolved.  On 4.1 the sound will 
stay rerouted.  I could actually use this to an advantage as stream routing is 
another open issue.  However, it is not really a good way to route streams.  I 
found that if a text message comes in the stream routes to the TTS stream OK 
but then when the music resumes it stays there.  If you pause the music, wait a 
second, and then play again it fixes the problem.  Often 4.1 will also leave 
the music paused after reading the text.

Original comment by JimR...@gmail.com on 21 Apr 2013 at 9:04

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 7 Sep 2013 at 3:57