I totally agree! I had just finished a 3 mile run and looked at my iPhone to see how my run went and I literally saw the Intensity minutes box disappear after the app sync'd. I was like wtf! I have tried everything to get it back but to no avail. I guess this is a server side feature which for some reason Garmin decided users did not need - wrong! Garmin, please return this feature it is very valuable part of the app experience.
? a server side feature which for some reason Garmin decided users did not need - wrong!
From what I've observed, intensity minutes are actually recorded by the wearable device, and the Garmin Connect service only decides whether or not intensity minutes are displayed on a web page and in the Garmin Connect Mobile apps.
It's not a case of whether users ?need? or want it, though. Garmin made it clear that FR235 users are not meant to have access to intensity minutes by virtue of their choice of device model (and what the money they have spent in exchange for the devices). Users who ?need? the feature can hand over more money and buy another device model that supports it.
Personally, I see nothing wrong logically with that position, even though of course it does me no favours as a device user and Garmin customer.
I realize that the Intensity Minutes are recorded by the FR235 and I see Intensity Minutes on the web page. So why display Intensity Minutes on the web page and not allow it to be displayed on the Connect App. It was once there on the Connect App - now taken away. If FR235 users are not meant to have access to Intensity Minutes, why even display this information on the web, and allow one to set goals etc, makes no sense. The FR235 can certainly support the measurement of Intensity Minutes so the feature is there. This is simply, as I thought, a decision as to whether to display the information on the web and/or Connect App - which is, I suggested as did you, a server side operation. If it were not supported it should not be there at all. The link you point to by the way does not reference any official Garmin statement on Intensity Minutes as far as I can tell. I think at one point it was not a feature on the FR235 but became available with a software update.
The link you point to by the way does not reference any official Garmin statement on Intensity Minutes as far as I can tell.
Did you actually read that thread?
The specific post to which I linked stated Garmin's view that devices that do not support the feature should not cause Intensity Minutes to be displayed in Garmin Connect, and post #3 above that (also by the same Garmin staff/moderator) stated that the FR235 does not support the feature. Try putting two and two together.
Garmin through their own mistake revealed that the Intensity Minuted feature is ACTUALLY BUILT INTO THE 235, a watch that all of us paid good money for. Now the are saying because we didn't pay enough we aren't allowed to have access to that feature? IMO an attitude that will generate NO GOOD WILL AT ALL with their users. I will also point out that took place due to an update that obviously wasn't well tested prior to it being shoved downstream.
Between the flaky optical HR monitor, very poor performing step counter, and now this I am starting to wonder why I thought moving up from the Forerunner 15 was a good idea. Garmin really needs to re-think their approach to how they are doing business because I can see trends that lead me to conclude that they are becoming the Microsoft of wearable products instead of the Apple of wearable products. Survey Microsoft users and Apple users and you will find a Night and Day difference in Customer Satisfaction.
What really bothers me is that I've been a Garmin user since the model 12XL marine GPS unit and until the 235 I was always pleased with the performance of my Garmin products. Now with the 235 I am constantly getting updates shoved on me I didn't ask for and too many updates seem to have a new set of bugs to contend with.
Now the are saying because we didn't pay enough we aren't allowed to have access to that feature?
No, but Garmin is saying that we have no entitlement to that feature, and so stop banging on about it as if it was part of the package it promised in the model's marketing collateral and technical specifications, or hassling the company if it stops working or gets removed. Access to it now is given only by Garmin's mistake, oversight, goodwill or whatever, and will remain at the company's sole discretion; you have neither any rights, nor any say or control in that regard. If you believed differently, then it's now a good time to challenge that belief and recalibrate. That's the message, and I don't see why it's so difficult to grasp.
?Possession is nine-tenths of the law? is an idea that has no relevance in today's always connected, frequently updated software in which features can easily be disabled by the developers/providers from afar, so any argument on the basis of having had access is pretty pointless; formal entitlement to something is key.
IMO an attitude that will generate NO GOOD WILL AT ALL with their users.
OK, and? Maybe the company is quite prepared to test whether its firm stance will retard sales of new or more advanced models that actually promise more on paper.
I will also point out that took place due to an update that obviously wasn't well tested prior to it being shoved downstream.
The relevance of that being what?
Now with the 235 I am constantly getting updates shoved on me I didn't ask for?
Now that's just hyperbole. When was the last time an updated to the FR235 firmware was available/offered/pushed to product owners? Eight weeks ago. Besides, unlike on the v?voactive‑HR, FR235 users have the explicit option of not installing a firmware update.
Okay, my last stab at this. As I understand it, as an end-user, and of course I may be wrong but isn't the point of the Connect App to port the web Dashboard (desktop) to a mobile experience. If true, the data presented in the Dashboard should be available in the Connect App. This appears to be true for everything, as far as I can tell, except Intensity Minutes. So can someone from Garmin or anyone, explain what the rationale for this apparent inconsistency is.
sigh...and so remove a specification that Garmin states the device supports, as stated on the Garmin website, for the FR235...again, not so consistent.
