AM Debug v4.0.0-beta01 Run#2768
Usage Attempt to fix the usage time calculation method
The usage events returned by the UsageStatsManager was assumed to be in order of
their timestamp which does not seem to be true and resulted in missing a few
events due to the standard calculation method, that is, calculating the time
difference between activity resume and pause time. In addition, it appears that
the system may log activity stop time without logging any pause time (a typical
cycle would be resume --> pause --> stop) causing further miss of events. All of
these issues are addressed by sorting the events in order of their timestamp as
well as measure the time difference between resume and stop times instead of
resume and pause times. However, this does not solve the problems with access
count since it is still is a summation of the resume-stop cycles.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Usage Attempt to fix the usage time calculation method
The usage events returned by the UsageStatsManager was assumed to be in order of
their timestamp which does not seem to be true and resulted in missing a few
events due to the standard calculation method, that is, calculating the time
difference between activity resume and pause time. In addition, it appears that
the system may log activity stop time without logging any pause time (a typical
cycle would be resume --> pause --> stop) causing further miss of events. All of
these issues are addressed by sorting the events in order of their timestamp as
well as measure the time difference between resume and stop times instead of
resume and pause times. However, this does not solve the problems with access
count since it is still is a summation of the resume-stop cycles.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
❤4👍1🎉1
AM Debug v4.0.0-beta01 Run#2770
UITracker Display current activity name when possible
In addition to displaying class name and its hierarchies, the window will now
display the activity name when there's is an activity (not all windows are
activities). This requires the usage stats permission which is enforced here
even if it's disabled in the settings. This is because this feature is meant to
be used as a useful tool separated from the rest of the app, but with some level
of integration.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
UITracker Display current activity name when possible
In addition to displaying class name and its hierarchies, the window will now
display the activity name when there's is an activity (not all windows are
activities). This requires the usage stats permission which is enforced here
even if it's disabled in the settings. This is because this feature is meant to
be used as a useful tool separated from the rest of the app, but with some level
of integration.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍4🎉3❤1🔥1
AM Debug v4.0.0-beta01 Run#2771
Usage Attempt to fix the “times opened” value
In order to calculate a more reliable number of times an app was opened, the
time difference between each activity opening and closing are now relaxed. So,
when the user navigates to another activity from an activity belonging to the
same app and the time difference is less than 500 ms, the time difference is
added to the total usage time. This calculation is technically more precise than
the system's own open count because certain navigation involves the use of
system UI (e.g., the arrow in the gesture navigation is emitted from the System
UI app and should be considered as such) which are ignored. However, the issues
with choosing 500 ms (half of a second) time difference are as follows:
1. Due to an user waiting a long time to trigger the back gesture or simply bad
coding, an app may take more than this time to open an activity which will
cause them to be listed as two accesses.
2. Some apps support multiple windows. If the user opens another activity in a
new window shortly after opening the first activity, the two accesses may be
counted as one instead of two.
These events are considered extraordinary and can be negligible in a real-life
setting.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Usage Attempt to fix the “times opened” value
In order to calculate a more reliable number of times an app was opened, the
time difference between each activity opening and closing are now relaxed. So,
when the user navigates to another activity from an activity belonging to the
same app and the time difference is less than 500 ms, the time difference is
added to the total usage time. This calculation is technically more precise than
the system's own open count because certain navigation involves the use of
system UI (e.g., the arrow in the gesture navigation is emitted from the System
UI app and should be considered as such) which are ignored. However, the issues
with choosing 500 ms (half of a second) time difference are as follows:
1. Due to an user waiting a long time to trigger the back gesture or simply bad
coding, an app may take more than this time to open an activity which will
cause them to be listed as two accesses.
2. Some apps support multiple windows. If the user opens another activity in a
new window shortly after opening the first activity, the two accesses may be
counted as one instead of two.
These events are considered extraordinary and can be negligible in a real-life
setting.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍7❤2
App Manager | DEBUG
AM Debug v4.0.0-beta01 Run#2771 Usage Attempt to fix the “times opened” value In order to calculate a more reliable number of times an app was opened, the time difference between each activity opening and closing are now relaxed. So, when the user navigates…
Note: In some ROMs, gestures are handled by the Launcher instead of System UI. So, you may see the Launcher being opened several hundred times throughout the day but with really small usage. This may seem out of place, but the report is correct.
👍10❤1
AM Debug v4.0.0-beta01 Run#2772
AppDetails Reduce the amount of internal refreshes
Reload on the relevant sections instead of refreshing the entire UI.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AppDetails Reduce the amount of internal refreshes
Reload on the relevant sections instead of refreshing the entire UI.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
❤1👍1🔥1
AM Debug v4.0.0-beta01 Run#2773
Usage Fix view recycling issue in the RecyclerView
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Usage Fix view recycling issue in the RecyclerView
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍3❤1🔥1
AM Debug v4.0.0-beta01 Run#2774
Refactor Attempt to fix the spinner text color in M3 dynamic theming
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Attempt to fix the spinner text color in M3 dynamic theming
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍5❤1
Weblate has gone insane, once again. It started replacing whitespaces with the unicode equivalent
\u0020 causing issues in multiple places. So, I need to merge 91 commits and take care of these at the same time. My initial finding is that it’s replacing the newline characters with \u0020 (space).🔥5😱2
AM Debug v4.0.0-beta01 Run#2775
Locale Update translation for French
Currently translated at 100.0% (6 of 6 strings)
Translation: App Manager/Disclaimer
Translate-URL: https://hosted.weblate.org/projects/app-manager/disclaimer/fr/
Signed-off-by: acress1 <cress1@atcat.fr>
Locale Update translation for French
Currently translated at 100.0% (6 of 6 strings)
Translation: App Manager/Disclaimer
Translate-URL: https://hosted.weblate.org/projects/app-manager/disclaimer/fr/
Signed-off-by: acress1 <cress1@atcat.fr>
AM Debug v4.0.0-beta01 Run#2776
Locale Update translation for Hindi
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Locale Update translation for Hindi
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v4.0.0-beta01 Run#2777
Refactor Fix suspending packages in Android 14 r29 onwards
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Fix suspending packages in Android 14 r29 onwards
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
👍3
It came to my attention that recent Android versions report sensors to be disabled despite them being enabled. One solution is visiting the app info page in App Manager while the target app is open. We'll add a few more options in the future to make it easier for people to disable sensors in apps.
👍7❤1🎉1