When reinstalling the app on another device, please load the initial edition purchased from AppStore/PlayStore. Start LapTimer afterwards and follow Administration / Add-Ons. Press Restore to have all upgrades restored from here. You can find a full FAQ on app and data migration here: http://forum.g...

Have you used the standing start trigger?

Hello,

Provided you keep your ID - yes. See viewtopic.php?f=39&t=3341 for he details.

- Harry

O.k. Unloading removed the local copy and keeps just a "shadow". When selecting the video (Video Details), you should see a "Download" button to replace the shadow by an actual copy. As reloading a cloud copy is a system function, it may take some time until the video appears aga...

Do I understand right that you have used the ”Unload” function? This will leave an empty video locally and the remote copy in the cloud. In case you want to use the video, you need to load it again first. iCloud should not be considered a network drive, it is about keeping a number of copies in sync.

I have installed HLT on 2 other iPhones (iPhone X and 13). On each (iPhone 6, X and 13) I set up an autocross to test. The iPhone X and 13 worked fine but the iPhone 6 did not. I think I will give up on the iPhone 6 and transfer the database to the iPhone X. What is What is the best way to transfer...

Thanks, I have received it. Actually I found two issues with tires: #1 problem in inport (which occurred for me when importing your export) ;-) #2 crash when drawing wheel images using a blur effect that LapTimer uses for the iOS version The later is what happened for you. It looks like it is an iss...

Please export a lap that crashes to .hlptrl and send it to me (Harry@gps-laptimer.de). I will check if I can reproduce the problem.

Hello, We will check the 5-mile CW configuration and come back on this. The correct way to handle the configuration switches is to re-load (Load Track) the respective configuration once it is started. When LapTimer tells you there is a conflicting configuration, allow it to purge the conflicting tra...

The problem is around iOS's memory management. It uses all free storage for caching. Once apps request more space, the caches are freed up. So technically, there is no memory available, but once an app requests more space, it is receiving it. Later iOS versions allow to check for free plus cache-use...