Versa 4 Always-On shows some watch face instead of custom face I selected

[Allways]

When the watch is active it displays the Glance face I selected.

I enabled Always-On Display and I expect the watch displays always the Glance face but it shows a different face (with the date and time)!

Sleep Mode is Off, Do not Disturb is off, Focus Mode is off, battery is at 51% currently.

How can I make it show the Glance face at all times? I don't care if I trash the battery.

Thank you

[Allways]

This worked just fine for a few months since I got the watch, but a few days ago it broke. Is it possible that a recent update broke it, or is it my fault?

[LZeeW]

Hello @Allways and welcome to the Community.  Thank you for adding the additional information that your Glance clock face was working correctly.  The details don't specifically mention always on display and there's no AOD screenshot in the details.

What general troubleshooting have you tried?  Do you have other stored clock faces and is this the AOD display for a different clock face?  I'm not aware of any update that would cause this problem.  I've never seen a post that described your experience -- a completely different AOD image.

You can always contact the developer for more help.  Tap on your device/battery icon in the upper left > Versa 4 > Gallery > tap on your Glance clock face > See all details > swipe up to Contact developer at the bottom of the page.

[Allways]

One week ago the Always-On was working as I expect it to work. The Glance face was always visible. But now this is not the case. 30 seconds after the latest interaction with the device I see four big digits representing the hour and minute.

To troubleshoot I tried to check the settings of the Fitbit and searched for this issue on the net, and I ended up writing this post. I also tried to reboot the watch.

Glance is the only watch face I use. There is also the default Paths face but I never use it. The HHMM "face" seems to be some special face. Definitely not something I installed.

The same behavior happens with the Paths face. I don't think the Glance face developers can help.

In the Gallery screen on my phone I see these faces are called "clocks". I just removed the Paths face, now I only have Glance, but still the same.

I only need the watch to display the time and some extra data, no sensors, no anything. Fail. 🙂

How does it work for you?

[LZeeW]

@Allways   I don't use the Glance clock face.  I am trying to get more information that might help troubleshoot your problem.  I think you should contact Support for more help, given the additional information that you are getting the same AOD error with different clock faces.  Tap on your profile picture/gear icon in the upper right of your app > Help & Support > Contact Customer Support.

[SteveDallas]

I am having exactly the same issue as AllwaysOn with my Versa4. Doesn’t matter what clock face I install (tried glance and Blue something) - always on defaults back to time only instead of the clock I installed which sort of defeats the always on function. Spent an hour with support with no resolution. Can anyone help?

[Guy_ · Accepted solution]

Hi @Allways  @SteveDallas  - have you tried restarting the watch and changing to another Always On clock face.

If a clock face doesn't have it's own Always On face it will revert to the default Always On display from the watch.

If the clock face was updated or developed a fault it's behaviour can change.

If the restart doesn't fix it uninstall it and reinstall it, may.

The Glance (by Ryan Mason) is not shown currently as an Always On clock face.

Also check your Quick Settings, pull down on the watch face to make sure you have the correct settings, (and even in Settings there is an option to change the amount of time the display stays on).

[Allways]

---

If a clock face doesn't have it's own Always On face it will revert to the default Always On display from the watch.

The Glance (by Ryan Mason) is not shown currently as an Always On clock face.

---

This must be it.

Sad that such basic functionality of fetching and displaying data does not work. Fitbit knows better than the users. 😞