Second BT device no longer connects after upgrading to Android 4.2.2

[GoogleCodeExporter]

Device (phone) brand: HTC
Device (phone) model: One XL
Android OS version: 4.2.2
App version number: 2.9.8
What steps will reproduce the problem?
1. Pair with device A (eg. car hands-free for phone audio)
2. Pair with device B (eg. car A2DP audio for music)
3. Configure device A setting "Also connect to bluetooth device" to connect 
device B
4. Cause device A to connect

What is the expected output?
A connection to device B should be made

What do you see instead?
No connection is made to device B

Please provide any additional information below.
This worked fine before installing an OTA update on my device to Android 
version 4.2.2
Other actions, such as launching an app still work as expected.

My particular situation is that my car's hands-free will connect automatically, 
however the music streaming will not, so I have configured the following:

Handsfree connection triggers music streaming connection which triggers my 
podcast app to launch.

Now the chain is broken because the music streaming does not connect. When I go 
into the BT settings and force it to connect, the podcasting app then launches 
as it should.

This has been an incredibly useful app for me. By automating the connection of 
the car devices and launching my usual listening (podcasts) it saves many taps 
each time I get in the car. I drive a lot for my work.

Thanks for such a useful app. I hope this issue can be resolved easily. I would 
be pleased to provide further information or to do testing if this will help.

Original issue reported on code.google.com by g...@gcsupport.com.au on 18 Sep 2013 at 4:36

[GoogleCodeExporter]

I tested this and it works fine for me.  I can't duplicate your issue.  I have 
a device with CM10.1 (4.2.2) that I am testing with.  

I presume your car kit is only hands free?  If not, make sure it is not 
selected to support A2DP.  You do that in Android Bluetooth settings.  

If you still have problems, try using A2DP Connect2 (available in the play 
store).  It uses the same basic source code to connect as A2DP Volume but has a 
simple widget you place on a home screen to just toggle it on and off.  If it 
works with that, it should work with A2DP Volume.  I am not suggesting this as 
a replacement but more of a test.  I also made a car mode toggle that can be 
used for testing.  Then you can use a car mode virtual device in A2DP Volume to 
trigger the connect to see if that works.  If it does, then it may have 
something to do with timing or profiles on your particular devices.  The car 
mode toggle is available here in downloads.  

Let me know what you find out.

Original comment by JimR...@gmail.com on 18 Sep 2013 at 11:11

[GoogleCodeExporter]

Thank you for testing this, even though you couldn't duplicate the issue.

My car kit does not have A2DP which is why I have a separate A2DP receiver.

I installed A2DP Connect2 as advised, however when attempting to place the 
Widget, it comes up with the error "Unfortunately Bluetooth Share has stopped" 
twice.

I then uninstalled both apps, restarted the phone and reinstalled A2DP 
Connect2, but the result was the same.

Original comment by g...@gcsupport.com.au on 20 Sep 2013 at 9:26

[GoogleCodeExporter]

OK, it looks like you have a problem with your Bluetooth stack on that device.  
I found some similar issues on the web:
http://forum.xda-developers.com/showthread.php?p=31244684

Try wiping your cache.  Often during an upgrade stuff is left in the cache that 
is not actually compatible with the new OS.  
http://forum.xda-developers.com/showthread.php?t=2130328

Another thing you could try is to un-pair and re-pair your Bluetooth devices.  

Original comment by JimR...@gmail.com on 20 Sep 2013 at 11:13

[GoogleCodeExporter]

Thanks for your help. I did try un-pairing and re-pairing earlier, but I will 
try again.

Still working out how to wipe the cache. My device has not been rooted and the 
update was an official update from the carrier (Telstra Australia) and HTC, not 
a custom ROM.

Original comment by g...@gcsupport.com.au on 20 Sep 2013 at 2:50

[GoogleCodeExporter]

There should be a way to wipe the cache even on unrooted devices.  My current 
daily device is also unrooted (Droid Bionic).  There is a button sequence I can 
use to access the stock recovery screen.  

A quick web search yielded this:
http://forum.xda-developers.com/showthread.php?t=2130328
and
http://forums.androidcentral.com/verizon-htc-one/315416-how-clear-cache-partitio
n-stock-recovery-un-rooted-phone.html

Looks like you hold the volume down button during boot.  This can be tricky as 
timing of sequence matters.  It often take me a few tries to get it right.  

Original comment by JimR...@gmail.com on 22 Sep 2013 at 2:47

• Changed state: CanNotFix