Performance issues with latest 4.1.

[HarriBuh]

Please check before submitting an issue

• I know what my device, OS and App Manager versions are
• I know how to take logs
• I know that generating a report, in whole part or in part, using AI/LLM is prohibited
• I know how to reproduce the issue which may not be specific to my device

Describe the bug

Since the update to 4.1.0, the app has become significantly slower. This is particularly noticeable when refreshing the app list. To be honest, I'm not sure if the loading process even completes successfully in the case described—I usually lose patience and cancel the process after about 20 seconds, then manually close the app, clear the cache, and restart it. That fixes the issue, but of course it's not a permanent solution.

To Reproduce

1. Open App/ App list
2. Swipe down to start the refresh process
3. Notice the "bug"

Expected behavior

It should refresh much faster.

Device info

• Device: Google Pixel 9
• OS Version: 16
• App Manager Version: 4.1.0
• Mode: Root

Additional context

I did a fresh install and did not update from the previous version to prevent issues like these...

[J4CKED]

When I click on “Backup/Restore,” I also have to wait about 12 seconds.
This happens when I open the AppManager 4.1.0 app from a force-closed state, but if it's already open, the Backup function works correctly.
Android 12, root mode.

[MuntashirAkon]

When I click on “Backup/Restore,” I also have to wait about 12 seconds.

When App Manager is launched, it invalidates its cache to retrieve the latest info. You cannot use certain features while the cache is being invalidated in order to prevent consistency issues. This is not a new change, it was added a few years ago. The time you need to wait depends on the amount of apps installed and speed of the backup storage. There is a better way to handle this situation, which will be adopted in the future.

[HarriBuh]

When I click on “Backup/Restore,” I also have to wait about 12 seconds.

When App Manager is launched, it invalidates its cache to retrieve the latest info. You cannot use certain features while the cache is being invalidated in order to prevent consistency issues. This is not a new change, it was added a few years ago. The time you need to wait depends on the amount of apps installed and speed of the backup storage. There is a better way to handle this situation, which will be adopted in the future.

Does that also apply to my original report?
I can understand that the app needs to scan all apps the very first time it’s launched; however, that shouldn’t happen with every minor change (updates to individual apps, deleting individual apps...).
It’s also true that the endless loading was already a problem in previous versions, but it didn’t occur constantly, as it does now.

[MuntashirAkon]

I can understand that the app needs to scan all apps the very first time it’s launched; however, that shouldn’t happen with every minor change (updates to individual apps, deleting individual apps...).

There's no API that only retrieves the changes. The API retrieves everything each time you call them. So, even if it is a minor change, App Manager needs to go through all of them just like the first time.

App Manager uses cache to reduce the loading time for the main page. But certain features were implemented in a way that they only work when the latest information is available. Backup/restore and debloaters are two examples.

[HarriBuh]

That didn't directly answer my question, so I'll ask again: Can this problem (because that's what it is) be fixed or not?
It can't be the solution to have to completely restart the app every time I want it to update its app list(manually close it, possibly clear the cache, then restart it).
The endless loading is a real problem—there's no progress here, since the app apparently freezes and no longer responds. Might as well be crashing.

[MuntashirAkon]

The endless loading is a real problem—there's no progress here, since the app apparently freezes and no longer responds. Might as well be crashing.

I am not aware of an endless loading on any of my test devices (Pixel 10 Pro, Samsung S26 Ultra, Moto G Stylus 5G all running Android 16 and 15 in ADB and no-root mode).

[HarriBuh]

Will changing this setting make any difference? It was turned off by default.