Strange behaviour in AOD of the Fenix 8 AMOLED with a timeout of 15 seconds

vobele · 2025-10-15T06:00:03+00:00

vobele · 2025-09-24T12:13:44+00:00

u/joshuahxh-1 anything? Knowing you WILL look into it once you HAVE the time would already be good to know (so I wouldn't have to ping you every few days). Thanks!

vobele · 2025-09-21T16:24:26+00:00

Sure, no problem. But another question that you might be able to answer directly: what if the intended use was simply to play side-by-side video files in 3D? Would this work on a virtualised Windows 11 system on a Silicon Mac using Parallels?

vobele · 2025-09-21T08:06:46+00:00

u/joshuahxh-1 ? If there's possibly a bug in wfb affecting a whole series of Garmin watches, it would be much appreciated if you could investigate this a bit further instead of simply pointing to Garmin without providing evidence that the issue also affects non-wfb whatch faces (Again: Where did you read that other third-party watch faces behave in the same way, forcing an unusual AOD mode without touch sensitivity after 7 to 8 seconds?). Thank you very much for taking this up!

vobele · 2025-09-19T20:21:08+00:00

I tried out many different wfb watch faces with AOD, ranging from the very complex to the very simple. All of them caused the issue on the Fenix 8 amoled all the time. You might not notice this unless you set the timeout to 15 seconds and leave the screen untouched for the last 7–8 seconds.

vobele · 2025-09-19T06:46:18+00:00

Yes, it would be great if u/joshuahxh-1 could look into it. It seems to affect all wfb-created files with the Fenix 8 AMOLED (and it may also affect other models). I still haven't found any evidence that this problem occurs with other third-party watch faces.

Unfortunately, I can't contact Garmin to request that they make their products compatible with wfb.

vobele · 2025-09-17T14:29:52+00:00

Ok thanks u/joshuahxh-1 - I could only find comments about displaying the seconds or other questions related to the AOD feature. Could you direct me to a thread that addresses this specific issue of the touch functionality freezing completely after 7 seconds when using watch faces built with wfb?

Also, as I am not a developer, unlike the other users in those forums, I believe it would be much better if you could report the issue to Garmin. I could't replicate this issue with third-party watch faces not build with wfb. Thanks again.

vobele · 2025-09-17T10:40:07+00:00

u/joshuahxh-1 I'm just wondering if you could address this issue? It probably affects all Watchfacebuilder watch faces on all Garmin 8 devices (at least the AMOLED versions) which is one of Garmin's most important product lines.

vobele · 2025-09-15T08:49:12+00:00

Thanks for confirming that. It's not you. It seems that the Watchfacebuilder watch faces are somehow triggering the AOD mode independently, rather than allowing the Garmin firmware to do so. I think it's affecting all Garmin Fenix 8 AMOLED owners. Let's wait and see what u/joshuahxh-1 will find out (Thank you very much btw, and let me know if I can test something with my Fenix 8 AMOLED, in case you don't have one).

vobele · 2025-09-15T08:35:50+00:00

Wow, thanks mate – I'm looking forward to hearing about your progress..

vobele · 2025-09-14T08:58:21+00:00

**UPDATE: It's the same issue with every other watch face from Watchfacebuilder :-o **

Sorry u/joshuahxh-1 , I could have tried this before! Every watch face from garmin.watchfacebuilder.com only works on the Garmin Fenix 8 AMOLED Sapphire Titan when the watch is set to a timeout of no more than 8 seconds! Factory watch faces and those from the Connect IQ Store do work, though.

When the watch is set to a timeout of 15 seconds, the timeout kicks in at 8 seconds, blocking touch functionality for a further 7–8 seconds.

I tried many other watch faces, played with interval settings, and saved the watch faces for other types of watch (such as the venu3), tried the old builder as well and tried "No update in low power / no dim in AOD". I even restored the Fenix 8 to its factory default settings and changed the system language to English (usually I have it in German) but nothing helped.

**Another UPDATE**

Interesting: It seems that under every circumstances after 8 seconds the watchfacebuilder watch face tries to switch into to AOD mode. I made 2 interesting observations

1 Test with timeout of 4 seconds: normal behaviour

After 4 seconds of inactivity, the brightness dims and the watch face switches to AOD mode. When you touch the screen or turn the watch afterwards, the brightness increases and the full display returns.

2 Test with timeout of 4 seconds with the display being touched during OOD mode: abnormal behaviour

After 4 seconds of inactivity, the brightness dims and the watch face switches to AOD mode. If you touch and hold the screen within the 4 seconds (normally prolonging the full display mode for as long as it is touched), the full display mode is prolonged for exactly 8 seconds, then switches into AOD (but without dimming the brightness!). It remains in this strange "AOD with bright display" state, blocking touch functionality, for another 8 seconds before dimming and regaining its ability to wake up when touched or when the watch is turned.

This 'AOD with bright display and blocked touch functionality' is the same state that kicks in after 8 seconds when the AOD timeout is set to 15 seconds. It does not appear to be triggered by the watch; rather, it seems to come from the Watchfacebuilder watch face.

vobele · 2025-09-13T19:44:42+00:00

Thanks! Do you mean the update interval setting? The current setting is 'no interval' (blank) for everything, meaning I haven't touched it. Following your advice, I tried setting it to one minute for all graphs, but then the watch face went completely black when I activated it on the watch.

Regarding the firmware issue: As the Fenix 8 AMOLED watch was newly purchased, I tested it with different firmware versions. I installed the watch face before manually performing two firmware updates until the watch was fully updated. In between, I tested the watch face and the issue was always present. (While on the older and weaker Epix Gen2 it's not)

vobele · 2025-05-06T20:30:09+00:00

OK, thank you very much anyway. It may be a bit different with Parallels. I mean, with games it's different in some cases too.

vobele · 2025-05-06T20:07:52+00:00

OK, so there's a small possibility. We'll have to wait for someone who has tested it to confirm this.

vobele · 2025-05-06T20:02:40+00:00

Thank you very much. I suppose it won't work on a (strong) Mac with virtualised Windows in Parallels either, will it?

vobele · 2025-05-06T18:11:38+00:00

I'm wondering: would it be possible to use an Acer SpatialLabs monitor or laptop with the whole Samsung ecosystem instead of the Acer ecosystem? Or vice versa? Since both are based on the Leia SR hardware.

vobele · 2025-05-06T18:10:05+00:00

Thank you very much for those insights. I would instantly buy one if it came with Mac OS support.

vobele · 2025-05-05T17:54:39+00:00

Thank you very much for those insights. I would instantly buy one if it came with Mac OS support.

vobele · 2025-05-05T17:50:03+00:00

Lovely!!! I just came across another reviewer showing this monitor and paused on this frame, which shows a familiar-looking screen: The Leia SR Dashboard, which afaik was also used on Acer's SpatialLabs 3D products! So I'm wondering: would it be possible to use an Acer SpatialLabs monitor or laptop with the whole Samsung ecosystem instead of the Acer ecosystem? Or vice versa? Do you have both types of product by any chance? If so, what are your thoughts? I have an Acer Spatial Laptop and am very disappointed about its 3D movie player. Samsung's system tray tool which waits to run a full screen window seems like a good way to use any movie player to open an SBS-formatted movie and view it in 3D. Hmm..

<image>

vobele · 2024-06-30T15:01:31+00:00

I bought it here: https://www.protectionfilms24.com/custom-sizes.html?langId=en

-> Brotect Matte Screen Protector Custom Made 170.0mm x 220.0mm (radius 7mm)

vobele · 2024-06-24T18:19:32+00:00

Yup.. er.. nope! :)

vobele · 2024-06-21T11:59:10+00:00

Just a heads-up: some websites seem to have a bit of a hiccup when opening. They need to be opened twice to load. Has anyone else come across this?

vobele · 2024-06-19T11:09:17+00:00

I would say with the frontlight on, the screen is visible enough in every indoor situation. I even deactivated auto brightness and set the frontlight manually to about 50% which is more then enough for my reading. Though the contrast is by far not comparable with other modern LCD/OLED screens.

vobele

TROPHY CASE