AM Debug v4.0.5 Run#3068

backup: check if the given package can be backed up using ADB

If the package cannot be backed up using ADB, it falls back to "Internal data"
and "External data".

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v4.0.5 Run#3070

backup: add tests for AB to AM and AM to AB conversion

In order to ensure consistency among the backups, ADB/Android full backup (AB)
to App Manager (AM) formatted backup and vice versa needs to be ensured. The AB
backup created by App Manager via ADB backup API is different from a regular
ADB backup in the following way:
1. It does not take backup of the APK files or OBB files, because they are
handled separately by App Manager. This does not affect the backup, however.
2. Each backup (.ab) file contains backup of just one application package,
because App Manager always takes backup in a per-package basis.
3. No backup password should be given in the backup prompt that the user
receives. App Manager handles the necessary encryption using its own backup
scheme. Besides, Android backup still uses AES/CBC/PKCS5Padding algorithm
for backups which is vulnerable to padding oracle attacks (CWE-326).

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

What is the use of this, you may ask. This offers a certain level of interoperability between App Manager and ADB backups which may have many uses. One particular that I can think of now is converting a backup taken in root mode in a different device and restore it in another device in ADB mode. This is, of course, assuming that the app supports regular backup/restore. That being said, many mainstream apps do not support ADB backups and some only supports key-value backups (which cannot be converted to App Manager-style backups).

AM Debug v4.0.5 Run#3072

refactor: enable new features in non-debug builds

- "filter" profile (via profile type selector)
- "Use system font" setting (in Appearances settings)
- "ADB data" flag for backups
- Backup metadata v5

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v4.0.5 Run#3073

settings: add option to disable terminal emulator in enable/disable features setting

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v4.0.5 Run#3074

debloater: add "Frozen apps" and "Unfrozen apps" filters

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v4.0.5 Run#3075

main: add "Unfrozen apps" filter

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v4.0.5 Run#3076

refactor: simplify time interval handling in app usage

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v4.0.5 Run#3077

usage: remove "Yesterday" option from the interval selector

Also, replaced "Today" with "Daily".

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v4.0.5 Run#3078

usage: add next/previous button to browse usage in other weeks/days

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

Even in a very capable device, Android only stores less than two weeks worth of usage data (depending on the amount of activity). In Google's own wellbeing app, they use a database to store four weeks of usage data. I guess we'd need a feature like this (possibly user configurable) in order to provide usage statistics for a longer period of time. This is a potential future work.

AM Debug v4.0.5 Run#3079

usage: display bar chart for screen time

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>