help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Charge screen goes to max brightness on tap

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎03-30-2023 02:48

‎03-30-2023 02:48

After the recent updates, my device goes to max brightness whenever I tap on it to wake it up. 

 

I have my always on display enabled.

 

I’m currently on 3.78 app version and on the latest software update for the tracker. 

Best Answer
0 Votes
2 REPLIES 2

‎03-30-2023 03:03

‎03-30-2023 03:03

Welcome to the Fitbit community, @sparsh33!

Please check the display brightness setting of your Charge 5. To do so, swipe down from the device's clock face then scroll to the Settings icon and tap on that. Next tap Display Settings.
Now tap the Brightness icon to cycle through Dim, Normal, and Max settings and choose whatever brightness level you prefer.

Stefan
Charge, Charge HR, Blaze, Versa, Versa 2, Charge 5, Charge 6, Versa 4, Aria, Aria 2, Pixel 4a, Pixel 7
Best Answer
0 Votes

‎07-19-2023 08:52

In response to Talahthas

‎07-19-2023 08:52

My Charge 5 started having the same issue about a week ago and modifying the Brightness settings does nothing. This is obviously a firmware bug.

Best Answer