Honda Customizer 3.4.10 — Custom cluster controls

Honda Customizer 3.4.10 — custom cluster controls and refresh correction

Download Honda-Customizer-3.4.10-Full.zip for the APK, unchanged custom UPDE,
application source, firmware extension source/tests, validation and checksums.
The APK and UPDE are also separate release assets.

APK changes

• Requesting FYT data preserves real readings until their original 30-second
  expiry instead of deleting them immediately. Silent requests never refresh
  timestamps or manufacture readings. Expired values remain unavailable.
• Main screen adds Solicitar dados FYT and the read outcome. Settings distinguish
  expired, invalid and never-received feedback.
• Separate experimental cluster menu: layout, color variant 1, color variant 2,
  navigation display setting, tachometer display and ambient-change behavior.
  All 24 protocol choices are explicit numeric inputs, not current vehicle values.
  Color names and the physical meaning of each option remain unverified.
• These six commands require the custom XP111 cluster-v2 extension. The app cannot
  detect its installation. Exact FYT profile 0x4012A, parked acknowledgement and
  explicit per-command confirmation gate dispatch through command 1030.
  Dispatch remains unconfirmed; the app disconnects and requires explicit reconnect.
• No CAN-box firmware flasher is included. The existing application ID/signing
  certificate are retained for installation over the prior APK.

Firmware and limits

XP111-Cluster-Custom-v2.UPDE is the existing 75,984-byte custom application-only
container, unchanged. It excludes the bootloader. SHA-256:
1043ed024245872ed2d5ce7cf56d1df7537f89e61f0027255702894c653959df

This is an experimental prerelease, not verified flash-ready firmware. Tests do
not establish updater acceptance on the installed XP108 box, physical cluster
compatibility or a working recovery route. There was no physical flashing/test.
The navigation command is a setting candidate, not navigation-data streaming.

FYT can suppress unchanged values. The refresh correction does not solve that
service limitation or guarantee that locked settings will become available.

Validation

• Release build and lint passed; 121 Android unit/UI tests passed, zero failures,
  errors or skips. All 24 custom choices match the existing firmware packet vectors.
• APK signature verified; test vectors and firmware are excluded from the APK.
• Existing custom firmware: 3,333 isolated dispatcher checks passed; header gate
  and transfer checksum checks passed under the documented XP111 test fixtures.
• Fresh paired QEMU execution: 43 stock-command scenarios matched on measured
  behavior; 41 cluster scenarios per binary covered all 24 valid private choices.
  Stock rejected those choices; custom reached its extension/internal acceptance.
  No sampled fault flags. No post-input UART replies or completed CAN transmission.
• Decoded UPDE application matches the tested custom BIN application exactly;
  declared application length matches. This is not full flashing validation.

Source and evidence

Use the attached application source ZIP for the source matching this APK.
GitHub-generated source archives refer to the existing repository anchor commit,
not the local source snapshot used for this build. Firmware-source-tests.zip
contains extension source, test scripts and evidence; reproduction also requires
its documented stock image and modified emulator environment.