Does anyone use a USB for their music (Media Player) and have voice commands work?

[Sharbotcom]

I see the same on my 24. Given that Ford is drowning in recalls (people, money) they must be cutting costs any way they can. Earlier this year they let go programmers.

Same on my 24.

 

[markfm]

I see the same on my 24. Given that Ford is drowning in recalls (people, money) they must be cutting costs any way they can. Earlier this year they let go programmers.

I'd still log an issue, it sounds like this should honestly be readily fixable, as it works as expected on other AAOS vehicles.

Frequently Asked Questions

AudioWagon. Android Automotive OS USB music player

moleman1024.github.io

"This is usually a flaw in the car maker’s implementation of Android Automotive. Google provides a piece of software that can fix this: car-usb-handler. This problem can usually only be fixed by the car maker."

 

[angore]

A thought. If the Lincoln software updates are applied via USB, could the default handler aspect impact that? This would be the difference between working as design or a software bug.

 

[markfm]

A thought. If the Lincoln software updates are applied via USB, could the default handler aspect impact that? This would be the difference between working as design or a software bug.

That shouldn't be it. What they're talking about setting the default USB handler for files of type music. Things using the "Play" type commands. It does work within a session, they're just not properly storing/using the tick box selector.

______________________________

Help support this site so it can continue supporting you!

 

[angore]

Is there any default handler for media (not just usb)? When I ask to play music it always asks if I am want youtube, spotify, etc. It never defaults to any and never saw an option to do that. But still learning how stuff works. And if I do not click the audiowagon setting, it will not even recognize it via voice or touch.

 

[markfm]

It has the built-in sets of AM, FM, SiriusXM, doesn't have a built-in that works for USB music that I've seen.

Needing to click the audio wagon setting is due to the lack of persistence, that it is ignoring the "Always open AudioWagon..." checkbox to allow it to have continued access/control for USB (music).

Google has the software to allow third party apps to access the USB, with proper persistence, called car-usb-handler. It's on the car makers to actually use it, integrate it properly, in their infotainment systems.

The AudioWagon FAQ I pointed to details this. It took Volvo/Polestar multiple years to get around to adding it, works fine now. GM has the same issue with their '25 Chevy Equinox EV.

For Lincoln we have the '24+ Nautilus - need to log complaints via Concierge or similar, tell them what is wrong and what needs to be done (implement the Google-supplied car-usb-handler software, test that it is properly working by adding AudioWagon from Play Store, see if retains access to the USB across multiple audio system restarts).

(It may well be a problem in the '25 Navigator too, since that now has AAOS. If so, Navigator owners should also log complaints via Concierge.)

 

[angore]

The issue I saw was that audio wagon could not even access the USB key files until the setting was checked (looked like a permission issue on access) but then you have to have the usb handler to know the difference between a music usb key and a software update usb key since one wants software update keys to get priority. The attachment of a phone is more complex - usb key, phone, navigation.

I agree software needs to be improved.

 

[markfm]

The car-usb-handler associates an app (e.g., AudioWagon) as the handler for a specific USB device, not a global "use-this-for-all-USB".

The issue is that in Lincoln's existing implementation, "a" in the below (comments in the Google video) isn't occurring. For whatever reason that choice to always have AudioWagon associated with a specific USB isn't being captured properly.

/**
* Activity to handle USB device attached.
* <p>
* When user plugs in USB device: a) Device was used before and user selected handler for it. In
* this case handler will be launched. b) Device has not handler assigned. In this case supported
* handlers will be captured, and user will be presented with choice to assign default handler.
* After that handler will be launched.
*
* <p>Note: Activity launched by the system and by {@link BootUsbService}.
*/

______________________________

Help support this site so it can continue supporting you!