It’s weird that it works when I do this manually and it doesn’t when I do this through the app. The modified entry is being deleted during the next boot for some reason. I must be missing something. However, this (and the SAF entries) can easily be modified without needing for a restart once zygisk comes out (but we still have to support the other non-zygisk users).

AM Debug v2.7.0 Run#1604

Scanner Scan JNI libraries for potential trackers and libraries

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1605

Backup Replace : (colon) in backup names

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1606

Refactor Fix sanitizing . (dot) prefix from a file name

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1607

Profile Display all possible apps in the selection list

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1608

Update trackers and native libraries

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1609

Scanner Apply proper escaping to patterns, improve efficiency

According to Android documentations, \. in XML should be literally \ and
., but in reality, it is only .. To mitigate this issue, the \ (escape)
characters in the regular expressions are further escaped. In addition,
patterns are compiled only once in order to improve efficiency while matching
the native libraries.

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1610

Scanner Skip fetching package info if it is a split

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1611

AppInfo Add APK selector for scanner if there are splits

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1612

AppDetails Enable advanced options for disabling components

On long clicking on the block/unblock button, a context menu would appear where
the user can block/enable/disable a component in various ways, such as--
1. Block using Intent Firewall (IFW) and PackageManager (PM)
2. Block using IFW only
3. Disable using PM
4. Enable using PM
5. Set to default (as specified in the manifest) via PM

It should be noted that, operation no. 2 does not change component status i.e.,
if it is previously disabled, it will remain disabled. However, all actions
modify the IFW rules (if applicable) as they should be.

Regarding tests, the tests have not been updated to include the new scheme.
As a result, there is no guarantee that the new scheme is foolproof.

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>

AM Debug v2.7.0 Run#1613

Setting Add option to select default blocking method

There are three blocking methods to choose from:
1. Blocking using Intent Firewall and Package Manager (recommended)
2. Blocking using Intent Firewall (not recommended)
3. Disable using Package Manager (recommended in ADB modes for test-only apps).

Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>