activity recording paused and addLap weirdness

I believe that this has already been addressed, but I don't know for certain whether the fix was in 3.00. Is there any way you can collect crash logs from your beta testers? That would allow me to verify whether it's the same issue or a new one.

The folks beta testing already have the fixed version. I can try to reproduce it, but I'm already on 3.10.

update: I looked back at the problem report, and it turns it wasn't a crash, but a lock up needing a hard boot ( I was able to reproduce it on the 3.10 FW)

Not much in the log:

1907 (vívoactive) SW ver: 310
Build Type: RELEASE
ESN: 3900590391
Battery Voltage: 4.162000V
07/17/15 19:01:44
AP
LVD
POR

Again, it was calling addLap() when the recording was stopped. Got the std "save/discard" screen, and if you hit "discard", then the check mark to confirm it, it keeps saying "discarding" until a hard reset.

Again, it was calling addLap() when the recording was stopped. Got the std "save/discard" screen, and if you hit "discard", then the check mark to confirm it, it keeps saying "discarding" until a hard reset.

Sound similar to my issue.

Sound similar to my issue.

I was able to avoid it by just not calling addLap() if I was "paused". Could there be times you're calling addLap() after a recording.stop() and before a recording.start()?

Hmm... The app does not allow for that to happen. (Coded that way)
Only way to add a lap is
1) when session is on
2) when auto lap is on
3) when user presses lap key

But all depends on #1

Issue will still happen if u do something like stop/start WHEN the lap screen comes up.

If u re read my post. (My forum thread. Not this post in this thread)
Whenever u do something when the native lap screen comes up, all control u fm codes in your all goes out the window. It's not your app controlling anymore. It's the native one.

Try this
1) add lap
2) press start/stop
3) save/discard comes up
4) press Resume Later
5) it will drop u back to watch face
6) go to native run app
7) go to settings.
8) observed if u see auto lap set at 8.05km (or 5miles)

If u see it. I bet it's the same bug.

If u see the save / discard. The following is what u need to do to not need to reboot.
1) press resume
2) stop
3) press discard

Whatever it is, u need to START THE session again if u get to the native save/discard. Once u done that, u will notice your original app session is Alry saved as well in your history.

I just tried doing something similar to what you describe. It might be my app or that I'm on a va, but when the std lap screen is displayed (while recording), none of the buttons but "back" have any effect (and back just takes me back to my app.

Hello CIQ guys -
On the F3 - updated to 4.4 FW.
I noticed that the default LAP screen is no more appearing? Can someone please confirm ?

I was liking that screen :-(

Btw - I can't find the thread that has Brandon/Brian commenting about the lapscreen and "user selection" for enabling or disabling it.

The lap screen was removed at this time because it was not properly incorporated with ConnectIQ. When the lap banner was up, pressing buttons would trigger unintended behaviors from the native recording modes. We may eventually be able to re-enable the native banner using an option in the ActivityRecording Session, but for now, you will need to push your own view if you need a lap screen.

Boo hoo hoo.... :-(

That (pushing. View) just ads more code and inches closer to the max memory size.

Double drats