Crash Problem when try to record a own gps lap -

[Hekken]

Hey people,

got an strange Problem with the newest version of Harrys Laptimer, it seems that the Programm is to heavy for my Iphone 4.
Sometimes the Programm did not react to my enters, and when it react's than 2 till 4 seconds after pressing any button.

But that is not the Mainproblem:

I've tried to test HLT at home because i didn't find the time to get to the Nürburgring Nordschleife this week. So i entered my Datas like
Name, Car and all that information. The GPS was in the Green scale, so good GPS-Respones.

what i've done:

1. The Helper Menu, than i've pressed "Load new Track/ Neue Strecke"
2. At a special Point on my Street i've pressed "Set/setze"
3. After it, the Programm tells me that the timing will start when i drive over the set Point.
4. Now i press "Lets Start / Los gehts" and the timer menu starts.
5. drive my car and turned it, so that i can drive over the set Point. But the Timer doesnt Start timing and always Crashes to Springboard/Iphone menu.
The same if i try to make a Timing-Video after 2 - 10 Minutes the Timer Crashes without a response.

Backround Programmes are all Closed.
BT or Something is set off.
The Only thing that is Connected is the ELM327 WIFI Dongle, but seems to run good, HLT connected to it and also Dashcommand can read obd Data without Problems.

Also tried to find a Crash-log but there is nothing to find after installing to itunes...

Do you have an idea?

Greetings from NRW

[Harry]

In case you find no crash logs, the problem is usually a main memory constraint. You have not written which version of LapTimer and iOS you use? Maybe you reboot your phone and start LapTimer only - and repeat your tests. Btw. I have an iPhone4 in my set of test devices. It is certainly a lot slower compared to a 5, but works fine. Despite cpu speed, the big difference between the two is the 4 has 512MB main memory, while the 5 has 1024MB. LapTimer requires between 15 and 20MB at runtime (not including video).

- Harry

[Hekken]

Hey Harry,
thanks for answering!

I've got new details, but the problem is also there

Restarted the iphone and repeat the tests on my Street and other places, it seems to crash everytime HLT wants to start Counting. When i Drive over the Start Trigger, nothing happens, after crossing the Start trigger for some meters, than the App crashes.

I'have attached you some pictures how i tryed the MAP-Trigger function and the GPS-State, also the iphone Settings.


Could it be that the Cydia Jailbreak disturbes the HLT? I think not cause the Phone works very well but HLT.

[Harry]

You never know what jailbreaks do, you get moved into an indeterministic space But first check another item: are you on HLT 17.4.1 already?

[Hekken]

You know what jailbreaks do, you get moved into an in deterministic space But first check another item: are you on HLT 17.4.1 already?

What u mean with "deterministic space" ? (Maybe my englisch )

I used Version 17.4 at the tests, updated know to 17.4.1, you think that solves the Problem?
Sent you the Crash-logs from the last test per mail.

Thanks for Troubleshooting so far.

[Harry]

"in deterministic" should have been "nondeterministic"... (auf Deutsch "nichtdeterministisch" was ungefähr "nicht vorhersehbar" heisst).
The crash logs you sent show 3 different bugs. Two if them are fixed in 17.4.1 (including the problem LapTimer crashed when starting a new lap with an empty database).

- Harry

[Hekken]

Thanks Harry! i will try the new Laptimer Version today and report back.

What about the third Bug? Do you already know how to solve this?
Could you give some Details about the problem?

[Harry]

No, you will most probably not even realize it.

Harry

[Fernando Nogueras]

Two if them are fixed in 17.4.1 (including the problem LapTimer crashed when starting a new lap with an empty database).

- Harry

That bug has cost me a good place in the last GLP
Since then, I reinstalled all and was about to ask about this problem. That is why I registered today here.

Hope your Fix really works as the next one is coming soon.

Boy, that bug hit me strong last weekend. Glad to see that it is reported and fixed now

Greetings