I don't think so but I'm still a little confused about how call handling and mic hand-off (for voice command) works. Bluetooth was disabled on my phone and I made a call. It used the handset speakerphone for the call which I thought was strange. While on the call I turned on Bluetooth and the phone connected to the Acura system and the call audio switched over to the car speakers.Do you see the joystick input delay when you are on phone call using AA?
You were right. After locking the door and waiting about 30-45 seconds it stopped charging.Hmmm well it gets power from intercepting the harness of the head unit, so it should power off with the head unit. It is possible that the head unit has a delayed shut down, where the power cuts off totally after things like door opening or after a certain time. Maybe try waiting a bit next time you turn off the mdx and see how long before you lose power indication on the phone end.
Sent from my Pixel using Tapatalk
When I talked to support they said that on the MDX Bluetooth is used for calls and that the wired mic is only for voice commands. Without Bluetooth calls come thru the handset speakerphone.Did you try to make phone call through Navtool mic? Do people hear your sound?
Did you connect to the correct mic cable? And try to speak to the mic as close as possible.
Sent from my iPhone using Tapatalk
So you are able to make calls without Bluetooth and have the incoming audio route over the Aux input and thru the car speakers and it uses the wired mic? If so that directly conflicts with what navtool support told me for my 2016 MDX. Maybe it changed in a recent navtool software update?The Bluetooth + Carplay at the same time caused freezing issue for me, and it seems to confuse the car/Navtool as well.
I removed my phone from my car Bluetooth device list, and it seems to work well.
No, I'm not aware of anyone did these steps. If I understand the situation correctly, it seems they try to ask you to update the BIOS (Basic Input/Output System. firmware) of the Navtool. It is different from the software (updated via updater).@leochen,
I tried disabling bluetooth and making calls and it just sends the audio through the handset speakerphone. The only options I have (using Android Auto, not Carplay) is phone or speakerphone. Both use the speakers on the handset itself.
I'm still having a ton of crashing/freezing issues where the display in the car freezes and the phone gives a fullscreen error that says something like "Android Auto encountered an error, communication error 12". I've been going back and forth with support on Facebook chat and they are telling me there is a new firmware he referred to as R7 that fixes this. He sent me a dropbox link to a RAR file with some files it in and instructions to load them onto a thumb drive and flash the Navtool via USB (not using the sotware updater). In short the instructions involved
1. formatting a thumb drive as FAT32
2. copying the files to the root of the drive
3. unplugging the main connector to the navtool
4. insert USB drive into the navtool USB
5. plug in wiring harness back into the navtool to restore power
6. wait 10min
7. unplug wiring harness
8. unplug USB thumb drive
9. plug in wiring harness
I've tried countless times and can't get this stupid thing to update. The person responding on chat insists there are thousands of customers who update Navtool using this process and that I'm not doing it right. Has anyone updated their Navtool like this? If so I'd love some help.
UM132129. Software is 2.3No, I'm not aware of anyone did these steps. If I understand the situation correctly, it seems they try to ask you to update the BIOS (Basic Input/Output System. firmware) of the Navtool. It is different from the software (updated via updater).
Can you provide your device model and software version in the updater tool?
Does the Carplay work on your wife's phone?
It is the same device and software version as mine.UM132129. Software is 2.3
I'm not sure. I mean it works long enough to test it but then again so does mine. For me it may crash 5 minutes into a drive or 55 minutes. It only seems to happen when I'm using AA for navigation. I've seen it happen with both Waze and Maps.
She's never used Carplay aside from the initial testing I did.
For what it's worth I've tested with 5 different cables including 3 new that I bought just to try and fix this. I also tested with a Google Pixel XL running stock Android 9 so if it doesn't work on that with the factory cable it's a Navtool issue.
Its hard to really test Carplay because it's not my phone and it would have to be a pretty long drive to really know if it would happen if I were using AA.It is the same device and software version as mine.
For the BIOS/firmware update, did they mention how to check the BIOS/firmware version of the device? I can't find this info to compare with your device, but I only use Carplay, so I'm not sure how valuable it is even we can find the BIOS/firmware version.
I would recommend trying Carplay, and see if it works. If it doesn't, it is probably device issue, you should get return/replace it.