I just switched from AT&T to Verizon in April. My AT&T plan had a Galaxy S4, S5 and S6. All 3 phones paired with the nav system in my 2013 Hyundai Sonata Limited and all features worked. With Verizon, I have one Galaxy S7 and two S7 Edge's. According to Hyundai's website, both of these devices are compatible with the nav system in my car for all features. Alas, that is not true, at least not for me...the phones will pair with the nav system with no issues, but the nav doesn't load the contacts from the phone, even after clicking "Allow" when asked to do so. Because of this, I can't make a hands-free call. I give the nav system a voice command to "Call Name", it will ask for the name, I say the name and the reply is "Name not found", because it does not load the contacts. The system then reverts back to whatever it was previously set for (FM, satellite, CD, etc.) I can make a call on the phone and it will run the call through the nav system; likewise, if I receive a call and am connected to the nav, I can answer the call on my phone and it will run through the nav system.
I have talked to the service manager at a local Hyundai dealer and he said there is not an update that he is aware of and he said to go to the Verizon store and make sure the phones are not the issue. I did that yesterday and spent most of an hour on the phone with a Verizon tech. He had me completely un-pair the phone from the nav system, un-pair the nav system from the phone and re-pair both to each other as if doing it for the first time. I also tried depressing the pin-hole reset button on the top left corner of the nav unit and the only thing that did was knock out the radio station pre-sets. I feel pretty certain that the issue is with the nav system, but can't seem to find a solution.
Has anyone seen this problem and know of a solution other than taking it to the dealer? If I have to take it to the dealer I will, just hoping to avoid that if possible. Thanks, Jeff.
I had issues with my system as well, although I don't know if they are the same cause. What I found in my case was that is was related to the new way that Marshmallow asks for permissions. When I looked at the specific Bluetooth settings for my car, there were settings that were not toggled and if I toggled them manually they would just turn back off. I had to repair my phone to the vehicle and keep the bluetooth settings open as my car finished the setup. I had to physically access the bluetooth messaging settings in my car in order to get the permissions to pop up on my phone. It may be something similar in this case, where you need to wait until you car actually starts the phonebook download in order to allow it on your phone. Just a guess, but it's worth a try.
Related
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.
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.
I have a Volsmart Android 5.1 headunit I recently purchased. I can connect my android phone via blue tooth and use the touch screen dialer on the headunit to make a call without any issues. The issue comes if I try to use Google voice option on the headunit and say "Ok Google Call Henry". Henrys number pops up on the screen and it says calling Henry and I see the number on the page however it does not call. I am assuming the headunit is trying to use itself to make a call and not trying to go through the bluetooth connection to my phone and since the headunit itself does not have a sim card the call doesnt actually start. Anyone ever got this to work or know wht I should do to fix the issue?
i tried this before on my Joying and had the same end result as you posted. I think i read about a few people trying things on here, but I don't recall of anyone getting it done successfully.
there is a firmware for the tonghai create 2nd gen called "iq navi" that includes this feature by default. there is an intermediary app required called "bridge" or something other. It effectively links the phone's bt app with google now services of the HU.
I searched but couldn't find much about it. When i received my PX5 Xtron unit, Ok Google would dial and call people, however the past few days it will no longer call someone.
It will load the Google as if it's going to call them, but it doesn't then open the bluetooth dialler and proceed.
Any fix?
OK Google has never called anyone for me, unless I used Mtcdialer? Perhaps OEM's have started putting that on their devices? Wouldn't surprise me.
skezza said:
OK Google has never called anyone for me, unless I used Mtcdialer? Perhaps OEM's have started putting that on their devices? Wouldn't surprise me.
Click to expand...
Click to collapse
Hmmmm, i did have 'ok google' switched on my phone, so unless it was allowing call actions through that whilst my phone was locked and then bluetoothing the call through. Coincidently, i switched ok google off on my mobile and it would be the same time that it appeared to not work on the head unit.
I'm not sure what's wrong, but my Xtrons headhunit responded to "OK google" sometimes intermittently and my phone is an iPhone so it probably wasn't because of your phone (unless you never properly got it work on you headhunt at all).
To get voice activation turned on I installed the "google assistant" app, but I suspect it does not reopen after a reboot causing the issue of only working sometimes. Also, if you open the bluetooth app on the headhunit it can take over the audio from the rest of the system. It's kind of confusing, so I'm not sure where the issue is.
300cnewbie said:
Hmmmm, i did have 'ok google' switched on my phone, so unless it was allowing call actions through that whilst my phone was locked and then bluetoothing the call through. Coincidently, i switched ok google off on my mobile and it would be the same time that it appeared to not work on the head unit.
Click to expand...
Click to collapse
halopend said:
I'm not sure what's wrong, but my Xtrons headhunit responded to "OK google" sometimes intermittently and my phone is an iPhone so it probably wasn't because of your phone (unless you never properly got it work on you headhunt at all).
To get voice activation turned on I installed the "google assistant" app, but I suspect it does not reopen after a reboot causing the issue of only working sometimes. Also, if you open the bluetooth app on the headhunit it can take over the audio from the rest of the system. It's kind of confusing, so I'm not sure where the issue is.
Click to expand...
Click to collapse
It responds to 'OK Google', the issue is that it won't dial phone numbers anymore through it. If yours is intermittent, ensure that any music/ audio is turned down, as it won't pick it up on the mic.
Atoto a6 pro bluetooth
I have same issue on atoto a6 pro, ok google don't interface with native bluetooth dialer, i try with tmcdialer but don't work on my chipset...any fix???
Maurizyo85 said:
I have same issue on atoto a6 pro, ok google don't interface with native bluetooth dialer, i try with tmcdialer but don't work on my chipset...any fix???
Click to expand...
Click to collapse
I bought about 9 months ago, directly from Seicane a radio of 9 "android 8 PX5 for a Subaru Forester, the integration and the connectors are excellent but the radio had problems with the bluetooth handled by google and when connecting the cell phone via usb Easyconected, it did not recognize the cell phone, I asked for support but the solution from them was simple, and it was still the same, at the end I found a firmware of Hal9k, I installed to the radio and with this all these problems were solved, the link is "https: //forum.xda -developers.com/android-auto/mtcd-software-development/rom-hal9k-rom-3-mtcd-e-head-units-t3847477 ", check for your problem
Thank you for answer, i try to install this mod when i have a bit time, sure this work on atoto chipset?
Looking for a modified MTCDialer of my version too
I have an Atoto S8, and this is my first Android powered head unit (coming from their linux-based F7, which was more of an appliance UI instead of a smart OS). I love the extra functionality it gives me, running apps and video players directly on the unit. But Bluetooth support is wonky.
My wife and I share the car, and ever since swapping to the Android powered unit, it only reconnects to whoever drove last. So if I drive the car all the time, its fine. But when my wife drives, she says bluetooth isn't working, so I have to go into settings on the BT app (BT1 as they call it) and see the three phones listed as paired (my old phone, my new phone and my wife's phone), and click on hers. Wait a bit, and then she is good to go. But then next time I drive, I realize my phone isn't connecting now, so I have to go do it again. Which means she's going to complain next time that her phone isn't working again.
I've installed a few bluetooth powered head units before, and even the Android Auto supporting F7 before this one, worked as expected: If the last device isn't available, try to connect to another recent paired one. It seems to just get stuck on the last one for some reason. Is this a limitation of how bluetooth works on these units?
have you solved this issue
i am finding it very frustrating
i thought i would solve it using the app "automate"
this would star a sequence of checks and sytematic attempted connections
but, oddly enough you cant automate the triggering o fthe flow
so it would only start if actioned
Yes, or rather THEY solved it.
Reach out to customer support. There is an update to the Bluetooth module that makes this work the way I described.
I got an A6pf in my other car and had them make an update for that one too. Much happier now.