Hello, hopefully this will be a quick, easy question for someone. For some reason, when I try to make a call from my in-car bluetooth, it always returns 'Dialing Failed'.
ie, I push the 'Call' button on the steering wheel, say "Call Bob", the car will confirm "Calling Bob at Home" (which tells me it downloaded the phonebook properly), but then will just say "Dialing Failed".
The phone pairs fine, will receive calls with no issues, will play music and internet radio without a problem, and will even make calls if I hit Dial from the phone instead of the car buttons. It also used to work just fine with my old Motorola Milestone.
So, any suggestions? Is there some setting somewhere I'm missing? Do I have to start downloading some 3rd party apps? (would seem strange if I did)
Currently running Paranoid Android 3.99, stock kernel. Bluetooth is Chevy's MyLink, if it matters.
Thanks for your help!
I also discovered that it will make calls if I say the number instead of the contact name, or if I scroll through the car's screen and select the contact name.
Any suggestions? It just seems odd that it worked fine with a much older phone, but I can't get it to work with the Nexus.
I've tried a few different 3rd party apps, and nothing seems to help - the phone doesn't even seem to see any sort of command, I never see it try to do anything.
Is it something with the kernel? With the radio? Does anyone have this working properly? (ie bluetooth dials from the phonebook downloaded into the bluetooth device). I'd like to have some idea before I start mucking around and wasting too much time.
I'm a little disappointed, I just got the Nexus, and bluetooth functionality should be something straightforward and flawless, not have significant flaws like this.
So I've tried a few different ROMs, different kernels, and different radios, with the same results. Is this a known bug? This must be happening to other people. Is there anyone that can help?
Should I post this somewhere else?
CanAndroid said:
So I've tried a few different ROMs, different kernels, and different radios, with the same results. Is this a known bug? This must be happening to other people. Is there anyone that can help?
Should I post this somewhere else?
Click to expand...
Click to collapse
Does the Chevy MyLink software download your contact list or access the list from a synced phone? If it downloads the list, I'd try removing it and re-downloading it to the car.
GoPadge said:
Does the Chevy MyLink software download your contact list or access the list from a synced phone? If it downloads the list, I'd try removing it and re-downloading it to the car.
Click to expand...
Click to collapse
Yes, it downloads the phonebook. I've re-paired and re-downloaded it numerous times now, with each of the new ROMs/kernels/radios.
I'm thinking it is an Android 4.3 issue, assuming you have 4.3 on your Nexus.
I have had exactly the same issue with my HTC One since I changed the ROM from Android 4.2.2 to 4.3. With 4.2.2, voice dialing worked perfectly when paired with my Camaro Mylink.
Did you ever find a solution?
k818mn1 said:
I'm thinking it is an Android 4.3 issue, assuming you have 4.3 on your Nexus.
I have had exactly the same issue with my HTC One since I changed the ROM from Android 4.2.2 to 4.3. With 4.2.2, voice dialing worked perfectly when paired with my Camaro Mylink.
Did you ever find a solution?
Click to expand...
Click to collapse
Try removing all brackets and hyphens from the phone book numbers. Worked for me.
Not a solution but a workaround.
Related
Good morning fellow forum member. I've recently begun having some significant bluetooth connectivity issues with my continuum and Ford Sync system in my 2011 Fiesta. Now, before you start ranting about your loath for microsoft or Ford please hear me out. In theory, the Sync system, combined with bluetooth technology, is a great way to go hands free. It also allows for the coordination of the system and Pandora & Stitcher Radio on an Android phone.
Anyway, lately my bluetooth connection to my car has been causing FCs on my phone. They are the type of FCs that cause the "long-short-short-short" haptic feedback but doesn't throw a pop-up message describing the cause of the FC. So, when the feedback occurs the phone will sometimes lock up but it always disconnects the bluetooth. I don't use bluetooth in any other fashion so I can't be positive that it's not an issue with the car's bluettoth system.
With all of that said, is there an inherent issue with the bluetooth system on our phone? If so, is there a fix for this? I'm currently running the EC07-clean_new ROM. This was installed over the SCH-I400-EC07-FROYO-REL-PRODUCTION ROM. My broadband version iss:i400.0.6v.EC06, Kernel 2.6.32.9 and build SCH-I400.EC07.
Any help that you brilliant folks could offer would be much appreciated.
Thanks,
Ray
I run bluetooth constantly (it's the only way I talk on my phone, driving or not.) I've never run into this issue. Have you recently downloaded any new apps? I found that there are some apps that simply don't play well with our phones. Especially radio based apps (I.E. the issues a lot of us were having with gps based apps, or gps losing it's lock, after a while. Wireless tether 3.06 beta completely screwed my phone up... etc). The only other thing I could suggest is to drop your phone from the sync, and reconnect it... I do this with all my bluetooth devices at least twice a week as a matter of course. And if you want to experiment to see if it's sync or your phone, assuming you have bluetooth stack on your computer, you could connect it to your phone. Other than that, maybe find a friend that has bluetooth and connect it?
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Reborn627 said:
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Click to expand...
Click to collapse
I think you should be good with rourine disconnect/reconnect. Asfor too many apps, the only thing rhat matters there is storage space. Android wint let you run "too many" at once. Itll delete from ram as needed. I was just saying that certain apps dont seem to play well with others. But that is an android issue, not your phone in particular.
I'm not here for a long time. I'm here for a good time. To hell with the red wine. Pour me some moonshine. - King George
I'm totally stumped here. Yesterday I decided to reflash my phone. I figured any issues might be ironed out. It must be an app issue, although it is going to be a PIA to uninstall then reinstall each app and test the BT after each app install. I thought that it might be the trailblazer101 car cradle, desk cradle or the sticher apps that were giving me the problem but that doesn't seem to be the case. Maybe I'll try replacing the BT files with the ones from eclair to see if I end up with the same trouble. Any idea if that might cause more problems? Are the BT files android version specific?
Peace
EDIT: I've not swapped the BT files from eclair but I did spend an hour or so listening to Stitcher radio via a bluetooth headset. It doesn't seem to be a BT issue. More likely an issue with the connection to the Sync system itself. Connecting via bluetooth is no problem in the car. It's not until I attempt to engage a function other than the phone that an issue occurs. I may try to reflash the EC07-clean ROM and see if there was something with the EC07-Clean_new version that I've been running for the last few weeks.
OK, the BT issue seems to be corrected. I flashed adrenalyn's EC07-clean ROM and that seemed to do it. Something must have gotten corrupted. So, issue resolved...i guess.
Hey all,
Recently got my n4 and am currently running cm10 nightlies on it, but today I picked up our new car (Hyundai i30 premium) which has bluetooth built into the audio system and I can't get my n4 to sync with it properly. My partners Desire HD syncs no problems and all her contacts phone book everything shows up fine. My n4 wouldn't even sync originally then I just kept retrying and eventually it synced but nothing really works, music won't play through the speakers (the audio system just sits there waiting for music and nothing happens) my phonebook etc don't show up (after me allowing them permission) I can't even make calls.
I have heard that the n4 has some bluetooth problems but nothing this bad, anyone have any suggestions that I can try? Happy to go to another ROM if that will help??
Thanks,
Hosh
this build has serious BT issues. i can't even find a mouse that works. wait and see what the 4.2.2 update brings.
I own a Hyundai Elantra GT which is the US version of the i30 - I didn't seem to experience any issues when I paired it this morning, but I"ll double check when I get out of work this afternoon that the contact sync is working. I am, however, on the stock rom.
I own a 4 day old Dodge Journey and it pairs with no issue to Uconnect.
Try a different rom?
If thats not it, then its your hardware.
The new bluetooth stack in Android 4.2 is causing a lot of issues. Personally, I don't have any problems connecting to UConnect (Jeep Grand Cherokee) or my SmartMini (bluetooth music streaming).
I am waiting on delivery for my MetaWatch, there have been complaints that 4.2 isn't connecting well with it but I guess we'll see. CM10.1 users don't seem to have as many problems. I'm running Xylon w/ Franco r53.
I had the same problem with Chevrolet captiva until I have installed custom ROM and is working perfect now.I have tried every custom ROM and is OK with all.
I have this problem but there is a way around it (for me anyway).
Download Bluetooth file transfer from the market.
Delete the connections with your car. Both on the phone and your car.
Open Bluetooth file transfer. Select the Bluetooth screen.
Make a connection. The default android Bluetooth will ask for a password. Don't enter it. Instead go to your recent apps and select Bluetooth file transfer. Put the password in the request screen the app supplies.
Bluetooth file transfer should pair the devices and make a connection.
Once done. Kill Bluetooth file transfer as you won't be able to exit.
You can then uninstall Bluetooth file transfer if you want (although I tend to keep it for when I change ROMs or have to do a factory reset etc).
Hope this works for you
Sent from my Nexus 4 using xda premium
Hey all,
Sorry for the late reply, been away for the weekend. Thanks for all the advice, tried them all and no luck. Will try out a mates n4 tomorrow and see if he has any luck syncing with the car, if he does might just flash roms again.
after flashing a new rom, I had problems pairing w/bluetooth and connecting w/wi-fi. I fixed the problem by restoring my system settings w/titanium backup thanks to someone's suggestion.
Seems the only thing that worked for me is when it asks to sync my phonebook I have to say no, if I say yes it seems to freeze the whole thing. Makes me think if I click yes I might just need to give it 10-15 mins to sync, might try that tomorrow. But for the moment at least it's half working!
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.
I have a new issue, and need some ideas...
I have a Mazda 3 2014 with built in Infotainment system, and I can of course place calls from it over bluetooth. My Nexus 5 would dial, and as you expect the car remains connected and the audio and dialling occurs through the car system. With my Nexus 6P, the car talks to my phone, and then immediately cuts off the bluetooth, a bit like a failure to communicate, but the phone will then carry on calling, and only if I try to dial from my car, and if the person has answered does it then lock on and maintain the call via the car system.
I can not find anything in either settings to explain it.
So, anyone have any ideas crutually why the 6P fails me where the 5 worked.
I have the exact same issue. I have a Mazda CX-5.
nahuelarg86 said:
I have the exact same issue. I have a Mazda CX-5.
Click to expand...
Click to collapse
Would be the same system if yours is the current model too. Guessing it was fine on your previous phone too?
Yes, I think so. It is a 2016, so it is the latest system I suppose. I had a Samsung Galaxy S5 previously and it worked perfectly. This is my first Nexus, so I thought it was a Nexus thing at first, however it is really annoying. It is hard to explain because the bluetooth kinda works, it just has this thing that it drops and picks up again...
Bluetooth working fine with my 2013 kia forte. Maybe something to do with Marshmallow and Mazda Bluetooth system?
Yea, it is kind of hard to explain. Only found out today, so not been able to test it over and over, but seems that unless the other person answers, you have no idea it is dialling. It is like it (Mazda system) is being told it an not carry on. I once had the same issue (Nexus 5) when there was another phone option and it was waiting for a default to be set on the phone before it dials. It did not do it today, but I wonder if I make sure it is set in settings as the default right....
... nope, only app for calls is the inbuilt.
It seems like some people are having similar issues? --> http://forum.xda-developers.com/nexus-6p/help/bluetooth-phone-completely-borked-t3241196
I had the phone for a couple days and tried some things like upairing/re-pairing with no results. I discovered it when I called my wife, the call dropped (or the car did the call drop sound) but all of the sudden my wife answered. I tried calling different numbers and it's the same deal. I haven't tried receiving a call.
nahuelarg86 said:
I have the exact same issue. I have a Mazda CX-5.
Click to expand...
Click to collapse
And I have the same issue with a 2015 Honda Accord Hybrid. I don't have the issue with any of my other phones. Google Support doesn't know why it's happening.
Reading this https://code.google.com/p/android/issues/detail?id=189188 it seems clear it is Marshmallow on many devices and systems
AllyGraham said:
Reading this https://code.google.com/p/android/issues/detail?id=189188 it seems clear it is Marshmallow on many devices and systems
Click to expand...
Click to collapse
Nice find. I'll chime in in that thread. I hope Google can solve this soonish since it is kinda a major annoyance at the moment.
Hi,
After upgrading to Android 8.0 on my H870 I'm encountering multiple issues.
Using my G6 with Ford Sync 2 or 3 keeps crashing Bluetooth. Meanwhile using Bluetooth with my Marshall Stockwell works absolutly fine. Unpairing and pairing again doesn't seem to work.
Also GPS in Google Maps only works for locating me, but when using it with Navigation my location keeps being stuck at my original position and doesn't move...
HERE also keeps being stuck with "Waiting for GPS".
Restarting the phone didn't help.
Does anyone have a solution to my problems? :crying:
Many thanks in advance
Solution:
After restarting my G6 about 3 to 4 times and disabling Call and Contact Access in the Bluetooth device settings and then restarting everything works fine now. (including GPS)
Update:
The problem is back again
Somewhat new solution:
By enabling the developer options my "Bluetooth AVRCP Version" was set to AVRCP 1.5, which isn't the default...
So by changing it to AVRCP 1.4 Bluetooth works fine now...
VS988 here: Everything seems mostly okay, except for the constant bluetooth crashes. Anybody else seeing that? Also, FWIW, not enjoying the system notifications. Trying to figure out how to turn those off.
Usual first fix after a major update is factory reset, did you try that yet?
boomboomer said:
Usual first fix after a major update is factory reset, did you try that yet?
Click to expand...
Click to collapse
That would be my next move if the problem still persisted.
marco_wack said:
I upgraded to Oreo but now the animation when pressing the home button is gone. This little dots around it from Google assistant don't show up anymore. Anyone know how to fix?
Click to expand...
Click to collapse
Did you try to reinstall Google Assistant?
hi to all ! i found multiple issues.
-Bluetooth
-fast battery drain
-when it is connect to usb , the screen don't start easy.
i make a factory reset but situation is still the same
boomboomer said:
Usual first fix after a major update is factory reset, did you try that yet?
Click to expand...
Click to collapse
No, that is such a time-consuming PITA that I always wait until I have no other option. Thanks, though.
crazyracer98 said:
Hi,
After upgrading to Android 8.0 on my H870 I'm encountering multiple issues.
Using my G6 with Ford Sync 2 or 3 keeps crashing Bluetooth. Meanwhile using Bluetooth with my Marshall Stockwell works absolutly fine. Unpairing and pairing again doesn't seem to work.
Also GPS in Google Maps only works for locating me, but when using it with Navigation my location keeps being stuck at my original position and doesn't move...
HERE also keeps being stuck with "Waiting for GPS".
Restarting the phone didn't help.
Does anyone have a solution to my problems? :crying:
Many thanks in advance
Solution:
After restarting my G6 about 3 to 4 times and disabling Call and Contact Access in the Bluetooth device settings and then restarting everything works fine now. (including GPS)
Click to expand...
Click to collapse
I'm H870 EU user, no problems so far after oreo update (without factory reset), BT pairing works as it should...
GPS and navigation also works without bugs.
Just do a factory reset
I had frequent bluetooth crash notifications on nougat. On oreo bluetooth will not connect a2dp/avrcp beyond first pairing with my Pioneer car stereo ..still works fine on bt headsets that dont pull phonebook including my old basic sony car stereo.
---------- Post added at 10:32 PM ---------- Previous post was at 10:28 PM ----------
rfarrah said:
VS988 here: Everything seems mostly okay, except for the constant bluetooth crashes. Anybody else seeing that? Also, FWIW, not enjoying the system notifications. Trying to figure out how to turn those off.
Click to expand...
Click to collapse
If you're talking about persistant battery notification hold on it from notification panel..unfortunately it's all or none. Wish Google had the foresight to allow disable on a per app basis, but you know how wishes go...
I'm having the same problems with bluetooth. My headphones can connect, however after about 3 seconds they automatically disconnect for audio (though they somehow still connect to the phone, just not on audio).
My car still connects and works, however it does sound now like I am listening to a scratched CD (whereas both were working absolutely fine before the update). Haven't found anyone with a solution so far.
Verizon G6 VS988 here.
To respond to a couple of the suggestions here, I did a factory reset first because of bluetooth and battery problems. That didn't fix the problems. I just changed to AVRCP 1.4 Bluetooth and hopefully that fix works for bluetooth. I also have a Ford with Sync.
Something new ive noticed is if i place a call it puts up the audio output notification and everything works as normal. Having reset my phone and car both i can only say LG missed out on my next phone purchase even when running low on phone options.
How do u change to that ? Is it on the phone device settings cant seem to find out how
GPS problem in G6 is a common issue. No solutions so far.
Bluetooth wont work with any device I've tried it with. Many restarts, unpairing, turning on/off bluetooth. Nothing works, need this fixed.
Just adding another testimony of the issue.
T-Mobile
I really hate to say this, but I really cannot recommend LG to anyone anymore after all the issues I've got with my phone...
Another question:
I have 2 NFC payment apps installed.
I'm now on version V20c-EUR-XX and since the upgrade I cannot change my default payment app, so when I'm in the store it always tries to pay with app 2 instead of app 1, even when app 1 is on the screen with the card I want to use...
This really frustrates me, because app 2 doesn't always work in stores (but is my preferred app)...
crazyracer98 said:
I really hate to say this, but I really cannot recommend LG to anyone anymore after all the issues I've got with my phone...
Another question:
I have 2 NFC payment apps installed.
I'm now on version V20c-EUR-XX and since the upgrade I cannot change my default payment app, so when I'm in the store it always tries to pay with app 2 instead of app 1, even when app 1 is on the screen with the card I want to use...
This really frustrates me, because app 2 doesn't always work in stores (but is my preferred app)...
Click to expand...
Click to collapse
Is that issue because it's an LG phone? Or does it happen because of that version of Android?
One of my friends is using a Galaxy S8+ and he is running Android 8 (same as mine).
I just cannot think of any reason why they removed this feature...
(So it is a issue with my LG H870)