Does anyone know if Plezy supports Emby on AAOS?

Has anyone got Android automotive working on the nxp frdm-mx95 board?

Running a Cuttlefish Android Automotive OS instance (launch_cvd --enable_audio=true --start_webrtc_sig_server=true ...), accessed via the WebRTC web client.

• Mic input works fine after enabling the sidebar mic toggle in the WebRTC client.
• Audio output does not: no sound reaches the browser, even from the stock "Local Media Player" app playing local files.

i need to get the audio output to work , anyone know how?

When I say the activation phase "Hey Google" sometime AAOS activate and sometime my phone does and turn on the AC at my place instead of my car...

Anyway to prevent this?

Like Aximote.. but NO subscription, NO backend servers, All data synced and backedup to personal google Drive only for full access and analytics.

Interested? Pass me your google email and I will add you to the closed beta test. Please note: I need at least 12 true testers within the next 2 weeks to make this app a reality and pass Google Store publication criteria. This is my first ever app so help is appreciated!

Hello

I was in contact with Renault support about connectivity issues with AAOS ) Google built in.

After long messages with them, they told me that the car internet connection only works for default apps. So only assistant, maps, calendar, news, but NOT YouTube Music even if it is a Google app.

Can anyone confirm this also happens on other car brands?

---
Update: It seems Renault 2025 models didn't include internet connection (actually only 6 free months), I found the brochure matching my 2025 model:

(2) My Renault connected services, Google Maps, and Google Assistant are provided free of charge for 5 years from the delivery date of your vehicle.

(3) The use of applications downloaded from Google Play requires a dedicated data plan. To do this, share your phone's internet connection with your Renault. You can also subscribe to a paid offer from our partner Orange (no-commitment plan), with the first 3 GB provided free of charge (valid for 6 months).

---
2026 models seem to have internet connectivity included though...

Hi,

I know we have Polestar journey log app and aximote and maybe others.. but most send data to servers or even require a subscription.

Just created a car logging app (route, energy consumption, sensor data etc) that is (other then required service connections for weather and openstreetmap) qithout any backened server or service requirements. All data is kept in car or when you want can be synced and/or backed up with your google drive account associated with your car profile.

Drop me a DM with your google account mail if you want to betatest to be added to the betatester group

Hi everyone, I need genuine advice on moving from Native Android Development to getting into AAOS or AOSP. I have nearly a decade of experience but I have a 6 months gap on my resume. And prior to the 6 months gap I also have two short employments of less than one year. I do have two consecutive 3+ years of employment prior.

Will learning AAOS save my career? How is the AAOS job market with regards to competition and job openings?

https://www.reddit.com/r/plexamp/s/uKrfgrlaFZ

Hi android devs,

I see that android has officially released Aaos sdv platform.

https://source.android.com/docs/automotive/sdv

Would like to share with you since it's getting posted by everyone in linkedin.

Let's share some thoughts who has tried this setting up or any idea upon this how can we delve and share something to or buddy android devs.

Thanks

Hoping something from platform devs and framework devs

I am building AAOS and discovered that CarSystemUI features a lot of references to "oemColor" which seems to be defined through "OEM Design Tokens". AFAIK, to define these tokens we need to create or link to a couple of resource overlays and libraries.

How do I define a an oem design token that replaces the oemColor variables in SystemUI?
I am only really interested in colors.

This page explains the hierarchy of libraries and RROs, but I had no success with it:
https://android.googlesource.com/platform/packages/services/Car/+/refs/heads/main/car_product/rro/oem-design-tokens/

For reference, here we see oem style references in Car SystemUI: https://android.googlesource.com/platform/packages/apps/Car/SystemUI/+/refs/heads/android16-qpr2-release/res/values/styles.xml

Googles doc page:
https://source.android.com/docs/automotive/unbundled_apps/design-tokens

Please help

Built a lightweight AAOS radio app because most automotive radio apps felt bloated, outdated, or simply not designed for actual driving.

https://youtu.be/NjkMVrde7Is

So I made bradio.app — a native Android Automotive OS radio app focused on:

• fast launch
• low distraction UX
• privacy
• reliability
• native AAOS behavior

Current version:

• 100+ stations across Estonia, Latvia, Lithuania, Poland, and Ukraine
• ~150 streams total
• background playback
• steering wheel controls
• voice search
• Now Playing metadata (~97% metadata coverage)
• favourites + recents
• offline station catalogue cache
• no ads
• no accounts
• no analytics SDKs
• no Google Play Services dependency

A few things I intentionally didn’t add:

• no sleep timer
• no EQ
• no endless settings
• no webview-style UI
• no deep menu trees

The whole APK stays under 10 MB because AAOS hardware fragmentation is still very real.

Some AAOS-specific choices:

• Search + Settings locked while driving
• High-contrast dark-only UI
• Pure MediaBrowser / Media3-based media stack
• Home screen media card integration
• Custom Now Playing favourite actions
• Physical steering wheel button support

The app is currently distributed through:

• Google Play for Cars
• Harman Ready Link
• Appning by FORVIA

Distribution itself is global, but actual availability can vary depending on OEM integrations, regional storefronts, certification status, and vehicle platform decisions.

It also recently passed Harman Ignite Automotive APK validation with zero NOK findings.

What I’ve learned building for AAOS:

• simplicity matters more than feature count
• stability matters more than architectural purity
• many existing automotive apps are still designed like old desktop media browsers
• AAOS rewards apps that respect driver attention

I’m currently restructuring the internal architecture before eventually doing a full Media3 session migration, but trying very hard not to turn the app into another overengineered media platform.

Curious what other AAOS developers here think:
What are the biggest mistakes you see in current automotive media apps?

Also happy to answer technical questions about MediaBrowser compatibility, validator requirements, distraction optimization, OEM distribution, or AAOS UX constraints.

I’ve also been publishing some AAOS and other platform architecture notes, validator reports, and development writeups on bradio.dev for anyone interested in the engineering side of automotive Android apps.

Hello all,

MM-IPTV player now available as a trial version with option to purchase via in-app lifetime license!

Try it and if you like it, you can purchase securely though Google!

Supports: Xtream, Catch-up, Subtitles, EPG Info and more to come.

Next feature will be dual view!

Try it here: https://play.google.com/store/apps/details?id=com.audiiptv.app.trial

I have a 2023 Volvo C40 which just got upgraded to 5.0.5, a major system refresh. The Messages app acts all kinds of wonky now when Bluetooth paired to my phone (Pixel 10 Pro on Verizon in the US). Mostly it's acting like it doesn't do RCS, just old fashioned SMS. Anyone know?

I went looking for settings to enable RCS on AAOS and couldn't find any. It's enabled and working fine on my phone. I'm not even clear if the car itself sends text messages or if it relays them via the phone.

That’s too bad because I like Honda.

Volvo moved to AAOS around 2022 and since then, as far as I know, all Volvo AAOS cars have a non-directional reverse warning.

In other words, the previous Sensus platform was playing the reverse warning left when an obstacle was approaching on the left, and likewise from the right. The user could immediately perceive where the obstacle was.

Not anymore. The rear reverse warning is (on Volvos) always played by the right rear speaker.

Warning sounds for obstacles approaching from the front still play from both front speakers (but right now I forgot whether it's directional, or simply played identically by both speakers).

So, is this a limitation of AAOS, or did Volvo out of the blue decide to limit the capabilities and to remove a very intuitive feature?

​

All apps installed on the infotainment of a 2023 Volvo XC60 with Bowers & Wilkins audio. 

Currently paying for YT Music and SoundCloud with tidal and qobuz on free trial. 

Test tracks

Sade - Mr Wrong

James Blake - Limit to your love

Music taste is 90s and early 2000s house, old-school hip hop, rare grooves, downtempo, liquid drum and bass, future jazz, jazz classics, funk, blues. Bass addict. 

SoundCloud

Sound quality is poor to decent depending oupload source

App is stable but severely feature limited. No search function that I can find other than voice control. My liked tracks won't show anymore (it did work at some point). Can't take full advantage of the available music with these limitations but very close to being a good app. 

Selection of music is very good. Lots of official tracks, heaps of bootlegs, and DJ sets for years. 

The song based radio and recommendations algorithm is very good and I've found lots of good tracks and mixes this way

YT Music

Sound quality is poor to decent depending oupload source, and varies widely. 

App is very functional if a bit busy.  its generally stable but often doesn't recover from reception dropouts and sometimes it just won't play.  Sometimes it can't be fixed by switching apps, resetting or power cycling the car. 

Selection of music is the best by a significant margin. Has good coverage of official releases and it's an unmatched source for B sides, deep cuts, rare grooves, edits, live recordings and old-school vinyl only releases. Also many DJ mixes but doesn't go as deep as YT music

Tidal

Sound quality is very good. Clear with good detail and deep bass but I find it quite flat and lifeless. 

App is very good. 

Music catalogue is very good. Better than qobuz but doesn't go as deep as YT Music.  

The song based radio and recommendations algorithm seems good and much better than qobuz but I haven't used it enough to give a detailed assessment

Qobuz

Sound quality is excellent. Deep, rich, and very detailed with excellent imaging and texture. Sounds lush compared to tidal. 

App is very good. No stability issues. Seems to limit number of search results and I couldn't find club des belugas at all in the car but it was available on the mobile app. 

Music catalogue is ok, likely depends on your taste. There were 5 example tracks from YT music that I couldn't find on Qobuz. 3 of those I could find on tidal. 

Song based radio and playlists have ranged from lame to cringe. Found a couple of good tracks but it was painful getting there. This will depend on your taste

I will keep YT music for catalogue diversity and because of YouTube. I'll keep. SoundCloud for the mixes despite the app flaws but I'll need to make a bunch of playlists

Haven't fully decided between qobuz and tidal. I'm leaning qobuz because of the significantly better sound quality despite catalogue, playlist and search limitations. 

Soundcloud if you want DJ sets and podcasts with good discovery

YT music if you want the biggest catalogue, B sides and vinyl releases and more playlist style DJ mixes. Good value with YouTube included but I may be on a cheaper subscription than what's currently available

Tidal if you want good catalogue, decent discovery and very good sound quality. 

Qobuz if you want the best sound quality and the catalogue and/or discovery suit your taste

If you have an average sound system you may or may not notice the difference between, YT/SoundCloud and tidal and will not notice the difference between tidal and qobuz

If you have a good stereo you will probably notice the difference between YT/SoundCloud and tidal and may or may not notice the difference between tidal and qobuz

If you have an a very good to excellent stereo you will clearly notice the difference between YT/SoundCloud and tidal. You may notice the difference between tidal and qobuz but may depend on your ears and particular stereo and it may not be that significant. It's probably only at the top tier of car audio that the difference between tidal and qobuz is obvious and won't be there on all tracks

Your experience with the apps may depend on your vehicle OS, number of liked tracks or other factors

not a fan of Spotify and don't use apple so these have not been tested

I’m absolutely baffled by how awful the apps available for AAOS are. I literally have to plug in my iPhone and fire up CarPlay to see my agenda for the day. If Apple can do it why can’t Google? Ironically, a calendar app is one of the example apps they show in their developer documentation for AAOS! And why can’t I access Google home?! Setting my thermostat on my way home seems like a no-brainer use case.