Volume Control while listening to XM and Navigating in Android Auto

While traveling yesterday, listening to XM Radio, and Navigating with Android Auto, I found that changing either volume control affected only the navigation messaging loudness, not the XM programming. The top of the screen showed "Guidance Volume" while I was trying to change the loudness, and I was unable to find a way to change the XM volume without interrupting the Navigation activity, so I finally just shut off Audio until we arrived at our destination.

I've been digging through the Owner's Manual to try to find a way to switch the XM volume without success. I'm hoping someone else has found a solution, assuming there is one.

 

I could be wrong, but it seemed that the touch screen control acted the same as the steering wheel control. I'll try it again tomorrow with the car in the garage. It's really hard to troubleshoot those problems while driving. My passenger was complaining about it being too loud, and I just gave up by turning it off.

 

It makes sense that it would affect any Audio program source - XM, bluetooth, FM, etc.

I guess it's a good thing that it's apparently a known problem, but a bit troubling that he said that they "might" address it. While it's not a problem that shows up every driving day, being unable to adjust programming volume while navigating on a long road trip is a pretty annoying failure.

 

It's worse than I thought. I confirmed that Android Auto doesn't have to be actively navigating to disable control of audio volume from the entertainment group. Android Auto can be in any mode, it just has to be plugged in. The steering wheel and screen volume controls affect only the Android input.

Unless Honda comes up with a fix, I will first need to find an acceptable volume level for my XM or other source. then plug in my phone to also use Android Auto. I wonder if the Clarity has the same issue with Apple Car Play.

 

You might see an edit option for your own posts, in the lower, right hand corner, next to Quote, Reply, etc. I wouldn't worry about it, though - it was an honest recollection of a prior experience, and it's possible it may have worked that way under the right circumstance - I appreciate the feedback on the issue. It's funny that I never noticed the problem in my first 9+ months of ownership, but this was my first long road trip, using Navigation via Android Auto with XM playing. Had my daughter not complained about the loudness, I never would have noticed it.

Correction - Edit is in the lower left corner, next to Delete and Report

 

After more experimenting, I found that I could have Android Auto active, and still have the volume controls work properly with the other audio input sources, XM, bluetooth, FM, AM, etc - up until the point that I started an active navigation session in Android Auto.

After that, it didn't matter what I did with Android Auto. I could terminate the nav session, or switch to other functions, but it didn't release the Volume Control back to the other inputs, so I could no longer change volume on the other inputs.

 

Thanks for the detail, Reissc and KevinW. I'll try it out in the morning to make sure I can do the same on mine. Either way, though, we have to give up something, either the turn by turn instructions, or the ability to turn the program volume up or down. I suspect I would opt to set the program volume to an acceptable level prior to starting a navigation cycle, and utilize the turn by turn stuff.

 

If I "Mute" the navigation, I am able to continue to control volume on the other sources, but if I select "Traffic Alerts Only", if it ever does a reroute during the trip, the accompanying beeping sound causes it to lock the volume control to navigation only, until I disconnect the phone.

For my use, I plan to first set an acceptable volume level for the programming audio, prior to starting a navigation session. I don't want to miss the turn by turn instructions, or the Traffic alerts.

I don't know when the problem started, but I've only had one software update applied to the Clarity, that being the HV Mileage Fix, some months ago. The problem is insidious, and easily missed, in that everything works fine until I do an active navigation cycle via Android Auto (with Mute not selected).

 

Thanks, Numbernine for your suggestions of a workaround. I appreciate your time and effort to help by sharing what you have found.

I tried it tonight. While Navigating, I called out "OK Google", then when it responded I said "Cancel". After Google Assistant bleeped off, volume control did switch over to the normal audio source. That continued until the next navigation message, which switched control back to the Nav messaging.

That workaround will be helpful if I ever encounter the problem again, especially if there are significant times between Nav messaging, that will allow some time, as in a long road trip, to get it to switch and for me to make the desired program volume change. I typically don't use Navigation for short trips in my area, so it should work when I will mostly likely need it, with no need for the distraction of me to be poking around on the screen.

 

That's great news, Numbernine. Following your lead, I took an easy way to update the app and signed up for the Google Play Services beta: <https://developers.google.com/android/guides/beta-program>, using the recommended opt-in URL. It looks like it's easy to opt-out later, if I encounter any problems with it. There were no warnings about opting-out resulting in anything like a Factory Data Reset, so I expect it will be transparent, if I do.

It hasn't started downloading yet, but I'll check it out on my phone as soon as possible. Thankful that this turned out to be an Android problem, rather than Honda, and we don't have to wait for a Service Bulletin for a fix.