Galaxy SIII Doesn't Auto Connect to 2012 Kia Sedona

[GoogleCodeExporter]

Device (phone) brand: Samsung
Device (phone) model: Galaxy S3 (SGH-I747)
Android OS version: 4.0.4
App version: 2.8.17
What steps will reproduce the problem?
1. Followed all settings in the help guide
2. Take phone into my car and start car (2012 Kia Sedona EX)
3. Nothing happens - no recognition of the BT connection

What is the expected output? What do you see instead?
App worked the first time I tried it but then failed to repeat.  Tried wiping 
the data and setting up again but no go.

Please provide any additional information below.
Not sure what to try next but I'm willing to help troubleshoot.  I want this 
app to work.

Original issue reported on code.google.com by gene.tei...@gmail.com on 31 Dec 2012 at 6:25

[GoogleCodeExporter]

A2DP Volume does not initiate a Bluetooth connection except as part of another 
device connection.  For instance, if you have a car dock (physical device your 
phone recognizes when you clip the phone into the dock) and you have an A2DP 
Bluetooth receiver then you can have the car dock "connection" respond in A2DP 
Volume by force connecting the A2DP device.  It sounds like your case is that 
you have Bluetooth built into the car.  You have only the car Bluetooth.  You 
are not using a car dock.  In your case the car and phone should automatically 
connect.  Initiating that connection is not dome with my app.  Hands Free 
profile connections auto-initiate when the devices come in proximity.  Its is 
just the A2DP profile that sometimes requires manual connection.  Make sure 
your phone is paired with the car.  It sounds like you have done that.  Also 
make sure your car is set up to connect to your phone and not another phone as 
priority.  Different systems handle this differently.  Ford Sync has a 
configuration for primary device.  Motorola T605 always auto-connects the last 
connected device.  Other handle it differently.

A quick internet search found others with similar issues:
https://community.verizonwireless.com/thread/783974
http://www.kia-forums.com/2011-xm-sorento-forum/81177-issue-ios-6-bluetooth-stre
aming-uvo.html
http://www.kia.com/#/bluetooth
http://www.kia.com/content/media/en/modules/bluetooth/vehicle-quick-reference-gu
ides/2012%20BT%20NON-NAV%20AM-SL-TD-QF-VQ-XM.pdf

Many phones will require you accept the auto connection the first time you 
reconnect after pairing.  Mine does this for instance.  Watch the phone as the 
connect the device.  Sometimes you have to go back into your settings -> 
Bluetooth and then click on your car in the list.  It may then ask you if you 
would like to allow auto-connect.  After you manually connect, then turn OFF 
the car for several minutes to ensure the Bluetooth connection disconnected.  
Now turn the car back on and wait.  Sometimes it takes several seconds or even 
a minute to connect.  Watch the phone for any dialogs asking to allow auto 
connection.

Hope this helps.

Original comment by JimR...@gmail.com on 31 Dec 2012 at 2:06

[GoogleCodeExporter]

Original comment by JimR...@gmail.com on 31 Dec 2012 at 2:23

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by JimR...@gmail.com on 31 Dec 2012 at 2:24

• Changed title: Galaxy SIII Doesn't Auto Connect to 2012 Kia Sedona

[GoogleCodeExporter]

Thank you for the comprehensive response. It appears that my problem is with 
the auto connect feature of my Kia bluetooth system so I'll attempt some of the 
fixes I read about in the forums you provided. You are correct that I am using 
the car BT directly without a dock. 

If I can get the auto connect to work properly, can I expect your app to 
automatically adjust my volume and open apps etc.? or does it still require 
some kind of dock in between? 

Original comment by webmaste...@gmail.com on 31 Dec 2012 at 4:02

[GoogleCodeExporter]

You are correct.  Once you get the auto connect working between the phone and 
car, my app will trigger when the Bluetooth connects and disconnects to the 
car.  Then all the features of my app will work.  Make sure you run the [find 
devices] in my app.  Then edit the car in the list by clicking on it and then 
click [edit].  Select the features you want to use for that car.  Save (button 
at the bottom).

Original comment by JimR...@gmail.com on 31 Dec 2012 at 4:23

• Changed state: CanNotFix

[GoogleCodeExporter]

I was able to auto connect this morning and your app worked perfectly 
recognizing the connection, opening the app I specified and adjusting the 
volumes correctly.  I will keep using it and will post a review after enough 
time to assess it completely with my other BT devices.  I have already tested 
it with the audio jack connection and it worked flawlessly.  Great idea for an 
app - things my iPhone was never capable of and makes me glad I switched.

By the way - information in case others report auto connect problems ......I 
was able to auto connect with the car by making sure my GS3 was not screen 
locked and the BT manager screen in settings was active.  I will test some 
other scenarios to see if it still auto connects when it's not screen locked 
but some other screen is active and the BT manager / settings is not running in 
the background.  Seems to be a flaw in the BT program of the S3 and I'm sure 
there's a workaround for it until it's addressed by Samsung.  I read about 
using NFC tags but this seems to be basically creating a dock by contacting a 
tag that is programmed to trigger certain events and changes to the phone 
settings - still wouldn't force an auto connect from what I can see.  It would 
be better if everything you've provided could be triggered by the presence of 
the BT signal from the car. 

Original comment by gene.tei...@gmail.com on 31 Dec 2012 at 5:44

[GoogleCodeExporter]

Thanks for the update.  I see 2 potential enhancement requests above:

1) Respond to NFC tags.  This would be similar to implementing the home dock or 
car dock, sort of.  The biggest problem I have implementing this now is that I 
don't have a device that supports NFC.  I am due for an upgrade I guess.  Feel 
free to post an enhancement request for this so you are notified of progress.

2) Actively search for nearby Bluetooth devices and respond when a paired 
device comes in range.  This has been requested in the past and I did not 
implement because I would worried about battery power concerns.  If I create an 
active listener it will drain the battery.  I could look deeper to see if there 
is an intent fired when a device is in range but I think I looked before and 
there is not.  If there was it may be possible to do this without effecting 
battery life.  Issue 86 addressed this: 
http://code.google.com/p/a2dpvolume/issues/detail?id=86&can=1&q=range  

Original comment by JimR...@gmail.com on 31 Dec 2012 at 5:52

[GoogleCodeExporter]

I have found on Jelly Bean that you can use A2DP Volumes connect a BT device 
feature to connect the device back to itself.  This helped keep the connection. 
 It seems that JB connects and then disconnects very quickly.  As if it does 
not authorize incoming connections.  Using A2DP Volume to connect it back makes 
it an outgoing connection so it will stay connected.  

To enable this functionality edit the device in the A2DP Volume device list.  
Click the [also connect to Bluetooth device] button.  Find the same device in 
the list and select it.  I tested this on the Xoom and it worked.

Another strange thing I found was that the Xoom would not even stream audio to 
the T605 car kit.  I went in to the Android Bluetooth settings and clicked 
[rename device].  I then left the name and hit OK.  Then it worked.  Go figure. 
 Not sure what that was all about.

Original comment by JimR...@gmail.com on 1 Jan 2013 at 6:07

[GoogleCodeExporter]

I made the change to connect the BT device back to itself and this seems to 
make it more stable.  App seems to be working very well now with streaming 
audio, opening other apps upon connection and auto connecting to my car. 
Doesn't seem to matter anymore whether the S3's screen is locked or what I'm 
doing with the phone. 

Thanks for all the help.

Original comment by gene.tei...@gmail.com on 13 Jan 2013 at 5:10