Volume normalization not working

[jnrfalcon]

Plan

Premium

Country

Device

Pixel 7 Pro projecting to Android Auto

Operating System

Android 15 beta

My Question or Issue

Volume normalization on Android is not working, at least through Android Auto. It now makes loud music louder and quiet podcasts quieter.

[Vasil]

Hey @jnrfalcon,

Thanks for reaching out!

This issue could either be caused by the Pixel phone, its Android Auto connection to the vehicle or because of the Android Beta version and how it handles the Android Auto connection. Testing which one it is would also be a bit difficult because of the specific device/ OS combination but we can try out a few things here 🙂

Does the same thing occur when setting the Volume Normalization to off/ high/ low (in case it's currently set to normal)?
Does the issue appear only when using Android Auto? What if you use a regular USB cable/ Bluetooth connection?
We'd also like to know when the issue has started appearing and if it has ever worked before.

Note: Keep in mind that Volume Normalization with Android Auto (or other Connect devices) has caused similar issues in the past. Turning it off was the effective workaround at the time.

Keep us posted on how things go! We'll be on the lookout.

[jnrfalcon]

Limited testing this morning.

Start with projecting to AA, Normalizing, continue podcast: volume is fine, switching between normalization modes produce expected results 

Switch to music: volume is fine 

Switch back to podcast: volume very low

Turn off normalization: podcast volume back to normal 

Switch back to music: volume very high

Switch back to podcast: volume normal

I'd say the issue started about 1 months ago. But I don't know for sure.

[Eni]

Hey @jnrfalcon, 

Thanks for keeping us in the loop. 

In this case, could you ask a friend or a relative to log in to their account on your device to see if they can replicate this with their account?  If so, could you give a different phone a go to see if the same happens? 

Additionally, make sure to send us all details @Vasil asked for previously. All this info will help us determine what might be causing this behavior. 

We'll be on the lookout.