BYDMate Waze 3.16.0-dev.7

BYDMate Waze 3.16.0-dev.7 (development pre-release)

Development channel. The instrument-panel path is now a port of openbyd's field-proven
implementation, taken as the working solution rather than reconstructed from catalogues.

What openbyd does that we now do the same way

• Street name in UTF-16LE to feature 0x43FA1008, followed by the SDK call
  sendNextPathName. dev.6 wrote UTF-8 bytes and the panel decoded them as UTF-16LE, which is
  exactly the run of Chinese characters seen under the arrow. The write status 0 is now read as
  success (it always was; the code demanded > 0). The charset picker is gone; instead a
  "Sanitize HUD text" switch (on by default, like openbyd) transliterates the name to Latin.
  Switch it off to test raw Cyrillic on the glass.
• Navigation start/stop sequences: status 2 plus the setting-device screen layout 3 and the
  statistic-device navigation flag 1, re-armed whenever the panel reports anything but 2/621;
  stop clears every feature openbyd clears (icon, distance -1, street, trip fields, statistic
  segment fields, all lane slots) and calls the SDK sendAutoNaviStatus(4).
• Maneuver, rest route: the SDK calls sendSimpleGuidanceInfo and sendRestRouteInfo follow
  the feature writes; the remaining-seconds feature is written; roundabouts without an exit
  number draw glyph 25, unknown maneuvers draw straight (11), arrival draws 48.
• Lanes: 14 setting-device writes plus one 25-value instrument batch, exactly the donor's
  layout and glyph tables.
• Waze arrow recognised from pixels: the donor's 15×15 signature classifier with its 45
  reference shapes. Checked offline against the Waze APK pulled from this car: all 56 arrow
  drawables match, 54 of them bit-for-bit. The roundabout exit number comes from
  navBarDirectionText, so a roundabout with exit N draws glyph 24+N. Classification runs every
  2 s on every read, not only when the text path failed.
• Timing: 200 ms event debounce, route considered over after 40 s of silence.

Also fixed

• Two daemon verbs shared transaction code 40, so accessibility-service recovery through the
  daemon never ran.

Not in this build (next)

• Lane guidance read from pixels (the donor's column segmentation) and the HUD test screen for
  checking the glass while parked.

Trip log

Every classification writes a VISUAL line: target, matched shape, distance, glyph, exit number;
an unmatched arrow records its 225-bit grid so a new reference shape can be built from the log.