Samsung has published its One UI 9 Good Lock compatibility list, and the 16-to-8 split in favor of working modules obscures what actually matters. The eight modules confirmed incompatible with the One UI 9 beta govern the home screen, lock screen, navigation bar, quick settings, and notifications, surfaces that Good Lock users are most likely to have customized.
Samsung says it is working to restore compatibility for all eight affected modules before One UI 9 reaches stable release. No date is attached to that commitment.
The beta opened last week for Galaxy S26 series owners in Germany, India, South Korea, Poland, the UK, and the US, with enrollment through the Samsung Members app, Samsung Newsroom confirmed. One UI 9 is built on Android 17, and promises expanded creative tools, customization options, a more accessible mobile experience, and stronger security protections. The customization pitch makes the timing of these Good Lock gaps notable for users who depend on that layer.
Why Good Lock breaks during major beta cycles
Good Lock modules don't sit loosely on top of One UI. They integrate directly with the OS's core layers, which is what makes their depth of customization possible, and any major OS update can invalidate those connections. The tradeoff is structural: the tighter the integration, the more fragile it becomes when the underlying system changes.
This isn't the first time the pattern has played out. During the One UI 8.5 beta, Home Up and QuickStar failed to open entirely on Galaxy S25 hardware, while LockStar and NotiStar lost partial functionality, Android Police confirmed at the time. All four of those modules are now fully unsupported on One UI 9 beta, joined by four additional ones. The Good Lock ecosystem has historically lagged behind major Android and One UI transitions, a pattern that predates both of these beta cycles.
There's a useful distinction buried in that history. During the One UI 8.5 beta, "not working" meant different things for different modules: Home Up and QuickStar failed to open entirely, while LockStar and NotiStar were only partially supported, meaning some features functioned, and others didn't. Samsung's current One UI 9 compatibility disclosure uses the blanket label "incompatible" without specifying which modules crash on launch versus which lose only specific features. The practical severity of the current gaps isn't fully documented yet.
Good Lock modules compatible with One UI 9: what works and what doesn't
The 8 non-compatible modules
The modules reportedly not working on One UI 9 beta are ClockFace, Game Booster+, Home Up, LockStar, MultiStar, NavStar, NotiStar, and QuickStar.
Five of those cover the most frequently touched surfaces of the phone. Home Up customizes home screen layout, LockStar manages lock screen appearance, NotiStar controls how notifications are displayed, NavStar modifies the navigation bar, and QuickStar reshapes the quick settings panel. These are the modules that "modify the core layers of One UI." Users who rely on any of these five will notice the gap immediately after installing the beta.
The remaining three affect narrower use cases. ClockFace handles always-on display and lock screen clock styles; MultiStar extends multi-window functionality for DeX and split-screen power users; Game Booster+ provides in-game performance controls and overlays. Users who don't regularly reach for those tools are unlikely to notice their absence during the beta period.
The 16 confirmed-compatible modules
The Good Lock modules confirmed working on One UI 9 are Camera Assistant, Display Assistant, Sound Assistant, Theme Park, One Hand Operation+, RegiStar, Wonderland, Edge Lighting+, Edge Touch, Routine+, Keys Cafe, Nice Catch, Nice Shot, Gallery Assistant, Galaxy To Share, and Dropship.
The compatible set includes several of the platform's most frequently used customization tools. Camera controls, audio settings, edge panels, themes, and Routine+ automation are all covered. That's a meaningful working core, even with eight modules missing.
It's also worth noting what this split reflects structurally. The 16 working modules tend to be those that extend or enhance specific features, such as camera behavior or sound output, without deeply modifying how the OS presents its fundamental navigation surfaces. The eight that are broken are almost uniformly the ones that rewrite those surfaces. The distinction lines up with how tightly each module is coupled to the OS architecture that One UI 9 has changed.
What Samsung's fix timeline means in practice
Samsung says it is actively working to make all eight incompatible modules functional, with the goal of full compatibility before stable release. The Good Lock team reiterated that goal in a Samsung Community update posted after the beta program opened on May 13.
No date is attached to that goal, and the sources do not report a stable One UI 9 release date. The historical precedent from One UI 8.5 offers the only concrete reference point: fixing broken modules during a beta cycle could take days to weeks. That was a different beta under different circumstances, but it's the closest comparison available.
Two questions remain unanswered in the current reporting: when exactly the fixes will arrive during the beta phase, and whether any unsupported module could affect or reset configurations users have already saved. Neither Samsung's statement nor the available coverage addresses those points. What Samsung has confirmed is that this is a temporary beta-phase limitation, not a signal that Good Lock compatibility is being dropped from One UI going forward.
One additional note on historical context: the One UI 8.5 beta cycle was reportedly one of the rougher ones for Good Lock support. A Samsung Community post from that period described it as unusual when all modules were eventually functional, with users praising the coordination between the Samsung and Good Lock teams. One UI 9 is starting from a more disrupted baseline.
Impact for S26 beta users
For Galaxy S26 owners in the six beta markets, the current situation breaks down along predictable lines. Users whose Good Lock setup centers on camera controls, audio, edge panels, themes, or Routine+ automation are largely unaffected. The 16 supported modules cover those workflows, and the beta transition should be comparatively smooth.
Users who rely on Home Up, LockStar, NotiStar, NavStar, or QuickStar face a different picture. These five tools cover the surfaces most people interact with constantly. Installing the beta means losing access to whichever of those modules are part of a current setup, for however long the fixes take to arrive.
For anyone outside the six beta markets or on hardware other than the Galaxy S26 series, the beta is not currently available. Samsung's stated goal is full compatibility before stable release, which means the situation described here may be resolved before One UI 9 reaches a broader audience. Whether fixes arrive early in the beta cycle or closer to launch is the open question as testing continues.
Comments
Be the first, drop a comment!