BYDMate Waze 3.15.0-dev.2
Pre-release
Pre-release
BYDMate Waze 3.15.0-dev.2 (development pre-release)
Development channel only. The first car test of dev.1 (BYD Tang L EV 2025, DiLink 150) showed the
SOME/IP gateway binding fine while the glass stayed empty and the export warning stayed open. This
build carries the fixes from that investigation; it still needs a car test before anything reaches main.
Fixed
- HUD on the Tang L AR-HUD. The car's own map app sends the raw Gaode maneuver code in field 28 and never uses the
speed-sign trick in fields 6/7. New setting Settings -> Display -> HUD -> HUD type: Auto (from
ro.vehicle.type, DiLink150 -> AR-HUD), Classic (Atto 3 / Seal / Sea Lion), AR-HUD (Tang L). The AR-HUD dialect builds the field set the factory map sends (remaining route/time,
maneuver PNG, limit, arrival and remaining-time strings, progress) and sends the factory clear frame.
Details:docs/investigations/tang-l-hud-someip.md. - Export warning auto-close. The window is an
AlertDialogofcom.byd.vehicledialogshown at
power-on, before any accessibility event reaches the app. The dismisser now scans at service connect
(with retries up to 40 s) and recognizes the window by label, package or the warning text, then
clicks its single button or sends BACK (the dialog is cancelable).
Added
- Field diagnostics that survive the release build (info level): first and every 33rd HUD frame with
return code, dialect, maneuver code, distance and road; every changed Waze read; the resolved
dialect and opened service keys. Capture with
adb logcat -v time HudController:I HudSomeIpBridge:I HudPushLoop:I NavA11yFeed:I NavGuidanceHub:I VehicleDialogDismisser:I *:S.
Car test checklist (Tang L)
- Settings -> Display -> HUD shows "AR-HUD (Tang L)" as the detected type under Auto
- Waze route in the foreground:
HudPushLooplogs frames with rc=0 and the glass shows the turn - Arrow direction and roundabout glyphs match Waze
- Export warning closes by itself after power-on with the switch on
- If the glass stays empty under Auto, try "Classic" once and report the logs
Correction (dev.3): the different-service-key claim above was an arithmetic slip; every app uses
0xB010A00010000. Superseded by v3.15.0-dev.3.