AM Debug v3.0.0-alpha03 Run#1791
BatchOps Hide “uninstall” option displayed mistakenly in no-root mode
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
BatchOps Hide “uninstall” option displayed mistakenly in no-root mode
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
🔥3
AM Debug v3.0.0-alpha03 Run#1792
Refactor Update libsu to 5.0.1
Libsu (by John Wu) is now the core of App Manager's privileged environment.
While libsu's core library is used as it is, nio and service libraries have
been modified to meet App Manager's needs, specifically to support both root
and ADB (as opposed to only root) with low-level access to the Linux file
system.
The new API has renewed the logic of handling file system via a remote service
which replaces the ugly API previously used to prevent a major refactoring.
Throughout App Manager, a custom path API is extensively used which provides
abstractions of Linux file system, virtual file systems as well as Storage
Access Framework (SAF). However, further refactoring is needed in order to move
the entire I/O API out of the main module.
New security features have also been copied from the mentioned library to
prevent third-party apps from snooping into the privileged environment of App
Manager. This includes the creation of remote process within App Manager (root)
or shell (ADB) as well as the prevention of snooping into the remote service
sent by the remote process by the creation of a random action (instead of a
fixed one).
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Update libsu to 5.0.1
Libsu (by John Wu) is now the core of App Manager's privileged environment.
While libsu's core library is used as it is, nio and service libraries have
been modified to meet App Manager's needs, specifically to support both root
and ADB (as opposed to only root) with low-level access to the Linux file
system.
The new API has renewed the logic of handling file system via a remote service
which replaces the ugly API previously used to prevent a major refactoring.
Throughout App Manager, a custom path API is extensively used which provides
abstractions of Linux file system, virtual file systems as well as Storage
Access Framework (SAF). However, further refactoring is needed in order to move
the entire I/O API out of the main module.
New security features have also been copied from the mentioned library to
prevent third-party apps from snooping into the privileged environment of App
Manager. This includes the creation of remote process within App Manager (root)
or shell (ADB) as well as the prevention of snooping into the remote service
sent by the remote process by the creation of a random action (instead of a
fixed one).
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍1🔥1
App Manager | DEBUG
AM Debug v3.0.0-alpha03 Run#1792 Refactor Update libsu to 5.0.1 Libsu (by John Wu) is now the core of App Manager's privileged environment. While libsu's core library is used as it is, nio and service libraries have been modified to meet App Manager's needs…
You may have to restart or reinstall App Manager after installing this update.
👍1🔥1
App Manager | DEBUG
You may have to restart or reinstall App Manager after installing this update.
Note that this is a major code refactoring since the integration of Material design 3. Root/ADB users are requested to extensively test this build. Thanks.
👍3🔥1
AM Debug v3.0.0-alpha03 Run#1793
Refactor Rename am database to apps.db and move it cache folder
apps.db is primarily used by App Manager to cache application information in
order to speed up the loading process. As a result, it should be located in the
cache folder.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Rename am database to apps.db and move it cache folder
apps.db is primarily used by App Manager to cache application information in
order to speed up the loading process. As a result, it should be located in the
cache folder.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
🔥2
App Manager | DEBUG
AM Debug v3.0.0-alpha03 Run#1793 Refactor Rename am database to apps.db and move it cache folder apps.db is primarily used by App Manager to cache application information in order to speed up the loading process. As a result, it should be located in the…
It might take sometime to load the app list due to reindexing.
🔥1
AM Debug v3.0.0-alpha03 Run#1794
Locale Update translation for Portuguese
Currently translated at 97.8% (1030 of 1053 strings)
Translation: App Manager/Main
Translate-URL: https://hosted.weblate.org/projects/app-manager/main/pt/
Signed-off-by: SC <lalocas@protonmail.com>
Locale Update translation for Portuguese
Currently translated at 97.8% (1030 of 1053 strings)
Translation: App Manager/Main
Translate-URL: https://hosted.weblate.org/projects/app-manager/main/pt/
Signed-off-by: SC <lalocas@protonmail.com>
Hosted Weblate
App Manager/Main — Portuguese
App Manager is being translated into 35 languages using Weblate. Join the translation or start translating your own project.
🔥2
AM Debug v3.0.0-alpha03 Run#1795
Docs Update Japanese and Simplified Chinese translations
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Docs Update Japanese and Simplified Chinese translations
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
🔥3
AM Debug v3.0.0-alpha03 Run#1796
AppDetails Log potential issue on creating AppDetailsViewModel
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AppDetails Log potential issue on creating AppDetailsViewModel
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍1🔥1
AM Debug v3.0.0-alpha03 Run#1797
AppDetails Fix displaying wrong component status
In the components tab, component status (blocked, disabled, enabled, etc.) is
calculated based on how it was blocked or disabled. This is particularly
applicable if the component is enabled by the application itself or by any
other means after it was blocked in App Manager. The behaviour in this case
should be as follows:
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AppDetails Fix displaying wrong component status
In the components tab, component status (blocked, disabled, enabled, etc.) is
calculated based on how it was blocked or disabled. This is particularly
applicable if the component is enabled by the application itself or by any
other means after it was blocked in App Manager. The behaviour in this case
should be as follows:
+ ------------------------------------- + ----------------------------------- +
| Blocking method | After it was enabled externally |
+ ------------------------------------- + ----------------------------------- +
| Blocked via Intent Firewall (IFW) and | It stays disabled since Intent |
| disabled via Package Manager (PM) | Firewall has higher priority. |
+ ------------------------------------- + ----------------------------------- +
| Blocked via Intent Firewall only | Same as above. |
+ ------------------------------------- + ----------------------------------- +
| Disabled via Package Manager only | It is displayed as enabled. |
+ ------------------------------------- + ----------------------------------- +
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍2🔥1
Here’s a little statistics before purging the emails sent before June 2021:
Time interval: November 2020 - May 2021
Total crash reports: 265
Total active crash reports: 3 (262 reports were deleted)
Total missing signatures reports: 26 (All reports were deleted)
Time interval: November 2020 - May 2021
Total crash reports: 265
Total active crash reports: 3 (262 reports were deleted)
Total missing signatures reports: 26 (All reports were deleted)
👍1🔥1
AM Debug v3.0.0-alpha03 Run#1798
Scanner Prevent reloading trackers and libraries on pressing back button
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Scanner Prevent reloading trackers and libraries on pressing back button
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍2🔥1
HELP WANTED.
There shall be several release candidates as mentioned earlier with the first release to be made real soon. However, the primary release could be delayed as I do not have enough time to write changelogs (there are about 1400 commits that I need to go through in order to write a changelog) and update screenshots in the repository.
If there is anybody willing to contribute in this two topics in their free time, you can create a discussion or open an issue on GitHub. The commits, as you might have noticed already, are quite readable unlike most other projects and since this is a major release, you’re only expected to include only the major changes (you can see the old changelogs as an example). The format doesn’t have to be in Latex, you can use RTF or Markdown or even docx format (I can convert it later). If you have further questions regarding a particular topic while writing the changelog, you can always ask me in the issue/discussion that you’re going to open. Thanks.
There shall be several release candidates as mentioned earlier with the first release to be made real soon. However, the primary release could be delayed as I do not have enough time to write changelogs (there are about 1400 commits that I need to go through in order to write a changelog) and update screenshots in the repository.
If there is anybody willing to contribute in this two topics in their free time, you can create a discussion or open an issue on GitHub. The commits, as you might have noticed already, are quite readable unlike most other projects and since this is a major release, you’re only expected to include only the major changes (you can see the old changelogs as an example). The format doesn’t have to be in Latex, you can use RTF or Markdown or even docx format (I can convert it later). If you have further questions regarding a particular topic while writing the changelog, you can always ask me in the issue/discussion that you’re going to open. Thanks.
👍2🔥2😱2