Skip to content
Theme
OnDevice Tools

AndroidGoogle Pixel

November Pixel update leaves screensavers stuck at full brightness

Pixel owners report that the low-light mode for screensavers stopped dimming after Google's November update, with manual brightness changes only helping temporarily.

Illustration of a Google Pixel phone charging on a bedside table with a bright clock screensaver at night

Key takeaways

  • Pixel users report that screensaver low-light mode stopped dimming after the November update.
  • Manually lowering brightness only helps temporarily, as the screen creeps back up.
  • The issue appears on Reddit and the Google Support forum but does not seem widespread.
  • Google has not yet confirmed the problem or announced a fix.
In this article
  1. Screensavers no longer dim at night
  2. How the feature is meant to work
  3. Manual brightness fixes do not last
  4. How widespread is the problem
  5. What Pixel owners can do now

Screensavers no longer dim at night

Google's November update for Pixel phones appears to have broken the low-light mode for screensavers, according to Android Authority. Several Pixel owners say their screensavers stay unusually bright while the phone charges overnight, instead of dimming to suit dark surroundings.

The complaints have appeared on Reddit and the Google Support forum. Most affected users say the feature worked correctly before they installed the November update.

How the feature is meant to work

Illustration: bulb, settings, Pixel logo, update and the labels November Update, Screensaver, Android

The screensaver option lives under Settings, then Display & touch, then Screen saver. It shows a built-in screensaver while the device charges, and can be limited to charging only, charging while upright, or wireless charging only.

A low-light mode adjusts the screensaver to the lighting around the phone. Many people use a Pixel as a bedside clock, so the feature keeps the screen from lighting up a dark bedroom. That is the behaviour that now seems faulty.

Manual brightness fixes do not last

Affected users report that lowering the brightness by hand does not solve the problem. The screen slowly creeps back up to a brighter level, which makes the manual workaround ineffective.

One user also said their clock screensaver looked functionally different after the update, alongside being too bright. Android Authority notes that other users have not confirmed that design change, but the repeated reports about dimming suggest something is genuinely wrong.

How widespread is the problem

Based on the number of reports so far, Android Authority says the issue does not appear to be widespread. It is not isolated either, and it can disturb sleep for anyone who charges a Pixel beside the bed.

The publication has contacted Google to ask whether it knows about the problem and whether a fix is planned. There is no confirmed fix at this time, and no official statement from the company yet.

What Pixel owners can do now

There is no verified workaround in the reports beyond lowering brightness manually, which users say only helps for a while. Anyone affected can add their experience to the Google Support forum thread, which may help Google confirm the bug.

The screensaver problem is one of several issues attributed to the November update in user reports. Until Google responds, affected owners may prefer to disable the screensaver or turn the phone face down at night.

Sources

  1. Google’s November Pixel update is leaving screensavers stuck at full brightnessAndroid Authority

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.