VivoActive Screen timeout

Former Member over 9 years ago

I have a general question that I can be more specific if necessary.

I have been troubleshooting a Triathlon application (pmTriathlon).

It is setup to log all three disciplines with transitions in-between.

The issue is that once the first discipline is completed (by pressing the right button) it starts the transition phase. all is well and will do the same for each time the button is pressed.

The issue is that after the application starts and the button is pressed to transition it will work fine until 45 seconds later where it exits the application with no errors. (used to be one minute but now sure why it changed).

In troubleshooting I found that if I press the light button before the 45 seconds, I will get an additional 45 seconds and I need to keep doing that if I want it to keep going until ready to press the enter button again.

This seems to be the same behavior as with pressing the app button to see the apps and then after 45 seconds of not selecting anything it goes back to the main screen. Pressing the light button tells it I am still working on the screen.

The problem is that when the problem is running it is running fine and updating the clock (refreshing the time) so not sure what else the issue could be or there is any way I can prevent the time out.

Enough of the ramble. let me know if I need to clarify anything.

Thanks,

John

Brandon.ConnectIQ over 9 years ago

I am able to reproduce this on 3.40 firmware and on the latest unreleased development version of firmware. It takes one minute on my watch to time out, rather than 45 seconds, but the issue is generally the same.

Watch-app type apps should not time out, so it's not clear to me what's causing this. For example, I have another app installed on this same vivoactive, and if I launch it and let it sit, it will keep running until I hit the back button to exit. That suggests to me that it's more likely something in your app rather than a firmware-related issue. I won't rule out firmware entirely, though. ;)

During this transition period in your app, is activity recording paused? Do you have anything that might be popping the view (which may inadvertently cause the app to exit)?

If you're unable to locate the bug, we'd be willing to inspect your source to see if we can find a potential cause.

jim_m_58 over 9 years ago

For the different parts, are you creating, recording, and then saving parts separately? For example, do you record a "SPORT_RUNNING", and a "SPORT_CYCLING" as two different activities, or do you just record a single activity?

Maybe using "SPORT_TRANSITION" and "SPORT_MULTISPORT"? (I'm not sure they work right on the VA and have never tried using them, and the FW might not support "Multi Sport" like some of the higher end watches)

chrishares over 9 years ago

I can provide a couple of inputs here:
1. I have a Vivoactive, and my App isn't timing out; so I don't believe it's an generic problem.
2. You can't use the Multi Sport activity type as per my other thread https://forums.garmin.com/showthread.php?343397-More-problems-with-ActivityRecording

Cheers
Chris

jim_m_58 over 9 years ago

1. I have a Vivoactive, and my App isn't timing out; so I don't believe it's an generic problem.

Same here. I have recording apps that do SPORT_RUNNING, SPORT_WALKING, or SPORT_HIKING, that I run pretty much daily on a VVA and never seen this. The apps also uses "stop" and "starts" of a recording to handle "pause", so that's not involved, IMHO.

Former Member over 9 years ago

update

Sorry I was not notified there was responses to the original post so I will respond to all here.

Yes, each activety was stopped and saved before starting another. Yes, the first sport used swtichtoview so popped and then pushed.

The original code was not mine.

Yes, it used to be one minute timeout and then 45 seconds strange but no biggy.

I have since come up with a solution (temporarily since I do not think it is the best solution.)

It seems that the "save" is what was causing the timeout in combination with the switchtoview.

So, now I stop, change sports and then start again. it seems to work although the screen take a long second to update and switch.

I create a new app under my name to keep it separate from the original. It is called jTriathlon (for now).

The API docs are not that robust and I am new to Monkeyc so pardon me but spent several hours debugging and was able to come up with at least a temporary solution.

I tend to think that when popping/pushing a new view and then saving it will consider that done even if I start a new session without a new view.

I tried to push a new view and got a too many timers condition so it would be good to know the best way to start/stop/save and sart again without a timeout condition.

BTW, it is my understanding that the SPORTS and SUBSPORTS are only to categorize data after it is uploaded and should have no effect on recording itself.

Thanks for the feedback.

John

Former Member over 9 years ago

feedback

Any feedback on my previous post?

Looking to see how I can "Save" a FIT file and start another without having a timeout condition.

Just using "Stop" seems to also save once I start again but it is sluggish to switch views (maybe 4 seconds).

Thanks,

John

Brandon.ConnectIQ over 9 years ago

I'll have to look into this a little more. It sounds like it's the save that's doing it, like you mentioned, but I'm not sure whether this is by design.

Former Member over 9 years ago

Thanks

I'll have to look into this a little more. It sounds like it's the save that's doing it, like you mentioned, but I'm not sure whether this is by design.

Thanks. As a reminder, I was able to determine with print outs that when it exits it does so with a OnStop() so the app is not crashing.

Also, pushing the light button frequently will keep it alive.

Ideally, the application should not exist without an explicit call to do so by the application.

John

jim_m_58 over 9 years ago

Been meaning to check what happens after I save a recording on the va (type=SPORT_HIKING). In the app, after the save, I display a summary screen, and sure enough, it times out after a minute and returns to the watchface. (normally, after I review the summary, I just back out of the app). It's not the "stop" of a recording, as I use stop and start to do pauses all the time (often for 5-10 minutes)

No timeout like this on the 230, BTW....

Former Member over 9 years ago

Thanks for the confirmation Jim. The original programmer likely used save as a means to start another sport. It seems that this is not necessary as Garmin still splits out by activity correctly once uploaded however the application is more sluggish when switching sports than it is when saving for some reason.

John