BYDMate Waze 3.16.0-dev.5
Pre-release
Pre-release
BYDMate Waze 3.16.0-dev.5 (development pre-release)
Development channel. Street names on the instrument panel, debug mode, default automations.
New
- Street name on the panel. Its next-street features take a byte array and the helper daemon
only wrote integers, so the name was never sent. A new daemon transaction carries bytes by
calling BYD's own SDK the way the factory navigation does, rather than guessing an undocumented
binder transaction against a live vehicle bus. BYD ships two such features, domestic and
overseas; both are tried, overseas first, and the one the panel accepts is kept. The trip log
records which one won. - Debug mode: trip logs (Settings -> Service and data, off by default). The car writes its own
guidance record per ignition cycle toDownload/BYDMate-trips: every changed Waze read with the
raw street text, the lane cell labels and what they parsed to, the maneuver code sent to the
panel and whether it was accepted. Wi-Fi is not involved, so the drive that matters is finally
observable. Newest 12 trips kept. - Default automations, seeded once and then yours: open Spotify and start playback, and open
Waze. Both fire on start-up, once per trip. Updates never re-add or overwrite them. - Adds a media_play action - launching a player opens it but starts nothing.
Fixed
- Maneuver glyphs. The panel numbers its icons differently from our internal codes. The raw
code drew a detour for a roundabout, a slight left arrow for a slight right, and the Chinese
destination glyph on arrival. All three reported from the car, all three covered by tests now. - Lane direction inside a multi-direction lane follows the maneuver instead of the first arrow.
- Lane labels come from a new
lanessection in the language packs, so they work in every
language rather than only Ukrainian by accident.
Faster start-up
The boot worker was a plain WorkManager request waiting on the scheduler while the head unit was
busy booting. It is now expedited. How much this saves on your car will show in the trip log and
ChainLog, which now carry the timestamps to measure it.