In this guide, we will show you a nifty workaround that might help you fix the issue of calls not working via Android Auto on Pixel 8 Pro. This service from the Silicon Valley giant has completely streamlined the process of mirroring features of an Android device onto a car’s infotainment system. However, it tends to hit a roadblock or two at frequent intervals as well. For instance, numerous users have voiced their concern that calls not working via Android Auto on Pixel 8 Pro.
“We cannot make any calls though the car’s speakers. If we try to connect solely to the Bluetooth, the connection fails. If we connect by cable got Android auto, the music will stream through the car speakers. But receiving a call or making a call only goes through the phone’s speakers. No option to go through the car speakers…. [Source]”
The connection tends to fail every time they try and establish a Bluetooth connection with the car to make a voice call. Along the same lines, it tends to affect both incoming and outgoing audio during voice calls as well. The issue first came to light after the latest Android 14 update and has been bugging users ever since. If you are also currently affected by this issue, then this guide will make you aware of various workarounds to address this concern once and for all. Follow along.
Fix Pixel 8 Pro Calls via Android Auto not working
For some users, the below-listed workaround has spelled out success. So let’s give it a try and check if it works out in your favor or not.
- Go to the Bluetooth settings and tap on the settings icon next to your device.
- Then set the Device Type from “unknown” to “Headset” or “Hands-free talking”.
- Now check if calls are working via Android Auto on Pixel 8 Pro or not.
If you are still facing this issue, then refer to our guide on Android Auto Not Working on Android 15: How to Fix which comes with an additional 16 fixes, any one of which should help you mitigate this problem, at least till the time being. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.
