AM Debug v4.0.0-alpha02 Run#2616
Refactor Automatically grant usage stats permission in privileged mode
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Automatically grant usage stats permission in privileged mode
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v4.0.0-alpha02 Run#2618
Update funding campaign dates
Start date: 21 Dec 2023
End date: 1 April 2024
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Update funding campaign dates
Start date: 21 Dec 2023
End date: 1 April 2024
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v4.0.0-alpha02 Run#2620
Allow launching non-exported activities in no-root/ADB mode
The “Search assistant” (usually set to Google Assistant) feature allows
setting arbitrary activity via the ‘assistant’ key-value pair stored in the
secure settings database. Hence, non-exported (that is, app private) activities
can be launched even in no-root mode by exploiting this feature. However,
modifying secure settings require android.permission.WRITE_SECURE_SETTINGS
permission which is granted automatically in ADB mode and has to be granted
manually in no-root mode via ADB.
Working procedure:
1. Check if App Manager can write to secure setting. If it can, the launch and
shortcut buttons in the Activities tab are enabled
2. Backup existing activity stored in the ‘assistant’ setting to restore it
later
3. Set the value of ‘assistant’ to the activity that the user is going to
launch
4. Trigger assistant (ADB mode), or ask the user to trigger assistant (no-root)
mode
5. Restore the value of ‘assistant’.
App Manager cannot trigger assistant on its own in no-root mode, because it has
not enough permission (requires android.permission.INEJECT_EVENTS permission
which cannot be granted to user applications).
Thanks: Theray Tharow <TharowT@Tharow.net>
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Allow launching non-exported activities in no-root/ADB mode
The “Search assistant” (usually set to Google Assistant) feature allows
setting arbitrary activity via the ‘assistant’ key-value pair stored in the
secure settings database. Hence, non-exported (that is, app private) activities
can be launched even in no-root mode by exploiting this feature. However,
modifying secure settings require android.permission.WRITE_SECURE_SETTINGS
permission which is granted automatically in ADB mode and has to be granted
manually in no-root mode via ADB.
Working procedure:
1. Check if App Manager can write to secure setting. If it can, the launch and
shortcut buttons in the Activities tab are enabled
2. Backup existing activity stored in the ‘assistant’ setting to restore it
later
3. Set the value of ‘assistant’ to the activity that the user is going to
launch
4. Trigger assistant (ADB mode), or ask the user to trigger assistant (no-root)
mode
5. Restore the value of ‘assistant’.
App Manager cannot trigger assistant on its own in no-root mode, because it has
not enough permission (requires android.permission.INEJECT_EVENTS permission
which cannot be granted to user applications).
Thanks: Theray Tharow <TharowT@Tharow.net>
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v4.0.0-alpha02 Run#2621
Keep freeze/unfreeze launcher and profile applier in history stack
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Keep freeze/unfreeze launcher and profile applier in history stack
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v4.0.0-alpha02 Run#2622
Implement multi-user mode and no-root fallback in activity shortcuts
If App Manager has enough permissions, it will use “Search assistant” to
launch the activity when a shortcut is triggered.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Implement multi-user mode and no-root fallback in activity shortcuts
If App Manager has enough permissions, it will use “Search assistant” to
launch the activity when a shortcut is triggered.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v3.1.3 Run#2624
Fix crashing in the AppInfo tab
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Fix crashing in the AppInfo tab
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v3.1.4 Run#2628
Prepare for v3.1.4
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Prepare for v3.1.4
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
I am basically working on improving libadb-android for now, as there seem to be a growing number of ADB users. This may take a week or so.
AM Debug v4.0.0-alpha02 Run#2629
Avoid detecting port number if Wi-Fi not active
When wireless debugging is enabled but Wi-Fi is inactive, App Manager will
simply fall back to the no-root mode instead of trying to connect to ADB.
This will not alter the current mode of operation. Instead, it will display
no-root as the inferred mode operation.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Avoid detecting port number if Wi-Fi not active
When wireless debugging is enabled but Wi-Fi is inactive, App Manager will
simply fall back to the no-root mode instead of trying to connect to ADB.
This will not alter the current mode of operation. Instead, it will display
no-root as the inferred mode operation.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v4.0.0-alpha02 Run#2630
LogViewer Prevent an NPE thrown when device configuration changes
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
LogViewer Prevent an NPE thrown when device configuration changes
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>