How to translate Docs

Docs are written using Latex, a widely used language used in writing technical documentation. It has some specific keywords and symbols that needs to be kept intact. Here are few simplified guidelines to get you started:

  1. Anything that begins with \ is a known as a command. Example, \textbf, \chapter, \label, \item, etc.

  2. \begin and \end are collectively known as environment. Anything inside them are part of the environment.

  3. { or [ marks the beginning and } or ] marks the ending of an argument i.e. something you supply to a function (or say, a machine). Example, \textbf{App Manager} (display App Manager is bold).

  4. While most arguments can be edited, a few cannot. Examples:

  5. \label{ch:pages}. Here the argument cannot be edited. Similar commands are \includegraphics, \includesvg, \url, \ref, etc.

  6. \hyperref[sec:main-page]{Main Page}. Here the first argument cannot be edited while the latter might be edited. Similar commands are \href, \hyperlink, \begin{name}, \end{name} where name can be anything such as itemize, tebular, etc.

  7. \caption{A caption}. Here the argument can be edited. Similar commands are \chapter, \section, \subsection, \subsubsection, \paragraph, etc.

    Use your intuition or ask question if you're confused.

Those who were part of the old team on Crowdin

You can still find your translations here: https://crowdin.com/project/app-manager-docs. Please do not edit anything there as the project has been discontinued. However, you can use it to migrate your translations on Weblate. Partially completed languages will be deleted permanently from Crowdin when a threshold is reached.

For New Contributors

Weblate does not offer membership control in their OSS license. As the platform is getting popular, more abusive behaviour is being noticed. As a result, even if you contribute to App Manager, your contribution will not be added to the project unless you submit a request via GitHub or E-Mail asserting that you've read and understood the translation policies (click the Info tab). Existing contributors will not be affected by this (but translations policies are still applicable to them).

Source strings

401 Strings 100%
Browse Translate
19,235 Words 100%
136,332 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
401 19,235 136,332
All strings Browse Translate Zen
401 19,235 136,332
Translated strings Browse Translate Zen
401 19,235 136,332
Strings waiting for review Browse Translate Zen
127 13,655 97,763
Strings with any failing checks Browse Translate Zen
1 2 13
Translated strings with dismissed checks Browse Translate Zen
2 1,162 7,587
Failing check: Unpluralised Browse Translate Zen
38 7,508 53,857
Failing check: Multiple failing checks Browse Translate Zen
93 6,662 47,721
Failing check: Long untranslated Browse Translate Zen
1 2 11
Strings with comments Browse Translate Zen
401 19,235 136,332
Strings without a label Browse Translate Zen

Other components

Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Disclaimer GPL-3.0 0 0 0 0 4 0 0
Main GPL-3.0 0 0 0 0 216 0 1
Browse all components

Overview

Project website muntashirakon.github.io/AppManager
Instructions for translators

Translating App Manager

Some of the regular translators have complained that some new contributors are hampering their efforts by repeatedly mistranslating strings and/or translating strings without context because they do not actually use the app or are not particularly familiar with its features. Translating App Manager requires some domain-specific knowledge meaning that not everybody is able to understand the context of a string unless they are familiar with it. In the light of these events, we feel the necessity to enforce some rules and regulations to limit such abusive behaviours.

Requirements

  1. You should have an account in GitHub so that you can communicate with the other contributors should you encounter any issues or have problems understanding the context of a string.
  2. You must have some knowledge regarding Android ecosystem. For example, you must be familiar with terms such as permissions, API/SDK, components, signatures, app operations, etc.
  3. You must only translate App Manager into a language you are quite familiar with in the context that you actually use the language to communicate with people. Learning a language only theoretically may make you expert on the language, you may still lack the knowledge regarding how people actually use the language in real life. “No translation” is better than “bad translation”. While it is perfectly okay to take help from a machine, final translations should be decided by you, not the machine.

Penalties

  1. If we are convinced that you didn't fulfil the requirements above, we shall permanently block your account.

  2. If we discover any attempts of spamming or any other malicious behaviour, your account will be blocked permanently. No appeal can be made against the decision.

  3. If we find that you are involved in mistranslating a string either intentionally or due to machine translations, or involved in a translation war where you are the adversary, you're account will be blocked temporarily or permanently depending on how abusive your actions were.

  4. The use of NSFW is considered an abusive behaviour, and if you use such words in a comment in Weblate's App Manager project, you will be blocked temporarily.

    Except penalty no. 2, you can appeal against the decision using the official channels such as GitHub, Matrix or E-Mail.

Changes to the policies

Changes to the policies shall be announced via the announcements.

Effective since: 7 February 2023 Last edit: 18 September 2023 (Replaced Telegram with Matrix)
Project maintainers User avatar muntashir
Translation license GNU General Public License v3.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language is editable.
Source code repository https://github.com/MuntashirAkon/AppManager.git
Repository branch master
Last remote commit [Finder] Fix applying usage filters 5da368dde
User avatar muntashir authored yesterday
Last commit in Weblate Translated using Weblate (Chinese (Simplified Han script)) c04742dca
User avatar Astoritin authored 23 hours ago
Weblate repository https://hosted.weblate.org/git/app-manager/main/
File mask docs/raw/*/strings.xml
Monolingual base language file docs/raw/en/strings.xml
Translation file Download docs/raw/en/strings.xml
Last change Nov. 11, 2024, 11:07 p.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Number of speakers 1,728,900,209
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
4 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 401 19,235 136,332
Approved 0% 0 0% 0 0% 0
Waiting for review 100% 401 100% 19,235 100% 136,332
Translated 100% 401 100% 19,235 100% 136,332
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 31% 127 70% 13,655 71% 97,763
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 4 changes 0 changes 42 changes 0 changes 1 change 1 change 1 change 0 changes 0 changes 0 changes 4 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 72 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

19,235
Hosted words
401
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+5%
Hosted words
+100%
+4%
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Resource updated
Parsing of the “docs/raw/en/strings.xml” file was enforced. 8 days ago
User avatar muntashir

Comment resolved
Comment resolved a month ago
User avatar None

Resource updated
The “docs/raw/en/strings.xml” file was changed. a month ago
User avatar None

String updated in the repository
Short for \textbf{Network policy} or network policies.
It is usually located in the Android settings under \textbf{Mobile data \& Wifi} section in the app info page of an app.
Not all policies are guaranteed to be included in this page (e.g.\ Samsung), and not all settings are well-understood due to lack of documentation.
App Manager can display all the net policies declared in the \href{https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/net/NetworkPolicyManager.java}{NetworkPolicyManager}.
Policies unknown to App Manager will have a \textit{Unknown} prefix along with the policy constant name and number in the hexadecimal format.
Unknown policies should be reported to App Manager for inclusion.

Net policy allows a user to configure certain networking behaviour of an app without modifying the ip tables directly and/or running a firewall app.
However, the features it offers largely depend on Android version and ROM. A list of known net policies are listed below:

\begin{enumerate}
\item \textbf{None} or \textbf{\texttt{POLICY\_NONE}}: (AOSP) No specific network policy is set.
System can still assign rules depending on the nature of the app.

\item \textbf{Reject background data on metered networks} or \textbf{\texttt{POLICY\_REJECT\_METERED\_BACKGROUND}}: (AOSP) Reject network usage on metered networks when the application is in background.

\item \textbf{Allow background data on metered networks even when Data Saver is on} or \textbf{\texttt{POLICY\_ALLOW\_METERED\_BACKGROUND}}: (AOSP) Allow metered network use in the background even when data saving mode is enabled.

\item \textbf{Reject cellular data} or \textbf{\texttt{POLICY\_REJECT\_CELLULAR}} (Android 11+) or \textbf{\texttt{POLICY\_REJECT\_ON\_DATA}} (up to Android 10): (Lineage OS) Reject mobile/cellular data.
Signals network unavailable to the configured app as if the mobile data is inactive.

\item \textbf{Reject VPN data} or \textbf{\texttt{POLICY\_REJECT\_VPN}} (Android 11+) or \textbf{\texttt{POLICY\_REJECT\_ON\_VPN}} (up to Android 10): (Lineage OS) Reject VPN data.
Signals network unavailable to the configured app as if the VPN is inactive.

\item \textbf{Reject Wi-Fi data} or \textbf{\texttt{POLICY\_REJECT\_WIFI}} (Android 11+) or \textbf{\texttt{POLICY\_REJECT\_ON\_WLAN}} (up to Android 10): (Lineage OS) Reject Wi-Fi data.
Signals network unavailable to the configured app as if the device is not connected to a Wi-Fi network.

\item \textbf{Disable network access} or \textbf{\texttt{POLICY\_REJECT\_ALL}} (Android 11+) or \textbf{\texttt{POLICY\_NETWORK\_ISOLATED}} (up to Android 10): (Lineage OS) Reject network access in all circumstances.
This is not the same as enforcing the other three policies above, and is the recommended policy for dodgy apps.
If this policy is enforced, there is no need to enforce the other policies.

\item \textbf{\texttt{POLICY\_ALLOW\_METERED\_IN\_ROAMING}}: (Samsung) Possibly allow metered network use during roaming.
Exact meaning is currently unknown.

\item \textbf{\texttt{POLICY\_ALLOW\_WHITELIST\_IN\_ROAMING}}: (Samsung) Possibly allow network use during roaming.
Exact meaning is currently unknown.

\item \textbf{Reject data on metered networks} or \textbf{\texttt{POLICY\_REJECT\_METERED}}: (Motorola) Reject network usage if it is a metered network.

\item \textbf{Reject background data} or \textbf{\texttt{POLICY\_REJECT\_BACKGROUND}}: (Motorola) Reject network usage in the background.

\item \textbf{Disable network access} or \textbf{\texttt{POLICY\_REJECT\_ALL}}: (Motorola) Reject network access altogether.
Like Lineage OS, it blocks internet connections via iptables. But whether it signals the unavailability of network to the configured app is not known.
\end{enumerate}

\begin{tip}{Note}
Corresponding Lineage OS patches are as follows:
\begin{enumerate}
\item \href{https://github.com/LineageOS/android\_frameworks\_base/commit/a04932bafbbf7d99efd18276152cc2c9c9b2073e}{fw/b: Squash of app fw restriction commits}
\item \href{https://github.com/LineageOS/android\_frameworks\_base/commit/02c8c82854348f52afe2199f310f44b5f578b5b8}{fw/b: Add support for per app network isolation}
\end{enumerate}
\end{tip}
Short for \textbf{Network policy} or network policies.
It is usually located in the Android settings under \textbf{Mobile data \& Wifi} section in the app info page of an app.
Not all policies are guaranteed to be included in this page (e.g.\ Samsung), and not all settings are well-understood due to lack of documentation.
App Manager can display all the net policies declared in the \href{https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/net/NetworkPolicyManager.java}{NetworkPolicyManager}.
Policies unknown to App Manager will have a \textit{Unknown} prefix along with the policy constant name and number in the hexadecimal format.
Unknown policies should be reported to App Manager for inclusion.

Net policy allows a user to configure certain networking behaviour of an app without modifying the ip tables directly and/or running a firewall app.
However, the features it offers largely depend on Android version and ROM. A list of known net policies are listed below:

\begin{enumerate}
\item \textbf{None} or \textbf{\texttt{POLICY\_NONE}}: (AOSP) No specific network policy is set.
System can still assign rules depending on the nature of the app.

\item \textbf{Reject background data on metered networks} or \textbf{\texttt{POLICY\_REJECT\_METERED\_BACKGROUND}}: (AOSP) Reject network usage on metered networks when the application is in background.

\item \textbf{Allow background data on metered networks even when Data Saver is on} or \textbf{\texttt{POLICY\_ALLOW\_METERED\_BACKGROUND}}: (AOSP) Allow metered network use in the background even when data saving mode is enabled.

\item \textbf{Reject cellular data} or \textbf{\texttt{POLICY\_REJECT\_CELLULAR}} (Android 11+) or \textbf{\texttt{POLICY\_REJECT\_ON\_DATA}} (up to Android 10): (Lineage OS) Reject mobile/cellular data.
Signals network unavailable to the configured app as if the mobile data is inactive.

\item \textbf{Reject VPN data} or \textbf{\texttt{POLICY\_REJECT\_VPN}} (Android 11+) or \textbf{\texttt{POLICY\_REJECT\_ON\_VPN}} (up to Android 10): (Lineage OS) Reject VPN data.
Signals network unavailable to the configured app as if the VPN is inactive.

\item \textbf{Reject Wi-Fi data} or \textbf{\texttt{POLICY\_REJECT\_WIFI}} (Android 11+) or \textbf{\texttt{POLICY\_REJECT\_ON\_WLAN}} (up to Android 10): (Lineage OS) Reject Wi-Fi data.
Signals network unavailable to the configured app as if the device is not connected to a Wi-Fi network.

\item \textbf{Disable network access} or \textbf{\texttt{POLICY\_REJECT\_ALL}} (Android 11+) or \textbf{\texttt{POLICY\_NETWORK\_ISOLATED}} (up to Android 10): (Lineage OS) Reject network access in all circumstances.
This is not the same as enforcing the other three policies above, and is the recommended policy for dodgy apps.
If this policy is enforced, there is no need to enforce the other policies.

\item \textbf{\texttt{POLICY\_ALLOW\_METERED\_IN\_ROAMING}}: (Samsung) Possibly allow metered network use during roaming.
Exact meaning is currently unknown.

\item \textbf{\texttt{POLICY\_ALLOW\_WHITELIST\_IN\_ROAMING}}: (Samsung) Possibly allow network use during roaming.
Exact meaning is currently unknown.

\item \textbf{Reject data on metered networks} or \textbf{\texttt{POLICY\_REJECT\_METERED}}: (Motorola) Reject network usage if it is a metered network.

\item \textbf{Reject background data} or \textbf{\texttt{POLICY\_REJECT\_BACKGROUND}}: (Motorola) Reject network usage in the background.

\item \textbf{Disable network access} or \textbf{\texttt{POLICY\_REJECT\_ALL}}: (Motorola) Reject network access altogether.
Like Lineage OS, it blocks internet connections via iptables. But whether it signals the unavailability of network to the configured app is not known.
\end{enumerate}

\begin{tip}{Note}
Corresponding Lineage OS patches are as follows:
\begin{enumerate}
\item \href{https://github.com/LineageOS/android\_frameworks\_base/commit/a04932bafbbf7d99efd18276152cc2c9c9b2073e}{fw/b: Squash of app fw restriction commits}
\item \href{https://github.com/LineageOS/android\_frameworks\_base/commit/02c8c82854348f52afe2199f310f44b5f578b5b8}{fw/b: Add support for per app network isolation}
\end{enumerate}
\end{tip}
a month ago
User avatar None

String updated in the repository
Backup options (internally known as backup flags) let you customise the backups on the fly.
However, the customisations will not be remembered for the future backups.
If you want to customise this dialog, use \hyperref[subsubsec:settings-backup-options]{Backup Options} in the \hyperref[sec:settings-page]{Settings page}.

A complete description of the backup options is given below:
\begin{itemize}
\item \textbf{APK files.} Whether to back up the APK files.
This includes the \textit{base APK} file along with the \texttt{split APK} files if they exist.

\item \textbf{Internal data.} Whether to back up the internal data directories.
These directories are located at \texttt{/data/user/<user\_id>} and (for Android N or later) \texttt{/data/user\_de/<user\_id>}.

\item \textbf{External data.} Whether to back up data directories located in the internal memory as well as SD Card (if exists).
External data directories often contain non-essential app data or media files (instead of using the dedicated media folder) and may increase the backup size.
However, it might be essential for some apps.
Although it isn't checked by default (as it might dramatically increase the size of the backups), you may have to check it in order to ensure a smooth restore of your backups.
\begin{warning}{Caution}
Internal data folders should always be backed up if you are going to back up the external data folders.
However, it could be useful to back up only the external folders if the app in question downloads a lot of assets from the Internet.
\end{warning}

\item \textbf{OBB and media.} Whether to back up or restore the OBB and the media directories located in the
external storage or the SD Card.
This is useful for games and the graphical software which actually use these folders.

\item \textbf{Cache.} Android apps have multiple cache directories located at every data directories (both internal and external).
There are two types of cache: \textbf{cache} and \textbf{code cache}.
Disabling this option excludes both cache directories from all the data directories.
It is generally advised to exclude cache directories since most apps do not clear the cache regularly and usually handled by the OS itself.
Apps such as Telegram may use a very large cache (depending on the storage space) which may dramatically increase the backup size.
When it is disabled, AM also ignores the \textbf{no\_backup} directories.

\item \textbf{Extras.} Backup/restore app permissions, net policy, battery optimization, SSAID, etc., enabled by default.
Note that, blocking rules are applied \textit{after} applying the extras.
So, if an item is present in both places, it will be overwritten (i.e., the one from the blocking rules will be used).

\item \textbf{Rules.} This option lets you back up blocking rules configured within App Manager.
This might come in handy if you have customised permissions or block some components using App Manager as they will
also be backed up or restored when you enable this option.

\item \textbf{Backup Multiple.} Whether this is a multiple backup.
By default, backups are saved using their user ID\@.
Enabling this option allows you to create additional backups.
These backups use the current date-time as the default backup name, but you can also specify custom backup name
using the input field displayed when you click on the \textbf{Backup} button.

\item \textbf{Custom users.} Backup or restore for the selected users instead of only the current user.
This option is only displayed if the system has more than one user.

\item \textbf{Skip signature checks.} When taking a backup, checksum of every file (as well as the signing
certificate(s) of the base APK file) is generated and stored in the \texttt{checksums.txt} file.
When you restore the backup, the checksums are generated again and are matched with the checksums stored in the said file.
Enabling this option will disable the signature checks.
This option is applied only when you restore a backup.
During backup, the checksums are generated regardless of this option.
\begin{warning}{Caution}
You should always disable this option to ensure that your backups are not modified by any third-party applications.
However, this would only work if you enabled encryption.
\end{warning}
\end{itemize}

\seealsoinline{\hyperref[subsubsec:settings-encryption]{Settings: Encryption}}
Backup options (internally known as backup flags) let you customise the backups on the fly.
However, the customisations will not be remembered for the future backups.
If you want to customise this dialog, use \hyperref[subsubsec:settings-backup-options]{Backup Options} in the \hyperref[sec:settings-page]{Settings page}.

A complete description of the backup options is given below:
\begin{itemize}
\item \textbf{APK files.} Whether to back up the APK files.
This includes the \textit{base APK} file along with the \texttt{split APK} files if they exist.

\item \textbf{Internal data.} Whether to back up the internal data directories.
These directories are located at \texttt{/data/user/<user\_id>} and (for Android N or later) \texttt{/data/user\_de/<user\_id>}.

\item \textbf{External data.} Whether to back up data directories located in the internal memory as well as SD Card (if exists).
External data directories often contain non-essential app data or media files (instead of using the dedicated media folder) and may increase the backup size.
However, it might be essential for some apps.
Although it isn't checked by default (as it might dramatically increase the size of the backups), you may have to check it in order to ensure a smooth restore of your backups.
\begin{warning}{Caution}
Internal data folders should always be backed up if you are going to back up the external data folders.
However, it could be useful to back up only the external folders if the app in question downloads a lot of assets from the Internet.
\end{warning}

\item \textbf{OBB and media.} Whether to back up or restore the OBB and the media directories located in the
external storage or the SD Card.
This is useful for games and the graphical software which actually use these folders.

\item \textbf{Cache.} Android apps have multiple cache directories located at every data directories (both internal and external).
There are two types of cache: \textbf{cache} and \textbf{code cache}.
EnDisabling this option excludes both cache directories from all the data directories.
It is generally advised to exclude cache directories since most apps do not clear the cache regularly (for some
reason, the only way an app can clear its cache is by deleting the entire cache directory) and usually handled by the OS itself.
Apps such as Telegram may use a very large cache (depending on the storage space) which may dramatically increase the backup size.
When it is disabled, AM also ignores the \textbf{no\_backup} directories.

\item \textbf{Extras.} Backup/restore app permissions, net policy, battery optimization, SSAID, etc., enabled by default.
Note that, blocking rules are applied \textit{after} applying the extras.
So, if an item is present in both places, it will be overwritten (i.e., the one from the blocking rules will be used).

\item \textbf{Rules.} This option lets you back up blocking rules configured within App Manager.
This might come in handy if you have customised permissions or block some components using App Manager as they will
also be backed up or restored when you enable this option.

\item \textbf{Backup Multiple.} Whether this is a multiple backup.
By default, backups are saved using their user ID\@.
Enabling this option allows you to create additional backups.
These backups use the current date-time as the default backup name, but you can also specify custom backup name
using the input field displayed when you click on the \textbf{Backup} button.

\item \textbf{Custom users.} Backup or restore for the selected users instead of only the current user.
This option is only displayed if the system has more than one user.

\item \textbf{Skip signature checks.} When taking a backup, checksum of every file (as well as the signing
certificate(s) of the base APK file) is generated and stored in the \texttt{checksums.txt} file.
When you restore the backup, the checksums are generated again and are matched with the checksums stored in the said file.
Enabling this option will disable the signature checks.
This option is applied only when you restore a backup.
During backup, the checksums are generated regardless of this option.
\begin{warning}{Caution}
You should always disable this option to ensure that your backups are not modified by any third-party applications.
However, this would only work if you enabled encryption.
\end{warning}
\end{itemize}

\seealsoinline{\hyperref[subsubsec:settings-encryption]{Settings: Encryption}}
a month ago
User avatar None

String added in the repository
Depending on the device and the version of operating system, you have to enable \textbf{Disable Permission Monitoring}.
Depending on the device and the version of operating system, you have to enable \textbf{Disable Permission Monitoring}.
a month ago
User avatar None

String added in the repository
OnePlus (Oxygen OS)
OnePlus (Oxygen OS)
a month ago
User avatar None

String updated in the repository
At the bottom of the page, there is a special item denoting the number of missing signatures (i.e.,
missing classes). The missing signatures are the ones that App Manager has failed to match against
any known libraries. The number itself has no particular meaning as many libraries contain hundreds
of classes, but clicking on the item will bring up a dialog containing the signatures which is
helpful in inspecting the missing signatures. \textbf{This feature is only intended for people who
know what a missing signature is and what to do with it, other users should ignore it.}
At the bottom of the page, there is a special item denoting the number of missing signatures (i.e.\ ,
missing classes).
 The missing signatures are the ones that AMpp Manager has failed to match against
any known libraries. The number itself has no
 particular meaning as many libraries contain hundreds
of classes, but clicking on the item will bring up a dialog
 containing the signatures which is
helpful in inspecting the missing signatures. \textbf{This feature is only intended
 for people who
know what a missing signature is and what to do with it, other users should ignore it.}
a month ago
User avatar None

String updated in the repository
\textbf{Scanner page} appears after clicking on the \emph{scanner} button in the \hyperref[subsec:app-info-tab]{App Info tab}.
External APK files can also be opened for scanning from file managers, web browsers, etc.

It scans for trackers and libraries, and displays the number of trackers and libraries as a summary.
It also displays checksums of the APK file as well as the signing certificates. If VirusTotal is
configured in the settings, it also attempts to retrieve reports from VirusTotal, or uploads the APK
file if it is not in the database. It also display a link to the \href{https://beta.pithus.org}{Pithus}
report provided the Internet features are enabled.

\begin{danger}{Disclaimer}
App Manager only scans an application statically without prejudice. The application may provide
the options for opting out, or in some cases, certain features of the tracker may not be used at
all by the application (e.g.\ F-Droid), or some applications may simply use them as placeholders
to prevent the breaking of certain features (e.g.\ Fennec F-Droid). \textbf{The intention of the
scanner is to give you an idea about what the APK might contain. It should be taken as an
initial step for further investigations.}
\end{danger}

Clicking on the first item (i.e.\ number of classes) opens a new page containing a list of tracker
classes for the application. All classes can also be viewed by clicking on the \textit{Toggle Class
Listing} menu. The SMALI or Java version of the class can be viewed by simply clicking on an item.

\begin{tip}{Notice}
Due to various limitations, it is not possible to scan all the components of an APK file. This
is especially true if an APK is highly obfuscated or packed. The scanner also does not check
strings (or website signatures).
\end{tip}

The second item lists the number of trackers along with their names. Clicking on the item displays a
dialog containing the name of trackers, matched signatures, and the number of classes against each
signature. Some tracker names may have $^2$ prefix which indicates that the trackers are in the
\href{https://etip.exodus-privacy.eu.org}{ETIP} stand-by list, i.e., whether they are actual
trackers is still being investigated.

The third item lists the number of libraries along with their names. The information are mostly
taken from \href{https://gitlab.com/IzzyOnDroid/repo}{IzzyOnDroid repo}.

\seealsoinline{\hyperref[subsec:tracker-classes-versus-tracker-components]{FAQ: Tracker classes vs tracker components}}
\textbf{Scanner page} appears after clicking on the \emph{scanner} button in the \hyperref[subsec:app-info-tab]{App Info tab}.
External APK files can also be opened for scanning from file managers, web browsers, etc.

It scans for trackers and libraries, and displays the number of trackers and libraries as a summary.
It also displays
 checksums of the APK file as well as the signing certificates. If VirusTotal is
configured in the settings,
 it also attempts to retrieve reports from VirusTotal, or uploads the APK
file if it is not in the database. It also display a link to the \href{https://beta.pithus.org}{Pithus}
report provided the Internet features are enabled.

\begin{danger}{Disclaimer}
App Manager only scans an application statically without prejudice. The application may provide
 the options for opting out,
 or in some cases, certain features of the tracker may not be used at
 all by the application (e.g.\ F-Droid),
 or some applications may simply use them as placeholders
 to prevent the breaking of certain features (e.g.\ Fennec F-Droid).
 \textbf{The intention of the
 scanner is to give you an idea about what the APK might contain. It should be taken as an
 initial step for further investigations.}
\end{danger}

Clicking on the first item (i.e.\ number of classes) opens a new page containing a list of tracker
classes for the application.
 All classes can also be viewed by clicking on the \textit{Toggle Class
Listing} menu.
A sneak-peek of each The SMALI or Java version of the class can be viewed by simply clicking on any class item. In Android 8 (Oreo) and later,
this includes the whole SMALI version of the class, and can be converted into Java using the corresponding option item.

\begin{tip}{Notice}
Due to various limitations, it is not possible to scan all the components of an APK file. This
 is especially true if
 an APK is highly obfuscated or packed. The scanner also does not check
 strings (or website signatures).
\end{tip}

The second item lists the number of trackers along with their names. Clicking on the item displays a
dialog containing
 the name of trackers, matched signatures, and the number of classes against each
signature. Some tracker names may have
 $^2$ prefix which indicates that the trackers are in the
\href{https://etip.exodus-privacy.eu.org}{ETIP} stand-by list
, i.e.\, whether they are actual
trackers is still being investigated.

The third item lists the number of libraries along with their names. The information are mostly
taken from
 \href{https://gitlab.com/IzzyOnDroid/repo}{IzzyOnDroid repo}.

\seealsoinline{\hyperref[subsec:tracker-classes-versus-tracker-components]{FAQ: Tracker classes vs tracker components}}
a month ago
User avatar None

String updated in the repository
Set an encryption method for the backups. App Manager currently supports OpenPGP (via
\href{https://f-droid.org/packages/org.sufficientlysecure.keychain/}{OpenKeyChain}), AES, RSA and ECC\@.
Like \hyperref[subsec:apk-signing]{APK signing}, The AES, RSA and ECC keys are stored in the
KeyStore and can be imported from other KeyStores.

\begin{danger}{Danger}
For your own safety, it is not recommended generating RSA and ECC keys inside App Manager.
Instead, they should be imported from a KeyStore stored in a secure place.\\
In case of AES, the generated key should be stored in a secure place, such as in a password manager.
\end{danger}
Set an encryption method for the backups. App Manager currently supports OpenPGP (via
\href{https://f-droid.org/packages/org.sufficientlysecure.keychain/}{OpenKeyChain}), AES, RSA and ECC\@.
Like \hyperref[subsec:apk-signing]{APK signing}, The AES, RSA and ECC keys are stored in the
KeyStore and can be
 imported from other KeyStores.

\begin{danger}{Danger}
For your own safety, it is not recommended generating RSA and ECC keys inside App Manager.
 Instead, they should be
 imported from a KeyStore stored in a secure place.\\
In case of AES, the generated key should be stored in a secure place, such as using a password manager.
\end{danger}
a month ago
Browse all translation changes