Garmin connect has changed to Chinese on my Edge 1040 does anyone know how to get it back to English
Garmin connect has changed to Chinese on my Edge 1040 does anyone know how to get it back to English
I don’t see a language option within the garmin connect app through settings
I logged a ticket today and got following reply;
Hello Steve,
I recommend reaching out to Product Support through their website at Garmin Support directly to report the issue.
I've been waiting for an update for at least 2 months. Come on Garmin! Their Support said it's a known issue, yet no fix to date.....
OK got that...added new IOS language in settings/language and region, then back to Settings/Apps/Connect/Language was now there, changed to new second language, opened Connect App, connected to Edge 1040, all app and indeed device menu was now second language...closed Connect app, back to IOS settings./Apps/Connect/Language back to primary English...opened Connect App, it was back to English but when connected to device, Chinese menu was back...
The latest beta version 26.11 contains a fix.
I can’t tell you when Garmin will make the next release on the regular channel. 24.19 and 25.24 came out about 4 and 2 months ago.
Hi all. I may have a fix for apple phones.
Open settings, open connect app from app list, at the bottom you should see language selection, open this and select Chinese Traditional.
Now open the connect app and it will be in Chinese, go to connected devices and open edge device, this is now in english.
Now go back to settings, open connect app from list, at the bottom you should now have both English and Chinese in your language list, now select English.
You should now have the edge part of the connect app in English.
I do not know if this will work for other languages.
New phone, just re-added my 1040 in Garmin Connect, and it shows up in Chinese? My watch re-synched and is in English. I checked any app specific language settings, there is nothing for Garmin connect. What the heck is going on? I see others are also having this issue, but no fix as yet?