Android Police writer replicates Pixel charging screensaver on Galaxy Z Fold 8
Using Samsung's Modes and Routines, a power user bridges the feature gap between Google and Samsung hardware.
A transition from Google to Samsung hardware often reveals small but irritating feature gaps. For one Android Police writer who recently switched from a Pixel 10 Pro to a Samsung Galaxy Z Fold 8, the most glaring omission was the Pixel's dedicated charging screensaver.
To solve this, the author utilized Samsung's "Modes and Routines" system to build a custom automation. By setting a trigger for "Charging status"—which applies to both wired and wireless charging—the routine automatically enables the device's Always-on Display (AOD) whenever the phone is plugged in. "I missed the screen that pops up every time I charged my phone," the writer noted. "But I did. So I remade it on my new Galaxy Z Fold 8."
The Pixel Advantage
Google Pixel devices include a specialized charging screensaver that integrates weather information and a dim clock optimized for low-light environments. While Samsung devices offer their own screensaver options, such as displaying personal photos or smart home controls, they lack the specific weather and clock integration found in Google's implementation. This creates a distinct difference in how the devices function as bedside clocks or desk accessories during a charge cycle.
Bridging the OEM Gap
This workaround highlights the utility of built-in automation tools for power users moving between different Android original equipment manufacturers (OEMs). By leveraging "if this, then that" logic, users can simulate missing behaviors to maintain a consistent workflow. However, the project also illustrates the limits of such tools; while the AOD can be triggered, the deep system integration of the Pixel's weather screen remains difficult to replicate without relying on paid third-party applications.
Remaining Hurdles
Despite the success of the routine, the implementation is not flawless. According to Android Police, the custom automation can be occasionally unreliable because "Do Not Disturb" mode has the power to overwrite the Always-on display settings. Users attempting a similar setup should monitor how their system-level focus modes interact with their custom routines to ensure the display remains active as intended.