App Manager | DEBUG
AM Debug v2.7.0 Run#1662 Installer Support installing APK with proof of rotation Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Examples of APK with proof of rotation:
1. Google Play Store (25.8.18) (No proof of rotation)
2. Google Play Store (28.8.17) (With a different signature and two proofs of rotation)
1. Google Play Store (25.8.18) (No proof of rotation)
2. Google Play Store (28.8.17) (With a different signature and two proofs of rotation)
AM Debug v2.7.0 Run#1663
Installer Fix signer detection when the app is being reinstalled
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Installer Fix signer detection when the app is being reinstalled
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1664
AppDetails Fix crashes if a component isn't found
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AppDetails Fix crashes if a component isn't found
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
🔥2
AM Debug v2.7.0 Run#1665
AppDetails Fix displaying components more than once
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AppDetails Fix displaying components more than once
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1666
MagiskHide Support for multi-process apps
Like the Magisk app, it is possible to hide Magisk root from the selected
processes in a multi-process app in the App Info page. It is also possible to
back up and restore them (and this does not depend on whether they are
configured within App Manager or not) when “Back up extras” option is selected.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
MagiskHide Support for multi-process apps
Like the Magisk app, it is possible to hide Magisk root from the selected
processes in a multi-process app in the App Info page. It is also possible to
back up and restore them (and this does not depend on whether they are
configured within App Manager or not) when “Back up extras” option is selected.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
🔥1
App Manager | DEBUG
AM Debug v2.7.0 Run#1666 MagiskHide Support for multi-process apps Like the Magisk app, it is possible to hide Magisk root from the selected processes in a multi-process app in the App Info page. It is also possible to back up and restore them (and this…
Note that AM does not apply any SafetyNet fixes. If you need it, you can try Danny Lin’s Universal SafetyNet Fix.
GitHub
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
AM Debug v2.7.0 Run#1667
AppInfo Display extra process info in MagiskHide
Apart from the typical checkbox to enable or disable a process, display whether
a process is isolated and/or running.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AppInfo Display extra process info in MagiskHide
Apart from the typical checkbox to enable or disable a process, display whether
a process is isolated and/or running.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1668
Refactor Fix various issues regarding component blocking
- Fixed storing IFW rules.
- Fixed crashes if a component is failed to be enabled/disabled.
- Cleanup unused logic.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Fix various issues regarding component blocking
- Fixed storing IFW rules.
- Fixed crashes if a component is failed to be enabled/disabled.
- Cleanup unused logic.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
🔥6
AM Debug v2.7.0 Run#1669
AppOps Fix permission issues
- Fixed inability to allow/ignore an app op if the corresponding permission is
a read-only permission.
- Prevent an attempt to grant/revoke the corresponding permission if it isn't
declared in the app's manifest.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AppOps Fix permission issues
- Fixed inability to allow/ignore an app op if the corresponding permission is
a read-only permission.
- Prevent an attempt to grant/revoke the corresponding permission if it isn't
declared in the app's manifest.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍2🔥2
App Manager | DEBUG
ADB Shell v1.0 DEBUG#2.apk
ADB Shell v2.1.0 DEBUG#3.apk
5.1 MB
Adb Shell v2.1.0 Debug Run#3
- Discover and connect to ADB automatically
- Update license (now under GPL-3.0 and Apache-2.0)
- Update Spake2 (fix memory leaks)
- Discover and connect to ADB automatically
- Update license (now under GPL-3.0 and Apache-2.0)
- Update Spake2 (fix memory leaks)
App Manager | DEBUG
ADB Shell v2.1.0 DEBUG#3.apk
Adb Shell v2.1.0 Debug#4.apk
5.3 MB
Adb Shell v2.1.0 Debug Run#4
- Automatically detect port number while paring
- Migrate to Material Design 3
- Automatically detect port number while paring
- Migrate to Material Design 3
How should I adopt the new Material Design 3 in App Manager?
Final Results
16%
Keep the colours as is.
84%
Adopt dynamic colours.
🔥9👎1
App Manager | DEBUG
How should I adopt the new Material Design 3 in App Manager?
I think we’re quite clear on what the most users want. Since somebody down-voted on the poll, I believe it is necessary to clarify things a bit regarding why I’ve been migrating to M3 only a few days after it’s been released:
The Material Design 2 has too many flaws and inconsistencies. I mean I’ve had to make many customizations just to make things look good, but even then, it wasn’t enough as I was modernizing the UI by adding the all-new technologies such as the bottom sheet dialog or chips. But the primary issue with M2 is its colours. While it is possible to tolerate the light theme, the dark theme was too white (as complained by many). As a result, I’ve needed to apply different hacks to actually replace the light-gray colours with more black ones, and adding new components have been very difficult. With M3, the developers have done quite impressive work on the colours and consistency (although there are still some minor catches and framework-imposed limitations) which has made it easy and exciting to work on designs.
However, we will go through a series of tests before deciding on the final designs. I am trying to follow M3 guidelines as close as possible but I might have to bend rules in a few cases or places. As always, be sure to report any UI/UX issues as it is not possible to find all the issues all by myself in such a massive project as this one.
The Material Design 2 has too many flaws and inconsistencies. I mean I’ve had to make many customizations just to make things look good, but even then, it wasn’t enough as I was modernizing the UI by adding the all-new technologies such as the bottom sheet dialog or chips. But the primary issue with M2 is its colours. While it is possible to tolerate the light theme, the dark theme was too white (as complained by many). As a result, I’ve needed to apply different hacks to actually replace the light-gray colours with more black ones, and adding new components have been very difficult. With M3, the developers have done quite impressive work on the colours and consistency (although there are still some minor catches and framework-imposed limitations) which has made it easy and exciting to work on designs.
However, we will go through a series of tests before deciding on the final designs. I am trying to follow M3 guidelines as close as possible but I might have to bend rules in a few cases or places. As always, be sure to report any UI/UX issues as it is not possible to find all the issues all by myself in such a massive project as this one.
🔥5👍1