This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connect Mobile Android ignores "first day of week", defaults to Monday

I have "first day of week" set to Sunday.

I go on Sunday for a nice long run.

Connect adds this to *last week's* intensity minutes graph, and continues to show the week as starting *tomorrow.*

This is true for all the other graphs as well; in short, the "weekly" view doesn't honor the setting for "first day of week" that I have specified.

The desktop (web) interface, however, counted my miles as on the *current* (starting with Sunday) week.
  • Yeah, basically, Connect on Android (and maybe on IOS too) is broken. It doesn't honor the "first day of week" setting on either the watch itself or what is set via a browser login to the web page, and there's no way to set it in the Android app either -- it defaults to Monday, like it or not.

    Thus the bug report / complaint.
  • No, I think you're missing the point, sorry.

    Weekly intensity minutes, as a metric, is calculated by the Garmin wearable fitness device, not by the back-end Garmin Connect service 'in the cloud'. The display preference that applies to Garmin Connect is not binding on the device; in other words, it is not an ecosystem-wide setting, no matter how much you would prefer to see the wearable device and back-end service as seamlessly integrated components. Your watch tells Garmin Connect what the weekly intensity minutes figure is, and Garmin Connect (online in your browser, or through one of the Garmin Connect Mobile apps) simply reports what it has told without performing any post-processing it isn't authorised (by the service designers) to do.

    That doesn't make Garmin Connect broken in that regard. It's not automatically a defect just because it defies your expectations (without reading the technical design documentation to cross-reference how it was specified) and as a user you don't like how it behaves.
  • No, I think you're missing the point, sorry.


    No I'm not. You're wrong as to how it actually works.

    Weekly intensity minutes, as a metric, is calculated by the Garmin wearable fitness device, not by the back-end Garmin Connect service 'in the cloud'. The display preference that applies to Garmin Connect is not binding on the device; in other words, it is not an ecosystem-wide setting, no matter how much you would prefer to see the wearable device and back-end service as seamlessly integrated components. Your watch tells Garmin Connect what the weekly intensity minutes figure is, and Garmin Connect (online in your browser, or through one of the Garmin Connect Mobile apps) simply reports what it has told without performing any post-processing it isn't authorised (by the service designers) to do.


    WRONG!

    On SUNDAY Connect said I had nearly 400 WEEKLY intensity minutes. The WATCH thinks the week starts SUNDAY. I performed ONE run on Sunday morning of approximately ONE HOUR.

    That does NOT account for 400 WEEKLY intensity minutes displayed in Connect. Connect, in fact, doesn't just give me a numerical value it in fact shows me intensity minutes PER DAY and totals them ITSELF.

    Right now Connect says I have 85 WEEKLY intensity minutes and shows ONE activity from this morning, which is correct since I ran a 5k this morning -- except that it is IGNORING my 7 mile run yesterday.

    The WATCH says I have 1:21 of running (which should amount to roughly 200 intensity minutes) and 10.04 miles THIS WEEK. It's correct, since it was told Sunday is the start of the week and it is honoring that.

    Connect on my phone is NOT taking the data from the watch and "not performing any post-processing." It in fact is aggregating the days' intensity minutes together over what it thinks is a week ITSELF, computing intensity minutes for the week ITSELF, and displaying it ITSELF. It is doing so despite being told in its app preferences that SUNDAY is the first day of the week, NOT MONDAY.

    That doesn't make Garmin Connect broken in that regard. It's not automatically a defect just because it defies your expectations (without reading the technical design documentation to cross-reference how it was specified) and as a user you don't like how it behaves.


    Yes it does make it broken. It is NOT simply taking the value from the watch for weekly intensity minutes; Connect is ITSELF aggregating the data, ITSELF calculating intensity minutes for the week and it is ignoring the fact that I have told it that the week starts on Sunday instead of Monday.