Android Auto Audio Nightmare: OnePlus 15 (Global)

[lucky_4_honey]

I'm reaching out from Australia hoping the collective wisdom of the community can save me from having to switch phones—a move that would be purely driven by a baffling technical glitch.

I recently upgraded to the OnePlus 15 (Global Version) and paired it with my car, a Genesis GV70, via Android Auto. While the phone itself is great, my workflow has hit a major roadblock that threatens my professional life. As a real estate agent, I rely heavily on being able to take meetings from the car, and my previous Samsung Galaxy S23 FE handled this perfectly.

The Problem: Video Works, But Audio Fails (Google Meet)​

My phone is set up with both a personal profile and a work profile (due to being logged into my work Gmail account). When I connect to Android Auto and join a Google Meet call:

1. Video: I can see the video feed of the meeting participants perfectly on the car's display.
2. Audio Failure: I cannot hear anything through the car’s speakers, nor can the meeting participants hear me. It's a complete, two-way audio blackout specific to the Meet application while connected via Android Auto.

It seems the phone is successfully passing the display stream, but it's failing to correctly route the audio input and output through the car’s Bluetooth or USB connection. Since this is an essential function for my business, I am seriously considering reverting to a Samsung device, which is something I really don't want to do.

Has anyone else experienced this specific issue on a dual-profile device, a Global Version OnePlus, or with a similar car head unit configuration?

My best guess is that the work profile permissions or the dual-profile setup is interfering with how Android Auto handles Bluetooth/speakerphone audio routing specifically for video conferencing apps.

Any advice, workarounds, or known fixes would be greatly appreciated! Please help me solve this audio routing conundrum.

 

[Venom0642]

I'm reaching out from Australia hoping the collective wisdom of the community can save me from having to switch phones—a move that would be purely driven by a baffling technical glitch.

I recently upgraded to the OnePlus 15 (Global Version) and paired it with my car, a Genesis GV70, via Android Auto. While the phone itself is great, my workflow has hit a major roadblock that threatens my professional life. As a real estate agent, I rely heavily on being able to take meetings from the car, and my previous Samsung Galaxy S23 FE handled this perfectly.

The Problem: Video Works, But Audio Fails (Google Meet)​

My phone is set up with both a personal profile and a work profile (due to being logged into my work Gmail account). When I connect to Android Auto and join a Google Meet call:

1. Video: I can see the video feed of the meeting participants perfectly on the car's display.
2. Audio Failure: I cannot hear anything through the car’s speakers, nor can the meeting participants hear me. It's a complete, two-way audio blackout specific to the Meet application while connected via Android Auto.

It seems the phone is successfully passing the display stream, but it's failing to correctly route the audio input and output through the car’s Bluetooth or USB connection. Since this is an essential function for my business, I am seriously considering reverting to a Samsung device, which is something I really don't want to do.

Has anyone else experienced this specific issue on a dual-profile device, a Global Version OnePlus, or with a similar car head unit configuration?

My best guess is that the work profile permissions or the dual-profile setup is interfering with how Android Auto handles Bluetooth/speakerphone audio routing specifically for video conferencing apps.

Any advice, workarounds, or known fixes would be greatly appreciated! Please help me solve this audio routing conundrum.

I'll see if i can find a solution, but on my Global Oppo Find X9 Pro i do lots of google meet and no issues here at all ,
Same with Android Auto no issues at all,

 

[spARTacus]

I think there's normally an ability to temporarily pause the work profile. That might help to confirm if it's something about the work profile causing the problem, if everything works fine for the Phone and Android Auto together for the personal profile when the work profile is paused. Did your old phone have work and personal profiles, and that all worked fine for both profiles for the Phone and Android Auto?

 

[lucky_4_honey]

I think there's normally an ability to temporarily pause the work profile. That might help to confirm if it's something about the work profile causing the problem, if everything works fine for the Phone and Android Auto together for the personal profile when the work profile is paused. Did your old phone have work and personal profiles, and that all worked fine for both profiles for the Phone and Android Auto?

Thank you, that was a good suggestion to try Google Meet from my main/personal profile in the car. I paused all apps on my work profile. And joined Google Meet from personal, but the issue persists. No audio through the car speakers and participants can’t hear me either—complete two-way blackout.
I deleted and reconnected the phone in the car’s settings, but the problem remains. Looks like an Android Auto or Bluetooth issue.

My old Samsung Galaxy S23 FE handled this perfectly fine with both personal and work profiles from day one

 

[Bkdodger1]

When I searched for solution this one came up, number 2 I've come across before where it was in phone audio ..



1. Check In-Call/In-App Audio Settings
When the Google Meet call is active:
Check the Google Meet Audio Source: On your phone screen (or car display if the option is available), look for an audio source/speaker icon within the Meet app. It might be set to "Phone Speaker" or "Wired Headphones" instead of the car's "Bluetooth" or simply "Speaker" (which should route through Android Auto). Tap it and select the correct output.
Check Phone Volume: Make sure the media volume on your phone is turned up. Sometimes the volume slider for calls/media gets separated when connected to Android Auto.
Is the Call Muted? Verify that you are not accidentally muted in the Google Meet app itself.
2. Address Bluetooth and Audio Conflicts
Since Android Auto uses a combination of USB (for wired) or Wi-Fi (for wireless) and Bluetooth for calls/audio, conflicts can happen:
Dual Bluetooth Connection: Your phone might be connected to your car's standard Bluetooth profile and connected via Android Auto. This creates a conflict.
Fix: Go to your phone's Bluetooth settings, find your car's connection, and disable "Media audio" for that connection, keeping only "Phone audio" enabled (or vice-versa, depending on your car's system). Some suggest unpairing/forgetting the car's stock Bluetooth connection entirely and letting Android Auto manage all media.
Restart Bluetooth: Simply toggling Bluetooth off and on again on your phone while connected can sometimes reset the audio routing.
3. General Troubleshooting for Android Auto
If the above doesn't work, try these standard fixes:
Restart Everything:
Restart your phone. This is the simplest fix for many Android Auto glitches.
Reboot your car's infotainment system (often by holding the radio's power button until it restarts, check your car's manual).
Clear App Cache:
Go to your phone's Settings > Apps > See all apps.
Find Android Auto and/or Google Meet.
Go to Storage & cache and tap Clear cache (do NOT clear storage/data unless you are willing to completely set up Android Auto again).

 

[Bkdodger1]

Additional GV70 query

1. Bluetooth Dual-Connection Conflict (Most Common)
Android Auto uses a dedicated connection for media/data, but sometimes it relies on the car's Bluetooth Hands-Free Profile (HFP) for calls. If your car is independently connected to your phone's Bluetooth Media Audio at the same time, it can cause calls (like Google Meet) to get routed incorrectly.
Action to Take on Your Phone:
Disconnect Android Auto (unplug, or turn off Wi-Fi/Bluetooth if wireless).
Go to your phone's Settings > Bluetooth.
Find your car's connection (e.g., "Genesis GV70").
Tap the settings gear/info icon next to it.
Disable "Media audio" or "A2DP" (Advanced Audio Distribution Profile). Keep "Phone audio" (HFP) enabled.
Reconnect Android Auto. This forces Android Auto to handle the audio fully.
2. Genesis Infotainment System Audio Settings
Check these settings in your GV70's infotainment system (usually under Setup > Sound):
Connected Device Volume:
Navigate to Setup > Sound > Connected Device.
Look for the "Android Auto" volume setting and ensure it is not set to a minimum level or muted.
Guidance/Navigation Volume Priority:
Navigate to Setup > Sound > Guidance.
Settings like "Navigation Volume Priority" lower all other audio volumes when a navigation prompt is playing. While this usually doesn't mute calls entirely, having too many "priority" sounds can disrupt the Meet audio channel.
Media/Call Switching:
In some Genesis models, you can find a setting under Setup > Device Connections (or Phone) that relates to "Activate Vehicle's Bluetooth Audio". Ensure this is set to allow the phone/Android Auto to manage audio switching and not restrict it only to the Navigation system.
3. Source Selection During the Call
While in the Google Meet call:
Check the Media Source: When the call is active, look at your GV70's display to see what the active Media Source is. It should show Android Auto. If it has reverted to FM, AM, or Bluetooth Audio, manually switch it back to Android Auto or the Phone Projection screen.
Summary Troubleshooting Steps
Phone Side Fix: Disable Media Audio for the GV70 connection in your phone's native Bluetooth settings (step 1 above).
In-Call Fix: Ensure the audio output is set to the correct source within the Google Meet app on your phone screen during the call.
GV70 Reset: As a last resort, try resetting the head unit (often by pushing a small reset button near the volume knob or tuning knob) and then completely unpairing and re-pairing your phone to the car.
Did disabling the "Media audio" profile on your phone's Bluetooth settings for the GV70 connection resolve the issue?