I am having problem with my LG V20 tmobile version 918. I am unable to sync the BT phonebook with the car. Other phones don't have this problem, but my phone also worked with another car. I did manage to sync the phonebook once after I forced stopped both Bluetooth activities and cleared data/cashe. But it doesn't work any longer.
I purchased phone with 10k installed and yesterday I had it downgraded to 10j. Still no go. I have tried a fair number of things based on online discussions (copy contacts to phone - display only the phone contacts, bluetooth file transfer app) but no success. Any ideas how to deal with this problem?
Bluetooth phonebook seems to do the trick. I may end up rooting the phone to try different kernels to get the phonebook work correctly. Quiet frankly that would be the only reason to root as Immersive view is part of Nougat now (no longer need to have xposed). Any other solutions would be welcomed though... I hate to rely on app to get basic functionality.
Related
A friend of mine has been nursing an old BlackBerry 8700G for many years now. Last week he decided to put it out to pasture and picked up a MyTouch 4G (due, in part, to my glowing review of the device).
He's not happy.
Some of his issues are the usual complaints which can be handled with a quick tutorial and a few tweaks here and there.
The real problem, though, is integration with Microsoft Sync in his 2009 Ford Escape.
The aged BlackBerry worked pretty much as expected with Sync but the MT4G does not. Making and receiving phone calls seems to work just fine but the SMS messaging features of Sync do not appear to be compatible with the MT4G.
This shouldn't matter, though, right? The "Genius Button" lets you send and receive SMS messages via voice control. Unfortunately, while he and I had both assumed that the Sync system would let him access all of the voice control features of the Genius Button (including full voice-control of SMS messages), we were mistaken. Sync doesn't seem to provide any mechanism for triggering a phone's built-in voice recognition system, thereby rendering the Genius Button features completely useless.
Now, I've never used Sync myself so I'm holding out hope that there is some kind of trick or software update that will get his setup working the way he wants it to work. Anybody know something about this that I don't or is he pretty much screwed?
Shouldn't have bought a Ford...
Sorry had to say it
I have SYNC in my 2010 Mustang, and to my knowledge it doesn't have the ability to forward a call button command to the phone like most Bluetooth headsets do. SYNC is more of a "command center" rather than a glorified BT headset in a car stereo, so it pulls in data and info from a variety of sources and you use the voice and button commands to access and control it. You would likely have to tell the car "Bluetooth Streaming" and have the phone playback information for you (unfortunately, the microphone won't forward anything so the handsfree profile will just tie that up).
If he's really, totally, and COMPLETELY hung up on that and still wants Android, I've read on the SYNC forums that the DROID, DROID 2, and DROID X all support SMS transmission through SYNC, including reading and replying. Of course, this might be mitigated by Gingerbread since it's supposed to be getting a new BT stack from what I've read. You know, or not.
Please post questions in the Q&A section.
Question, do they actually have Sync working correctly with their devices? I have a MT4G and am trying to sync with my 2010 Ford F-150. The phone book starts to download and then quits half way through and then the bluetooth causes the phone to freeze up and gets completely screwy. My Vibrant and HD7 do great....the MT4G not so much.
cmerrifield said:
Question, do they actually have Sync working correctly with their devices? I have a MT4G and am trying to sync with my 2010 Ford F-150. The phone book starts to download and then quits half way through and then the bluetooth causes the phone to freeze up and gets completely screwy. My Vibrant and HD7 do great....the MT4G not so much.
Click to expand...
Click to collapse
Mine works fine. My G2 would act strange with my Mustang until I figured out I had to disable WiFi before getting in the car. I'm not sure if it's just WiFi, or the WiFi calling app hanging or resetting the radio, but after doing that my SYNC system would download the phonebook and stay connected the whole time. My mT4G doesn't require this.
Edit: Just thought of this, but I'm using WiFi N at 5GHz at home now with the mT4G, whereas I was on 2.4GHz with my G2 and had the issues. Normally you get different radios for different frequencies, so I wonder if that's the case here.
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 read several posts for people having the same issue as I was having with my LG G2 running and AOSP based rom so I thought I would offer what worked for me YMMV>
I am running Carbon rom (have tried several different roms with the same results) and when I pair it with my Uconnect 8.4a system on my Ram 1500 it goes through the usual process of pairing, downloading the phones contact list and then it starts asking my permission to access my call logs and contact list. Then it will ask me to access my messages, if I answer yes to all of these then bluetooth starts an endless cycle of crashing and restarting and the only way I can stop it is to disable bluetooth on the phone.
Ok, that was the issue and here is what has worked for me to fix it.
1. In bluetooth settings on the phone set bluetooth to always be visible. May or may not be necessary on yours but it was on mine.
2. when pairing to the infotainment system do not allow it to access your messages. The Uconnect system reads out your text messages as they arrive and for some reason it doesn't work well with AOSP based roms. I hate this feature anyway so it's no sweat to me not having it. It's annoying for me to have whatever I'm listening to interrupted by a stupid text message! It can wait people!
Hope this helps someone!
Have been having issues getting mine and my wife's OP2's to work with my 2015 Toyota Corolla's Entune audio system via bluetooth. This Entune is the basic version NOT the one with all the apps.
Finally got the phonebook & contacts to transfer to the car buy installing Bluetooth Phonebook app on the phones. But trying to setup messaging with the Entune has resulted in a message on the Entune saying it's failed to bring over the messages/mail. I have tried a couple different SMS apps, same result.
Now we had no problems at all when we both had OnePlus One's. Both were running Liquid Smooth's Android 5. So is the issue Oxygen OS?
Sam
I'm pretty sure the issue is OOS, yes. I've gone through several different OOS-based ROMs in the past month or so, and none of them have synced contacts or messages to my car stereo.