new HTC One and 2012 A6
#2
AudiWorld Senior Member
I had the same problem when I first got my A6 with a ThunderBolt. Its not tied to Android but the phone, my current SIII works fine. If you're using Gmail, export your contacts as a vsd file. Place that on an SD card and using the MMI import that. Once I had done that changes to my phone contacts would update when the phone synced with the car.
#3
Audiworld Junior Member
Thread Starter
Join Date: Aug 2010
Posts: 14
Likes: 0
Received 0 Likes
on
0 Posts
I had the same problem when I first got my A6 with a ThunderBolt. Its not tied to Android but the phone, my current SIII works fine. If you're using Gmail, export your contacts as a vsd file. Place that on an SD card and using the MMI import that. Once I had done that changes to my phone contacts would update when the phone synced with the car.
#4
AudiWorld Senior Member
If you have a problem, delete all the MMI memory, remove the Bluetooth sync and set everything up again. I think I had to do that a couple times.
#5
Android and Audi
Audis are quite particular with what contacts they like to import (or not). The ones with Nav are worse. My phone, which would not import into my car, worked fine on an A6 loaner without Navigation.
There are a couple of experiments to try. First one, have a single contact with just a name and a phone number on the phone, and nothing else. See if that imports. If it does, then the issue is most likely a formatting thing.
In my case, I have a Rezound and I use Outlook for my contacts. What I noticed is that if I had any carriage returns in any contact, it would not import. I found this most commonly in addresses, where, typically, each field is separated by carriage returns. I substituted all CR with commas.
I also had a contact with two email addresses. That one did not work either. Removed one address.
What I ended up doing is deleting groups of ocntacts until it successfully imported, then figuring out which ones were the culprits by elimination. Knowing the carriage return thing was enough to fix most of mine.
You can also figure out what's going on (to some degree) by manually importing contacts; the car 'counts up' as it imports, but if it doesn't like a contact, regardless of how many it counts before the offending one, the import fails. But this will at least give you an idea of how many the car 'liked' before the first failed one.
I find this quite frustrating, but I got it to work in the end. Now, I re-read my contacts every couple of months to see if they still update; once you put a contact it doesn't like, the updates stop for the phonebook even though it retains the ones it already had. Whenever I run into a problem, I look at creation/modification time in my contacts to figure out which is the offending one.... but I really wish Audi would fix this. It's not rocket science! At the very least, it should feed back to the user which contact it cannot process!
There are a couple of experiments to try. First one, have a single contact with just a name and a phone number on the phone, and nothing else. See if that imports. If it does, then the issue is most likely a formatting thing.
In my case, I have a Rezound and I use Outlook for my contacts. What I noticed is that if I had any carriage returns in any contact, it would not import. I found this most commonly in addresses, where, typically, each field is separated by carriage returns. I substituted all CR with commas.
I also had a contact with two email addresses. That one did not work either. Removed one address.
What I ended up doing is deleting groups of ocntacts until it successfully imported, then figuring out which ones were the culprits by elimination. Knowing the carriage return thing was enough to fix most of mine.
You can also figure out what's going on (to some degree) by manually importing contacts; the car 'counts up' as it imports, but if it doesn't like a contact, regardless of how many it counts before the offending one, the import fails. But this will at least give you an idea of how many the car 'liked' before the first failed one.
I find this quite frustrating, but I got it to work in the end. Now, I re-read my contacts every couple of months to see if they still update; once you put a contact it doesn't like, the updates stop for the phonebook even though it retains the ones it already had. Whenever I run into a problem, I look at creation/modification time in my contacts to figure out which is the offending one.... but I really wish Audi would fix this. It's not rocket science! At the very least, it should feed back to the user which contact it cannot process!
#6
Did you get this to work? I was about to order the HTC One and was never able to get the HTC One X+ to work on my 2012 A6 with Nav. If the SD import works and then subsequent changes sync, I'd go ahead with the HTC One. Let me know - thanks.
#7
Audiworld Junior Member
Thread Starter
Join Date: Aug 2010
Posts: 14
Likes: 0
Received 0 Likes
on
0 Posts
I tried syncing to my wife's allroad and that wouldn't work either.
Trending Topics
#8
I find this quite frustrating, but I got it to work in the end. Now, I re-read my contacts every couple of months to see if they still update; once you put a contact it doesn't like, the updates stop for the phonebook even though it retains the ones it already had. Whenever I run into a problem, I look at creation/modification time in my contacts to figure out which is the offending one.... but I really wish Audi would fix this. It's not rocket science! At the very least, it should feed back to the user which contact it cannot process!
#9
I just received by HTC One and have no issues getting the car to import all my contacts. Was actually pretty quick compared to my Galaxy S2.
For reference, I have a 2013 A6 Prestige.
For reference, I have a 2013 A6 Prestige.
#10