Too long determining workmode

[AlexeiCrystal]

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

Every time the app is opened, there is a lengthy ‘determining workmode’ process in the new version 4.1.1, even in non-root mode. I used non-root mode because I’d previously experienced the same issue with other modes taking a long time to load, and having to wait for it to prompt for pairing or connect via wireless debugging.

To Reproduce

No response

Expected behavior

No response

Screenshots

No response

Logs

No response

Device info

• Device: Redmi Note 9 Pro
• OS Version: Android 12, MIUI 14
• App Manager Version: 4.0.1
• Mode: Root/ADB/NonRoot

Additional context

No response

[MuntashirAkon]

This usually happens when the local server is running or the default port (90001) is being used. When App Manager detects that there is a server running, it attempts to connect to it until it is timed out, even in no-root mode.

[AlexeiCrystal]

In previous versions, there was no issue with slow loading times in non-root mode. However, even in previous versions, there was still a problem with slow loading times in ADB mode. In this version, though, even non-root mode takes a long time to loading.

This causes inconvenience

[AlexeiCrystal]

The info card states that the remote server is active, but the remote services are inactive.

[AlexeiCrystal]

As I understand it, this is related to #1596

[AlexeiCrystal]

None of the apps I’ve seen (Shizuku, aShell You or others) that have the ability to connect to ADB via TCP or Wireless Debugging take this long to load into ADB mode. What’s more, Shizuku runs more stably and, if configured correctly, doesn’t need to be constantly restarted, unlike AppManager.

[e-t-l]

That's a great point. The dev has repeatedly said he doesn't want to integrate Shizuku because AM uses a different set of privileged APIs, but I has he considered that Shizuku would be an easier/more stable option just to establish the ADB connection?

AM can still use whatever APIs it wants just like it does in Wirelesa-Debugging or ADB-over-TCP modes; a Shizuku mode would just take the burden of establishing that connection off of AM.

[MuntashirAkon]

@AlexeiCrystal: The developer features vary across vendors, including ADB. It makes it difficult to understand and support every Android devices across the world. The best way to support App Manager is to help diagnose the issue rather than ranting about such and such applications that works in this situation. For example, I faced the same problem that you are facing only once ever since I have implemented this feature six years ago (I have used different devices, Xioami, Google Pixel over the years). Why? Because I have diagnosed the issue immediately when I faced it. The issue can often be very simple and can be fixed quickly.

@e-t-l: Shizuku is still non-free and we don't support or promote any non-free applications.

[MuntashirAkon]

The no-root mode issue is fixed by 9638823. I have reverted back the change to let no-root mode avoid checking for a remote server.