Hello.
my display shows the tripA data. but when I turn off the engine all data is reset. I remember exactly that there was no such thing before.
I’ve already looked at everything, and the code for arduino, and Triggers, and Actions … nowhere do I reset the trip.
In Settings “Save trips” is ON.
tell me where to dig more?
I can dig that for you.
funny joke, but I can’t figure out what’s wrong.
Hopefully I can.
Using back button and confirming exit may not save the current settings. Will be fixed in next release. As a temporary workaround, try to close RealDash from Android task switcher instead.
This should be fixed in 1.8.8 beta.
Oh… no no no…
problem not in exit from app…
the point is that I design a complete cluster. it NEVER exits the realdash application.
this is not an additional device in the car, it is the MAIN dashboard.
and I need TRIP to NEVER reset until I do it myself. by the standard car button.
but I found another problem … look at the video.
I 'm not tested 1.8.8… will later. tomorrow.
You do have quit or pause RealDash in order to save the data. I will not implement the system that data would be saved constantly while driving as pulling power while saving will corrupt the file system and probably prevent RealDash from starting next time. And this is not something I would enjoy troubleshooting on.
Here are the events when data is saved:
- On exit
- Screen is closed (App Pause event)
- App is sent to background
- The ‘Body Electronics->Ignition On’ input changes from 1 to 0.
I wlll take a look at max speed trip values if I can find something.
OK. I understood about saving.
Yes. 1,8,8 seems to remember the trip data.
but the max speed is set to the maximum, which is specified in the gauge settings.
Check if the 1.8.8 release fixes the max speed issue.
cannot check 1.8.8.
I have 1.8.9beta. in beta max speed not fixed (((
so, almost 4 years have passed,
I again faced the need to implement a normal trip computer. but it turned out that the problem in the latest version has not gone away: not all values are saved (for example, Trip B: average speed and Trip B: tripmeter).
I use the The ‘Body Electronics->Ignition On’ input changes from 1 to 0.
maybe this has already been decided somehow differently? but I didn’t find it, sorry.
Yes, some users still face this issue. Unless we can reproduce this problem in development environment we cannot fix it. I’m sure you understand that just throwing fixes blindly into the code will just make it worse.
As we are unable to make this happen in development environment, couple of things come to mind:
- This happens on devices that are not shutting down RealDash properly but just killing the process by force.
- This is related to some kind of specific combination of custom Triggers and Actions that we have been unable to figure out.
yes, i’m testing platform Series5. and it has two sleep stages. in the first stage is light sleep, when all processes are saved in memory, but the second stage is deep sleep, in which all processes are reset. for a real car it makes a lot of sense, but unfortunately, between stages there is no way to complete realdash. you can only forcefully interrupt light sleep, complete realdash and wait for deep sleep. but this is a very ugly solution.
the question is still why some IDs are saved, and some are not.
UPD. I’m sure that the average speed is calculated on the fly, and is reset because the tripmeter is not saved. The tripmeter is the reason.