Getting ECG app with japanese Fenix 7 Pro

Hi, I am living in Japan currently and bought a japanese model Fenix 7 Pro.

I'm planning to go to the US soon, so I was trying to see if I can enable ECG ahead of time.

The problem is that the unofficial process to get ECG doesn't work, which worries me that even when I go to the US it won't be available at all.

Is getting ECG even possible on japanese APAC models?

Did anybody manage to do it?

Top Replies

All Replies

  • What is to "dislike" on a ECG app? It´s a health feature, and Garmin is doing what is necessary to protect the user data. 

  • Yes. 2FA is being used for your SSO (single sign-on) across all their platforms such as Forums, garmin.com profile, Connect, etc.

  • Yeah, that's fine I prefer using 2FA in general so not an issue for me.

    But since ECG won't come up anyway...

  • While I do not have any ECG related data in my profile, as I already delete it along with the app, it doesn't make any sense for me to not being able to remove the 2FA as well. And such explanations as "its permanent" are just not serious for a company that pretends to be the best on the market.

    And yes, the app is not nice primarily because forces you to use 2FA, among other things, I do not see any benefit from it. But if you are physician and you can read and understand the measurement, that might be okay for you, but for me- a simple everyday user who likes to run, cycle and climb things, its simply non-sense.

  • Have in mind, once enabled, it will also enable 2FA,

    The user can choose to have 2FA or not. it's not needed for ECG on the watch only if the user wants to view the ECG in Garmin Connect. If you don't want to be stuck with 2FA then ignore the option to enable it.

    FWIW, I enabled 2FA when I set up ECG in New Zealand using the workaround and don't really mind the slight inconvenience. I don't bother with the ECG anyway now as it offers nothing of value for me.  I don't find 2FA a massive intrusion but I understand others will be annoyed and others just want to Garmin bash at any given opportunity.

  • If it’s not visible in Connect or exportable to PDF, I’m not sure why it’s only on the watch, especially since the watch only detects AFib. I enabled 2FA thinking I could view it in Connect, without realizing it was permanent. While it may have been mentioned somewhere, I don’t understand why I can’t remove 2FA, especially since I don’t plan to use it.

    On the bright side, I’m getting used to dealing with the verification codes every time I log in. No bashing, just a bit frustrated with how some things aren’t fully thought through.