App: Hiking

137

here is what im talking about.
this is not as severe as yesterday..but it still shows different numbers.
on todays small walk i had ZERO pause periods or rest.. it was just a walk there and back.


here is the watch face just as i was about to press pause


http://i64.tinypic.com/w72dr9.jpg

and here is my activity page on GC. the entry in concern is the top one


http://oi64.tinypic.com/r0nl8n.jpg

now its only 115 steps difference...but yesterday was much worse.

Matthew -

I'm not sure what's going on here, as Hike itself doesn't actually count steps. It just uses the numbers reported by the firmware. (which should be what's also written to the .fit file for upload).

There are two exceptions

- as of 0.14f, hike keeps track of how many steps occur while paused, and doesn't include "paused steps" in what's displayed by hike
- There is some code in hike to handle the case when you start hike before midnight and end after midnight, to handle the FW resetting the step count at midnight (ad midnight, it uses the history from the day before, and figures the "yesterday count" in addition to "today's count"

There could be a case where the FW is a bit behind it passing the count on to hike, which could explain a difference of ~100 steps.

Another thing could be is how the FW actually counts "steps" for a an activity vs just daily steps. For example, not every step is counted by the FW for 24/7, as there is some "false step" logic. With just a watchface or widget that shows steps, if you stand up and walk 3 steps and stop, you won't see those included. There is a "10 steps or more" trigger. You have to walk 10 steps before it considers them "steps", and then you get credit for those first 10. Maybe this logic is different for what's written to the .fit when recording. In hike, I ONLY have access to the 24/7 step count, and not what's being written to the .fit, and in one method, something could be considered a "step" where it's not in the other method

With the activities you mention, I'm guessing there are many start/stops in steps and a difference in how 24/7 steps vs "activity steps" are counted could be more visible.

I guess all I can say the numbers in GC are what Garmin thinks are correct, and in hike I don't have the same info available, and the number might be off until Connect IQ give apps access to what the FW thinks the step count is while recording an activity and not just 24/7 steps. For now, (with 0.14f) you can turn off the "steps" screen, and then just go by what you see in GC, or just use the steps shown by hike as a "best guess" based on info I can get.

There is another case where hike (and native apps) shows different info than you'll see in GC, BTW. It's the altitude/total Ascent/total Descent. The VVA and the 23x/630 use GPS for this info, and it can be quite inaccurate. When you upload an activity to GC, "elevation correction" is applied for devices that don't use a baro sensor for this, often showing very different (but more accurate) info than you see on the watch. Again, the apps can only use the data the FW provides..

Matthew -

when you start Hike, do you walk around a bunch before you press "start" to start the recording?

Looking at the code, that should work fine. I'm just seeing if I can find any way to correct the difference you see.

i wear the watch all the time except when sleeping and typing. its an uncomfortable item to wear.

SO when i get ready to hike...i put on the chest strap, put on my back pack..press the hike ap..wait for gps..then press start then i move.


i notice on the map of my 15km hike there seems to be a couple straight lines instead of it following the track, it looks to cut across some of it.

perhaps i lost gps signal and the app is not counting any steps made during the loss of gps which could account for thousands of steps not being counted?!??


ls there any way to have a comfirm icon on the discard screen? twice now ive accidently swiped the wrong way and when i went to swipe back it discards....i can manually enter the distance into GC, but i'l neever be able to put int he walked map

Now it crashes

Hi Jim,

I don't know, if I'm the only one, but since the f-update the app crashes "randomly".

As you know, I used it for weeks. Everythin fine. Every recording accurate. But since this update, it often crashes during saving.
Not every time, but 1 out of 3 or 4.

what I do:
stop/pause hike. ok
resume. ok
stop/pause again. ok
enter the house - pulse is shown as in the appropriate range
exit pulse message -> BAAANG!
autoreboot. reappears at save/resume/discard.
usually I choose to save now -> it's in "running" mode. the walk is saved as "running" calories seen to be ok. steps are lost. they are also lost in summary-frontpage-steps circle. don't Show up anywhere.

FR 235 FW4.10 (I just saw, there is a 4.20 available since a few hours, I'll try again)
hike 0.14f (Walk)
Tempe

pls find out what's wrong here, as I really like the app and use it on every walk.
and I like the ability to disable pages.

thx

Thanks. I'll look into it. I have a 230 that now on 4.20. I suspect it's because I'm getting close to the max memory. Because of the crash, when the watch starts back up, it saves it as a standard "run", as there's no native walk or hike on the 230, and the watch tries to recover the recording.

When you say "pulse" - are you using a HRM? That will take a bit more memory - could you try it a few times without the HRM? (I don't have one and that might push memory closer to the limit)

About how long do you run it at a time when you see get the crash? (an hour, 3 hrs, etc)?

update: it does look like a memory thing, and I'll be testing a quick fix for that this morning, and hopefully have an update ready later today. I added some stuff for the VVA-HR, and that pushed me out of what I see as a "safe zone" for memory usage on the 23x (it's all the same code)

The acut reason for my posting was the walk today:
11:42 - 2,03 km / 9:37 min/km / 19:29min (just to the postoffice and back during lunchbreak)

the first time was just after the update, I think
sun, 12,12km / 10:42 min/km / 2:09:48
and once inbetween, which I can't locate in my connect.

always using tempe an oHR from FR235.

@ tries to recover the recording
yes, everything looks fine in GC, except
a) "running" (although I understand the reason now)
b) total steps. any step between start and stop of the app is cancelled. the counter remains/restarts @ "before"; (the steps in/at the activity is recorded in GC!)
c) I'm not quite sure, if calories are

Version 0.14g

Just a quick fix for a possible memory problem on the 23x/630 watches.

As part of this, I reduced the maximum number of waypoints from 25 to 20, but will put it back at 25 in a future update when I find a better way to reduce memory. (this was a quick and VERY safe way of cutting memory usage)

meanwhile I've been forced to update to 6.20.
But I couldn't upgrade to 0.14g - or probably I did, but now I just see a IQ!; where the black "!" is inside a yellow circle. the capitals are garmin-lightblue.

uninstall/reinstall didn't help either.


sry