Unable to start A2DP Connect2 in Android 4.3

[GoogleCodeExporter]

What steps will reproduce the problem?
1.installed widget
2.unable to place on desktop
3.

What is the expected output? What do you see instead?
Expect to see widget on desktop

What version of the product are you using? On what operating system?

Version 1.0.2
Please provide any additional information below.

Trying to instal on Asus 10.2 tablet Android V4.3

Original issue reported on code.google.com by RDForsb...@gmail.com on 18 Apr 2014 at 4:03

[GoogleCodeExporter]

This will be hard for me to fix since I don't have a device with Android 4.3 or 
even 4.2.  I have 4.1.2 and 4.4.  Are there any errors?  What happens exactly? 
Do you have Bluetooth ON before trying to place a widget? 

Original comment by JimR...@gmail.com on 26 May 2014 at 7:04

• Changed state: Accepted

[GoogleCodeExporter]

Issue 6 has been merged into this issue.

Original comment by JimR...@gmail.com on 26 May 2014 at 7:04

[GoogleCodeExporter]

I am putting CM10.2 on a Bionic now to test.  Hopefully I can recreate the 
issue.  Thanks for posting.

Original comment by JimR...@gmail.com on 26 May 2014 at 7:52

[GoogleCodeExporter]

I ran it on the Bionic with CM10.1 (Android 4.2) and it worked fine.  Upgrading 
to 10.2 (4.3) now to retry....

Original comment by JimR...@gmail.com on 26 May 2014 at 9:37

[GoogleCodeExporter]

I now installed CM10.2 on the Bionic and tested it.  Everything worked fine.  I 
cannot duplicate the problem at this point.  

I did have issue with my Droid MAXX when I first got it.  A later OS upgrade 
fixed the issue though.  I suspect certain OS'es modified by the OEM's are 
causing the issue since I am using Android interfaces that are not public.  I 
use reflection to access them which is non-standard practice and likely not 
tested by the OEM's. I was not able to fix it on the MAXX but was lucky enough 
that Motorola did fix it on the OS upgrade I got a few months after I got the 
device. 

I will leave this issue open pending further investigation or a device I can 
duplicate the issue on.

Original comment by JimR...@gmail.com on 26 May 2014 at 9:51