Synchronous Bitmap decoding in onActivityResult of AccountInfoPresenceActivity.java blocks the UI thread

[nbd-boss]

Description
Inside onActivityResult(), the following code synchronously calls
AppImageUtil.scaledBitmapFromContentUri(...):

Bitmap bmp = AppImageUtil.scaledBitmapFromContentUri(
        this, resultUri, AVATAR_PREFERRED_SIZE, AVATAR_PREFERRED_SIZE);

Since onActivityResult() runs on the main (UI) thread, and
scaledBitmapFromContentUri() internally performs:

• ContentResolver.openInputStream() (disk / IPC I/O)
• BitmapFactory.decodeStream() (CPU-intensive and memory-heavy, called twice)

this can block the UI thread, especially when handling large images or on low-end devices.

Impact

• UI thread blocking
• Noticeable frame drops or "jank" after the user crops an image
• Potential ANR in worst cases

Suggested Fix

• Move bitmap decoding to a background thread (e.g. Executor, Coroutine, RxJava)
• Post the result back to the UI thread to update the ImageView

Additional Notes

• The Android official documentation strongly recommends avoiding I/O operations and other long-running tasks on the main thread to prevent ANRs.

[cmeng-git]

I have tried to crop an image size of 4032x3024 (3.93MB), it tooks only 5ms on my Note 10. Even an android device is 5 times slower than my note10, it will only take 25ms. This should not cause ANR to user experience.
I also tried similar test on my Samsung J7, the cropping return instanstly without any problem. J7 is considered a very slow machine, many of the aTalk features may not work well on this machine.

In android vital, I see that there are a lot of reported cases showing ANR for AccountInfoPresenceActivity even on Snapdragon 8 Gen 2 machines. It seems the problem only started after I changed the loadDetails() method to use ExecutorService from AsyncTask since 4.2.0. Prior to this, this problem was never reported when AsyncTask was used. I suspect the problem is SDK-related.

I nver see ANR or related problem in the course of aTalk system testing for far. In a few occassions, I see the logcat reported there are too many views in AccountInfoPresenceActivity class. It was constantly in my mind to use back AsyncTask instead to see if the android vital still reports ANR problem.