Database Users

Problems with Bluetooth car kit? Try this

Ever since I got the EB13, and subsequently, the EC05 update to Froyo, Bluetooth has been consistently crashing when I connect to my Jetta TDI's car kit. After lots of frustration, I began to investigate, using aLogCat, and found out the following.
My TDI's Bluetooth interface supports phonebook transfers. The car's interface, however, does not. Still, when I first pair the device, I receive a request to allow the phonebook to transfer, which of course I accepted. I thought nothing of this, as this already happened in DI18, without any problems. However, as of EB13, after I *end* a phonecall, I'll get the triple-buzz, and the BT stack will crash. I have to shut off the BT radio (which takes about 1 minute, as it sits there trying to shut down) and then re-enable and reconnect.
After running aLogCat, I found, pre-crash, that EVERY time I got in my car, the phone attempts to transfer the *entire* phonebook. Every single time I get in. This seems rather unnecessary, and slow, as each entry takes about 0.5 to 0.75 seconds to sync. For hundreds of contacts, my phone is sitting there for what could be an hour or more, syncing. It makes sense, then, that after I hang up on a bluetooth-enabled call, which likely got in the way of the transfer, that a buggy BT stack implementation crashes when it tries to resume. I confirmed this with aLogCat, seeing "ihup() call received!" entries showing up every second or so, after the stack crash. So, I decided to experiment.
I unpaired my car's BT system, and re-paired. This time, instead of accepting the phonebook authorization (which I can't use anyway in my 2009 TDI), I denied the request. It popped up again, and I denied again. (Now, I just simply ignore it, and it goes away.) The result is that I have *never* lost my BT connectivity to the car after a phonecall since I started doing this. Obviously, Samsung has introduced a bug, but because most people's headsets don't support phonebook functionality, it hasn't shown up.
So, if you're having the "I just ended a call, my phone triple-buzzed, and now my headset has disconnected" problem, remove the pairing, and don't allow phonebook transfer. Hopefully this can be of some help to people.

Thank you! That triple buzz was really starting to get to me (to say nothing of how unsafe it is to fiddle with re-pairing on the highway), and I couldn't even figure out a starting point to troubleshoot. I use a Parrot Mki system that does support phonebook transfer, but I'll try deselecting "Always allow" the next time I'm in the car aster permitting at least one sync.
I could swear that I only started noticing this with the recent Froyo builds, but I wasn't certain enough about it.
Thanks again!

Bluetooth Messages Permissions Not Saving

I have a Toyota Prius C and play music from my phone via bluetooth every day during my work commute. Since updating to 4.3, every time I my device connects it asks permission/access to my messages. It doesn't matter if I check the "always allow" box or not, it asks without fail every time I start the car. The first time I connected the device it also asked for access to contacts/calls/etc, but it is able to remember those selections and hasn't asked since...only asks for the messages.
Is anyone else having this issue/know a fix?
I'm running AOKP, but the issue exists on stock as well. This did not happen when running 4.2.

[Q] Bluetooth and Cars

There are some very old threads about this - but this is now, pretty certainly, a general stock android 4.3/4 problem with "older" car hands-free systems. My kit is a Galaxy Note with OmniROM right up to date. My car is an Opel/Vauxhall Zaphira with a Navi 900 onboard computer. However there are threads on many android forums complaining of the same symptoms for "pure" stock 4.3/4 devices (e.g. the Nexus range, including the Samsung Galaxy Nexus) and a variety of cars, and all describing the same workaround (and a few lamenting that Google haven't been very responsive in addressing the problem). The symptoms and workaround are:
The car recognizes and "partially" pairs with the phone
However, the contacts list and call lists are empty and the phone cannot be controlled from the car, neither for incoming calls nor for outgoing calls (dialing from the car interface always gives a failed message, while trying to receive or hangup from the interface just plain fails).
Calls using the phone work, and show up on the car interface, always as "Unknown" (not surprisingly - it doesn't have the contacts list)
HOWEVER if, after this "partial" pairing up, I make a 30-45 second call using just the phone itself, then, after the call has terminated, contacts and call lists are properly available through the car interface and the phone can be fully controlled from that interface (and, of course, the FIRST time this happens, I get the notification on the phone telling me the car wants this information, which, of course, I confirm)
A workaround like that can be scripted with something like "Tasker" and using, say, my voice mail number (with my provider here in France, plain fake number calls don't stay online long enough for the above to work).
But does ANYONE have any idea where to start looking for the root cause and possible solutions, or have any theories on those points?
EDIT:
Just to be clear - the workaround "make a call from the phone" trick has to be done every time the phone and car reconnect, not just the first time.

Had this happen in my ford the other day and it's sync system.
The fix for me was a not so visible notification upon establishing the Bluetooth pairing in the notification tray asking if I wanted to allow for my phonebook to be downloaded. Clicked yes and everything set up as normal.

Mgd_toronto said:
Had this happen in my ford the other day and it's sync system.
The fix for me was a not so visible notification upon establishing the Bluetooth pairing in the notification tray asking if I wanted to allow for my phonebook to be downloaded. Clicked yes and everything set up as normal.
Click to expand...
Click to collapse
I got that notification AFTER I had done the "make a call from the phone" trick, not before.
I should also point out that the "make a call from the phone" trick has to be done every time I want to reconnect to the phone to the car (while the notification only appeared the first time I did the trick - because subsequently the phone and the car "trust" each other).

Aside from maybe unpairing and trying to set it up again which I am certain something you've probably already tried; have you checked the cars firmware?
Could also try resetting your Vauxhall's system as well in case there is a gremlin in there causing a hang up with the sync.
Again with Fords sync I have had to do it a few times over the years when the systems been misbehaving with the Bluetooth and it fixed it.

Mgd_toronto said:
Aside from maybe unpairing and trying to set it up again which I am certain something you've probably already tried; have you checked the cars firmware?
Could also try resetting your Vauxhall's system as well in case there is a gremlin in there causing a hang up with the sync.
Again with Fords sync I have had to do it a few times over the years when the systems been misbehaving with the Bluetooth and it fixed it.
Click to expand...
Click to collapse
Indeed I did the resets. And yes, possibly, an upgrade of firmware MIGHT fix it, but these problems don't occur with Android 4.1.n (or, I, believe 4.2.n).
I've logged a bug with the OminROM developers, but would like some pointers so I myself can start looking at solutions and fixes.

Hmm... Unfortunately I don't know who to assign that JIRA bug to.
Problem is - none of us own vehicle headunits that we can reproduce/test this problem on. I used to have a Sony MEX-BT2500 (technically I still do...) but since I sold my old convertible it just sits and collects dust.

I would agree that this will be a difficult one to find. It reminds me of working with 802.11b/g with it's dozens of "pre-draft" variants that just didn't interoperate properly.
If you wanted to dig into this yourself, the first place I'd look is https://github.com/omnirom/android_external_bluetooth_bluedroid and its upstream and parallel variants. That is the code that generally handles the upper-level Bluetooth management functions.
Edit -- Also worth looking at https://source.android.com/devices/bluetooth.html if you want an overview of how Android implements Bluetooth.
The comments on commits there might also be worth reading through. For example
https://github.com/omnirom/android_...mmit/73ce8ab2ddd30cab6499d0062c46b3a16f9130a9
Fact is however, that the use of SDP features value for peer_features
is new since Android 4.2 and breaks existing good behavior on a BMW
2005/E46 car kit (navi professional). This kit never asks for AT+CHLD
and never via AT commands suggests it supports 3WAY (although it seems
to have the flag set via SDP).​
Not the same issue, but there might be clues of that nature in the commit messages.

Bluetooth settings reset every time it pairs

So I have this really neat new car radio called uconnect, yay, unfortunately it alerts me every time I get a text message. I am able, while paired, to uncheck access to messaging but every time I re-pair the device it is checked again giving the radio access to my messages and alerting me driving me nuts. And it may have even turned itself back on while paired this am (I got an alert but can't recall if I unchecked the box when I got back in the car that time)
So I guess I am asking if there is any way to make the Bluetooth settings for individual devices permanent? An app? Some other setting? Rom? Tool box? Specifically, I want to turn off Bluetooth text notifications on only one device.
I looked all over google and forum for answers but didn't find too much - lots of unhappy uconnect (my new radio) owners for text alerting but nothing on getting my settings to stick.
Thanks in advance everyone

Bluetooth Connection Problems -- Please help

Hello everyone, I bought a new 2015 Jeep Cherokee Trailhawk, it has the 8.4N Uconnect system installed.
I can connect with bluetooth with any other devices, and everything works properly....EXCEPT my phone which is a:
Samsung Galaxy S4
Branded by Fido in Canada
It is rooted, still using the default rom that came with it, but I'm running Nova Settings instead of Touchwiz
SGH-I337M
Android 4.4.2
-----------------------------------------------------------------------------------------------------------------------------------------------
In my car, I goto Phone/Bluetooth settings, have option to change PIN to anything I like but left it at '0000'
On my phone I goto Bluetooth, turn it on, make it visible, hit scan......it finds UCONNECT
I press on it to connect and THEN.......
On the car:
if it is the first time trying since reboot, you can see the passcode show up (six digits - 3 digits a space and then 3 more) and an ACCEPT button. This immediately disappears and it says 'There was a problem connecting with your bluetooth device. Please try again'
If it is not the first attempt after a reboot of phone, it just blinks that first screen showing the weird seperated 6 digit pin and immediatley goes to the error messager.
On the phone:
When it finds UCONNECT and u choose it, a message pops up saying to confirm the passkey and press OK or CANCEL.
It always shows a random 6 digit number.
At the same time, a system message appears for a couple seconds at the bottom of the phone that says 'Incorrect PIN or Passkey. Please try again'
Pressing OK or CANCEL just returns you to the bluetooth scanning screen which shows UCONNECT as an option.
If i try to set the pin on the car with what was shown in the phone, it doesn't work as each attempt to connect generates a random pin on the phone.
I have restarted phone, car etc. Reset car radio completely. Removed all devices remembered on the phones bluetooth. Checked with UConnect support that my phone is compatible -- they say that it might be that Fido in Canada has done something to the phone to prevent it to connect to cars, as it works fine with Verizon/At&T/ and apparently people on Rogers in Canada with S4 works too.
I have commented out the blacklist entries on the phone in /etc/bluetooth/auto_pair_devlist.conf - no change
I have removed all files in /etc/bluetooth - no change
Other phones connect to Uconnect with no problems.
My phone connect to my TV and a bluetooth receiver connected to my home stereo and a second TV different brand no problems.
This is my main phone, also my new car. It really sucks that I cannot get it to pair. Fido, Uconnect support can't help - they have never seen this issue before.
I don't understand why the car shows a pin of six digits with the space between the two groups of 3.
Also, why the phone says incorrect pin or passkey.
PLEASE HELP!! I am going crazy over this!
I really don't want to, but if there is no fix, I will have to backup everything, format the phone, install perhaps a Verizon or something build of Android and then try to connect with that (hoping it has no issues with phone/data use with Fido network over here)

Updated info
I just tested with anothers car....
2009 Nissan Rogue...works fine (is used as an audio device only...no phonebook etc features)
Also tested with an Iphone 5 to my Jeep and that phone connects fine.
I tried using an app called 'Bluetooth Fix Repair' from the app store. It gives an error at startup:
"Sorry this application cannot find your bluetooth setup folder on this device"
Can this be the issue?
The bluetooth folder I was working with in the OP was on the phone at etc/bluetooth
Should I have another one somewhere...maybe missing or corrupted?
Any help!?! Cannot find anyone else with this same issue here (xda) or on google etc.