Ok this might sound a bit dumb to you guys but I'm having a little situation here.
I got tomtom 5.1 and just got the glabalsat bt338 receiver.
I have paired the device with my xda as I have paired a nokia BT headset.
When I switch on the nokia headset and bluetooth, the pda and headset establish a connection automatically.
I would like to do the same for the bt338. As soon as the bluetooth is on, it should establish a connection.
I am not able to do this. I have to click on the bluetooth manager, double click the bt338 for it to establish the connection. Then I have to exit bt manager and turn on tom tom. Still tomtom does not detect the GPS receiver until I click on the GPS device settings and select OTHER BT RECEIVER and then select Blutooth receiver on COM5.
Only then does the GPS show any life.
I would like to know how to get the BT338 to work by just turning on TOMTOM.
It should authenticate and establish the connection on its own, and by the time its up, i should be able to input a destination.
Confusing? No?
easy there mate, give it time....once you have the BT338 paired with your handset, switch everything off.
then 1st switch on your BT338, then switch on your PDA...start up TomTom and leave it for at least 1 minute...it should switch on Bluetooth automatically and connect to the BT338, i had this issue and the 5.1 update solved it...let us know if successful.
Hey Phone connects fine to my car, but it doesnt seem to auto connect? I have to go into settings and press connect everytime despite telling it to auto connect. How do you fix this?
Id guess its because the device isnt discoverable? im not too sure
I've also a mk7 2010 fiesta with the usb bluetooth kit. Almost always it works automatically, assuming I've bluetooth on (but not discoverable) - give it sometimes up to 30s and the bluetooth icon illuminates on the Fiesta's HUD. Only once had issues with it forgetting and needing repairing.
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!
So I'm running cloudy G3 on my D850, but this doesnt seem to be specific to that ROM, since nobody else has reported it.
My issue is that once I connect to my car radio, it connects and works perfectly, but once I turn the car off and it disconnects, the saved bluetooth connection disappears and I'll have to go through the pairing process all over again. Anybody have issues similar to this? I know the bluetooth stack in 5.0 is buggy and I'm sure its related to that.
Hello,
I am frustrated with Oneplus 3 bluetooth issues. It often has trouble connecting to newer devices and connects sporadically. Right now it connects to my car radio and disconnects automatically after sometime. I can see in the car radio settings the bluetooth going from connected to paired to connected again. It also had a lot of trouble connecting to heart rate monitors. Is there a way to see bluetooth logs in a way that it can be easily understood what is going on with the bluetooth connections in lineage os. I understand that there is a bluetooth HCI snoop log but that is pretty difficult to understand.