AM Debug v2.7.0 Run#1277
Fallback to no-root if root/ADB not detected
Ensure thread safety in the server-related codes.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Fallback to no-root if root/ADB not detected
Ensure thread safety in the server-related codes.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1278
Refactor Fix false-positive in root-detection
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Fix false-positive in root-detection
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1279
Update trackers and libraries
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Update trackers and libraries
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
How to use Wireless Debugging in App Manager
Due to licensing issues, I couldn’t implement ADB pairing (we're changing license to allow that). However, if you have already configured ADB over TCP with the remember this PC option checked, you can also use the wireless debugging feature as App Manager has already been paired (you’d see AppManager in the paired list). Now, go to mode of operation section of the settings page and select Wireless Debugging. If everything goes well, App Manager should ask for a port number. After that, you’d see wireless debugging connected notification sent by the system. Like ADB over TCP, App Manager runs a background server for wireless debugging too. As a result, you can disable wireless debugging once the connection is successful and App Manager is working as expected.
Troubleshooting. If App Manager behaves randomly, just restart App Manager by removing it from the recents. If the background server is not running App Manager will ask for a port number. In this case, enable wireless debugging again and insert the port number displayed there.
Due to licensing issues, I couldn’t implement ADB pairing (we're changing license to allow that). However, if you have already configured ADB over TCP with the remember this PC option checked, you can also use the wireless debugging feature as App Manager has already been paired (you’d see AppManager in the paired list). Now, go to mode of operation section of the settings page and select Wireless Debugging. If everything goes well, App Manager should ask for a port number. After that, you’d see wireless debugging connected notification sent by the system. Like ADB over TCP, App Manager runs a background server for wireless debugging too. As a result, you can disable wireless debugging once the connection is successful and App Manager is working as expected.
Troubleshooting. If App Manager behaves randomly, just restart App Manager by removing it from the recents. If the background server is not running App Manager will ask for a port number. In this case, enable wireless debugging again and insert the port number displayed there.
AM Debug v2.7.0 Run#1280
SharedPref Make the key name in the editor dialog scrollable and selectable
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
SharedPref Make the key name in the editor dialog scrollable and selectable
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1281
Installer Remove AMPackageInstaller in favour of PackageInstallerCompat
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Installer Remove AMPackageInstaller in favour of PackageInstallerCompat
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1282
Merge remote-tracking branch 'weblate/master'
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Merge remote-tracking branch 'weblate/master'
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1283
Locale Update translation for Chinese (Traditional)
Currently translated at 98.0% (905 of 923 strings)
Translation: App Manager/Main
Translate-URL: https://hosted.weblate.org/projects/app-manager/main/zh_Hant/
Signed-off-by: Jason <jason5545@gmail.com>
Locale Update translation for Chinese (Traditional)
Currently translated at 98.0% (905 of 923 strings)
Translation: App Manager/Main
Translate-URL: https://hosted.weblate.org/projects/app-manager/main/zh_Hant/
Signed-off-by: Jason <jason5545@gmail.com>
Hosted Weblate
App Manager/Main — Chinese (Traditional)
App Manager is translated into 27 languages using Weblate. Join the translation or start translating your own project.
AM Debug v2.7.0 Run#1284
Installer Extract OBB files for the given user
Previously, OBB files are extracted only to the current user instead of the given user.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Installer Extract OBB files for the given user
Previously, OBB files are extracted only to the current user instead of the given user.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1285
Backup Backup external folders for the given users
Previously, App Manager was unable to backup external folders for users other than the current user.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Backup Backup external folders for the given users
Previously, App Manager was unable to backup external folders for users other than the current user.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1286
Installer Handle apps having a new signature uninstalled with DELETE_KEEP_DATA
When an app was uninstalled with DELETE_KEEP_DATA flag enabled and the app is
now being reinstalled with a different signature, the following situations have
to be considered:
1. For system apps, the APK is still present in the system as usual, and so
are the data. The proper way to handle this is to warn the user that the new
app can't be installed.
2. For user apps, the APK was deleted, but the signature was still kept.
In such case, the user will be warned that the new app cannot be installed.
It was found out that the app can still be uninstalled in all mode of
operations but the APK isn't actually present, and if the app is uninstalled
(again), Android system will no longer report it even when the list of apps
are fetched using the MATCH_UNINSTALLED_PACKAGES flag. This could be
problematic as there would be no way to find out the real cause if such
app is attempted to be installed with a different signature.
3. For user apps installed on multiple profiles but uninstalled from only one
profile, things are more complicated. However, they are handled like (2) in
order to avoid further complications.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Installer Handle apps having a new signature uninstalled with DELETE_KEEP_DATA
When an app was uninstalled with DELETE_KEEP_DATA flag enabled and the app is
now being reinstalled with a different signature, the following situations have
to be considered:
1. For system apps, the APK is still present in the system as usual, and so
are the data. The proper way to handle this is to warn the user that the new
app can't be installed.
2. For user apps, the APK was deleted, but the signature was still kept.
In such case, the user will be warned that the new app cannot be installed.
It was found out that the app can still be uninstalled in all mode of
operations but the APK isn't actually present, and if the app is uninstalled
(again), Android system will no longer report it even when the list of apps
are fetched using the MATCH_UNINSTALLED_PACKAGES flag. This could be
problematic as there would be no way to find out the real cause if such
app is attempted to be installed with a different signature.
3. For user apps installed on multiple profiles but uninstalled from only one
profile, things are more complicated. However, they are handled like (2) in
order to avoid further complications.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>