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

Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Main GPL-3.0-or-later 1% 84% 206 1,036 6,874 200 14 0 0
Disclaimer GPL-3.0-or-later 0% 0 0 0 0 0 0 0
Docs GPL-3.0-or-later 0% 51% 194 8,857 63,367 172 45 0 0

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
Language Korean
Language code ko
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 79,236,042
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,743 25,019 177,332
Approved 0% 0 0% 0 0% 0
Waiting for review 76% 1,328 59% 14,997 59% 104,853
Translated 77% 1,343 60% 15,126 60% 107,091
Needs editing 1% 28 8% 2,154 8% 15,517
Read-only 1% 15 1% 129 1% 2,238
Failing checks 3% 59 28% 7,127 28% 51,157
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 21% 372 30% 7,739 30% 54,724
Last 12 months Previous

Activity in last 12 months

133 changes 0 changes 50 changes 90 changes 16 changes 9 changes 0 changes 4 changes 84 changes 0 changes 62 changes 0 changes 15 changes 0 changes 0 changes 114 changes 12 changes 24 changes 2 changes 159 changes 0 changes 0 changes 0 changes 37 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

Quick numbers

25,019
Hosted words
1,743
Hosted strings
77%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

−1%
Hosted words
+100%
+1%
Hosted strings
+100%
−2%
Translated
+79%
—
Contributors
—
User avatar None

Resource updated
The “app/src/main/res/values/strings.xml” file was changed. yesterday
User avatar None

Resource updated
The “app/src/main/res/values/strings.xml” file was changed. 11 days ago
User avatar None

String updated in the repository
- <a href="https://github.com/zhanghai/AndroidFastScroll">AndroidFastScroll</a> (Apache 2.0)
- <a href="https://github.com/LSPosed/AndroidHiddenApiBypass">AndroidHiddenApiBypass</a> (Apache 2.0)
- <a href="https://github.com/MuntashirAkon/apk-parser">APK-parser</a> (BSD 2-Clause)
- <a href="https://github.com/MuntashirAkon/apksig-android">apksig for android</a> (Apache 2.0)
- <a href="https://github.com/REAndroid/ARSCLib">ARSCLib</a> (Apache 2.0)
- <a href="https://github.com/bcgit/bc-java">Bouncy Castle</a> (MIT)
- <a href="https://commons.apache.org/proper/commons-compress/">Commons Compress</a> (Apache 2.0)
- <a href="https://github.com/dkanada/frost">Frost</a> Icons (GPLv3.0)
- <a href="https://github.com/RikkaApps/HiddenApiRefinePlugin">HiddenApiRefinePlugin</a> (MIT)
- <a href="https://github.com/skylot/jadx">JADX</a> (Apache 2.0)
- <a href="https://github.com/MuntashirAkon/libadb-android">LibADB</a> (Apache 2.0/GPLv3.0)
- <a href="https://github.com/topjohnwu/libsu">libsu</a> (Apache 2.0)
- <a href="https://github.com/material-components/material-components-android">Material Components</a> (Apache 2.0)
- <a href="https://github.com/google/material-design-icons">Material Design Icons</a> (Apache 2.0)
- <a href="https://github.com/google/smali">smali/baksmali</a> (BSD 3-Clause and Apache 2.0)
- <a href="https://github.com/Rosemoe/sora-editor">sora-editor</a> (LGPL-2.1)
- <a href="https://github.com/MuntashirAkon/spake2-java">SPAKE2 for Java</a> (GPLv3.0)
- <a href="https://github.com/MuntashirAkon/sun-security-android">sun.security for Android</a> (GPL-2.0 "Classpath Exception")
- <a href="https://github.com/MuntashirAkon/unapkm-android">UnAPKM Android</a> (Apache 2.0)
 
11 days ago
User avatar None

Changes committed
Changes committed 3 weeks ago
User avatar None

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

String updated in the repository
Bloatware are the unnecessary pre-installed apps, usually system apps. Some of the apps are often
used to track users and collect user data which they might sell for profits. Many system apps do not
need to request any permission 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, Meta apps, and Twitter/X which can also track users
and/or collect user data without consent. You can disable a few permissions from Android settings
but be aware that Android settings hides many permissions a security researcher would call
potentially \emph{dangerous} (e.g., internet, sensor).

Were the bloatware user apps, they could be easily uninstalled either from Android settings or AM\@.
Uninstalling system apps is not possible without privileged permission, but even then, it 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 may still be able to apply full updates, but the
bloatware will be installed again, and consequently, you have to delete them all over again.

Another solution is to disable these apps either from Android settings 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. From v4.0.0, AM has a new feature called \textbf{Debloater} 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}
 
3 weeks ago
User avatar None

String updated in the repository
In order to ensure proper security, an authorization key is required. To generate a authorization key, go to \textbf{Settings} page and then \textbf{Privacy} > \textbf{Authorization Manager}.
If an authorization key has not been generated, it will be generated automatically. The key can be regenerated as required.

\begin{danger}{Caution}
Regenerating the authorization key can have some side effects such as invalidation of all the previously configured Intents.
\end{danger}
 
3 weeks ago
User avatar None

String updated in the repository
App Manager should be able to connect to ADB automatically if the mode of operation is set to
\textit{auto}, \textit{ADB over TCP} or \textit{Wireless debugging}. If this is not the case, select
\textit{Wireless debugging} in \textbf{Settings} > \hyperref[subsec:mode-of-operation]{Mode of operation}.
If App Manager fails to detect or connect to ADB, it will ask you to connect or pair ADB. Select
\textit{connect}.

Now, navigate to the \textbf{Wireless debugging} page in Android settings, and note down the port
number displayed in the page. In App Manager's dialog prompt, replace the port number with the one
you have noted earlier, and click \textit{connect}.

Once a connection has been established, you can disable \textbf{Wireless debugging} in Android settings.

\begin{danger}{Caution}
Never disable \textbf{USB Debugging} or any other additional options described in \Sref{subsec:enable-developer-options-and-usb-debugging}.
If you do this, the remote server used by App Manager will be stopped, and you may have to start all over again.
\end{danger}
작동 모드가 \textit{auto}, \textit{ADB over TCP} 또는 \textit{무선 디버깅}으로 설정된 경우 App Manager는 ADB에 자동으로 연결할 수 있어야 합니다.
그렇지 않은 경우 \hyperref[subsec:mode-of-operation]{설정 페이지}에서 \textit{무선 디버깅}을 선택하세요.
App Manager가 ADB를 감지하거나 연결하지 못하는 경우 ADB를 연결하거나 페어링하라는 대화 상자 메시지가 표시됩니다. \textit{연결}을 선택하세요.

이제 Android 설정의 \textbf{무선 디버깅} 페이지로 이동하여 페이지에 표시된 포트 번호를 기록해 두세요.
App Manager의 대화 상자 프롬프트에서 포트 번호를 이전에 기록한 번호로 바꾸고 \textit{connect}를 클릭합니다.

연결이 설정되면 Android 설정에서 \textbf{무선 디버깅}을 안전하게 비활성화할 수 있습니다.

\begin{위험}{주의} \textbf{USB 디버깅} 또는 \Sref{subsec:enable-developer-options-and-usb-debugging}에 설명된 기타 추가 옵션을 비활성화하지 마세요.
이렇게 하면 App Manager에서 사용하는 원격 서버가 중지되고 처음부터 다시 시작해야 할 수도 있습니다.
\end{위험}
3 weeks ago
User avatar None

String updated in the repository
In App Manager, navigate to \textbf{Settings} > \hyperref[subsec:mode-of-operation]{Mode of operation}
and then enable \textit{Wireless debugging}. At this, App Manager will try to establish a wireless
debugging connection automatically which will fail if it has not been paired before. Once it fails,
it will ask you to either connect or pair ADB\@. Select \textit{pair} and a new dialog will appear.
It will ask you to navigate to the \textbf{Wireless debugging} page.

\begin{tip}{Note}
As of v4.0.0, pairing is done using a notification prompt. So, if you have disabled notification
for App Manager, you must enable it first.
\end{tip}

In the \textbf{Wireless debugging} page, select \textbf{Pair device with pairing code}. At this, a
dialog containing a pairing code will be displayed. A notification asking for the pairing code will
also be visible almost instantly. Insert the pairing code in the input box in the notification
and click \textit{pair}. If the pairing is successful, App Manager will display notification with
the message ``paired'', and the dialog in the \textbf{Wireless debugging} page will be dismissed
automatically. You will also be able to see App Manager listed as an ADB client in the same page.

\begin{tip}{Notice}
If you do not use App Manager in ADB mode for a while, App Manager might be removed from the
list of clients. In that case, you have to repeat the above procedure.
\end{tip}
\textbf{무선 디버깅} 페이지를 열어 둔 상태에서 위로 스와이프하거나 전용 탐색 버튼을 사용하여 \textit{최근} 페이지로 이동한 다음 설정 로고를 클릭하여 \textit{분할 화면}을 활성화하세요. 다른 응용 프로그램을 선택하거나 시작할 때까지 기다립니다.
앱 관리자를 실행하거나 선택합니다.

이제 App Manager에서 \textbf{Settings}로 이동한 다음 \hyperref[subsec:mode-of-option]{Mode of Operation}에서 \textit{Wireless 디버깅}을 활성화합니다.
잠시 후 App Manager에서 ADB\@ 연결 또는 페어링을 요청합니다. \textit{쌍}을 선택하세요.

\textbf{무선 디버깅} 페이지(이제 분할 항목 중 맨 위에 있어야 함)에서 \textbf{페어링 코드와 장치 페어링}을 선택하세요.
이때 대화 상자 프롬프트가 표시됩니다. 페어링 코드를 기록해 두되 \textbf{DO NOT} 대화 상자 프롬프트나 창을 닫으세요.

마지막으로 앱 관리자에서 페어링 코드를 삽입하고 \textit{pair}를 클릭하세요. 포트 번호는 자동으로 감지되어야 합니다.
그렇지 않은 경우에는 포트 번호도 입력해야 합니다.

페어링에 성공하면 하단에 \textit{successful} 메시지가 표시되고 \textbf{무선 디버깅} 페이지의 대화 상자 프롬프트가 자동으로 사라지며 App Manager가 ADB 클라이언트.

\begin{tip}{주의사항} (기기에 따라) 한동안 ADB 모드에서 App Manager를 사용하지 않으면 App Manager가 목록에서 제거될 수 있습니다.
이 경우 위의 과정을 반복해야 합니다.
\end{tip}
3 weeks ago
User avatar None

String updated in the repository
In the \textbf{Developer options} page, find \textbf{Wireless debugging} and click to open it. In
the new page, turn on \textit{Use wireless debugging}. Depending on the operating system, you might
see a dialog prompt asking you to verify your decision. If that is the case, click \textit{Allow}.

\begin{tip}{Tip}
For easy access, you might want to add \textbf{Wireless debugging} in the notification tiles
section. To do this, find \textbf{Quick settings developer tiles} in the \textbf{Developer
options} page and click to open it. In the new window, enable \textit{Wireless debugging}.
In case you do not see this setting, you may find a \textbf{Wireless debugging} tile in the tile
customization panel.
\end{tip}
\textbf{개발자 옵션} 페이지에서 \textbf{무선 디버깅}을 찾아 클릭하여 엽니다. 새 페이지에서 \textit{무선 디버깅 사용}을 켜세요. 구성에 따라 결정을 확인하라는 대화 상자 프롬프트가 표시될 수 있습니다.
그렇다면 \textit{허용}을 클릭하세요.

\begin{tip}{Tip} 쉽게 액세스하려면 알림 타일 섹션에 \textbf{무선 디버깅}을 추가하는 것이 좋습니다. 이렇게 하려면 \textbf{개발자 옵션} 페이지에서 \textbf{빠른 설정 개발자 타일}을 찾아 클릭하여 엽니다.
새 창에서 \textit{무선 디버깅}을 활성화하세요. 그러나 이 옵션은 대부분의 운영 체제에서 사용할 수 없습니다.
\end{tip}
3 weeks ago
Browse all changes for this language