In the coming weeks, I’ll be applying for higher study (MSc/PhD, MSc preferred) with fully funded scholarship (as TA/RA, TA preferred). (Those who did this before know quite well that) this is a tedious task, and I’ve already taken leave for the entire month from my regular job. I’ll also be taking a break from open source development. Now, as some of you may have guessed, my particular interest lies in privacy, security and user experience (UX). If you happen to know any professor of these fields with available funding, you can contact me via my email <muntashirakon@riseup.net> where I’ll always be available. See you in the next month.
👍25🎉13🔥3❤1😱1
App Manager | DEBUG
In the coming weeks, I’ll be applying for higher study (MSc/PhD, MSc preferred) with fully funded scholarship (as TA/RA, TA preferred). (Those who did this before know quite well that) this is a tedious task, and I’ve already taken leave for the entire month…
UPDATE. So far, everything is going as planned. If everything goes smoothly, I will resume development after mid-November, otherwise after mid-December.
👍20❤7
AM Debug v4.0.0-alpha02 Run#2609
Refactor Fix blocking components in Android 14
Co-authored-by: Craig Gomez <craigacgomez@gmail.com>
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Fix blocking components in Android 14
Co-authored-by: Craig Gomez <craigacgomez@gmail.com>
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
❤6👍5
App Manager | DEBUG
AM Debug v4.0.0-alpha02 Run#2609 Refactor Fix blocking components in Android 14 Co-authored-by: Craig Gomez <craigacgomez@gmail.com> Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
It's not like I am back or something. This seems to be crucial for A14 users, and so, I provided a fix for it. This fix will also be available on both stable and alpha channel after 11 November.
❤13👍3😁2🤩2
AM Debug v4.0.0-alpha02 Run#2611
Refactor Move Path classes to libcore:io module
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Move Path classes to libcore:io module
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
🔥5
AM Debug v4.0.0-alpha02 Run#2612
Update dependencies
- Gradle to 8.3
- ARSCLib to latest commit
- Fastscroll to 1.3.0
- Sora Editor to 0.22.1
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Update dependencies
- Gradle to 8.3
- ARSCLib to latest commit
- Fastscroll to 1.3.0
- Sora Editor to 0.22.1
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍1
AM Debug v4.0.0-alpha02 Run#2613
Refactor Fix launching privileged service on OnePlus devices
Thanks: John Wu
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Fix launching privileged service on OnePlus devices
Thanks: John Wu
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
🤩5
AM Debug v4.0.0-alpha02 Run#2614
Refactor Disable image dex2oat as it can be quite slow in some ROMs if triggered
Thanks: weishu (tiann)
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Disable image dex2oat as it can be quite slow in some ROMs if triggered
Thanks: weishu (tiann)
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍11
AM Debug v4.0.0-alpha02 Run#2615
Installer Allow installing system apps with a different signature
The “Install only” button is enabled for system apps when the signatures
are different. This is useful for only those who have disabled signature
verification using methods such as CorePatch.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Installer Allow installing system apps with a different signature
The “Install only” button is enabled for system apps when the signatures
are different. This is useful for only those who have disabled signature
verification using methods such as CorePatch.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍7❤2😱1
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>
👍7
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>
👍8🔥1🤩1
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>
👍4🔥2❤1