I am beyond frustrated with Acura.

I purchased my TLX in February, and my phone did not work correctly with the HFL.
My phone is listed on their (very outdated) website that lists compatible phones. It lists my phone as fully compatible with all features (except Siri). My phone is an HTC One (M8) with Verizon.

So, my phone does not work with their system.
Basically the phonebook transfer feature transfers some data, but the phone entries all come up as "other" so i don't know if I'm calling someones office, mobile or cellphone. Quite frustrating.

Acura will not fix this.
Acura say that "everything is working as designed".

Their own manual (TLX manual, P243) shows that the phonebook should show the phone number and phone number TYPE when you open up a contact (it's in the 2nd image.)
It does not do this.

Acura say that they are no longer working on fixes, and will not be fixing this system.

I've escalated this through my dealership, and though Acura Customer Care.
The final person I spoke to made it very clear that they are not going to fix this, and he is the top person; they will not escalate this any further.

What the heck am I supposed to do.

Anyone any suggestions?

Nick.

 

<p>nick, you have to understand that car eletronic hard ware is outdated, as soon as the car begins production.</p><p>This is why they have said they are not going to go forward in trying to fix your issue.</p><p>&nbsp;</p><p>All manufactures do this. because they have to test the hard ware in advance before the car goes on sale. they are likely using technology from last generation.<br />&nbsp;</p>

 

Why do I have to understand that?

They made the car, and gave a list of phones that they are compatible with.
I have one of those phone.
I bought their car.
It does not work.

Now they won't fix it.

Do I get to flake on my loan and just tell them I'm not paying it anymore?
No, they would send me to collections.

So, their car does not work with my phone, when they said it would.
Solution: "Fuck you, sir" - which they said with a smile on their face.

As I said, I am beyond frustrated.

 

<p>^lol over a phone.&nbsp;</p><p>&nbsp;</p><p>what will you ever do?</p>

 

<p></p>

 

yes, it seems minor and trivial.
But I spend a lot of time in my car, and I often have to return phone calls, etc.

The car is great, and drives wonderfully.

But the fact that they cannot get their phone interface right really frustrates me.
My wife has a Honda with a HFL, and it works great, with every phone that I've had.

The Acura TLX does not.

I've tried the HTC M8 - the phone book does not work.
I've tried the Samsung S6 - it crashes the bluetooth every 10 minutes.
I've tried the Nexus 6 - the phonebook does not transfer.

Bottom line is that the HFL suck, and I am so frustrated that Acura will not stand behind their product.

Nick.

 

If you have not already tried, unpair the phone removing it from the car system, and pair it again. I had one instance where resetting my phone fixed an import issue.

 

Makes you wonder about the times before cellphones existed. HOW DID PEOPLE SURVIVE NOT BEING ABLE TO INSTANTLY GET IN CONTACT WITH ONE ANOTHER?!?!

 

My Droid Turbo from Verizon works fine with HFL. And it has totally awesome battery life, a fantastic screen, and it is rugged as hell, including water-resistant nano-coating. :-)

 

My BB Q10/TMo, is awesome; perfect clarity, & great connectivity!
It's two years old, & loves my TLX/SH-AWD/Tech!
Only hiccup is that the contact name, doesn't appear on the Nav. screen; only the phone#.
Make fun of BB all you want; it's the best BUSINESS PDA out there; Trix are for kids; NOT BlackBerry!

 

I have a Sprint M8 (mine), and a Verizon 5S iPhone (work) that both seem to work fine with my car, and that's for phone functions, and for bluetooth music streaming.

I have had issues here and there where I did unpair, and re-pair the phone to get my text messages read to me, etc. As was suggested, I would try that first.

What issues specifically are you having with the phonebook? When I have contacts with multiple numbers, when I open the contact up, the various numbers do pop up, but it sounds like that is not happening in your case/car.

The only time I don't see those details on the screens is when I go into the recently dialed numbers using the phone's call history. For everything else, scrolling through the phonebook, reading texts, speed dials, and the phone shortcut numbers I setup all work great.

 

The issue is simple.

The phonebook shows that a contact has multiple different phone numbers (office, home, cell, etc) but when I go into the contact all the numbers show as "Other".

The manual says that I'm supposed to be able to tell what kind of number I'm calling when I hit dial.
The experience in my car is different.

I have unpaired, and re-paired.
I have turned off, then on, the phonebook transfer.
I have upgraded the software on my phone.
I cannot get it to work with my phone.
My phone is on the list of compatible phones.

Nick.

 

I had an issue with a 2012 Honda on the contacts, turned out it was the source of the contacts that caused the problem. I had an Android phone but the contacts had been migrated from a Microsoft outlook/hotmail data base. I imported them to the gmail and I had to do some clean-up on the gmail contacts because of data that was not well field matched. Then I established the gmail account on the phone and all the contacts came from that source. The TLX has been problem free from the beginning on a first and second generation MotoX from Verizon.

 

"I've tried the Samsung S6 - it crashes the bluetooth every 10 minutes."

Well, the S6 works perfectly well for me.

 

Hmm... I wonder what the cheaper solution might be, get a different phone of get a new car?

 

buy an iPhone.....sounds easier than buying a new car. And think of all the time you will save

 

Even my $100 Windows works perfectly and does everything I need.

 

I tried with my original M8 - the only phone offically supported.

I then tried the Samsung S6 - but the bluetooth crashed every 10 minutes.
I replaced the phone with a new one - same issue.
I took the phone to their factory repair center in LA, they said there was no issues.
I put the phone in safe mode (no 3rd party apps) - same issue.

I tried with a Nexus 6.
Didn't even transfer the phonebook.

I need android tools on my job; I can't have an iphone.

Dammit Jim.

 

I gotta look into this if it occurs on mine. I mostly rely on Siri to make a call.

 

S4 has worked great since I paired the phone 11 months ago.

I have listened to hours and hours of audible books over BT.

 

Despite this being a first-world problem and not that big a deal in the grand scheme of things, I also understand the complaint. If the phone is specifically listed as supported then Acura has an obligation to deliver.

In the meantime, I would try the following: make a new, test contact in your phone. Make several phone entries for the test contact, one for every "type" category allowed (office, home, etc.). Make the fake numbers unique so that you can identify them: 1-555-0001 for home, 1-555-0002 for office, etc. Re-pair your phone to the car and see how they are listed. It could be that the indexed categories are different from the phone's listings to the imported values.

 

I just went out and tested this with my Nexus 6.



Set up a fake contact with fake Home, Mobile, and Work numbers as djsteve suggested.



Listed correctly, as OP's photo showed.



Correctly showed all phone number categories with the correct numbers attached to each one.

OP: Please post all of the details for each of the phones you used. My phone's details are as follows:

Model: Nexus 6
Android version: 5.1.1
Build number: LVY48E
Service provider: Project Fi
Root: Yes
Bootloader: Unlocked

If you need help finding any of this information, please let me know.

The goal is to eliminate the phones as a potential issue. Once the phones are out of the picture, only the car could be the source of the issue.

Also, I see you're located in Los Angeles. If you'd like, we could meet and you could try your phone(s) in my car (and vice versa) to see if the issue persists.