I assume you refer to the drill log feature. Indeed, the vivoactive doesn't have it.
I assume you refer to the drill log feature. Indeed, the vivoactive doesn't have it.
Max memory is under half of limit. I included println calls under the g[] = g[] + 1 and when the thing is run the prinln calls don’t go off so it’s definitley that that is the problem. I don’t know how to fix it though.
of course it's the bug, somewhere, device or simulator, both should run the same way
and yes, if something is by design should be described in documentation to this time it's a bug, to every bug report Garmin can answer - by design but if it's true…
Scrivo perché è da qualche giorno che il mio forum ed 245 non mantiene stabile la connessione con iPhone XR .
Ho provato di tutto, ripristinato sia l’orologio che il telefono, ma il problema non si risolve .
Così è veramente fastidioso…
I'm here about this too, it's the weekend and my stress levels are super high, were high throughout the night. I've gotten that a lot in the past few months.
Yeah, the VO2Max reported by the watch seems to be a moving average (like last X days).
One data point is that the free site https://www.runalyze.com can sync with your Garmin account and calculate its own VO2Max value per-run which is *not* a moving…
This is basically unacceptable for a product that costs hundreds of pounds and only lasts a couple of years. The replacement unit that I was sent last March under warranty to replace my original unit has now done exactly the same and the GPS has stopped…
If you are using dc calls and not layouts, you actually don't need to all View.onUpdate() at all. If you are mixing a lawout with dc calls, you need to do the View.onUpdate() before you do dc calls. View.onUpdate() clears the screen so any dc calls…
Thanks. I think the response could be more helpful. Making "expected behaviour" known and understood outside of Garmin is part of good documentation. The API docs for View.onUpdate() should contain full details of the behaviour and the expectations…
