Potential UI Thread Blocking Issues

[nbd-boss]

DNSFilterService.java – onDestroy() → shutdown()

onDestroy() is invoked on the main thread. Inside this method, shutdown() is called synchronously, and shutdown() itself contains several operations that may be heavy or slow, such as:

• runningVPN.stop(true)
• DNSFILTERPROXY.stop()
• dnsReqForwarder.clearForward()
• clearPortRedir()
  These operations likely involve VPN teardown, proxy shutdown, port cleanup, and other tasks that may take noticeable time. Executing them on the main thread could block the UI. So it is recommended to move it off the UI thread.

BootUpReceiver.java – onReceive() → getConfig()

onReceive() always runs on the main thread. getConfig() performs disk I/O when loading configuration files, which can block the main thread. According to Android’s official guidelines, file I/O should not be done on the UI thread.

DNSProxyActivity.java – onActivityResult() → onBackupRestore()

onBackupRestore() performs:

• File I/O
• ZIP compression/decompression
  These are typical long-running operations. Since onActivityResult() runs on the main thread, executing them synchronously may cause noticeable UI freezes.

[IngoZenz]

Thanks for analyzing this, I am already aware of these issues (I can see it in Playstore reports).
So far I did not give prio to this, as in practical usage it is almost not visible for users. On the other side, fixing this would be pretty much effort and risky...

[error-reporting]

DNSFilterService.java – onDestroy() → shutdown()

onDestroy() is invoked on the main thread. Inside this method, shutdown() is called synchronously, and shutdown() itself contains several operations that may be heavy or slow, such as:

• runningVPN.stop(true)
• DNSFILTERPROXY.stop()
• dnsReqForwarder.clearForward()
• clearPortRedir()
  These operations likely involve VPN teardown, proxy shutdown, port cleanup, and other tasks that may take noticeable time. Executing them on the main thread could block the UI. So it is recommended to move it off the UI thread.

BootUpReceiver.java – onReceive() → getConfig()

onReceive() always runs on the main thread. getConfig() performs disk I/O when loading configuration files, which can block the main thread. According to Android’s official guidelines, file I/O should not be done on the UI thread.

DNSProxyActivity.java – onActivityResult() → onBackupRestore()

onBackupRestore() performs:

• File I/O
• ZIP compression/decompression
  These are typical long-running operations. Since onActivityResult() runs on the main thread, executing them synchronously may cause noticeable UI freezes.

those operations don't take that long for how this app uses them