Hi all
I have the following setup:
Desire
Aux Input (for music)
SuperTooth One BlueTooth Hands Free
When I drive, I use the HTC Desire to play the sat nav instructions and music out of the Aux to the stereo however, if I enable Bluetooth, all music and commands are sent through the Bluetooth receiver instead.
On the iPhone, you have the option to route audio through headphones socket or through the BT device - but cannot find out how to do it on the Desire.
Are there any applications that make it possible to route calls out via BT and everything else out over the Aux?
I would really like this functionality too.
One option for you, is to long press the Supertooth in your Desire's bluetooth device list, and edit the options so that it's not a media bluetooth device but only a phone bluetooth device.
Thanks - didnt know about that option!
Does this option actually work for anyone?
I'm connecting to the bluetooth in my Mazda and every time I uncheck Media, it just re-checks it every time I reconnect.
matthewf01 said:
Does this option actually work for anyone?
I'm connecting to the bluetooth in my Mazda and every time I uncheck Media, it just re-checks it every time I reconnect.
Click to expand...
Click to collapse
+1
I'm having the same problem with my bluetooth. Every morning when i connect my bluetooth, i would have to go into the settings to uncheck the "media" part.
Really...is there a fix for this cos i've been doing it everyday for 3 weeks
Scann69 said:
+1
I'm having the same problem with my bluetooth. Every morning when i connect my bluetooth, i would have to go into the settings to uncheck the "media" part.
Really...is there a fix for this cos i've been doing it everyday for 3 weeks
Click to expand...
Click to collapse
Im new to Android so Im not sure which 'version' people reference when sharing firmware versions but my 'software number' is 1.21.405.2 and 'build number' 1.21.405.2CL174215release-keys if that helps anyone out who perhaps ISNT having this problem...
Hello everyone
I am running the Virtuous ROM and I'm having a small problem. Whenever I try to connect to my Kenwood car stereo (Parrot bluetooth hands-free system, I think) I can make and receive calls just fine, only the call lists don't get synced.
I might be wrong, but doesn't one usually have to give the hands-free permission to do that first? Interestingly enough, the two devices are pairing without any kind of password whatsoever. I find this rather strange and an FTP server aside, I haven't found many options to adjust in the bluetooth settings.
Am I missing something obvious here?
Regards and thank you.
Anybody? Anything?
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've switched from running stock, CM10, to AOKP and Liquid Smooth the results are all the same.
I have a belkin bluetooth adapter to add bluetooth to my car ( http://www.amazon.com/gp/product/B004CLYJ2I/ref=oh_details_o02_s00_i01?ie=UTF8&psc=1 [1] )
However, whenever I get in my car I have to toggle bluetooth on and off on my phone to get it to connect.
In my friends car he has a cheapo aftermarket stereo with bluetooth ( http://www.amazon.com/Dual-XML8100-Mechless-Receiver-Remote/dp/B002OR17LS/ref=pd_sim_cps_1 [2] with http://www.amazon.com/gp/product/B000PDR5O6/ref=oh_details_o02_s00_i00?ie=UTF8&psc=1 [3] )
When I tether my phone to his setup it connects automatically every time with no need to toggle anything!
I know its a minor inconvenience but since it works seemlessly on my friends car I know there must be an adapter out there that lets me automatically connect my phone when I enter my car. I guess its just a matter of finding a bluetooth chip the S3 is most compatable with?
So wise people of XDA, what Bluetooth a2dp adapter do you use and does it connect to your S3 automatically?
I'd be open to using an app that toggles my bluetooth off and on but searches have not turned up anything so far
Please note I don't care about the hands aspect I really just want to stream my music.
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...