Watch is being identify on the app as charlie tactix and not as fenix 5x

Hi,
I am on beta 10.52 since day one and after a long time everything was working great including the mobile sync...but ...for some reason in the last 5 days my watch is being identify on the app as charlie tactix and not as fenix 5x and the blue touth sync to my Galaxy S8+ stop working
I tried the following :
1. restart both watch and phone
2. reinstallng mobile app
3. pair again mobile and watch
4. installing previous app version

Still issue not solve, open for any other suggestion or tips, Thanks

0 66fra over 6 years ago

Same issue for me (fenix 5x; huawei p8lite 2017 - fenix 5x is identified as tactix charlie) but synchronization with bluetooth works well

0 pshare over 6 years ago

There is an HTML file on the watch that identifies the device. I would think that elements if the tactix probably were used for the update and forgot to change the tactix identifier in the file. You could try to edit that file and change it to say the Fenix. There isn't a lot of syntax but you need to spell it out exactly right to get a picture.

0 itsikV over 6 years ago

Hi Phil
i am more interested about the sync issue that started and less about watch name,
any idea if that cinnconed?

0 pshare over 6 years ago

I doubt it. However, there were some reliability issues with Connect yesterday for a few hours but that was only for part of one day. I really haven't had any sync issues for a very long time.but I don't have a Fenix.

0 sis651 over 6 years ago

I have Fenix 5X and saw it identified as Tactix Charlie during the first setup last week. After that I sent it to service for overheating during charging and they replaced the watch. After I initialize and sync the watch with the phone, I again saw that Tactix Charlie name. As these are different watches and one is even newer and not updated, I think Connect Mobile app has some issue identifying the watches. In the past I remember our Fenix 3's were identified as rubber ducky in Connect website. :D

0 nmyeti over 6 years ago

I posted this in another thread on this same topic, but it is a bug in Garmin Connect that has been fixed, but the fix hasn't rolled to production just yet (According to the beta software team).