Possible blocking issues on the UI thread

[nbd-boss]

Description:

HardwareBufferSurfaceView.kt

• In render(), the method initGLES() is called synchronously.
• initGLES() contains heavy GLES/EGL initialization logic that may block the UI thread, potentially causing jank or dropped frames.
• According to Android official guidelines, GPU/EGL/GLES initialization should not be performed on the UI thread to avoid frame drops or ANRs.

GUIConfigActivity.kt

• In onPause(), the method save() synchronously writes settings using SharedPreferences.commit().
• Synchronous commit may block the UI thread. It is recommended to use apply() for asynchronous writes to improve responsiveness.

GUIWidgetConfigurationActivity.kt

• In onCreate(), getIDMappingPrefs() is called synchronously.
• EncryptedSharedPreferences.create() inside this method can be time-consuming, as reported by multiple developers on StackOverflow.
• To avoid blocking the UI thread, this initialization should be moved off the main thread.
• Additionally, any commit() calls should be replaced with apply() to prevent potential UI blocking.

[tareksander]

First of all this seems AI generated from the formatting and lack of understanding. Doing heavy work in initialization is the point, to not do it when it could cause latency issues. Similarly the EGL init code checks the EGL state to avoid duplicating work, so it only runs once per view.