• For your own safety, you must remove all overlays before performing any kind of software\firmware upgrade (device OTA, ROM flash, etc) as you can boot to an unusable system if you don’t uninstall all overlays first.

• If you forgot to remove overlays before updating your device, then use the Rescue scripts found here. Keep ADB always enabled to be able to use the script even when the device is unresponsive, or if SystemUI is crashing.

• Due to Samsung restrictions, Samsung Music and Samsung Voice Recorder overlays won’t be enabled on their own. After you install the overlays and reboot, you will just need to run the enable script from your desktop or laptop to make it work correctly. You will only need to do this once, if you then keep the overlay installed. Please read the readme file to know how to run the script. Enable scripts can be found here.

Before you begin installing the overlays, make sure that you are using the default Samsung Theme. You can check this from the Samsung Theme Store app. Having a Samsung Theme set will cause issues and you will have wrong colors on the overlays. More on the matter below.

• Please avoid using the installer in conjunction with: Samsung Themes, Max Power Saving Mode and Substratum. Using these can cause issues and conflicts, resulting in apps getting different colors (dark grey, bright green and orange) compared to the one you chose in the personalization tab; it can also result to apps getting unthemed.

- Max Power Saving Mode, specifically, will disable all your installed overlays, and some can stay disabled even after you turn it off.

- This can usually be corrected by removing all overlays - you can use the Rescue scripts found here - then rebooting, and reinstalling every overlay from the installer again.

- Make sure that your Samsung Theme is kept at default, and that all Substratum overlays were removed before performing the installation procedure with Swift Installer. A quick way to clean up all the installed overlays from your device are the Rescue scripts found here.

• Swift Installer 6.0 now supports AOSP Oreo and Pie, and OOS Oreo and Pie. It requires ROOT to work on those systems, it won’t work without it. It keeps working with Samsung Oreo with and without root.

• While on Oreo you can use the rescue script found in the previous info entry, for Pie you will need to flash a rescue zip in TWRP. You can find it here.

• Pie Magisk modules users: as you may know some modules can cause a conflict with the overlays and disable them after a reboot. You can now solve this by using the Installer with its Magisk module too. You can find the module here or in the “Downloads” section in Magisk Manager, and the Installer will install overlays systemlessly with it.

When you swap to module mode, the Installer will attempt to convert all your current overlays to the systemless method. This conversion may fail if you currently have modules that are conflicting enabled, and the overlays will simply end up removed. Nothing to worry about - just reboot, reinstall all the overlays (it's super quick on Pie!), reboot again and you're good to go.

Alternative scenario: the conversion fails and the overlays in system don’t end up removed either; you need to simply open up the Installer, select all in the Active tab, and Update tab, uninstall all the overlays and reboot. You also can, as another option, flash the Pie TWRP rescue zip you find up here. After this is done and you boot back, and making sure the module is enabled, you can simply reinstall everything, reboot, and done.

Bonus for the Magisk module mode: if you need to disable all overlays for any reason, you can simply disable the module from Magisk Manager and reboot - overlays are gone!

• The Magisk Module 1.1 update allows for Gboard theming on both Android Oreo and Pie. When the module is installed, the Installer is able to create a custom Gboard theme, using your picked accent and background colors, to be selected inside of Gboard’s Settings>Theme option, under the System category.

Credit to @RKBDI ( for the find of MIUI-theme-based Gboard System theming via Magisk, and for his commented Gboard style sheets templates that made this possible.

• To make sure the theme works fine on OxygenOS, you MUST enable the native OxygenOS dark theme. You can do so from Settings > Display > Theme, and pick dark.

• Important notice about the System accent in OxygenOS: when you change the accent color in the Personalize tab and update the Android System overlay, the OxygenOS ROM will still keep the old SystemUI accent cached, and keep doing so even after a reboot. The way to make it update is: go to Settings > Display > Accent color; pick any random color (bonus: the bottom right accent will be changed to white, and you can pick it and keep it for Settings and SystemUI), apply it, then tap on Accent color again and pick the top left accent, which will be actually changed to the color you’ve selected in the Personalize tab of the Installer.

• The base of the overlays is currently a dark theme! White or any too light background can’t be input in the personalization tab, because it would end up making all the foreground elements, which are themed to be white or light grey, to get barely visible or invisible.

• Any too dark, or too light (including pure white) accent, can’t be input in the personalization tab. Explanations below:

- It can’t be too dark because the accent ends up being the foreground text color or icon tint color in many cases, and it would become barely visible or invisible.

- It can’t be too light because the accent color ends up being the background to foreground elements (both texts and icons) that are white or light grey, and it would render them barely visible or invisible.

• Beta versions of the apps and beta software are NOT supported. Please avoid reporting issues when using any betas. The overlays are based on stable releases and it is only expectable to have issues when trying to apply the theme on beta software. This is however different for apps that have a separate release channel for betas and for which we provide an overlay, which are for example Chrome Beta and Samsung Internet Beta. The fact those apps have overlays does NOT make a rule about beta apps being supported. The fact a beta version may work or may have worked before it got an update does NOT make a rule about beta apps being supported.

• Important: Refund window is 48 hours after the purchase is made, in line with Google Play’s refund policies for apps. Requests coming after the 48 hours window is expired cannot be processed.

• Please note: if you use Google Maps with Android Auto, it is advised to uninstall the Maps overlay before\when doing so. There are issues with Android Auto that can’t be fixed within the Maps overlay, and it’s better to remove the overlay when you will rely on it for navigation. The Maps app is very unfriendly to be themed, in the way it is coded, which leads to such problems.

Full changelogs are available in the app, from the 3-dot menu!