blob_db: shrink growable settings files on existing devices [FIRM-1893] - #1279
Merged
Merged
Conversation
gmarull
approved these changes
May 13, 2026
Signed-off-by: Joshua Jun <lets@throw.rocks>
Signed-off-by: Joshua Jun <lets@throw.rocks>
Signed-off-by: Joshua Jun <lets@throw.rocks>
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The growable-settings-file change only shrinks newly-created files, so devices that shipped before it keep their full-size allocation indefinitely, which on devices with many installed apps shows up as launcher scroll lag. This adds *_compact() APIs on every settings-file-backed blob DB plus an aggregate blob_db_compact_growable_dbs() helper, runs it once at boot via a
settingsDbsCompactedV1shell pref gate, and exposes a Settings -> System -> Debug -> Compact Settings DBs entry to trigger it on demand.