Set a higher quota for app backups

[John-Rodriguez-Git]

Im a heavy cromite user and a tab junkie/messie and have over 3GB User Data. I backup to my 512GB nvme and would want to set a higher quota.
Why was
03d2946
done?

Linking to #183 and #231 as the described solution to increase the quota is not available anymore since that commit.

[grote]

I don't think we should bring back the option to manually set the quota. Instead, we could bump the quota to a higher value, 5 GB maybe.

[oxalica]

I updated my phone system from LineageOS 21.0 to 22.1 (major update) yesterday and did a storage reset for clean installation. It turns out some of my apps failed to restore due to "quote exceeded".
The most painful one is fcitx5-android, the Chinese input method which contains my own manually-trained dictionary. It is 53MB in the backup but failed to restore due to quota issue. I guess I turned on "unlimited quota" on backup, but now that option is gone from expert mode. How can I restore my own existing data now?

[oxalica]

This ticket is unrelated to restore. If restore failed due to quota exceeded, then you did the backup with an old version and limited quota. The current quota of the recent version can handle 53MB just fine.

Okay maybe I misunderstood the issue. I'm on seedvault 15-5.2 which should contain the 1GB default change mentioned in the issue description. But in "Restore backup" I click the 2 days ago backup, and Fcitx5 shows "Last backup: December 10, 2024 (52MB)". When I select it and click "Restore backup", then it shows "Quota exceeded". Do you mean the first information is incorrect and the app is not actually backed up to my remote storage? This is also misleading to me...

[grote]

But in "Restore backup" I click the 2 days ago backup, and Fcitx5 shows "Last backup: December 10, 2024 (52MB)". When I select it and click "Restore backup", then it shows "Quota exceeded".

So the backup you did on December 10 most likely had a quota limit of 50 MB. Please do a new backup of this app with 5.2 and if that doesn't work for some reason, please open a new ticket with a log.

Is there a reason for why you wouldn't want to bring it back? Shouldn't the power be held by the user?

The UX philosophy of Seedvault is not to introduce an endless number of little toggles to modify its behavior in all details, but to function in a way that works well for the majority of users. Also see #822 (comment)