Warning
The apps in this repository are still being designed and tested. They are published here only so they can be installed straight from the Store for testing in the car. They may not work, may not work on your car, may behave differently from one version to the next, and may send commands to the car's control units. Use them at your own risk. Only test them while the car is parked, and don't rely on them.
Apps that work well move to aurelmarius/bmw-apps. That is the repository to use for everyday apps.
Custom applications for BMW iDrive 7 (MGU head units), compatible with Robert Nisipeanu's mgu-store and IterioDev's App Manager. Built with the same kit as aurelmarius/bmw-apps.
Graduated: Wheel Heating (
aurelm_wheel_heat) works in the car and moved to aurelmarius/bmw-apps (1.0.6); install it from there.Graduated: TVH works in the car and moved to aurelmarius/bmw-apps as TVH Player (1.0.0, with the TVH Player service; from TVH 0.1.10 / service 0.1.7). Remove TVH and its service from the Store, then install TVH Player from there and sign in again; its fixes are made there.
Graduated: AirPlay Test works in the car and moved to aurelmarius/bmw-apps as myAirPlay (1.0.0, with the myAirPlay service). Remove AirPlay Test and its service from the Store, then install myAirPlay from there; its fixes are made there.
native/uxplay-mgustays here: Emby's player builds its GPU decoder fromnative/uxplay-mgu/video.
The head unit as a cast target for the Emby phone app, as Emby's TV apps and Kodi's Emby add-on are.
Status: step 3, controls on the iDrive (0.3.12). Works in the car (0.2.x): the picture on the GPU, the sound on the speakers, pause, seek, volume from the phone, the cast menu, cast during a film on the phone, text subtitles drawn by the app (in ASCII), a 4K Dolby Vision film tone-mapped by the server. 0.3.0 in the car: the controls and the progress bar work from the iDrive controller; a touch on the picture or the iDrive controller shows a bar with the position, a progress bar (touch it to seek) and the buttons -10 s, play / pause, stop, +30 s, aspect (fit, zoom, fill) and exit; the controller's knob moves along the buttons, a press runs one, a push down hides the bar. 0.3.1: a touch on the film went to the status page underneath (its Sign in / Sign out pressed unseen: signed out, the QR code open); while the film shows, the page now takes no touch, and Sign out (and Sign in while signed in) wants a second press within 5 s. Show picture is the page's first button. 0.3.2: cast chosen while a film plays on the iPhone: the Emby app for iOS stops it and sends the car only SetVolume, never the film (the server's log); 0.3.3: the car takes over the film this account plays right now on another device (where it is, with its audio and subtitle tracks) and tells that device to stop; with none playing, the one stopped in the last 90 s. 0.3.4: the phone, told to stop, sent the same Stop on to the car (taken over, then stopped 1 s later); a Stop in the 5 s after a take-over is that echo and is ignored. Cast during a film on the phone works in the car (0.3.4). 0.3.5: a seek no longer shows the status page for a moment (each stream is a new player): the picture stays up, black with "Loading...", until the new one comes. 0.3.6: the progress bar follows a finger dragged along it (the target in yellow) and seeks where it lifts; before, only where it came down counted. 0.3.7: Stop on the iDrive pauses the film for the phone (whose Emby app has only play / pause for the car) and closes the player; play on the phone goes on from there. 0.3.8: streaming quality in Settings (8, 4, 2 or 1 Mbit/s: the most the car asks the server to transcode to) and, unless turned off there, the quality goes one step lower by itself when the stream runs dry (twice in a minute, or 8 s at once) and one step back up after 5 minutes without it (works in the car). 0.3.9: AUDIO and SUBS on the controls open the film's audio and subtitle tracks (subtitles with Off first, the current one marked); a touch, or the knob and a press, chooses one. Another audio is a new stream from where the film is; a text subtitle is drawn by the app at once; a picture one (PGS) is burned in by the server (a new stream). 0.3.12: the film on the instrument cluster, as TVH's channel: a card over the media widget in the right dial (its poster from the server, the film or series, the year or episode, h:mm of h:mm, the minutes left, a progress bar, paused), drawn through cluster-render (the Store; Waze on cluster installs it); on by default, moved by up to 160 px in the settings; a Cluster row on the page.
The service signs in once with your Emby account and stays connected to your Emby server, so BMW iDrive shows in the Emby app's cast menu. The phone only sends the command through the server: it does not connect to the head unit, and wireless CarPlay stays connected. The server must be reachable from the internet; the head unit gets there through mgu-uplink, as its own uid only.
- Install Emby: the Store installs the Emby cast service first. Restart the head unit once after installing.
- Open Emby on the iDrive and press Sign in: a QR code shows. Scan it with the iPhone (connected to the car with wireless CarPlay), enter the server's address, the user and the password. Only the access token is kept, never the password.
- Open the Emby app on the iDrive once (it routes the sound to the speakers and shows the picture). In the Emby app on the iPhone: play a film, tap the cast button, choose BMW iDrive.
- The film plays over the whole centre screen while the car is parked, with its sound on the car's speakers. Driving, the picture hides and the sound goes on. The setting Picture only while parked (on by default) can be turned off in the app's Settings, so the picture also stays while driving (for passengers, e.g. children watching cartoons). The centre screen is in the driver's view: where the law forbids a video in the driver's view while driving, leave it on. A touch on the picture or the iDrive controller shows the controls: the title, the position, a progress bar (drag along it: the film goes where the finger lifts), and the buttons -10 s, play / pause, stop, +30 s, aspect (fit the whole film with black bars, zoom, fill the screen with the edges cut; also in Settings) and exit (back to the status page; Show picture brings the picture back). With the controller: turn to move along the buttons, press to run one, push down to hide the bar. It hides after 5 s, not while paused. Pause, seek, volume, the audio and subtitle tracks and the next episode all come from the phone, which shows the position. Stop on the iDrive pauses the film (the phone shows it paused) and closes the player; play on the phone goes on from there.
- The server sends what fits as it is (H.264 up to 1080p with AAC or AC-3) and converts the rest (HEVC, 4K, HDR, DTS, E-AC-3, chosen subtitles), at 8 Mbit/s at most. If something does not work, the page says where it stopped (Playing, Picture, Sound): take a photo of it.
myAirPlay and TVH Player (bmw-apps) and Emby share the car's speakers' input: the one playing keeps it, and the others say so and wait.
Details: native/aurelm-emby/README.md, the player: native/emby-player/README.md.
Your Music Assistant server in the car, in the style of Spotify.
Status: 0.1.1. First car run of 0.1.0 (2026-11-17, Music Assistant 2.10.12): sign-in, Home, covers, Now Playing,
the cluster card and the steering wheel worked; no sound (the player waited for ever on a sound device nobody read
yet) and the knob made Home jump back and forth. 0.1.1: the sound device is non-blocking, as Emby's player (sound
not read yet is dropped, playing starts as soon as source 287 is connected), and the page moves only when the knob
goes on to another row.
0.1.1 in the car (2026-11-18): the sound reached the speakers, but as a garbled, metallic noise. 0.1.2: the player
writes each chunk no earlier than it is due (the service hands it over 1 s ahead, with its time on the monotonic
clock), as Emby's player does, instead of as fast as the device takes it; chunks over sound already queued (a
server's catch-up) are dropped, stream/clear with from_timestamp keeps what comes before it, and the same format
again no longer reopens the device. Test sound on the Status page plays a 440 Hz tone (2 s), then the same tone
decoded from Opus (3 s): both clean means the device and the decoder are right. The Status page counts the stream's
chunks (late, over others, gaps) and the device's depth. 0.1.3: Autoplay (Music Assistant's infinite play: similar music added when
the queue runs out) on the Playing page, as in the phone app (player_queues/autoplay, or dont_stop_the_music on an
older server).
0.1.3 in the car: the test tone clean, the music still a metallic noise, and the Status page told why: 157 bad
Opus packets and 4007 of 4573 chunks "over others". Run against aiosendspin 10.2.1 (Music Assistant 2.10.12's
Sendspin) locally: its audio chunks carry a 9-byte header (type, timestamp), not the newer spec's 13 (with
send_ahead), so every packet lost its first 4 bytes. 0.1.4 finds the header's length on a stream's first two
chunks (9 or 13: the Opus TOC and the timestamps' step, or for PCM the exact length), and the tests now check
that the tone comes out clean with both.
0.1.4 in the car: the song, but stuttering all along, and the player counted nearly every chunk late. 0.1.5 plays
as Emby's player does on the same input: a chunk goes into the device once it is due within 40 ms (0.1.2-0.1.4:
2 ms, while smartx reads whole periods of ~21 ms), a chunk late by more than 50 ms is dropped and one whose start is
late is cut, so the sound comes back onto the clock; and the clock offset the sound goes by follows the measured one
by 5 ms a second at most (a jump over the mobile network was a gap or a cut). The Status page's stream counts are
fresh (they were the ones from the stream's start) and show the cuts and the largest lag.
Then in the car: Apple Music clean, Spotify stuttering and falling behind. A file (Apple Music) is sent 30 s ahead;
a live source (Spotify through librespot) only as far as the player asks, and the client asked for nothing: the
server's default, 1 s, too little over a mobile network. 0.1.6 tells the server, in its client/state, to keep
5 s queued (min_buffer_ms) and to start 2 s after a play or a seek (required_lead_time_ms), with available
in place of the legacy state: against aiosendspin 10.2.1 with a live source, 5 s ahead instead of 1 s.
0.1.6 in the car: Apple Music and Spotify clean. 0.1.7 (with Emby 0.3.13 here, TVH Player 1.0.3 and myAirPlay
1.0.1 in bmw-apps): the speakers go to the app started last. Music Assistant playing, TVH Player started: the
channel came without its sound, since each app left another's 287 connection alone. Each app now keeps a claim in
/tmp/aurelm-287 (when it started wanting the speakers); the one holding 287 that sees a newer claim lets go, and
Music Assistant then pauses and lets the sound device go (play takes the speakers back).
0.1.8: the app ended and started again when a finger scrolled Home. It drew a frame at once on each change (each
move of the finger, each cover arriving) besides the kit's loop, which on the GPU already draws one each time the
renderer can take it: frames the renderer had not asked for, many a second. On the GPU the app now only marks the
change; the loop draws it. The pages follow the finger pixel by pixel (Home, Library, Search, an album's tracks), the
progress bar can be dragged (the time follows the finger, the seek goes where it lifts; the kit's targets take a
drag function), and the Status page shows the last crash read from the app's log. The cluster card: right 120 px,
down 40 px by default, and the dark field behind it smaller and see-through.
Then in the car: TVH Player started while Music Assistant played stayed silent: its player's snd_pcm_open got
"Device or resource busy" (Music Assistant's player held the device) and never tried again, and the app, its sound
failed, stopped asking for the speakers, so Music Assistant never let go. Emby 0.3.14 (service 0.3.13) and TVH
Player 1.0.4 (service 1.0.2, bmw-apps): the player tries the device again each second while it is busy, and the app
keeps asking for the speakers meanwhile; Music Assistant lets go within 2 s and the film or channel has its sound.
- Home: Music Assistant's home rows (Recently played, Recently added, the providers' recommendations: Apple Music's, Spotify's, podcasts...), each with its covers; Library: playlists, albums, artists, radio, tracks; Search with an on-screen keyboard; Playing: the cover, the title, the artist, the progress (tap the bar to seek), play / pause, previous, next, shuffle, repeat, and what comes next.
- The music comes over Sendspin, Music Assistant's own protocol, through the server's own address (as the phone opens it from outside): Opus, decoded on the head unit, on the car's speakers. 30 s are buffered: a gap in the mobile network goes unheard. The car is also a player in the phone's Music Assistant app ("BMW iDrive").
- Skip on the steering wheel: next / previous track while our music plays; held, back / forward 15 s (30 s held longer). The radio is not touched.
- On the instrument cluster: the cover, the title, the artist and the progress, over the media widget (needs cluster-render from the Store, as Waze on cluster; optional).
- Sign in once from the phone: Sign in, scan the QR code (the phone on the car Wi-Fi, as for wireless CarPlay), enter the server's address, your user and password (only the long-lived token the server gives is kept) or a token made in Music Assistant (an account that signs in through Home Assistant).
Installing: the Store installs the Music Assistant service with the app (it needs mgu-uplink). Restart the head unit once after installing. Music Assistant must be reachable from the internet (as for its phone app).
Details: native/aurelm-music/README.md, the player:
native/ma-player/README.md.
What the car offers a music player: the first step of a Music Assistant client.
Status: step 0 (0.1.3). 0.1.2 in the car (2026-11-13): an MP3 or M4A with tags played on source 1046 (the BMW MediaPlayer for apps, playFile) shows its title, artist, cover and progress on the instrument cluster and the media screen, as a BMW source; the steering wheel's buttons all reach the service (skip left / right, volume, the knurled wheel, the special button); button forwarding on the 1046 player works (it forwarded our own STOP). Did not work: CarLife (287: the HMI says "No device connected", its metadata unused), and on 1046 a file that grows (played only as far as it was), a pipe and http:// URLs (ITEM_UNPLAYABLE). 0.1.3 tests what is left, first in the list: skip with forwarding while 1046 plays, a native pause, and a 60-minute MP3 made at its whole size at once (a radio?).
do the steering wheel's skip buttons reach an app, can an app's title, artist and cover show where BMW's media
show them (the media widget, the instrument cluster), and which source plays a stream that never ends (an
internet radio)?
- Watched all the time (each change on the screen and in the log): the steering wheel's buttons
(
SteeringWheelPushButton: skip left / right, the knurled wheel, the star, voice), the source the HMI takes as playing (MediaSource,HmiMediaState), CarLife's bridge to BMW's media (CarLifeMp,BaiduCarLifeManager), and the BMW MediaPlayer'sCarLifeMediaandOapGenericMedia(state, metadata, forwarded buttons). - Tests (choose with Previous test / Next test, press Run / undo; a second press undoes one that stays
on): source 287 (CarLife's input, as TVH Player and Emby play) with a test tone; CarLife's metadata written
(
CarLifeMp); button forwarding on both players; source 1046 (the BMW MediaPlayer for apps, as RideTube plays) with an MP3, an M4A and an AAC file with tags and a cover, a file that grows while it plays, a named pipe, andhttp://127.0.0.1streams with and without an end; the environment (does the SOME/IP binding offer services too?). - Stop all undoes everything (routes, forwarding, CarLife's fields as they were). The service also undoes it as it ends, and never takes source 287 from another app.
- Report writes the log and a report and copies them to a USB stick if one is in
(
mediaprobe-<time>.log); on the unit:/var/opt/aurelm-mediaprobe/state/probe.log.
How to test 0.1.3 (parked, about 5 minutes): 1) 1046: play 2 min + forwarding: Run, then press skip left / right on the steering wheel, and next / previous on the media screen (and hold them); the line counts what was forwarded. 2) 1046: native PAUSE then PLAY: Run, wait 12 s (it pauses for 5 s by itself, then plays on); the line says whether it was a real pause. 3) 1046: preallocated 60 min MP3: Run, let it play 1-2 minutes (double beeps): does it go past 10 s, and what do the cluster and the media screen show? Then Stop all, Report, and the log over SSH.
No internet needed. Details: native/aurelm-mediaprobe/README.md.
- Open Store on your BMW central display.
- Go to Settings -> Add source.
- Enter:
aurelmarius/bmw-test-apps - Select Releases as the source type.
- Tap Install next to the app you want to test.
- Download
<id>@<version>.tgzfrom Releases. - Build a USB repository:
node mgu-install.js usb-repo E:\ aurelm-emby@<version>.tgz aurelm_emby@<version>.tgz
- Insert the USB drive into your car and install from the USB page of the Store.
/var/opt/mgu-deploy/mgu-deploy.sh install --artifact aurelm_emby@<version>.tgz --yesA service (aurelm-emby@<version>.tgz) installs the same way, before the app that needs it.
python3 kit/tools/build.py <id> # -> dist/<id>@<version>.tgz
cp dist/<id>@<version>.tgz packages/ # a push to main with a new package publishes a release
python3 tools/pack_tools.py # native/<id>/ services -> packages/<id>@<version>.tgzServices (tools). A native service lives in native/<id>/ with its component.json (the Store's tool
format); an app that needs one names it in its app.json ("requires": {"<id>": "<version>"}). Release
assets can carry apps only, so the release also updates the catalog release: catalog.json with every
app and service (absolute URLs into that release), every package and icon. The Store reads the source
through it (the source stays aurelmarius/bmw-test-apps on Releases), installs a service before the
app that requires it, and offers its removal with the app. The catalog release is never retired.
App ids start with aurelm_, as in bmw-games: ids are global on the
head unit, and the Store's publishing guide asks for a prefix of one's own. Each app has its own
<id>.png icon at the repository root, which the release carries for the Store.
A push to main that changes packages/ publishes a release straight away (no draft), so the Store
offers it at once, and every older release becomes a pre-release (tools/retire_older_releases.sh):
the Store reads every published release, so an app renamed or moved would otherwise show twice. To
withdraw a release by hand, run the Retire Releases workflow.
Kit: kit/ is the iDrive 7 custom apps kit (MIT), with the packaging changes from bmw-apps.