Android Auto Audio Apps: What React Native Track Player 5.13.0 Changes

The short answer is that React Native Track Player (RNTP) 5.13.0 is an app-library release, not a universal Android Auto or vehicle update. The official RNTP changelog says the release adds Android Auto and Android Automotive browse-folder grid support, restores iOS 15.1 support and fixes Android media-item extras that could change from strings into numbers.

That distinction matters for drivers and app teams. An audio app must adopt the library, publish the relevant browse data and run on a compatible phone-and-car setup before a driver can see a practical difference. The release does not make every Android Auto audio app show a grid, and it does not prove compatibility for a particular vehicle, trim or connection mode.

What RNTP 5.13.0 changes for Android Auto audio apps

RNTP 5.13.0 adds childrenStyle to browse categories and folders. According to the changelog, an app can ask Android Auto and Android Automotive to show a folder's children as a grid or a list. The setting can be chosen separately for browsable folders and playable items, which gives an app more control over how an audio catalog is organized.

The same release note says the setting is saved with the browse tree, so it also applies when the car starts the app cold. That is an implementation detail for the app team, not a promise that a car's entire interface has changed. Google's Android Auto media-app guidance also describes standardized browsing views, so the app provides content and structure while Android Auto and the car control much of the driving-optimized presentation.

Release detail	What it can mean	What it does not prove
childrenStyle for Android Auto and Android Automotive	Compatible apps can request a grid or list for browse-folder children.	Every audio app or every car will show the same layout.
Browse-tree setting persists for a cold start	The app can retain the intended browse presentation when it starts in the car.	A cold start, phone connection or vehicle compatibility is guaranteed.
CarPlay ignores the option	The documented grid/list behavior is specific to the Android Auto and Android Automotive path.	The same option can be transferred to CarPlay without separate implementation work.

Why the media-item extras fix matters

The second Android Auto-relevant change is less visible but important for app data. The RNTP changelog says that after a user picked an item from Android Auto, extras such as id: '14073' could come back as the number 14073 in MediaItemTransition and the queue. In v5.13.0, strings stay strings.

For an app, that can prevent a type mismatch when an ID is used to look up a track, episode or station. For a driver, the practical outcome is not a new button on the dashboard; it is a better chance that the selection continues to resolve to the intended content when the app handles the Android Auto event.

This is an app-data correctness fix. It should not be described as a universal Android Auto performance improvement, an audio-quality upgrade or evidence that a vehicle received a new infotainment system.

The iOS 15.1 change is separate from Android Auto

RNTP 5.13.0 also moves the minimum iOS version down to 15.1 from 16.0. The changelog explains that this matches React Native's minimum and notes that the player handles playback speed itself on iOS 15 because AVPlayer.defaultRate is only available from iOS 16.

That iOS change should not be mixed with the Android Auto browse-grid change. The release page lists Android Auto, Android Automotive and iOS behaviors in the same library version, but they remain different platform paths. Android Auto is a phone-to-compatible-car experience; Android Automotive OS is an infotainment platform built into some vehicles. Google's Android for Cars overview describes that distinction for app developers.

What drivers and app teams should verify

If an audio app appears different after an update, check the app version and its release notes first. The relevant question is whether that app adopted RNTP 5.13.0 and actually publishes a browse tree that uses the new option. A library release alone cannot change an app that still ships an older dependency or uses a different media implementation.

1. Record the app version. Check the store version and the app's own release notes before attributing a grid, list or selection change to RNTP.
2. Separate the platform paths. Confirm whether the test is Android Auto, Android Automotive OS or CarPlay. The v5.13.0 childrenStyle note is not a CarPlay feature.
3. Check the phone and car. Google's Android Auto overview and Android Auto Help separate compatible-phone, compatible-car and wireless requirements.
4. Test the cold-start path. If the app is expected to retain its browse layout when started from the car, test the browse tree after the app process has been stopped and restarted.
5. Test while parked. Update the app, pair the phone or clear a connection only while the vehicle is stationary. A media app is a driving aid, not a reason to interact with a screen while moving.

A missing grid or a failed selection does not identify one universal cause. The result can depend on the app's dependency version, the browse data it publishes, the phone, the Android Auto state, the vehicle and the connection path. Capture those details before changing hardware or assuming that an adapter is needed.

What this update means for adapters and compatibility

RNTP 5.13.0 does not establish that a specific vehicle supports Android Auto, that its connection is wireless, or that a CARLUEX adapter is compatible. An app library can change how an app supplies media content; it cannot create a missing factory phone-projection path or override the requirements of the phone and vehicle.

For a different vehicle whose factory-wired CarPlay path has already been verified, the CARLUEX compatible vehicles page and CARLUEX Help Center are conditional eligibility and setup references. The CARLUEX PRO+ 2.0 product page is also only a conditional reference for that separately verified case. This is not a product recommendation for the RNTP update, and it does not claim compatibility with a particular Android Auto vehicle.

Only consider an adapter after the exact vehicle's factory connection path and product eligibility have been independently verified. If the question is about the app itself, start with the app version, the official release notes and the phone-and-car requirements.

Frequently asked questions

What is new in React Native Track Player 5.13.0 for Android Auto?

The release adds childrenStyle, which lets compatible apps request grid or list presentation for Android Auto and Android Automotive browse-folder children. It also fixes Android string extras that could return as numbers after an item was selected.

Does v5.13.0 make every Android Auto audio app show a grid?

No. The app must adopt the library, publish the relevant browse data and run in a compatible Android Auto environment. The vehicle and Android Auto presentation layer can still affect what a driver sees.

What are Android media-item extras?

They are app-defined values attached to a media item, such as an internal ID. In v5.13.0, the documented Android fix keeps string extras as strings in the transition event and queue instead of converting them to numbers.

Does this update change CarPlay?

The changelog says CarPlay ignores the childrenStyle option. RNTP 5.13.0 includes an iOS 15.1 minimum-version change, but that is separate from the Android Auto browse-grid behavior.

Does this release prove that a vehicle or adapter is compatible?

No. Confirm the exact phone, vehicle, app version and connection path first. This article does not recommend a CARLUEX product or claim vehicle compatibility based on a library changelog.

For related reading, see the Android Auto music-player guide, the Android Auto music-app comparison and the Android Auto connection checklist. These are general references; the exact app, phone and vehicle remain the compatibility boundary.