RealDash version 2.5.6

2.5.6 released 12.8.2025

New:

  • Haltech CAN V3 support.

Fixes:

  • Lap Timer values are now updated correctly.
  • Gauge color slider setting transfers in copy-paste.
  • ‘Bring to Front’ and ‘Send Back’ now works with gauges in container.
  • Improved reliability of music info from external music players.
  • Fixed crash when changing font on autoscaling gauges.
  • Autoscale segment images now respect the mask.
  • OBDLink CAN Adapter 29bit ID:s now work.
  • Android: Minimum API level increased to 21.
  • Android: Restored bind to wifi when using WiFi OBD2 adapters.
  • OSX: Fixed paste adding character ‘v’ into pasted text.
  • OSX: Fixed UTF8 file paths.
  • MRD: Option to add vehicle service entries (will be live on next few days)

NOTES

Mostly a bug fix/maintenance release.

The minimum Android API level has been increase to 21 (Android 5), so Android 4.x devices are no longer supported. This change was forced by Google, so there is nothing we can do about it.

3 Likes

After the update. When you launch realdash, the xml files are lost

1 Like

Could you give a little bit more information?

  • What XML files (Settings, OBD2, CAN, from My RealDash, built-in XML, custom XML)
  • If custom files, do they remain when re-imported.

If you restart the device, the realdash program will display a message saying that the xml file has been lost. You will need to manually add the xml file to your device, and the xml file will be lost again after restarting.
Obd2 and can

  • What Android version?
  • How is the XML file imported (from Android filesystem, from My RealDash, from some other cloud storage)?

Is there something major changes on Haltech CAN V3 protocol? Can we see updated XML anywhere? Thanks.

This was provided by RealDash user. XML is in GitHub:

RealDash-extras/RealDash-CAN/XML-files at master · janimm/RealDash-extras

@SamiSmiley This was my pull request to get merged into RealDash so I can answer. Previous RealDash XML for Haltech was seemingly based on Haltech V2.35 CAN (Haltech-CAN-Broadcast-Protocol-V2.35.0)
The “V3” matches the currently published official Haltech (Elite Series ECU 3.10) and now contains the emulation of IOBox A as an example which is what I used to create my digital keypad:


Okey this makes sense. I thought Haltech updated their CAN protocol to “V3” :sweat_smile:.

Although, Realdash doesnt work newest Nexus R3 Beta firmware anymore. Dont know why. I roll one older firmware all good then.

When I connect via USB, every time I open the multimedia player, the USB option appears and I press the OK button. This was not present in the previous versions. How can I fix this? If not, where can I download the working version?

1 Like

I’m seeing problems with file system unavailability when starting on version 256 and older versions of android

1 Like

Thanks for reporting, which Android version?

Hello, thank you for this app. I would like to clarify a question. I want to make a dashboard for my Volkswagen Golf 7, MQB platform, and I need Real Dash to display the following: vehicle mileage, turn signal indicators, high beam indicators, warning lights (check, etc.), and the parking brake. How can I do this? I have an Arduino Nano and a MCP2515, and I am wondering which files I can use or if you have any instructions or configuration files for the MQB platform.

10 version Android - i stability get problem (at each start of the system)

I’m an amateur in programming, but maybe if you add the option to delay loading when starting xml & skin, it will completely solve the problem

Just to clarify; this issue happens only when ‘cold booting’ the device? After device is running it does not happen no matter how many times you restart RealDash?

cold booting - 30% ок (i check again)
start from sleep mode - 50% xml 50 % RD file is reset 0 % good start

1 Like

And in 50% of cases, the skin is reset to the default

1 Like

Thank you for reporting. We are investigating, but are yet to be able to reproduce this issue on any of our test devices.

We do use a generic Chinese Android stereo for office testing, and in addition 2 Android radio devices on DEATHFISH 2, which runs latest version multiple times a day. All these devices have a sleep mode when ACC is turned off. This issue never manifests itself on these conditions, no matter how many times sleep mode is on and off.

This issue must have a specific hardware and software configuration to be reproduced. I would need to be able to build the exact environment in order to catch the issue, or have more specific information about your setups.

2 Likes

At the moment, the solution is to update the device’s firmware and the problem is no longer observed on my devices. Thank you for investigating.