Multiple crashes with v19.0.1 on Galaxy S4

[vmbray]

This was a setup using the standard autocross setup routine. I realize to accomplish what I want I need to change the stop to a stop/start so hlt will keep recording but I haven't tried that yet. Pretty sure the button is the red record button when I push back at the end.

I'll test with the stop set up as a stop/start and see if it's any different.

[vmbray]

I made a new thread because that way you will fix it faster

[Harry]

No, slower. I'm well managed.

[vmbray]

Okay sorry I'm just excited about the new version. The next event here is in two weeks it would be really cool if this could be fixed. Okay I will let you be. Thanks!

[Harry]

On android when you manually start the video, after crossing the finish line when you press 'back' to return to the timer view, the program crashes every time. When it happens it loses the start/stop triggers and generally wrecks the setup of the track etc. Mine usually reverts to whatever the last start/stop triggers it had programmed which could be from days prior.

I could reproduce the problem. Not yet fixed but some comments / a workaround:

The lost triggers are due to the fact LapTimer had not saved it before it crashed. In situations like this, it will roll back the database to the state it had when it has been started the last time. So this part is easy to handle, just send LapTimer to background once you have creates the triggers. backgrounding LapTimer will always store unsaved changes.

There are actually two problems with the so called mixed mode recording (manually started and replaced by automatic timing).

The way it should work is a) users starts video recording (and a manual lap) when hitting Record Now/the small red button. b) when crossing a trigger, the manual lap is stopped and an automatic lap is started; video recording continues c) when crossing the finishing trigger, the automatic lap is stopped, but video continues d) user stops video recording manually.

Problem #1: During c), the small red button / Record Now button re-appears although video is still active. In this situations, a stop button should be shown to allow the user to stop the video without leaving the view. Not a big issue, but probably confusing as d) cannot be performed.
Problem #2: While closing video video, step d) is performed automatically. Instead of closing the view immediately, LapTimer asks the user if the video recording active should really be stopped, or if the operation should be canceled. That's o.k. The problem is this works when using the close button (black cross) in the top right, but it crashes LapTimer when pressing the back button. So the workaround is: press the black cross instead of back until it is fixed.

- Harry

[vmbray]

Thanks Harry that worked great and overlay with intro/extro was perfect. I thought I tried the X instead of the back button but anyway it's working perfectly.

[Harry]

You need to be brave