Hi, I've got a small issue with my bluetooth a2dp device. The device is this one:
BlackBerry Remote Stereo Bluetooth Gateway. It is made by RIM, but works with any device supporting a2dp. My issue with the Galaxy Nexus is that it no longer auto connects.
My setup is in my vehicle, I keep the bluetooth receiver connected to the aux power jack and aux audio in in the center console. This way, when I start the car, the receiver powers up and tries to auto-connect to the last device. On my vibrant with Android 2.1/2.2 this worked fine. When I dabbled with CyanogenMod and some other custom roms, it stopped working but I chalked it up to some problem with the custom rom.
Now, I'm seeing the same sort of problem: if I keep the screen of my nexus on, I can see the bluetooth icon change blue, and then immediately change back to gray. To me, this indicates that the receiver succeeds in connecting but is then disconnected for some reason. The device only supports a2dp, not the handsfree profile. When I looked into the Android kernel code, I found a place where the kernel will try to connect the handsfree profile if the a2dp profile is auto-connected, but it wasn't clear if that was the actual problem or not.
Anyone else have any similar experiences?
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
bigdawgr6 said:
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
Click to expand...
Click to collapse
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
Click to expand...
Click to collapse
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
jjohns63 said:
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
Click to expand...
Click to collapse
Strangely enough, the phone paired with the device twice without issue yesterday and failed once later on that same day. I'm toggling BT off and then on to get connection for now.
It seems like the phone and device are connecting without issue but I know I haven't done anything to change it. I'm on AOKP M3 and Leankernel V1.8 if that helps. When I first flashed those two, I still had connections issues, so switching to them wasn't a resolution.
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
I have been trying this for weeks and this app solved it!!! Thanks for making the app!
jroal said:
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
Click to expand...
Click to collapse
jjohns63 and bigdawgr6,
Any update on this problem? I don't have the Nexus, but I have Droid Incredible 2. I also run into the same problem when I use CyanogenMod 7.2, which is a AOSP based ROM. The connection is fine with the stock ROM. I have tried to change things in the audio.config but it does not seem to help. I think I ran into a post somewhere saying HTC stock ROM uses a propietary bluetooth stack and AOSP and CyanogenMod uses BlueZ open source stack, and that is where the problem is.
Anyway, it would be nice if you guys can share some info.
Thanks!
I have a new Fire Phone running the stock Fire OS 4.6.1, rooted and with Google Play Store Installed.
My vehicle is a 2007 Chrysler Town & Country with the UConnect feature built in. I have successfully paired my phone already.
The main issue is that I have to manually connect every time I get in the car. After I leave the car or the car is turned off, it disconnects as expected, just never reconnects automatically.
I just switched over from an iPhone 4 and this is a major inconvenience. WIth the iPhone it just worked. If I was on a call and got in the car, it would automatically switch over to bluetooth UConnect and come over the cars audio system.
Is there anyway to make this work properly? I have seen a couple apps in the Play Store that seem to state they can fix this, but I am a little weary of them. Like Bluetooth Auto Connect
Does anyone have any experience with this app or have any other general advice on this? Thanks in advance for any suggestions.
I did also check this thread with no real luck http://forum.xda-developers.com/showthread.php?t=1312576
drewb0y said:
I have a new Fire Phone running the stock Fire OS 4.6.1, rooted and with Google Play Store Installed.
My vehicle is a 2007 Chrysler Town & Country with the UConnect feature built in. I have successfully paired my phone already.
The main issue is that I have to manually connect every time I get in the car. After I leave the car or the car is turned off, it disconnects as expected, just never reconnects automatically.
I just switched over from an iPhone 4 and this is a major inconvenience. WIth the iPhone it just worked. If I was on a call and got in the car, it would automatically switch over to bluetooth UConnect and come over the cars audio system.
Is there anyway to make this work properly? I have seen a couple apps in the Play Store that seem to state they can fix this, but I am a little weary of them. Like Bluetooth Auto Connect
Does anyone have any experience with this app or have any other general advice on this? Thanks in advance for any suggestions.
I did also check this thread with no real luck http://forum.xda-developers.com/showthread.php?t=1312576
Click to expand...
Click to collapse
Does your car have multiple ways to connect a device to the car's stereo via Bluetooth? According to this post, using the steering wheel/voice commands makes a difference versus using the stereo's dials. Another post mentioning the same issue and fix for other phones and cars: https://discussions.apple.com/thread/6760095
Hello, I have some problems with the bluetooth connection to my Seat Leon (2016). Pairing worked fine but once I return to my car only the A2DP profile gets connected. In the car menu media control is working correctly but the phone part is shown as disconnected. The bluetooth connection state in the phone settings shows "connected (no phone)" then.
To fix this I have to manually disconnect and reconnect bluetooth on the phone - afterwards everything is working as expected. This is very annoying though and I had no such issues with my previous Nexus 6P (stock 8.1).
Any suggestions? If there is no solution I try to fix this with tasker, however I'd clearly prefer a "native" solution.
Thanks in advance.
Seems like it's working with the app Bluetooth Auto Connect, will test it more intensively in the next days. But I'm still wondering why it's not working out of the box...
Hi, I have a Joying android 10 head unit 7", I have an Autopmall heads up unit that uses the map app WiiYii, this app is auto connect to heads up unit when opened, you have to have data, location and Bluetooth turned on, the problem I can not find how to turn on the bluetooth on the Joying, no switch, I have installed many BT apps and have found the one that finds the head up unit HYHUD so I know it can be found. I `m hoping that if I can turn on BT It may connect. It will connect to a Samsung A71 android phone and an android 6 tablet, but they can`t keep up with GPS or location, if it can be connect to the Joying it has the the GPS antenna. Thanks for any help I can try. Bill
Same problem with Android 10 Gotech , please help
Helo.
I have chinese android navigation mcwauto 8001 for Audi Q5 8R.
My issue is lack of bluetooth connection when I am using Zlink app.
I am able to connect phone with naviagation via bluetooth, but when I establish android auto connection using USB port the bluetooth connection is lost.
Because of that I am not able to make a call using android navigation/zlink. The call is make by phone speaker instead of bluetooth (android navigation).
What is more I tried several times to force bluetooth connection with my phone when I am using wired android auto, but even I am able to connect bluetooth the connection is lost every time I am trying to call.
When I call I have the message "you are not connected with bluetooth"
My zlink app is 3.9.31 - according to my navigation this is the current version of zlink. I found few newest upgrades but I am not able to install it. Few of them stop installing in about 80%, the rest even installed properly not working, the app just stop responding, and the hard reset are required.
Does any of you know solution for my problem?
The red android auto icon (two triangles) on my navigation are showing and disappearing constantly, does anyone of you know what this is mean?
But it's not an MTCD device new member joined for free support.
Requested moderator move to (Android head-units) forum.
Also, what does seller suggest you do when contacted for support