I see what you mean
Having this kind of behavior would require additional and external server handling (odometer history is neither stored on the car neither given in a charge. An external server would be required to listen for charge launch, and store the current odometer). I don't think it would be a nice idea regarding personal data and so..
Concerning the android version I wasn't aware of the charges crash, I'll have a look at it. However I know that the widget is hardly working... I'll try to deploy a fix
Hi Kelyan,
according to Android version crash - i already wrote to you that it crashes always on first click of the app icon . It happens on both my Samsung phone and tablet. On a second click the app starts normally. Does anyone has the same issue?
Regarding the external server for history store, i can suggest using https://thingspeak.com . I already use it for some of my IoT projects . It has a useful API for store/read data. So the idea is everyone who has to use history store, to have account in this server and just provide the credentials in your app.
Best regards
Boby
PS your coffee cup is filled by me too 
