Session.AddLap Stops activity GPS & other funky issues w/ auto notification of LAP

Hi,

I am playing/testing with a custom built app and doing session.addlap at 1KM intervals. What I have noticed is that the during the times when session.addlap is executed, the following will occur.

Scene1
1) the AutoLap notification screen will come up. (this is a "bug" and per input prev from connectIQ guys - this should not be happening). When the AutoLap notification screen comes up, a few things happen

2) the AutoLap screen will take over the entire custom app. If i were to press the ESC (Could also be any other key) to dismiss the notification (much like how one can dismiss a SMS notification by pressing Up/Dn arrow key), I would in-advertently exit the custom app.

3) in my custom app code, the ESC key is used to either exit the app (only if there is no current recording session in progress) or to add a lap. In this case, when the autolap notification comes on, pressing the ESC key will EXIT the app and present me w/ the "save/discard" NATIVE dialog box. (not the custom save/discard dialog box I created). In this screen, it will show up as 0:00:00 min and _:__km ran or such.

4) when I click save/discard - I believe (i didn't verify in detail) that a new recording session is saved/discared (my custom app activity recording however is SAVED, I think even before this NATIVE save/discard dialog box comes up

Scene2
5) I have also noticed that doing session.addlap and during the instance when the autolap screen comes up, GPS will turn off. (I think. need ConnectIQ guys to verify based on the FIT file from the link)

6) Why I say this - when I look at the MyGPSfiles rendition of the route, I can see that at the autolap locations (each 1Km), I will see that the track will "break" apart and then the GPS track after that could "struggle" to get another GPS lock and end up possibly a drunkard.

In the pic below - you can see the "breaks"

Here's the link to myGPSFiles

http://www.mygpsfiles.com/app/#8szaGkUg

Please let me know if this is a known issue or something to do w/ my code or something to do w/ the Resume Later bug

F3. FW 3.6 GPS 2.9

Nikeow over 10 years ago

further testing (in the car.)

I think it's a recession of the same bug I pointed out (and You - Brian confirmed to be affecting FW a of F3. I prev was under the impression that it was fixed in 3.6 FW - which it did IN A Way)

But this is a regression. Previously was one had to exit the custom app, go to native app and then the save/discard native dialog box would come up.

This time round, it's when the NATIVE autolap comes up, I press start/stop on my custom app then the following happens
1) native autolap discarded
2) native save/resume appears
3) if press discard - watch goes into circling mode and need a power cycle to come back (same as prev)
4) if press save - I didn't test for this or I forgot
5) if press resume, u go to the native (and default setup I believe) run screen, run for a little while, stop and then discard and all is good again (again same as prev bug)

This time, I learnt a new thing and wanted to know what NATIVE app was running (since thr data screen that was shown is not something which I've already set up in any of my apps - custom or native). I pressed RESUME later, hopefully to be able to learn what app but that didn't stick as it just threw me back to the s-called current app it was running prior to resume later. So I long press menu, I get to the settings page, CURRENT APP (I see that it's running), then as I went in there, data screen1 and 2 was set up as what I saw when autolap kicked out, then I transverse the app and guess what... I saw the famous 8.05km autolap settings!!

I'm like EUREKA!! This is the infamous 8.05!!

Okay.. That's about it. I think it's done. I leave it to you guys to figure this out.

Let me know if any other help / clarification.

(One other thot I have now is - what if I self built an autolap banner - not sure if this will make it more "sane" - cos by adding an autolap at something other than 8.05 - the app is more "sane")

Nikeow over 10 years ago

justmsaw FW 3.8 is out. Didn't get pushed to the watch yet. So... Not sure it it helps or what not.

Changes made from version 3.60 to 3.80:
Fix potential issue with GPS acquisition, when resuming an activity.

If it's just that, then I don't think it helps me any.

Anyways...

Former Member over 10 years ago

Brian - on the addLap() and the native "lap" display, could this be an option, as I have an app that uses addLap(), and find I like getting the lap screen.

Maybe something like "addLap(showLapScreen)" ?

This is something we would eventually like to allow, but right now, the native page isn't handling running from ConnectIQ properly, so it is probably going to be disabled for a while before we can add it as an official feature.

Former Member over 10 years ago

Nikeow,

It appears pressing the start/stop button when the native lap page is up is triggering the native behavior for that key. When the native page is up it will block all input from your app, so that is why your own save menu does not appear. I'll add this new information to the investigation.

Nikeow over 10 years ago

Have a look at this GPS File.
http://mygpsfiles.com/app/#9tuAZWxX

Does it look like the GPS is still turning off after the session.addlap is done?

The tracks are not all that drunkard (I was driving) but seems there are discounuity in the circuit.

Former Member over 10 years ago

I don't know for sure why it would have an effect, but you should avoid messing with the GPS setting in the onShow method also. If you are re-enabling GPS when the lap banner returns to your app still, that could be causing what you are seeing there.

Nikeow over 10 years ago

Got it. Will remove that as well and report back.

Nikeow over 10 years ago

Just tried it and the results still shows that there are small little "breaks" in the track.
I'm not sure what exactly these are honestly. i looked at normal other FIT files and they don't have these.

http://mygpsfiles.com/app/#ai1toVxH

Nikeow over 10 years ago

I found out that by removing the GPS on the onShow(), I would essentially be getting to the current F3 "bug" whereby the GPS will get "lost" once user goes into watch-mode or to widget mode(long press DOWN button) and then return back to the app.

Can you confirm if this is intended behaviour or just a regression based on the FW on the F3?

jim_m_58 over 10 years ago

Just as additional data on this, today I used my CIQ app on a vivoactive that allows me to mark laps whenever I want, and see no drops in GPS when I do so. Also, I made a point of going back to the clock/widget screen a few times (for a couple minutes at a time) and saw no drop in GPS there either.

When I use my "pause" function, but move a distance while paused, the map just shows a straight line from when I paused to when I took it off pause (that's what I'd expect, as there is no GPS data recorded during that time).

One thing I didn't try is if I go through an area with little or no GPS reception (like going thru a tunnel), but i think that will just give the "straight line" I see when paused..

VA FW 3.00 - and it looks like there are no issues with it.