Where Does /e/OS Store Launcher and Store Data?
On /e/OS, Bliss Launcher layout and App Lounge cache live in private app data. Backup itself is cloud only.
Last updated
The /e/OS Backup entry is a Seedvault fork that writes to Murena cloud, not to a local file you can copy. Treat it as setup time restore rather than a file path. Restores apply during initial setup only, while media syncs apart through linked storage. There is no local backup file to carry between devices by hand.
Launcher layout and store cache are local. Bliss v3 is a Launcher3 fork under com.android.launcher3; retired v1 used foundation.e.blisslauncher. App Lounge cache clears from system app settings without touching your Murena account. Clear storage for the launcher only to reset layout to defaults, then re add widgets. Check the package name first since v1 and v3 differ.
Where /e/OS stores this, by platform
/data/data/com.android.launcher3
Launcher layout and icon state. v3 uses com.android.launcher3; retired v1 used foundation.e.blisslauncher. Backup itself is Murena cloud, not a local file.
Frequently asked questions
Where is the /e/OS Seedvault backup file?
No local file. Open Settings System Backup on the /e/OS device with a Murena Workspace account. Restores apply during initial setup only. Media syncs separately through eDrive.
How do I reset the Bliss Launcher layout?
Open Settings, Apps, Bliss Launcher, Storage and Clear Storage. Current v3 builds run as com.android.launcher3, older v1 as foundation.e.blisslauncher. Layout resets to default and widgets need re adding.
Notice an outdated path? Let us know.