Harry's GPS Suite Forum

So last night I had a fantastic track night and got great data from the LapTimer Pro and saw all the applicable data. Today I went to export my data for use in Dashware to overlay on my GoPro video and during the process LapTimer Pro crashed to the springboard and when I restarted it, it listed that it had to rebuild >24000 GPS points, during this process. When the screen went to sleep, upon unlocking, it had crashed to springboard again and I reopened the app and kept the iPhone from going to sleep with simply taping on the screen every so often as it went through the rebuild. When it finished it launched properly, but when I looked at my 29 laps from last night, they had resorted to just a car symbol beside all the lap times and no course profile when the laps are individually opened. When I then exported these laps, I discovered that these very small files contained only lap times and no speed, gps or G data. Essentially I have lost all useful data a side from my basic lap times. HARRY PLEASE HELP!!! Is there is anyway to recover my data?! For reference here are my devices specs as listed by the export process minus my UDID.

Product: Harry's LapTimer
MD5: 80bf5a7fdf5710bce530f94c84f9efb8
Version: v16.6.2 Professional
Build: Oct 26 2012, 08:24:26
Features: none

SYSTEM
Device: iPhone (iPhone4,1)
OS: iPhone OS 5.1.1 (jailbroken)
Available memory: 1.4 GB
GPS: Internal
UDID: ******ddc7
Name: NES' iPhone 4S

ONLINE CLIENT
DriverID: NES
Simplified UDID: *******4

Thank you in advance in either helping me recover my data or at least preventing this from happening again in the future, perhaps auto syncing of this data to Dropbox in the same sort of manner as Notability does? Just as an additional note, attempting to use the export to Dropbox feature failed on my phone and I am current with my Dropbox app and signed in.

Cheers,

Hi Sean,

So let first check if LapTimer stored recovery file for you. Can you please check the article viewtopic.php?f=8&t=679 for a tool named iExplorer. Please download it and have a look into LapTimer's Documents folder. In case you see sub-directories starting with "recovery", chose the most recent and check if you see many LapTimerGPSRecDB* files in there. In case you do, copy this recovery directory to your desktop, zip it, and send it to me. In case the latest recovery sub-directory only shows a small number of LapTimerGPSRecDB* files, try the next most recent sub-directory.

Sorry for the inconvenience, this is actually one of the very very rare "loss of GPS data" situations I have seen with 16.6

- Harry

Hi Harry,

First off thank you for the super fast reply, your support of this these incredible apps has always been astounding and well worth the value to say the least. There were two recovery directories in there with a large number of files, both created only a minute apart, so I have emailed both to you. I am thinking these were each created when it tried to rebuild the gps database twice as I described, the first one crashing to the springboard, either before or after it finished the process. Hopefully you can get something out of them for me. Thank you again! I think I will add that immediate Dropbox sync idea to the feature request cue, it would definitely help provide piece of mind and instant access to the data for analysis track-side.

Cheers,
Sean

Short roundup - the problem has been two fold: 1) there have been some memory leaks in LapTimer v16.6.2 that made auto-recovery fail - fixed in v17 2) the recording data showed wrong (future) dates for GPS fixes which ultimately were the reason the data has been purged. Reasons for the later are unclear. Sean runs a jailbroken phone using BTStack to integrate a Qstarz GPS. As these dates are passed to the database by LapTimer as received, it seems they came in wrong already. Due to the missing direct integration of BTStack and roqyBT4 connected devices, there are several transformations nevertheless: the chip send UTC dates (the ones we can assume correct), this UTC dates are parsed and interpreted by BTStack / roqyBT and passed on to Apple's location service. LapTimer receives this transformed dates from Apple's location service. So most probably it happened in the first transformation step...

Data has been fully recovered.

- Harry