There is a possibility that incompatible APK splits make a an app crash when starting after re-installing it.
With that config option each OEM can decide with they want to take this risk or not.
that tries to figure out compatibility only based on the name of the split.
This is not an exact science and there might be errors, but we hope to correctly identify most cases that matter in practice.
We are re-installing system apps if they are present on the restore device as a system app and have a newer version code.
Before, when one of those conditions is not true, we were showing a failure and gave the user the option to re-install the app from an app store.
Now, we don't offer the manual re-install option anymore and only show a success when a newer or same version of the system app is already installed.
When an app fails to install during restore, we offer the option to manually install it.
If this doesn't happen with the same app store,
it is likely that the installed app will have a different signature (e.g. Aurora vs. F-Droid).
If the signature doesn't match, the data restore will fail.
Therefore, we attempt to let the user only use the same store for re-install.
There's a known issue that F-Droid doesn't report the proper package name:
https://gitlab.com/fdroid/fdroidclient/-/issues/2085
When one or more apps fail to install, the user is shown a dialog explaining that we need the apps installed in order for restore to work.
After the dialog is dismissed, the list of apps is resorted so failed apps are at the top. They are made clickable and the user is brought to an app store to re-install them.
Otherwise gradle pulls in newer versions of some libraries that require
a newer Kotlin version at runtime and then make the app crash.
This also moves the dependency declarations into a dedicated file.
Updated by "Cleanup translation files" hook in Weblate.
Translated using Weblate (Portuguese (Brazil))
Currently translated at 100.0% (108 of 108 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 79.6% (86 of 108 strings)
Translated using Weblate (Spanish)
Currently translated at 99.0% (107 of 108 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 72.2% (78 of 108 strings)
Translated using Weblate (Russian)
Currently translated at 100.0% (108 of 108 strings)
Translated using Weblate (Chinese (Simplified))
Currently translated at 14.8% (16 of 108 strings)
Translated using Weblate (Norwegian Bokmål)
Currently translated at 94.4% (102 of 108 strings)
Translated using Weblate (Russian)
Currently translated at 7.4% (8 of 108 strings)
Translated using Weblate (Russian)
Currently translated at 6.4% (7 of 108 strings)
Translated using Weblate (Chinese (Simplified))
Currently translated at 3.7% (4 of 108 strings)
Translated using Weblate (German)
Currently translated at 70.3% (76 of 108 strings)
Translated using Weblate (Icelandic)
Currently translated at 100.0% (108 of 108 strings)
Translated using Weblate (Spanish (American))
Currently translated at 97.2% (105 of 108 strings)
Translated using Weblate (Spanish)
Currently translated at 34.2% (37 of 108 strings)
Translated using Weblate (Italian)
Currently translated at 60.1% (65 of 108 strings)
Translated using Weblate (Italian)
Currently translated at 38.8% (42 of 108 strings)
Translated using Weblate (Norwegian Bokmål)
Currently translated at 94.4% (102 of 108 strings)
Translated using Weblate (German)
Currently translated at 10.1% (11 of 108 strings)
Translated using Weblate (French)
Currently translated at 100.0% (108 of 108 strings)
Translated using Weblate (French)
Currently translated at 65.7% (71 of 108 strings)
Added translation using Weblate (Dutch)
Added translation using Weblate (Zulu)
Added translation using Weblate (Chinese (Traditional, Hong Kong))
Added translation using Weblate (Chinese (Traditional))
Added translation using Weblate (Chinese (Simplified))
Added translation using Weblate (Vietnamese)
Added translation using Weblate (Uzbek)
Added translation using Weblate (Urdu)
Added translation using Weblate (Ukrainian)
Added translation using Weblate (Turkish)
Added translation using Weblate (Tagalog)
Added translation using Weblate (Thai)
Added translation using Weblate (Telugu)
Added translation using Weblate (Tamil)
Added translation using Weblate (Swahili)
Added translation using Weblate (Swedish)
Added translation using Weblate (Serbian (latin))
Added translation using Weblate (Serbian)
Added translation using Weblate (Albanian)
Added translation using Weblate (Slovenian)
Added translation using Weblate (Slovak)
Added translation using Weblate (Sinhala)
Added translation using Weblate (Romanian)
Added translation using Weblate (Portuguese (Portugal))
Added translation using Weblate (Portuguese (Brazil))
Added translation using Weblate (Portuguese)
Added translation using Weblate (Polish)
Added translation using Weblate (Punjabi)
Added translation using Weblate (Odia)
Added translation using Weblate (Nepali)
Added translation using Weblate (Burmese)
Added translation using Weblate (Malay)
Added translation using Weblate (Marathi)
Added translation using Weblate (Mongolian)
Added translation using Weblate (Malayalam)
Added translation using Weblate (Macedonian)
Added translation using Weblate (Latvian)
Added translation using Weblate (Lithuanian)
Added translation using Weblate (Lao)
Added translation using Weblate (Kyrgyz)
Added translation using Weblate (Korean)
Added translation using Weblate (Kannada)
Added translation using Weblate (Central Khmer)
Added translation using Weblate (Kazakh)
Added translation using Weblate (Georgian)
Added translation using Weblate (Japanese)
Added translation using Weblate (Icelandic)
Added translation using Weblate (Indonesian)
Added translation using Weblate (Armenian)
Added translation using Weblate (Hungarian)
Added translation using Weblate (Croatian)
Added translation using Weblate (Galician)
Added translation using Weblate (French (Canada))
Added translation using Weblate (Finnish)
Added translation using Weblate (Persian)
Added translation using Weblate (Basque)
Added translation using Weblate (Estonian)
Added translation using Weblate (English (India))
Added translation using Weblate (English (United Kingdom))
Added translation using Weblate (English (Canada))
Added translation using Weblate (English (Australia))
Added translation using Weblate (Danish)
Added translation using Weblate (Czech)
Added translation using Weblate (Catalan)
Added translation using Weblate (Bosnian)
Added translation using Weblate (Bengali)
Added translation using Weblate (Bulgarian)
Added translation using Weblate (Belarusian)
Added translation using Weblate (Azerbaijani)
Added translation using Weblate (Assamese)
Added translation using Weblate (Amharic)
Added translation using Weblate (Afrikaans)
Added translation using Weblate (Spanish (American))
Added translation using Weblate (Spanish)
Added translation using Weblate (Arabic)
Added translation using Weblate (Italian)
Added translation using Weblate (Hebrew)
Added translation using Weblate (Norwegian Bokmål)
Added translation using Weblate (Hindi)
Added translation using Weblate (Russian)
Added translation using Weblate (German)
Added translation using Weblate (Gujarati)
Added translation using Weblate (French)
Translated using Weblate (Greek)
Currently translated at 29.6% (32 of 108 strings)
Added translation using Weblate (Greek)
Co-authored-by: Adolfo Jayme Barrientos <fitojb@ubuntu.com>
Co-authored-by: Allan Nordhøy <epost@anotheragency.no>
Co-authored-by: Catherine Pierattini <catherine.pierattini@gmail.com>
Co-authored-by: CatieC <catie@calyxinstitute.org>
Co-authored-by: Chirayu Desai <chirayudesai1@gmail.com>
Co-authored-by: Daniel <dan.ef1999@gmail.com>
Co-authored-by: H <joaquinfc@protonmail.com>
Co-authored-by: Hosted Weblate <hosted@weblate.org>
Co-authored-by: J. Lavoie <j.lavoie@net-c.ca>
Co-authored-by: Meili Huang <meilihuang1216@gmail.com>
Co-authored-by: Michael Bestas <mkbestas@gmail.com>
Co-authored-by: Mordur Aslaugarson <mordur@1984.is>
Co-authored-by: Nikita Epifanov <nikgreens@protonmail.com>
Co-authored-by: Robin Kunze <robinkunze@outlook.com>
Co-authored-by: Samuel Carvalho de Araújo <samuelnegro12345@gmail.com>
Co-authored-by: Santiago Cruz <scruz4@tuta.io>
Co-authored-by: Weblate <noreply@weblate.org>
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/de/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/el/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/es/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/es_US/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/fr/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/is/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/it/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/nb_NO/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/pt_BR/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/ru/
Translate-URL: https://hosted.weblate.org/projects/calyxos/seedvault/zh_Hans/
Translation: CalyxOS/Seedvault
Outside of SetupWizard restore, we don't offer to set up an account,
because we don't know if one already exists and the app was locked with
a passcode.
Apps that have FLAG_STOPPED will not get backed up, just like apps
without flag ALLOW_BACKUP will not get backed up.
In the UI both cases are shown the same way: app does not allow backup
This can be confusing for the user as it is not true for stopped apps.
Therefore, this commit introduces a new stopped state for apps,
so we can differentiate between both cases.
* Add Android.bp to compile using AOSP build system instead of gradle
* Add prebuilt external libs that are not available on AOSP
Fixes#97
Co-authored-by: Chirayu Desai <chirayudesai1@gmail.com>
* All previous aar versions have their modified date set to 0 which trigger
the following openjdk bug:
https://bugs.openjdk.java.net/browse/JDK-8184940
This fixes the following compilation error while building in AOSP environment:
java.time.DateTimeException: Invalid value for MonthOfYear (valid values 1 - 12): 0
The system triggers backup jobs periodically or when a package is
announcing that its data has changed. So far we were not showing
notifications for those. This commit shows a notification with an
indeterminate progress bar as we don't have any information about how
many packages will get backed up.
It turned out that call log backup is already in AOSP, but it is
disabled by an undocumented flag. This commit sets this flag (for new
and existing installs) to enable call log backup.
This commit makes creating new RestoreSets explicit.
Initializing a backup transport now actually cleans its data as the AOSP
documentation demands. This should be fine as we usually do a fresh
backup after a new initialization.
Contrary to before, an initialization does not create new RestoreSets
anymore, but works within the existing set. For now, only manually
choosing a new storage location creates a new RestoreSet.
Fine-grained progress reporting causes apps to show up twice which is
confusing. Also @pm@ metadata and opt-out APKs are too much detail for
normal users. So we decided to only show a percentage in the progress
notification.
When the backup finished, the app now shows "x of n apps backed up"
which is more positive when the previous negative message of how many
apps were not backed up.
Some further minor tweets were done to app counting to report proper
totals.
This adds @pm@ record backup and APK backup of opt-out apps to the
progress reporting since these two operations are slow when using a
cloud storage SAF backend.
Loading cursors can happen with cloud-based documents providers
such as Nextcloud.
When they return a cursor that is still loading,
we might continue with stale information.
So now we wait for a loading cursor to be fully loaded
before continuing.
This restores only the @pm@ keys that are really needed
and thus speeds up installation with auto restore considerably
when using cloud storage such as NextCloud for example.
@stevesoltys this removes your old way of retreiving installed packages
via getInstalledPackages(0, UserHandle.USER_SYSTEM) as I couldn't find a
difference to the official way.
Also IGNORED_PACKAGES isn't needed anymore since
filterAppsEligibleForBackupForUser() already filters those out.
This should also affect apps that have other errors during the backup
process, but it does not affect apps that opt-out of backup completely.
First part of #65
Apps that have nothing to back up start a backup but then get a call to cancelFullBackup()
and never even call finishBackup().
Do not write metadata for such apps, the call got moved to finishBackup().
These might return outdated or now content when queried,
then check their cloud storage and report back with up-to-date content.
We now detect this (when looking for backups on newly setup storage)
and wait until the content has been loaded before acting on the
response.
This is affecting and was tested with NextCloud.
as storage location.
The backup backoff time is not reliable for this as the system still
attempts to backup the magic @pm@ package without checking for the
backoff value.
This is needed to reliably identify USB mass storage devices.
If someone has several identical thumb drives,
this prevents a backup from being performed when non-backup drives get attached.
Also allow auto-completion when entering the 12-word code.
This makes testing and entering the code easier
and does not compromise security as the word list is public anyway.
Before, we were always returnign a dummy RestoreSet,
if one was actually available or not.
Now, we also include the device name.
Note that it is planned to store the actual device name
and other metadata in an encrypted file
so that the backup server will not learn it.
The implementation is rudimentary for now.
E.g. The notification is only shown when a device init fails
which seems to be triggered after the first failure.
* to get rid of global state
* to have a testable architecture
* to allow for authenticated encryption
* to have a backup format version
* to potentially allow for other storage plugins
* With the upcoming changes, and the increasing number of external
libraries being used, plus the usage of Kotlin, it's getting harder
and harder to build this with the AOSP build system.
* It's best to leverage the existing gradle build system instead,
and use the apk that builds.
* Add a script which downloads the apk matching the tag if a tag is
checked out, otherwise downloads the latest.
For the current transport it is important to know when the backup ends,
because it resets its state only then and closes the ZIP file.
The detection was broken,
because some packages didn't have data to back up (LOG_EVENT_ID_NO_DATA_TO_SEND),
so the transport's methods weren't called and the package counter not updated.
The hacky solution is to use the BackupObserver to call back into the
transport at the end of backup.
Ideally, future transports won't need to know when the backup finishes.
We do this as a temporary fix, because our backup methods are not called
which are updating the package counter. So our mechanism to find out
about the end of the backup is broken. Excluding key-value backups fixes
it for now.
This is being done to implement automatic background updates
and not supposed to be part of a release.
The backup key will later be generated and shown to the user instead of
allowing them to choose their own.
Prior to this commit, some of the application data was not included during encryption. This is a breaking change, any backups made prior to this commit can no longer be restored.
1. Encrypt 'full' backup data.
2. Increase number of key generation iterations to 32767.
3. Change cipher to 'AES/CBC/PKCS5Padding'.
1. Add prompt for entering password during backup and restore.
2. Use PBKDF2 to generate a secret key that is used to encrypt backups.
3. Store salt in backup zip file.
4. Fetch salt from backup zip file during restore and use it to decrypt restoration data.
The output file descriptor was not being closed after each chunk was written.
1. The output stream will no longer be stored in the restore state.
2. The output file descriptor will be closed after a chunk is transferred.
