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.
Related
Hello, I have installed TomTom Navigator 5 in my Qtek s200, but I can't connect it with the bluetooth GPS if the telephone is switched off.
Tomtom runs ok, but doesn't find GPS device.
If I switch on the telephone there isn't any problem, tomtom runs ok and find the GPS device.
I have used tomtom, and dell GPS bluetooth GPS reveivers.
Someone knows if is there a solution to use the GPS with the telephone utility switched off?
Thanks!
ive got this problem too with my xda 1 which i only use as a satnav unit
I use the xda with a wired gps but tomtom complains there is no gps device because the unit is in flight mode, even tho im not trying to use any wireless signals.
anyone help ?
thanks.
I don't know if I understand you right, but I might have an explanation for this. On my Qtek 9100, I can't use a bluetooth GPS-receiver when the device is in flight-mode. Flightmode disables all radiosignals...and since bluetooth is sort of a radio signal, it's disabled as well
A solution might be to turn off and on your device and "cancel" when you're asked to enter your SIMs PIN-code. This way, the device is not in flight mode (so bluetooth works) but the telephone-reception is disabled.
I hope this helps, if not: let me know!
--Marc
yes that works but the phone device is still switched on so uses battery
the gps in question in my situation is a wired unit going directly to my old xda 1's com port so shouldnt matter if the phone or bluetooth are on or not. Even if the pda was in flight mode it shouldnt affect use of my wired gps as there are no radio signals.
seems like a 'bug' in the tomtom software that if the pda is in any kind of flight mode including the phone being off, it decides it cant communicate with any gps, no matter how its connected, as if they expect everyone to be using bluetooth gps' and just include the wired configuration as a legacy function.
malty
maltloaf said:
yes that works but the phone device is still switched on so uses battery
the gps in question in my situation is a wired unit going directly to my old xda 1's com port so shouldnt matter if the phone or bluetooth are on or not. Even if the pda was in flight mode it shouldnt affect use of my wired gps as there are no radio signals.
seems like a 'bug' in the tomtom software that if the pda is in any kind of flight mode including the phone being off, it decides it cant communicate with any gps, no matter how its connected, as if they expect everyone to be using bluetooth gps' and just include the wired configuration as a legacy function.
malty
Click to expand...
Click to collapse
Darn...sorry, I misunderstood. I'm using a bluetooth GPS-receiver myself, so I just took for granted that you also used a bluetooth device And indeed, looks like a bug...not very convenient.
--Marc
Concerning bluetooth devices:
This seems not to work with Windows Mobile 5.0.
With Pocket PC 2003 devices it is possible to use with TomTom bluetooth while in flight mode.
Here's a work around for Win 5.0:
1) Enable the phone and bluetooth in the Comm. manager.
2) Make the link to thte bluetooth gps in TomTom.
3) Disable the phone in the Comm. manager.
4) Return to TomTom.
The bluetooth link will be maintained until you exit Tomtom or try to link again.
This might also be the case with a wired gps.
AJ.
can anyone tell me if I can update the Bluetooth in my HTC Desire or have more profiles. the phone is branded o2 but can be rooted. I dont want to change anything else in the ROM just make the bluetooth connect automaticaly & reliably to the car.
There are newer software builds available but have no mention of updating bluetooth.
Ther are no OTA updates available.
Software Number is 2.14.207.1
Andriod 2.2
Thanks for any advice in advance.
Trampsdad
Can't you just pair the 2 devices together? I personally don't use Bluetooth so no idea on that aspect. Also, the software is so out of date because o2 cba to release and update. There are major updates since yours. It might be worth considering to root so then you can flash a newer ROM, or infact, you don't need to root and just use an RUU. With the newest software. No need to root it then and less chance of it mess up.
Hope this helps
I still have some strangeness with Bluetooth. From what I read there are some updates in Honeycomb and maybe gingerbread. But I don't have a feeling what you are looking for is in FroYo
Sent from my HTC Desire using XDA App
Well I have a Kenwood Headunit with Bluetooth and the connection to that using stock Froyo and LeeDroid showed some interesting results. Gaps in the phonebook for instance. However, putting a 2.3 ROM (Ginger Villain) sorted that out, its fine now.
Bluetooth depends on the other device too.
What exactly is the problem you are having?
What Car do you have?
What Bluetooth system is installed (is it standard)?
I have used my desire in a number of cars (Vauxhall, Ford, BMW) without any isses with pairing, using the Phonebook,etc. is a different matter.
Personally, I have just received a new BMW 528i, and it doesn't get on well with my Desire at all.
It pairs OK and can use both the phone and music, but when I leave and return to the car, it just refuses to auto-connect again, and I have to go through the pairing procedure again.
Oh, except one - the time I went back to the garage to 'complain' about it and ask for advice, when it worked perfectly. Until I got home again!
Have experimented with my old Nokia N85, and that works fine, too. So it's either the Desire or an incompatibility between it and the car.
Oh, my Desire is running MCR r9 (FroYo) at the moment. Are there known issues with this? Info on any Bluetooth updates I could apply would be gratefully received!
i have to enter my pairing code every time i connect my bt headset - i took this to be a quirk for the moment - hoping its fixed in 2.2.2/2.3.x etc.
Lothaen said:
i have to enter my pairing code every time i connect my bt headset - i took this to be a quirk for the moment - hoping its fixed in 2.2.2/2.3.x etc.
Click to expand...
Click to collapse
Im having this same problem also with a Pioneer Head Unit in my car.
Bluetooth has always been troublesome as it doesn't auto connect. It will connect if I either manually click on "Pioneer Head Unit" or turn Bluetooth off and on (which I automate with tasker).
The pin thing is new and happens with all roms I have tried except LeeDroid, (which I prefer not to use as I don't like sense much). Leedroid still has the auto connect problem.
daveaus said:
Bluetooth has always been troublesome as it doesn't auto connect. It will connect if I either manually click on "Pioneer Head Unit" or turn Bluetooth off and on (which I automate with tasker).
Click to expand...
Click to collapse
Some good hints there - thanks!
I can connect far more reliably if I initiate the connection from the phone than from the car.
Likewise, if BT is switched off on the phone and then turned on after the car is on, then it sometimes works, too. Certainly don't need to re-pair anywhere near as often.
Can I ask how you use Tasker to automate the BT switching? I've not used that (I use Setting Profiles instead which I understand does roughly the same thing), so am curious what kind of rule you have that's useful for this.
Cheers.
TheMegaMan_ said:
Can I ask how you use Tasker to automate the BT switching? I've not used that (I use Setting Profiles instead which I understand does roughly the same thing), so am curious what kind of rule you have that's useful for this.
Click to expand...
Click to collapse
I use the following rules:
On wifi connection turn off bluetooth
On wifi disconnection wait 30 seconds and turn bluetooth on.
If not wifi connected & not bluetooth connected turn bluetooth off and on every 5 minutes.
If not wifi connected & not bluetooth connected and incoming call turn bluetooth off and on.
If not wifi connected & not bluetooth connected when display switched on turn bluetooth off and on.
The battery drain hasn't been a problem, if I go away or won't be using my car for a while I disable tasker. Of course this doesn't help when it keeps asking for the pin.
daveaus said:
I use the following rules:
Click to expand...
Click to collapse
Ah, cunning! Of course...toggle it when it's not already connected. Prifile Settings doesn't seem to let me toggle things like BT directly, although I could probably do so by setting some appropriate profiles.
I'll have to experiment...or just buy Tasker, instead!
daveaus said:
Of course this doesn't help when it keeps asking for the pin.
Click to expand...
Click to collapse
True, but so far in my case, I've only had that when I've tried to initiate connection from the car. Hopefully your trick will mean I don't need to do that so often.
Anyone found a gingerbread rom (or any rom!) with improved Bluetooth?
I have found the bluetooth to be terrible on the desire. I have got about 3 devices that my phone just refuses to pair with.
Currently I am trying to get it to connect with an Elm 327 Obd scanner. No luck, it asks for a pin, then I enter the pin, but it immediately rejects it.
I have tried oxygen rom, leedroid, stock froyo, everything...
I also have a parrot hands free kit that does the same thing, asks for pin, then does nothing...
Something makes me think it might be the radio or something. Except that my phone DOES connect with my scala motorbike helmet... So frustrating
Sent from my HTC Desire using XDA App
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!
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...
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.