Screen Brightness Stuck or Dims on Its Own?

It is 6 pm and you are walking to a friend's birthday with the transfer app already open. The sun sits low, the gate is close, and you want the money sent before you step inside. Your my phone flares white in the last of the sun, and the amount you typed is gone.

The dusk version hurts too: backlight stuck low at the shop with the sun gone down. You drag the slider up, and it sinks right back down. I am the friend who fixes phones on the couch. I had that on my phone. The fix cost nothing. It started with the governor's name and one battery-saver check.

If the charging sign shows and the percentage falls, that is the battery draining while charging post. If the phone runs hot and the screen dims, that is the overheating post. You came for the stuck slider, or the screen that dims by itself.

Every other fault lives in the Android problems hub.

Why the screen will not hold a level

Five suspects sit behind this fault: adaptive brightness (the governor that reads the light), Extra dim, battery saver, the proximity sensor, and heat. Heat belongs to the overheating post.

The governor is the one doing both jobs. It rides over your slider, or it dims the screen on its own. One suspect, one fix order.

Tecno, Infinix and itel print nothing about this fault. Carlcare, Transsion's service arm, is the only service-side print for these phones. itel's own FAQ is the closest itel publishes.

The ordered fix

Run the checks in order, and stop at the first one that holds the level. The table is the map.

The order is the makers' own, cheap first.

Check	What you do	What it tells you
1. Adaptive brightness	Switch it off, then set the level by hand	The governor was fighting you
2. Extra dim (Pixels and stock Android)	Settings > Accessibility, switch it off	The screen comes back above minimum
3. Battery saver (Galaxy and Motorola)	Check whether battery saver is on	The screen lifts with saver off
4. The light sensor	Clean the sensor, check the case and pockets	Call and pocket dimming stops
5. Update and restart	Download and install, then restart	Samsung prints this step first
6. The reset	Clear Device Health Services storage, if it exists	The governor retrains from zero

The sections walk the table from the top.

Step 1: switch adaptive brightness off

Samsung's US page, read on 12 November 2026, prints the Quick panel route: touch and hold the brightness slider, then tap the switch. The Samsung dimming page prints the Settings path: Settings > Display > Adaptive brightness, tap the switch off.

On a Pixel, adaptive brightness is on by default. Google's Pixel page names the toggle, and lets you change brightness while it is on.

Tecno and Infinix print nothing themselves. Carlcare's Nigeria page, dated 2022-09-17, prints the 'A' button by the brightness slider. It also prints Settings > Display > Adaptive Brightness. It is Carlcare's print, not a Tecno or Infinix page.

For a flicker, itel's FAQ prints its own wording: "You enabled“Automatic brightness”, please disable it." It is the closest itel publishes.

Set the level by hand

Pick a level you can read by, and hold it for days. On Pixel 4 and later, adaptive brightness can briefly push past the normal maximum in direct sun. That boost is printed behaviour, by design.

Hold a manual level and the governor stops helping. Hold it for days, and the governor starts learning.

If the slider feels dead only at the top end, this step is not your fix.

Teach the governor your level

Motorola's Android 14 page prints why the governor recovers. "When you change the brightness slider, your phone learns your preferred levels for various lighting environments." Google prints the same learned behaviour for Pixels.

So hold your level. The governor is not fighting you forever; it is taking notes.

Step 2: Extra dim and the too-dark screen

Google's accessibility help prints Extra dim in one line. "You can dim your screen beyond your phone's minimum brightness so it's more comfortable to read."

Settings > Accessibility > Extra dim switches it off. Pixel 10 and later keep it inside the Quick Settings brightness slider. Pixel 9 and earlier use the Accessibility path. Google scopes those steps to Pixels.

Samsung prints Extra brightness instead. It boosts past the default maximum, and it cannot run with Adaptive brightness on. Tecno, Infinix, itel and Xiaomi publish nothing about Extra dim. Search Settings for "Extra dim"; if it is not there, it is not on your phone.

Step 3: Battery saver and the screen

This claim splits by brand. I will not blur it. Samsung prints the saver line on its dimming page, read on 12 November 2026. The path is Settings > Battery and device care > Battery > Power saving.

In Samsung's own words: "Some power saving modes will make your phone's screen dim in order to save battery life."

Motorola prints the same for its phones: "If Battery saver is on, the screen dims when the battery gets low."

Google publishes no screen-dim line. Its Android battery page prints Dark theme and background limits. Tecno, Infinix and itel publish nothing on the point either.

If the saver drops the screen on those phones, no maker page confirms the cause. The battery drain guide owns the cell side. The screen side is this one's.

Step 4: Dark during calls and in pockets

Samsung prints the proximity sensor first. A case or screen cover can block it. Samsung says to clean it with a dry microfiber cloth.

itel prints the same fault from its side. The sensor works only on the call screen with no headsets connected. Dirt blocks it, and removing the screen protector is the next step.

Carlcare Kenya, page dated 2024-02-17, names the phone in a pocket. Its steps: restart, a soft cloth on the sensor, a case and guard check, then an update.

Step 5: update, then restart

Samsung prints the update step first: Settings > Software update > Download and install. Then restart. Two-finger swipe down, tap the power icon, tap Restart.

Other makers print no universal path. Search Settings for "software update" and take what it offers.

Step 6: reset the governor, if it exists

Motorola prints the reset: Settings > Apps > All apps, tap Show system apps, search for "Device Health Services". Tap Storage & cache, Clear storage, then Reset adaptive brightness.

Nothing confirms this reset exists on HiOS, XOS or itelOS. Search Settings for "Device Health Services" first. I have not run that search on my phone, so treat this step as untested there.

When the slider will not move at all

Samsung prints three steps for a dead slider. Software update, then restart, then Reset all settings under Settings > General Management > Reset.

Reset all settings skips "Security settings, Language settings, Accounts, Personal data, and Settings for downloaded apps". Samsung prints that list with the reset.

Samsung scopes the note to its own phones: the limits of human visual perception. "When you adjust the brightness slider to a high level, you may not observe any noticeable changes in brightness."

If no step moves the slider, the Motorola reset is the next step, only if your phone has Device Health Services.

If it still will not hold a level

Software update, restart, and on a Galaxy the Reset all settings step are the printed endings. itel prints its own pattern, read on 12 November 2026. "After setting auto-brightness, screen shakes when in dark places, but it's normal in bright places."

Its resolution is a software update at the local customer service centre. That is itel's print, not a general fact.

If none of them moves the screen, a repair shop is the honest next step. Carlcare is the after-sales arm for Tecno, Infinix and itel phones. Walk in with the story: when it started, which checks you ran, what each changed. No price prints here, because none was read for this page.

The stop rule

Cool the phone, run the order, and stop at the first check that holds the level. A slider that will not move after update, restart and, on a Galaxy, Reset all settings, is past free checks. Carlcare is the honest next stop for Tecno, Infinix and itel phones.

The rest of the faults wait in our Android problems hub.