How to Fix the One UI 8.5 Dark Mode Issue on Galaxy Phones

Samsung's One UI 8.5 has a dark mode problem: the deep AMOLED blacks that Galaxy users expect have been replaced by washed-out grey across the system UI, phone dialer, and Google apps. A workaround exists, Samsung support has confirmed it helps, and a support representative suggested a future update may provide an official fix, though that is not a confirmed roadmap commitment.

The One UI 8.5 dark mode issue was visible before the stable release shipped. A notification-panel visual bug was spotted during Beta 6 in late February and was still present in Beta 10 in April, TechCabal reported. Whether the broader grey-across-the-UI problem in the stable build is the same underlying issue is plausible but not confirmed by available reporting. What is clear: it shipped, and users noticed quickly.

Two separate dark mode complaints

Not all One UI 8.5 dark mode reports describe the same problem. It's worth separating them.

The first, and more widely reported, issue is that dark mode surfaces look lighter than expected throughout the OS: the phone dialer, system UI, and Google apps all display a grey tone where true AMOLED black would appear in earlier builds. This is the issue the Color Palette workaround addresses, at least partially.

The second is a scheduling problem. In a Samsung Community US forum, an S25 Edge user in the UK reported that the Sunrise to Sunset dark mode setting activates in the evening but fails to trigger in the morning. At least one US-based user confirmed the same behavior in the thread. Color Palette does not address this; it appears to be a different bug with a different root cause.

What users are seeing

The symptom is consistent across complaint threads: dark mode in One UI 8.5 looks noticeably lighter than it did in previous versions, and on OLED screens the difference is hard to miss.

An early Samsung Members bug report describes the phone dialer using a mid-grey background where AMOLED black should appear, with Google apps looking "very grey" without Color Palette enabled. Users in the Samsung Members India forum recently described the same shift across the full system UI, with screenshots posted that they say show a darker appearance on One UI 8 compared to One UI 8.5.

TechCabal characterized the beta-era notification-panel version as "a cosmetic issue rather than a functional one," but the scope users are describing in current forum threads is broader: dialer, full system UI, and third-party Google apps.

On OLED panels, true black means pixels switch off entirely and consume no power. Grey pixels do. Samsung has not quantified any battery impact from this specific change.

How to fix the One UI 8.5 dark mode issue for now

The most reliable workaround currently available is enabling Color Palette, found under Settings > Wallpaper and style > Color palette.

Users in the Samsung Members bug thread independently discovered that turning it on pushes dark surfaces back toward deeper tones across the system UI and Google apps. A Samsung support representative confirmed the behavior directly: "enabling the Color Palette does adjust the background to a darker tone." The same representative acknowledged that users should not need this extra step, and said, "Hopefully, a future update will provide an official fix" framing it as a workaround, not the intended behavior.

The fix is partial. The user who surfaced it asked Samsung to "fix it for the default setup," suggesting Color Palette reduces the grey cast but does not fully restore AMOLED black.

Which devices are affected

The clearest evidence is concentrated on S25-series hardware, but the full scope has not been systematically established.

Detailed bug reports come primarily from S25 users across multiple regions. One commenter in the Samsung Members bug thread said the issue may be specific to the S25 because "S26 doesn't have this issue" — a single anecdotal observation, not a verified finding.

Users in the Samsung Members India forum claim the problem affects everyone running One UI 8.5, regardless of device. However, it's not a documented finding. Samsung's stable One UI 8.5 rollout covers the Galaxy S25 series, S24 series, Z Fold 7, Z Flip 7, Z Fold 6, Z Flip 6, and Galaxy Tab S10 and S11, per TechCabal, meaning those are the devices capable of being affected, not necessarily confirmation that all of them are.

The safest read: confirmed on S25-series hardware across forums in India, the US, and the UK; broader impact on other One UI 8.5 devices is plausible but undocumented. Any Galaxy device with an OLED panel is where the difference would be most perceptible; on LCD panels, the shift from black to dark grey is harder to detect.

Samsung's response so far

Samsung has not publicly named or confirmed the grey dark mode as a known bug. Support responses offer limited confirmation.

In the India forum thread, support asked the reporting user to submit log files, screenshots, and video to "investigate further and resolve this issue." The earlier bug thread received a more direct response, with the support representative confirming Color Palette's effect and pointing toward a future update.

Samsung has already shown it can ship targeted fixes for One UI 8.5 without a full firmware release. It patched a confirmed Voice Recorder crash through the Galaxy Store after launch, TechCabal reported earlier this month. That mechanism exists for the dark mode issue too, though Samsung has not committed to that path.

Filing a bug report

If Color Palette does not sufficiently improve the display, filing a detailed report through Samsung Members gives Samsung more device-specific data to work with.

Samsung's own guidance specifies submitting the error report within three minutes of encountering the bug. Keep the Samsung Members app open until you receive confirmation the report has been sent, which can take up to five minutes, and closing the app early may leave log data incomplete.

The beta-era evidence adds some context here. The notification-panel visual anomaly survived from Beta 6 in late February through Beta 10 in April without being resolved, which indicates this wasn't introduced at the last minute. Whether that history makes a quick patch more or less likely is unclear, but more detailed reports from more devices would at minimum help Samsung understand the actual scope.