Stabilityfix: Do not trust lastDiveLogID == 0 at startup: If dive settings are reset for some reason also the lastDiveLogID is set to 0. Most likly the consostency check will find a valid entry. But this entry might not be the last one => return an error value to trigger the find function. Calling "find" at every startup is normal behavior if TRUST_LOG_CONSISTENCY is not set and was default for a long time => low risk In addition a check of the header adresses has been added to identify a potential error while writing log samples

1b9be6040d8279117c7fc99d528790611638f10b V1.4.7 release
ba9d99a2e310da601a948ff11ad665260c600e18 v1.4.8 release
143fe85f82a2e2aca50eb0c29bc55066cb4fe497 v1.5.0 release
afa55a50cc724b11b959fa81567d59ede251ef22 v1.5.1 release
54a480c43e977db8fc6969551ad6148f2ad46e15 v1.5.2.beta release
5b4c78c36b0456ff65d1a0870d07d4072045480d v1.5.3 release
e9ca66ce36e5c7b023e2b75168c3c8246c6519f2 v1.5.4 release
02e7e11fdbe8c12fdd250074b97db921ef9f1164 1.5.5 release