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).

Please sign in to see the alerts.

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.
  • 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] Add new filter: permissions b04fa22a5
User avatar muntashir authored yesterday
Last commit in Weblate Translated using Weblate (Chinese (Simplified Han script)) 5210eff8c
User avatar Astoritin authored 19 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
5 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 4,411 211,585 1,499,652
Source 401 19,235 136,332
Approved 0% 0 0% 0 0% 0
Waiting for review 41% 1,844 35% 75,943 36% 541,347
Translated 41% 1,844 35% 75,943 36% 541,347
Needs editing 1% 30 1% 800 1% 5,407
Read-only 0% 0 0% 0 0% 0
Failing checks 6% 307 19% 42,246 20% 302,681
Strings with suggestions 1% 19 1% 497 1% 3,985
Untranslated strings 57% 2,537 63% 134,842 63% 952,898
Last 12 months Previous

Activity in last 12 months

17 changes 14 changes 125 changes 22 changes 13 changes 0 changes 70 changes 10 changes 699 changes 4 changes 68 changes 48 changes 71 changes 10 changes 11 changes 7 changes 141 changes 6 changes 19 changes 0 changes 59 changes 12 changes 10 changes 1,023 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

211 k
Hosted words
4,411
Hosted strings
41%
Translated
5
Contributors
and previous 30 days

Trends of last 30 days

+5%
Hosted words
+100%
+4%
Hosted strings
+100%
+3%
Translated
+38%
+80%
Contributors
+100%
User avatar None

Changes committed
Changes committed 5 hours ago
User avatar Astoritin

Translation changed
Bloatware are the unnecessary apps supplied by the vendor or OEM and are usually system apps. These apps are often used
to track users and collect user data which they might sell for profits. System apps do not need to request any
permission in order to access device info, contacts and messaging data, and other usage info such as your phone usage
habits and everything you store on your shared storage(s).

The bloatware may also include Google apps (such as Google Play Services, Google Play Store, Gmail, Google, Messages,
Dialer, Contacts), Facebook apps (the Facebook app consists of four or five apps), Facebook Messenger, Instagram,
Twitter and many other apps which can also track users and/or collect user data without consent given that they all are
system apps. You can disable a few permissions from the Android settings but be aware that Android settings hides almost
every permission any security specialist would call potentially \emph{dangerous}.

If the bloatware were user apps, you could easily uninstall them either from Android settings or AM. Uninstalling system
apps is not possible without root permission. You can also uninstall system apps using ADB, but it may not work for all
apps. AM can uninstall system apps with root or ADB (the latter with certain limitations, of course), but these methods
cannot \emph{remove} the system apps completely as they are located in the \emph{system} partition which is a read-only
partition. If you have root, you can remount this partition to manually \emph{purge} these apps but this will break Over
the Air (OTA) updates since data in the system partition has been modified. There are two kind of updates, delta
(small-size, consisting of only the changes between two versions) and full updates. You can still apply full updates,
but the bloatware will be installed again, and consequently, you have to delete them all over again. Besides, not all
vendors provide full updates.

Another solution is to disable these apps either from Android settings (no-root) or AM, but certain services can still
run in the background as they can be started by other system apps using Inter-process Communication (IPC). One possible
solution is to disable all bloatware until the service has finally stopped (after a restart). However, due to heavy
modifications of the Android frameworks by the vendors, removing or disabling certain bloatware may cause the System UI
to crash or even cause bootloop, thus, (soft) bricking your device. You may search the web or consult the fellow users
to find out more about how to debloat your device.

From v2.5.19, AM has a new feature called \hyperref[sec:profile-page]{profiles}. The
\hyperref[sec:profiles-page]{profiles page} has an option to create new profiles from one of the presets. The presets
consist of debloating profiles which can be used as a starting point to monitor, disable, and remove the bloatware from
a proprietary Android operating system.

\begin{warning}{Note}
In most cases, you cannot completely debloat your device. Therefore, it is recommended that you use a custom ROM
free from bloatware such as Graphene OS, Lineage OS or their derivatives.
\end{warning}
臃肿软件 (Bloatware，国内也称之为预装软件) 是由供应商 (vendor) 或 原始设备制造商 (OEM) 提供的不必要应用，并且通常情况下是系统应用。
这些应用经常用于跟踪用户和收集用户数据以出售并从中获利。
系统应用并不需要请求任何权限对设备信息、通讯录和信息数据进行访问，
以及其他使用情况信息，诸如你的手机使用习惯和你在共享存储器存储的一切内容。

臃肿软件 (Bloatware) 也可能包括 Google 应用 (诸如 Google Play 服务、Google Play 商店、Gmail、Google、信息、电话、通讯录)、
Facebook 应用 (Facebook应用由四或者五个应用组成)、Facebook Messenger、Instagram、Twitter 以及许多其他可跟踪用户
和/或未经许可收集用户数据的应用，并且他们全部都是系统应用。
你可以从 Android 设置中禁用一些权限。
但是请注意，Android 设置中隐藏了几乎全部的权限，任何专家都会称其为潜在 \emph{危险}。

若臃肿软件 (Bloatware) 为用户应用，则你可以通过 Android 设置或 App Manager 轻易卸载它们。
无 Root 权限时无法卸载系统应用。你也可以通过 ADB 卸载系统应用，但这并不会对所有应用有效。
App Manager 能够通过 Root 或者 ADB 卸载系统应用 (当然，后者存在某些限制)，
但由于它们位于只读的 \emph{system} 分区，这些方法无法完全 \emph{移除} 系统应用。
如果你有 Root 权限，你可以手动重新挂载该分区并 \emph{清除} 这些应用，
但因为系统分区数据被修改，会破坏 OTA 更新 (Over the Air，无线下载)。
对 Android 而言有两种更新方式，增量更新 (delta) (占用小，仅包括两个版本之间的变化) 和全量更新。
你仍可使用全量更新，但臃肿软件 (Bloatware) 会被再次安装，
结果你不得不再次删除它们。此外，也不是所有的供应商会提供全量更新。

另一个解决方案就是从 Android 设置 (无 Root) 或 App Manager 中禁用它们，
但由于它们能被其他系统应用通过进程间通信 (IPC，Inter-process Communication) 启动，某些服务仍然能在后台运行。
一个可能的解决方案是禁用所有的臃肿软件 (Bloatware) 直到服务最终停止 (重新启动后)。
然而，由于 Android 框架被供应商各种魔改 (相当重度的胡乱修改)，移除或禁用某些臃肿软件 (Bloatware) 可能会导致系统界面崩溃
甚至是引导循环 (bootloop，手机不断重启，卡在开机第一屏或者开机动画但无法正常进入系统)，
因此，你的手机会变(软)砖。你可能需要上网搜寻资料或咨询同 (机型) 用户以找到救砖办法。

从 v2.5.19 开始，App Manager 新增 \hyperref[sec:profile-page]{配置文件} 功能。
\hyperref[sec:profiles-page]{配置文件页面} 具有一个选项，可从其中一个预设创建新的配置文件。
该预设包括去臃肿软件 (Debloat) 的配置文件，
可作为专有 Android 操作系统监控、禁用、移除臃肿软件 (Bloatware) 的起点。

\begin{warning}{注释意}
绝大多数情况下，你无法将臃肿软件 (Bloatware) 完全从你的设备中移除。
因此，推荐你使用第三方 ROM，诸如 Graphene OS、Lineage OS 或其他衍生 ROM 以摆脱臃肿软件 (Bloatware)。
\end{warning}
19 hours ago
User avatar Astoritin

Translation changed
Back up/restore is a part of \hyperref[subsec:batch-operations]{batch operations}.
It is also located inside the \hyperref[subsubsec:app-info-options-menu]{options menu} in the
\hyperref[subsec:app-info-tab]{App Info tab}.
Clicking on \textbf{Backup/Restore} opens the \textbf{Backup Options}.
Backups are located at \texttt{/storage/emulated/0/AppManager} by default.
You can configure custom backup location in the \hyperref[subsubsec:backup-volume]{settings page} in which case the backups
will be located at the \texttt{AppManager} folder in the selected volume.

\begin{tip}{Note}
If one or more selected apps do not have any backup, the \textbf{Restore} and \textbf{Delete Backup} options will
not be displayed.
\end{tip}
备份/还原是 \hyperref[subsec:batch-operations]{批处理操作} 的一部分。
它也位于 \hyperref[subsec:app-info-tab]{应用信息标签页} 的
\hyperref[subsubsec:app-info-options-menu]{选项菜单} 中。
Clicking on \textbf{Backup/Restore} opens the \textbf{Backup Options}.
默认情况下，备份存放在 \texttt{/storage/emulated/0/AppManager} 。
你可以在 \hyperref[subsubsec:backup-volume]{设置页面} 配置自定义的备份位置。
无论如何配置，备份都会存放在所选卷的 \texttt{AppManager} 文件夹。

\begin{tip}{记住注意}
若一个或多个应用程序并没有任何备份，
则不会显示 \textbf{还原} 和 \textbf{删除备份} 选项。
\end{tip}
19 hours ago
User avatar Astoritin

Translation changed
List of colours used in this page, and their meaning:
\begin{itemize}
\item \colorbox{uninstalled-day}{\textcolor{black}{Red (day)}} / \colorbox{uninstalled-night}{\textcolor{white}{dark red (night)}}
-- Denotes any app ops or permissions having the dangerous flag, or any components blocked
within App Manager, or any unsupported but required features.

\item \colorbox{disabled-day}{\textcolor{black}{Light red (day)}} / \colorbox{disabled-night}{\textcolor{white}{very
dark red (night)}} -- Denotes the components disabled outside of App Manager, or any unsupported
but optional features.

\begin{tip}{Note}
A component marked as disabled does not always mean that it is disabled by the user: It could also be disabled
by the system or marked as disabled in its manifest. The components of a disabled application are also
considered disabled by the system (and App Manager).
\end{tip}

\item \colorbox{tracker-day}{\textcolor{black}{Vivid orange (day)}} / \colorbox{tracker-night}{
\textcolor{white}{very dark orange (night)}} -- Denotes the tracker components

\item \colorbox{AMSoftMagenta}{\textcolor{black}{Soft magenta (day)}} / \colorbox{AMVeryDarkViolet}{
\textcolor{white}{very dark violet (night)}} -- Denotes the running services.

\item \colorbox{AMDarkCyan}{\textcolor{black}{Dark cyan}} -- Used in the tracker-indicator tag
to denote that all the trackers in the application are blocked.
\end{itemize}
本页中使用的颜色列表，以及对应的含义:
\begin{itemize}
\item \colorbox{uninstalled-day}{\textcolor{black}{红色 (日间模式)}} / \colorbox{uninstalled-night}{\textcolor{white}{深红色 (夜间模式)}}
-- 表示任何应用操作(App ops)或权限存在危险的标志(flag)，或者任何组件在 App Manager 中被阻止，
又或者是任何需要却又不受支持的功能特性。

\item \colorbox{disabled-day}{\textcolor{black}{亮红色 (日间模式)}} / \colorbox{disabled-night}{\textcolor{white}{暗红色 (夜间模式)}}
-- 表示组件在 App Manager 外被禁用，或任何不受支持的
可选功能特性。

\begin{tip}{注意}
标记为禁用（停用/阻止）的组件并不意味着它被用户禁用，它也可能是被系统禁用的，
或者是在其清单(Android-Manifest.xml)中被标记为禁用（停用/阻止）。
被禁用（停用/阻止）的应用程序也会被系统（和App Manager）视为禁用（停用/阻止）。
\end{tip}

\item \colorbox{tracker-day}{\textcolor{black}{鲜橙色 (日间模式)}} / \colorbox{tracker-night}{
\textcolor{white}{暗沉色 (夜间模式)}} -- 表示存在跟踪器组件

\item \colorbox{AMSoftMagenta}{\textcolor{black}{紫色 (日间模式)}} / \colorbox{AMVeryDarkViolet}{
\textcolor{white}{深紫色 (夜间模式)}} -- 表示存在正在运行的服务。

\item \colorbox{AMDarkCyan}{\textcolor{black}{靛青色}} -- 表示当前应用程序中的所有跟踪器
已在 跟踪器指示器 标签页内被阻止。
\end{itemize}
19 hours ago
User avatar Astoritin

Translation changed
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}
网络策略 (Network policies)，简写 \textbf{Network policy}。
网络策略通常位于 Android 设置的应用详情页面中的 \textbf{移动数据和 WLAN} 这一节的下面。
该页面中并非所有策略会被授权使用 (比如三星)，以及由于缺少文档，并非所有设置都能被很好地理解。
App Manager 可以显示所有在 \href{https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/net/NetworkPolicyManager.java}{网络策略管理器} 声明的网络策略。
对 App Manager 而言位置的策略会被加上 \textit{Unknown} 前缀以及十六进制格式的策略常量名称和编号。
未知策略应报告给 App Manager 以供纳入。

网络策略允许用户配置应用的某些网络行为，而不是直接修改 IP 地址表和/或者使用防火墙应用。
然而，其提供的功能很大程度上依赖于 Android 版本和 ROM。已知网络规则列表如下所示：

\begin{enumerate}
\item \textbf{无} 或 \textbf{\texttt{POLICY\_NONE}}: (AOSP) 并未设置特定的网络策略。
系统仍可通过应用程序的性质分配规则。

\item \textbf{禁止在后台使用移动数据 (流量计费的网络)} 或 \textbf{\texttt{POLICY\_REJECT\_METERED\_BACKGROUND}}: (AOSP) 当应用在后台运行时，禁止使用移动数据 (流量计费的网络)。

\item \textbf{允许后台使用移动数据 (流量计费的网络)，甚至在流量节省程序开启时} 或 \textbf{\texttt{POLICY\_ALLOW\_METERED\_BACKGROUND}}: (AOSP) 允许后台使用移动数据 (流量计费的网络)，甚至是启用流量节省模式的情况下。

\item \textbf{禁止移动数据 (蜂窝数据)} 或 \textbf{\texttt{POLICY\_REJECT\_CELLULAR}} (Android 11+) 或 \textbf{\texttt{POLICY\_REJECT\_ON\_DATA}} (直到 Android 10): (Lineage OS) 禁止使用移动/蜂窝数据。
向配置的应用程序发出网络不可用的信号，就像未激活移动数据 (蜂窝数据)一样。

\item \textbf{禁止 VPN 数据} 或 \textbf{\texttt{POLICY\_REJECT\_VPN}} (Android 11+) 或 \textbf{\texttt{POLICY\_REJECT\_ON\_VPN}} (直到 Android 10): (Lineage OS) 禁止使用 VPN 数据。
向配置的应用程序发出网络不可用的信号，就像未激活 VPN 一样。

\item \textbf{禁止 Wi-Fi 数据} 或 \textbf{\texttt{POLICY\_REJECT\_WIFI}} (Android 11+) 或 \textbf{\texttt{POLICY\_REJECT\_ON\_WLAN}} (直到 Android 10): (Lineage OS) 禁止使用 Wi-Fi 数据。
向配置的应用程序发出网络不可用的信号，就像该设备未连接到 Wi-Fi 网络一样。

\item \textbf{禁用网络访问} 或 \textbf{\texttt{POLICY\_REJECT\_ALL}} (Android 11+) 或 \textbf{\texttt{POLICY\_NETWORK\_ISOLATED}} (直到 Android 10): (Lineage OS) 禁止所有情况下的网络访问。
这与执行上述其他三项策略不同，推荐对可疑/狡诈的应用而言使用该策略。.
若该策略被执行，则没有必要执行其他策略。

\item \textbf{\texttt{POLICY\_ALLOW\_METERED\_IN\_ROAMING}}: (三星) 可能是在漫游时允许使用移动数据 (流量计费的网络)。
目前不知道其确切含义。

\item \textbf{\texttt{POLICY\_ALLOW\_WHITELIST\_IN\_ROAMING}}: (三星) 可能是在漫游时允许使用网络。
目前不知道其确切含义。

\item \textbf{禁止使用移动数据 (流量计费的网络)} 或 \textbf{\texttt{POLICY\_REJECT\_METERED}}: (摩托罗拉) 若是移动数据 (流量计费的网络) 则禁止使用网络。

\item \textbf{禁止使用后台数据} 或 \textbf{\texttt{POLICY\_REJECT\_BACKGROUND}}: (摩托罗拉) 禁止后台使用数据。

\item \textbf{禁用网络访问} or \textbf{\texttt{POLICY\_REJECT\_ALL}}: (摩托罗拉) 禁止所有的网络访问。
与 Lineage OS 类似，会通过 iptables (防火墙) 阻止网络连接。但不知道它是否向配置的应用程序发出网络不可用的信号。
\end{enumerate}

\begin{tip}{笔记注释}
相应的 Lineage OS 补丁如下：
\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}
19 hours ago
User avatar Astoritin

Translation changed
Bloatware are the unnecessary apps supplied by the vendor or OEM and are usually system apps. These apps are often used
to track users and collect user data which they might sell for profits. System apps do not need to request any
permission in order to access device info, contacts and messaging data, and other usage info such as your phone usage
habits and everything you store on your shared storage(s).

The bloatware may also include Google apps (such as Google Play Services, Google Play Store, Gmail, Google, Messages,
Dialer, Contacts), Facebook apps (the Facebook app consists of four or five apps), Facebook Messenger, Instagram,
Twitter and many other apps which can also track users and/or collect user data without consent given that they all are
system apps. You can disable a few permissions from the Android settings but be aware that Android settings hides almost
every permission any security specialist would call potentially \emph{dangerous}.

If the bloatware were user apps, you could easily uninstall them either from Android settings or AM. Uninstalling system
apps is not possible without root permission. You can also uninstall system apps using ADB, but it may not work for all
apps. AM can uninstall system apps with root or ADB (the latter with certain limitations, of course), but these methods
cannot \emph{remove} the system apps completely as they are located in the \emph{system} partition which is a read-only
partition. If you have root, you can remount this partition to manually \emph{purge} these apps but this will break Over
the Air (OTA) updates since data in the system partition has been modified. There are two kind of updates, delta
(small-size, consisting of only the changes between two versions) and full updates. You can still apply full updates,
but the bloatware will be installed again, and consequently, you have to delete them all over again. Besides, not all
vendors provide full updates.

Another solution is to disable these apps either from Android settings (no-root) or AM, but certain services can still
run in the background as they can be started by other system apps using Inter-process Communication (IPC). One possible
solution is to disable all bloatware until the service has finally stopped (after a restart). However, due to heavy
modifications of the Android frameworks by the vendors, removing or disabling certain bloatware may cause the System UI
to crash or even cause bootloop, thus, (soft) bricking your device. You may search the web or consult the fellow users
to find out more about how to debloat your device.

From v2.5.19, AM has a new feature called \hyperref[sec:profile-page]{profiles}. The
\hyperref[sec:profiles-page]{profiles page} has an option to create new profiles from one of the presets. The presets
consist of debloating profiles which can be used as a starting point to monitor, disable, and remove the bloatware from
a proprietary Android operating system.

\begin{warning}{Note}
In most cases, you cannot completely debloat your device. Therefore, it is recommended that you use a custom ROM
free from bloatware such as Graphene OS, Lineage OS or their derivatives.
\end{warning}
臃肿软件 (Bloatware，国内也称之为预装软件) 是由供应商 (vendor) 或 原始设备制造商 (OEM) 提供的不必要应用，并且通常情况下是系统应用。
这些应用经常用于跟踪用户和收集用户数据以出售并从中获利。
系统应用并不需要请求任何权限对设备信息、通讯录和信息数据进行访问，
以及其他使用情况信息，诸如你的手机使用习惯和你在共享存储器存储的一切内容。

臃肿软件 (Bloatware) 也可能包括 Google 应用 (诸如 Google Play 服务、Google Play 商店、Gmail、Google、信息、电话、通讯录)、
Facebook 应用 (Facebook应用由四或者五个应用组成)、Facebook Messenger、Instagram、Twitter 以及许多其他可跟踪用户
和/或未经许可收集用户数据的应用，并且他们全部都是系统应用。
你可以从 Android 设置中禁用一些权限。
但是请注意，Android 设置中隐藏了几乎全部的权限，任何专家都会称其为潜在 \emph{危险}。

若臃肿软件 (Bloatware) 为用户应用，则你可以通过 Android 设置或 App Manager 轻易卸载它们。
无 Root 权限时无法卸载系统应用。你也可以通过 ADB 卸载系统应用，但这并不会对所有应用有效。
App Manager 能够通过 Root 或者 ADB 卸载系统应用 (当然，后者存在某些限制)，
但由于它们位于只读的 \emph{system} 分区，这些方法无法完全 \emph{移除} 系统应用。
如果你有 Root 权限，你可以手动重新挂载该分区并 \emph{清除} 这些应用，
但因为系统分区数据被修改，会破坏 OTA 更新 (Over the Air，无线下载)。
对 Android 而言有两种更新方式，增量更新 (delta) (占用小，仅包括两个版本之间的变化) 和全量更新。
你仍可使用全量更新，但臃肿软件 (Bloatware) 会被再次安装，
结果你不得不再次删除它们。此外，也不是所有的供应商会提供全量更新。

另一个解决方案就是从 Android 设置 (无 Root) 或 App Manager 中禁用它们，
但由于它们能被其他系统应用通过进程间通信 (IPC，Inter-process Communication) 启动，某些服务仍然能在后台运行。
一个可能的解决方案是禁用所有的臃肿软件 (Bloatware) 直到服务最终停止 (重新启动后)。
然而，由于 Android 框架被供应商各种魔改 (相当重度的胡乱修改)，移除或禁用某些臃肿软件 (Bloatware) 可能会导致系统界面崩溃
甚至是引导循环 (bootloop，手机不断重启，卡在开机第一屏或者开机动画但无法正常进入系统)，
因此，你的手机会变(软)砖。你可能需要上网搜寻资料或咨询同 (机型) 用户以找到救砖办法。

从 v2.5.19 开始，App Manager 新增 \hyperref[sec:profile-page]{配置文件} 功能。
\hyperref[sec:profiles-page]{配置文件页面} 具有一个选项，可从其中一个预设创建新的配置文件。
该预设包括去臃肿软件 (Debloat) 的配置文件，
可作为从专有 Android 操作系统监控、禁用、移除臃肿软件 (Bloatware) 的起点。

\begin{warning}{笔记注释}
绝大多数情况下，你无法将臃肿软件 (Bloatware) 完全从你的设备中移除。
因此，推荐你使用第三方 ROM，诸如 Graphene OS、Lineage OS 或其他衍生 ROM 以摆脱臃肿软件 (Bloatware)。
\end{warning}
22 hours ago
User avatar Astoritin

Translation completed
Translation completed 22 hours ago
User avatar Astoritin

Translation added
External format is used for importing or exporting rules in App Manager.
\begin{Verbatim}
<package_name> <component_name> <type> <mode>|<component_status>|<is_granted>
\end{Verbatim}
This the format is essentially the same as above except for the first item which is the name of the package.

\begin{danger}{Caution}
The exported rules have a different format than the internal one and should not be copied directly to the
\textbf{conf} folder.
\end{danger}
外部格式用于 App Manager 导入或导出规则。
\begin{Verbatim}
<package_name> <component_name> <type> <mode>|<component_status>|<is_granted>
\end{Verbatim}
除了第一项是包的名称外，其格式与上述 (内部格式) 基本相同。

\begin{danger}{小心}
导出的规则具有与内部格式不同的格式，
不应该被直接复制到 \textbf{conf} 文件夹。
\end{danger}
22 hours ago
User avatar Astoritin

Translation added
The format below is used internally within App Manager and is \textit{not compatible with the external format.}
\begin{Verbatim}
<name> <type> <mode>|<component_status>|<is_granted>
\end{Verbatim}
Here:
\begin{itemize}
\item \texttt{<name>} -- Component/permission/app op name (in case of app op, it could be string or integer)
\item \texttt{<type>} -- One of the \texttt{ACTIVITY}, \texttt{RECEIVER}, \texttt{PROVIDER}, \texttt{SERVICE},
\texttt{APP\_OP}, \texttt{PERMISSION}
\item \texttt{<mode>} -- (For app ops) The associated \hyperref[subsec:mode-constants]{mode constant}
\item \texttt{<component\_status>} -- (For components) Component status
\begin{itemize}
\item \texttt{true} -- Component has been applied (\texttt{true} value is kept for compatibility)
\item \texttt{false} -- Component hasn't been applied yet, but will be applied in future (\texttt{false} value
is kept for compatibility)
\item \texttt{unblocked} -- Component is scheduled to be unblocked
\end{itemize}
\item \texttt{<is\_granted>} -- (For permissions) Whether the permission is granted or revoked
\end{itemize}
下述格式在 App Manager 内部使用，且 \textit{与外部格式不兼容。}
\begin{Verbatim}
<name> <type> <mode>|<component_status>|<is_granted>
\end{Verbatim}
此处：
\begin{itemize}
\item \texttt{<name>} -- 组件/权限/应用操作 (App Ops) 名 (对于 App Ops，值可能为字符串或整数)
\item \texttt{<type>} -- \texttt{ACTIVITY}、 \texttt{RECEIVER}、 \texttt{PROVIDER}、 \texttt{SERVICE}、
\texttt{APP\_OP}、 \texttt{PERMISSION}的其中一个
\item \texttt{<mode>} -- (用于App Ops) 相关的 \hyperref[subsec:mode-constants]{模式常量}
\item \texttt{<component\_status>} -- (用于组件) 组件状态
\begin{itemize}
\item \texttt{true} -- 已应用组件 (\texttt{true} 值因为兼容性被保留)
\item \texttt{false} -- 尚未应用组件，但将来会生效 (\texttt{false} 值因为兼容性被保留)
\item \texttt{unblocked} -- 计划解除阻止的组件
\end{itemize}
\item \texttt{<is\_granted>} -- (用于权限) 是否授予或撤销权限
\end{itemize}
22 hours ago
User avatar Astoritin

Translation changed
AM currently supports blocking activities, broadcast receivers, content providers, services, app ops and permissions,
and in future I may add more blocking options. In order to add more portability, it is necessary to import/export all
these data.

Maintaining a database should be the best choice when it comes to storing data. For now, several \texttt{tsv} files
with each file having the name of the package and a \texttt{.tsv} extension. The file/database will be queried/processed
by the \texttt{RulesStorageManager} class. Due to this abstraction, it should be easier to switch to database or
encrypted database systems in future without changing the design of the entire project. Currently, All configuration
files are stored at \texttt{/data/data/io.github.muntashirakon.AppManager/Files/conf}.
App Manager 目前支持阻止活动、广播接收器、内容提供者、服务、应用操作 (App Ops) 和权限，
并且在将来可能会添加更多阻止选项。
为了增加更多便携性，导入/导出所有的这些数据是有必要的。

由于数据库专门用于存储数据，维护数据库是最佳选择。
目前为止有多个 \texttt{tsv} 文件，每个文件都有包名和 \texttt{.tsv} 扩展名。
\texttt{RulesStorageManager} (规则存储管理器) 类负责查询/处理相应的文件/数据库。
由于这种抽象概念，
将来在不更改整个项目设计的情况下切换到数据库或加密数据库系统会更加容易。
目前所有的配置文件
存储在 \texttt{/data/data/io.github.muntashirakon.AppManager/Files/conf}。
22 hours ago
Browse all component changes