BYDMate Waze 3.16.1-dev.2

BYDMate Waze 3.16.1-dev.2 (development pre-release)

The SDK camera call returns 0 on the Tang L and the panel draws nothing for any of its twenty
types. This release tries the instrument features BYD's own catalogue lists, and writes down what
Waze shows for the maneuver after the next one.

Added

• HUD Tester: raw-FID rows. "Camera (raw FIDs)" writes the type, distance and state straight
  to 0x43F03010 / 0x43F0301C / 0x43F03018 — type, then distance, then the display state —
  bypassing sendCameraGuidanceInfo. "Safety (raw FIDs)" does the same on
  0x43F04010/1C/18, and "Then (raw FIDs)" sends a secondary maneuver (icon, distance, action) to
  0x43F08010/18/30. Every write's raw status is shown on the card and written to the trip log as
  a PANEL line — logcat on the car rotates in minutes, the trip log is the only evidence that
  survives a drive. The existing SDK camera row now logs a PANEL line too.
• The Waze "then" glyph is recorded. navBarThenDirection is read on every pass and, when it
  changes, written to the trip log as a THEN line with the character and its code points
  (U+XXXX). It is an icon-font character, so the code points are the key the panel's secondary
  maneuver icons have to be mapped from. Nothing is sent to the panel from it yet.

Changed

• Node discovery reaches the lists. The per-read walk now visits 800 nodes instead of 300, and
  inside routeDetailsRecycler, eventsOnRouteContainer, eventsOnRouteView and
  instructionView it also records rows that carry no view id at all, as
  TREE new text='…' desc='…' class=… under=<container>. Those rows are exactly what the maneuver
  and report lists are made of, and the id-only walk never wrote down a single one. Deduped by
  text and description, 300 such lines per session.