Where Does Kvaesitso Store Backups and Data?
Kvaesitso backs settings to user-chosen files with version-matched restores on Android. Widgets and PWAs need separate re-setup.
Last updated
Kvaesitso backup works with strict rules. Settings export to user-chosen files and restore cleanly into the identical version. Cross-version restores crash or silently drop pieces, with widgets and PWA launchers as the consistent casualties.
The package ID de.mm20.launcher2.release anchors the private tree glimpsed in crash logs. F-Droid, GitHub and Play flavors share the flow with signing quirks between stores. Match versions exactly and rebuild widgets after.
Where Kvaesitso stores this, by platform
/data/data/de.mm20.launcher2.release
Private storage under the verified launcher package with a files child seen in crash traces. Root needed to browse. Settings backup files remain the supported transfer with version matching mandatory.
Frequently asked questions
How do I move Kvaesitso to a new phone?
Use Settings Backup and restore to write a file, then restore into the identical version. Cross-version restores crash or drop widgets and PWA launchers, per tracked issues. Graphics settings return while widgets need manual rebuild.
Why are my widgets missing after restore?
They do not transfer. Restore brings graphics and configs while widgets, widget settings and PWA or website launchers stay behind across every tested version. Re-add those by hand after restoring on the matching build.
Where is the Kvaesitso data folder?
It names private storage under the verified de.mm20 package with a files subfolder seen in crash traces. Root is needed to browse. Backup files remain the supported path rather than direct copies.
Notice an outdated path? Let us know.