Andreas Mandel

Looks good for local testing. Please make additionally sure that the configured portal url does not start with https might be in `Uploader::uploadFile`, setting `mLastStatusMessage` to avoid a insecure connection...

If you do the upload using the web ui, you can see the message, if you hover over the error indicating red cross, as a tool-tip. Related to #96

Could you already detect the cause by using the web ui for the upload? I prefer a more user friendly and resolvable way. To access the log on the SD...

Seems the file is not closed after the transfer - this is more likely the reason. I'll check with the other file handling changes #95 etc.

I see your point and we had this behavior before. I changed it when there was demand to be able to directly confirm the next overtaking after the button press....

What is the demand, what are the accepted trade offs? Stating that is difficult is one thing :)

GPS fix should be not an argument here. If the OBS is just switched off for a short time, GPS should be back in seconds. Why would you need this...

This happens if DEVELOP is defined in custom builds, not in the release build. I'll add a comment as a warning to mitigate this for now.

Looks like the display data is updated way to often in the current implementation. Chances are good that if we reduce this, that the display is more stable in all...

might be #219 is a solution