Seriously though, perhaps you have the sapphire (by accident)? Actually mine shows Fenix 5 - Sapphire edition in the mobile app as well even though I have the normal one (and no wifi stuff here, just the wifi folder when connected to the computer).
(And why do they put red on it anyway? You can customize the color of the strap and the watchface but hey here's some red bits to clash with it).
I did this by testing the LiveTrack feature. After the run, I turned off LiveTrack in the app, but noticed the watch wasn't syncing the activity with the phone even though it was connected. So I went into the controls menu and tried to sync manually and it said:
So I hit continue and then it tries to search for Wi-Fi.
Bonus content: sometimes when you hit continue instead of the wi-fi message you just get a blank screen, or if you're really lucky you get this:
I rebooted the watch, and rebooted the phone, but the watch remained convinced I was in a LiveTrack session and wouldn't sync.
I've since got home and plugged the watch in via USB and it synced there.
It still won't work with phone though, keeps giving me the LiveTrack message.
I had the same problem twice already (Livetrack staying on and cannot be disabled). First time I did a factory reset, which is tedious as you have to setup everything again. The second time I deactivated LiveTrack autostart from the GC app and tried to manually start a Livetrack session through the app afterwards. This failed the first time, but the watch didn't think it was stuck in a Livetrack session any more and worked as expected.
I had the same problem twice already (Livetrack staying on and cannot be disabled). First time I did a factory reset, which is tedious as you have to setup everything again. The second time I deactivated LiveTrack autostart from the GC app and tried to manually start a Livetrack session through the app afterwards. This failed the first time, but the watch didn't think it was stuck in a Livetrack session any more and worked as expected.
Thank you for the info!
Garmin told me to do the factory reset too, which I've done.
It's not just the tedium of setting everything up again, but I guess we also lose personal records, training metrics etc that apparently take weeks to build up.
I had a feeling the same thing would happen again if I try LiveTrack, so it's good to hear you found a workaround. Maybe I can avoid the reset next time.
I had also noticed the problem after using the auto start livetrack when the watch was on 2.40; but the issue seems to be fixed with 2.72 beta (that's my experience so far).
Garmin told me to do the factory reset too, which I've done.
It's not just the tedium of setting everything up again, but I guess we also lose personal records, training metrics etc that apparently take weeks to build up.
I had a feeling the same thing would happen again if I try LiveTrack, so it's good to hear you found a workaround. Maybe I can avoid the reset next time.
Firmware 2.90 is up which fixes the issue (says so in the changelog)! Concerning the training metrics etc - isnt there a way to back them up?!
That's the fastest bug fix ever :) (Ok yeah, it was already fixed in a beta)
I found you can put the records back onto the device. The performance measurement stuff I'm not sure how that works yet, it's all there in Connect so I hope the device still knows about it.
