Problems with Bluetooth car kit? Try this - Epic 4G General

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!

Related

Bluetooth pairing problems with all 2.1 ROMs.

So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Is that an older Motorola Bluetooth?
I've paired the Motorola H720 with the leaked Eris. Smooth like butter. All I did was enter "0000." Worked fine. Try another bluetooth device, possibly one of more recent vintage. (Don't know how old a model your 270? is.)
I have not had any problems with my Clarion car stereo or my plantronics headset. In my car, in fact, the 2.1's have worked better than stock, since my car stereo picks up the phone and streams the audio automatically every time I get into the car without having to delete and re-pair (as I had to do with stock).
Pete
I have had no luck pairing my phone and any of my cars with any ROM based on 2.1. It pairs, but will not stay connected. Phone says "paired but not connected"; car says "paired, connected; then disconnected"; then endless loops of connected/disconnected. Sucks!
The sad thing is it seems most of these amazing ROM cookers do not use BlueTooth so it is not something they worry about. I bet this is what is holding up releasing the official Sprint update.
I too have tried searching through endless posts about bluetooth and 2.1. All I can come up with is there are some libraries missing from the 2.1 BlueZ; or something to that effect.
I love Damage's 2.0.7.2 ROM! But I have to go back to stock since driving and talking on the phone without a handsfree device is now illegal here in El Paso, TX.
I don't have a car or stereo bluetooth device to pair against. Just tried pairing my bluetooth with the new 2.0.2v2? Alysious ROM. Took 2 sec and nearly totally automatic. Amazing.
My issue with all 2.1 roms is that I can pair, dial and audio stream all day. I just cant talk as no sound or mic. I reflash back to 1.5 and all works well. BT in the car is now useless. sigh
2.1 paired fine, but its a crappy connection on 2.1, on 1.5 i had a better connection
finally used my BT last night with my phone ...worked like a champ! everything was clear to me....i don't have no sound probs and haven't used any of the fixes...
I pair with my bluetooth headset most of the time without problem. I do occasionally have to turn on and off my headset and the bluetooth on the phone to get it to reconnect. Thankfully, it only happens occasionally.....
Maybe I'm just one of the lucky ones (this time) but I have been streaming audio from my hero to the car stereo while while using google navigtion, which politely talks over the music, and have not had any problems. I'll get an occasional skip in the music (probably during downloads of map data), but nothing worth complaining about.
Pete
poor_red_neck said:
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Click to expand...
Click to collapse
Guys, sorry to revive an old post but I am having this exact same issue as the OP. If anyone has found a fix, please post. Thanks.
Looking at FroYo they have updated some Bluez stuff (what makes out BT work) maybe it will be better when we get that.
Hopefully...

[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.

XT1575 6.0 Marshmallow - Bluetooth from car keeps requesting messages access

I keep running into an issue since upgrading to stock rooted Marshmallow on my Moto X Pure.
Every time I connect to my bluetooth media center in the car, it requests access to "messages". Whether I say "yes" or "no", it will ask me the next time I connect.
It is more of a nuisance than anything else, but I would like it to stop, so sometimes I can get in my car without mounting it and have it just work, since right now I need to see the screen, because that message will vibrate the phone about every 60 seconds until I respond.
Has anyone else even seen this issue? I tried wiping app data for various related items, as well as re-pairing the bluetooth, since some apps I restored had problems with the new permissions setup, but none of this worked so far.
I get this too when initially pairing with my vehicle. It only ask me twice though and I say not both times. For mine vehicle, it allows it to read the messages out loud through the speakers. Try saying yes, then go into bluetooth settings. Under that device uncheck messages and see if it sticks.
I tried doing a mix of "yes" and "no" on the phone and neither seem to actually do anything. As well, when I look at the setting on the phone for my car as the "device" connected, there isn't even an option for checking messages, it just has two check boxes; one for "Phone audio" and another for "Media audio".
In the car is has similar limitations, as far as only device connection options for "Phone", "Media", and "Internet".

Bluetooth problems and need to reset

I have a retus version on stock ROM (non-Amazon). I have 5-6 BT devices connected (Moto 360 watch on persistent, some headsets, headphones, speakers, car, etc.). They are all different brands (Plantronics, JBL, Taotronics, etc.). Almost every time I use a device and then it off, after awhile when I try to connect another device it won't connect. Then I need to reboot phone before it will connect again. Not every time, but most times. Just turning off the BT on phone and back on used to work sometimes but doesn't now. Anyone else have this problem and any suggested fixes? Thanks.
Has your phone done any updates, security patches etc, used to have to remove all previous Bluetooth items on my samsung, then reboot and add them back, before they would automatically reconnect, could be the same for moto.
Ray

Bluetooth problem

Hello to everyone.
From when i bought it the op8pro has some problem with the bluetooth. Is like if the device can connect to one device only. I have a fossil 5 gen, one fiesta mk8 with android auto and the bluetooth headset but is like if the bluetooth has some problem to connect to two or one devices. For example every time my car doesnt connect to the phone automatically and today when i was to the gym my headset doesnt connect automatically too. My previous note 10 pro was able to connect without any problem... Someone has some problem with the bluetooth? Thanks
I have another problem. Every time that i enter in my car the device is connect to android auto but if i want to play an audio from whatsapp i have to tap a lot of time on the play botton.!!!???why
I see this same issue, I'd say 80-90% of the time (the other 10-20%, it "just works", which is truly odd, given the protocol).
For example, I use some bone-conducting open-air headphones, while cycling (long time road cyclist), and sometimes I want to connect my Garmin Edge 1030, to download a route, when I'm out.
Good luck, even upon returning, I'm often sitting in the garage, trying 20+ times (after shutting my headphones off, even), to try and download my ride-data, for the day. Sometimes it requires rebooting both devices, flushing the Bluetooth app-cache, and the Garmin app-cache, and then it'll work, that's perhaps 40% of the time.
For another 40%, it will NOT connect, what-so-ever, across multiple reboots and app-cache flushes, period (I tend to give up at around the 20+ attempt mark, depending).
The last 20%, it works, perfectly, as you'd expect, and as my OP7 Pro did, I can't recall a single BT connectivity issue, with it, either solo (Garmin) or with headphones concurrently.
I've filed bugs with OP (along with NUMEROUS other radio bugs, like the fact you can't connect to a 5G-mobile signal, if you're connected to a WiFi signal, on the INO2025 model, bug filed, trace-logs submitted, including pointing out log-lines where the radio(s) fail).
Unfortunately, with the Bluetooth issues, it will not repro, if I use the OP debug-mode, which is how they want to receive logs (and how I've submitted many bugs, previously), so I'm at a loss, short of finding a hardware Bluetooth debug module (I used to work on h/w and s/w boundary driver stuff, so I've used a h/w BT debugger before, but not for some years, and have no access to one, currently).
OP seems to just ignore the bugs, at that point, when I can't provide the logs, they pretty much abandon the bug-thread, so I'm not sure how they're going to get some of these resolved (I've noted that the debug-mode seems to introduce some latency, or similar, that prevents repro, no response to that, what-so-ever).
I have reset the radio-stack, a couple of times, and did one full factory-reset (shortly after getting the phone, about 1 month back now), with no real change in results, for reference.
I feel like I'm back in the late-90's, when Bluetooth was super-flaky. on most devices, in the 1.x and 2.x days.
Not exactly a "flagship phone experience", or even a decent budget phone Bluetooth experience, for this day and age...
I'm open to ideas on how to debug further, I'm really more of a storage and display guy, and memory-management, in terms of the bulk of my dev/debug skills, communication protocols were something I did on the fringe, of sorts, when they overlapped, or similar.

Categories

Resources