Galaxy phone owners using wireless controllers in DeX Mode have dealt with a frustrating input failure since last fall: the moment the phone screen timed out, analog sticks and D-pad inputs went dead. Face buttons kept working. Movement didn't.
The Samsung DeX controller bug fixed status is now reported by Android Authority, based on hands-on emulation testing after installing One UI 8.5 alongside the May 2026 security patch. Samsung has issued no changelog entry, root-cause explanation, or formal confirmation. What exists is one publication's hands-on test. That's meaningful, but it's not the same as an official fix.
The bug traced directly to One UI 8, which Samsung shipped last year. Community reports go back to at least late July 2025, and reports confirmed working controller behavior this week, placing the gap from the earliest community thread found to the tested fix at roughly 10 months.
What the One UI 8 regression actually did
The failure was specific enough to be maddening. When a Galaxy phone's screen timed out during a DeX session, wireless gamepads lost directional input entirely, while face buttons, the start button, and select kept working. The controller wasn't disconnecting. Enough inputs stayed live to confirm it was still paired. The analog sticks and D-pad just stopped registering.
That partial failure is what made the bug so disruptive. A fully disconnected controller is at least a clean problem with an obvious fix. This wasn't that. The gamepad appeared functional. Games could receive button presses. But without an analog stick or D-pad input, any game requiring directional control or camera movement was effectively unplayable unless the phone screen stayed permanently on.
A Galaxy S24 5G (Snapdragon) owner documented the same pattern with a Cosmic Byte Stellaris controller in mid-October 2025, noting that the joystick and D-pad went dead the moment the display shut off, while certain buttons stayed active. A separate Samsung Members thread that began July 27, 2025, described the same screen-off controller failure on a Galaxy Z Fold 7, with later replies reporting similar behavior on other Galaxy devices. The regression arrived with One UI 8. That much was unambiguous.
The pattern held across multiple users and at least two different controller types, which pointed toward a software-level input-handling problem in the updated DeX stack rather than a one-off hardware compatibility issue. Samsung debuted an overhauled DeX Mode in One UI 8 last year, built in partnership with Google. Whether the bug lived in Bluetooth input handling, Android power management behavior, or the new DeX architecture itself is something Samsung has never publicly addressed.
How users coped: workarounds that treated the symptom, not the cause
While waiting for a software fix, affected users had two options. Neither addressed the underlying problem.
The most widely used workaround was enabling "Stay awake" in Developer Options, which prevents the phone screen from sleeping while the device is charging. Users were advised to reduce display brightness alongside it to limit burn-in risk. The second option was installing a third-party app like BleKip to keep the phone display continuously active during DeX sessions.
Both approaches amounted to the same thing: stop the phone from reaching the state that triggered the failure. They were functional in a narrow sense, but forcing users to defeat screen-timeout behavior, manage burn-in risk, or install keep-awake utilities just to preserve basic controller functionality in a desktop-mode environment represented a significant usability gap. DeX Mode's value proposition is precisely that a Galaxy phone can function like a desktop machine while the phone itself fades into the background. A bug that requires the phone screen to stay on at all times works directly against that.
When users posted about the issue in the Samsung Members community in October 2025, moderators directed them to file complaints through the Samsung Members app, attach diagnostic logs, and wait for a future update. That fix arrived roughly seven months later. The community feedback almost certainly contributed to getting it resolved, but the timeline reflects how Samsung typically handles software regressions that don't affect core phone functionality.
One UI 8.5 gaming bug fix: what changed in DeX Mode
Testers installed One UI 8.5 alongside the May 2026 security patch and ran emulation sessions with the phone screen off. Controllers functioned correctly throughout. That's the specific condition that had been breaking input since last fall, and it's the only hands-on verification published as of this writing.
The controller fix isn't the only DeX regression One UI 8.5 appears to address. The update also restores the auto-hide taskbar and audio output toggles that went missing from DeX Mode in One UI 8. Two separate quality-of-life features vanishing in One UI 8 and returning in 8.5 suggests the release is doing cleanup work on the broader One UI 8 DeX overhaul. Samsung hasn't framed it that way publicly, but the pattern is there.
What the testing did not cover: cloud gaming apps, non-emulation game categories, or non-gaming controller use in DeX. Users relying on those scenarios should test the update themselves, because Android Authority's verification was specific to emulation. The controller fix may extend further than what was tested, but that hasn't been established.
It's also worth noting what Samsung has not done here. There is no patch note describing this fix, no official support document explaining what changed, and no statement from Samsung confirming that the bug existed or that 8.5 addresses it. The company built a new DeX architecture, shipped a regression in it, and has let user testing and third-party reporting carry the story.
Verifying the fix on your device
The bug had a consistent and reproducible trigger: a wireless controller connected in DeX Mode, phone screen allowed to time out. Galaxy owners who update to One UI 8.5 can test the fix using that same condition. Connect the controller, start a session in DeX, let the phone screen time out normally, then test the analog stick and D-pad response. If both register correctly, the fix is working on that device.
If the problem persists after updating, the workarounds from the previous section still apply in the short term. Filing a report through Samsung Members with a diagnostic log attached remains the recommended path to escalating a persistent issue, based on the guidance moderators gave last October 2025. The community reports that the original bug likely contributed to the fix eventually shipping; the same logic applies to any users still experiencing the issue after 8.5.
What One UI 8.5 signals about Samsung's DeX trajectory
The controller bug was disruptive, but it also revealed something about how Samsung manages DeX as a platform. The overhauled DeX Mode in One UI 8 was a significant architectural shift, built in partnership with Google and pitched as a more capable desktop experience for Galaxy users.
Shipping that overhaul with a regression that broke wireless controller input, and then needing seven months and a separate update to address it, is a reasonable data point for anyone evaluating how quickly Samsung can respond when a feature-level bug affects a specific use case rather than the broader user base.
The return of the auto-hide taskbar and audio output toggles alongside the controller fix is worth noting in that context. These were baseline DeX features that disappeared in One UI 8 and stayed missing until 8.5. Their return in the same update suggests Samsung had a backlog of visible regressions to clear, and that 8.5 is, at least partly, the release that closes that list.
Galaxy owners using wireless controllers in DeX Mode have a tested reason to update. Users running cloud gaming or other controller-dependent workflows in DeX should update and test independently. The workarounds can come down once the fix is confirmed on your device. If the issue persists, report it, because the community thread that kept this bug visible was the same one that gave Samsung's support team something concrete to act on.
Comments
Be the first, drop a comment!