The iPhone lists three cluster contents in its /info altScreenURLs: the
map, an instruction (turn) card and "instrumentcluster", which draws the
map with the turn card on it. A new "Dashboard shows" choice picks the
one DiPlay asks for as the alt screen's initial URL; the map stays the
default. On the tested car the turn card fit the Small screen navi
window well and streamed 0–5 kbit/s against 0.3–4 Mbit/s for the map.
The iPhone lays out the map, the car marker and the card inside the
same safe area, so the existing position settings move whichever is
shown; they are now labelled "Car marker" or "Turn card" to match.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- values-ar / values-ru / values-es for common (387 keys each; brand and
technical keys intentionally fall back to English) and shared module
- Format specifiers verified identical to the English source
- zh-rCN coverage confirmed at 399/399
CarPlay marks guidance audio apart from media, but the sink always built
its AudioTrack from usage/content-type attributes. On head units that
expose navigation on a dedicated mixer output, guidance shares the media
channels, so the next turn is announced over the music in every seat.
BYD puts navigation on stream type 14, the driver-side speaker.
Add an "Audio routing" section with a 0-20 stream type grid and a test
tone, persist the selection, and build the AudioTrack on that stream
type. When the ROM rejects the stream type the track is rebuilt from
usage attributes, so devices without such an output keep today's
behavior (the diagnostic log reports route=usage or
route=streamType=N(fallback=usage)).
The advanced audio channel mapping switch is now visible on the mobile
flavor too, still off by default, so usage/content-type routing can be
picked at runtime instead of by editing resources, and the automotive
map routes default and compatibility to the navigation bus rather than
sharing media.
Replace the manual bottom/right insets with a measured safe area. A
calibration grid on the cluster showed what BYD draws over the
projection area in Full screen navi (status row, ADAS icons and lane
view, speed/power readouts, bottom band) and that Small screen navi
crops the panel to a centre window. The panel centre, x 35-64 % and
y 16-75 %, is clear in both modes, so the car sits there by default;
the owner confirmed it centred in both modes.
"Car marker · horizontal" (Left 40 % … Right 40 %) and "Car marker ·
vertical" (Up 30 % … Down 30 %) move the marker in 10 % steps. The safe
area keeps its size around the marker and shrinks only near a panel
edge. Settings show a small drawing of the cluster with BYD's readouts
and the marker, and a reset button.
"Cluster map size" sets the stream to 100, 83 (default, 1600x600 on
1920x720) or 67 % of the panel; the cluster scales it up, so the map
grows while staying sharp at 83 %. Apple Maps ignores the reported
physical size on the cluster, so that stays fixed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
When a BYD cluster projection display is visible to the app, DiPlay can
declare CarPlay's second (instrument cluster) screen, ask Apple Maps for
its cluster map through initialURL, and render stream 111 in a
Presentation on the shared projection display. The driver picks Small or
Full screen navi in the cluster's own menu; no ADB is needed.
Safe-area insets place the car marker. The defaults (25 % from the
bottom, about 1/9 to the left) fit the tested DiLink 5.0 cluster. The
feature is opt-in and marked experimental.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
shihabal3amri