Backlight Issue

I'm experiencing this backlight bug. https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-55-series/365681/backlight-bug on the latest firmware v11.01

Backlight settings are set to 'after dark' and when scrolling through glances the backlight briefly comes on for a fraction of a second on some glances. If you press the up / down buttons repeatedly and fast enough then the backlight stays on, until the timeout elapsed. And I had the backlight come on while editing an activity data screens.

0 flocsy🤠 24 days ago

Can you give examples of which widgets do have , don't have the issue? Can it be related to whether it's a built-in widget vs one that was downloaded from the Connect IQ store?

0 Jacquers 24 days ago in reply to flocsy🤠

All built in glances, e.g. HR, Body battery, Performance, etc.

I'll make a video demo of it soon.

0 flocsy🤠 24 days ago in reply to Jacquers

Cool, please upload to YouTube, add the link here, then report to Garmin Customer Support at support.garmin.com/.../ and tell them you have a video you'd like to upload via the Secure File Upload, they'll send you the steps.

0 Jacquers 21 days ago in reply to flocsy🤠

Here's the video: https://youtube.com/shorts/CHZdb03gltE?feature=share

Sometime the backlight also comes on without having to scroll through multiple glances and it also doesn't seem to be the correct brightness level. Let's see if Garmin will fix it.

0 flocsy🤠 21 days ago in reply to Jacquers

Ok, I can see it. I wasted lot of time to re-watch the beginning of the video a couple of times because I wasn't able to see anything unusual... util I understood that up to 1:16 everything is OK. Am I right? And from 1:16 - 1:26 we can see the problem. Which is very clear and impossible to not notice it when it happens. Clearly a bug

0 Jacquers 21 days ago in reply to flocsy🤠

Yeah, I just wanted to show the settings, although I could probably have done that after showing the bug.

0 2888126 1 day ago

I just picked up a forerunner 55 yesterday (bone stock, running v11.01) and am having this exact same issue. Showed up after I installed the 11.01 update today.