Hello everyone, I have run into an unusual issue recently while testing network stability across our mobile test units and wanted to see if anyone with Java runtime experience has seen this before. We are trying to debug persistent background handshake timeouts on an Android client, specifically when handling local listener sockets alongside custom security profiles.
While trying to find reference implementations of desktop Java runtimes being wrapped for mobile environments, I came across an interesting setup discussed on a community website that optimizes runtime assets for similar mobile workflows. The problem seems to be that newer OS updates aggressively throttle background socket requests and drop local pipe listeners the moment memory thresholds shift.
Has anyone here dealt with comparable socket termination issues when running customized Java environments on modern mobile devices, and did you resolve it through OS-level battery exemptions or specific socket timeout flags in your configuration? Any troubleshooting tips or insights would be greatly appreciated.
While trying to find reference implementations of desktop Java runtimes being wrapped for mobile environments, I came across an interesting setup discussed on a community website that optimizes runtime assets for similar mobile workflows. The problem seems to be that newer OS updates aggressively throttle background socket requests and drop local pipe listeners the moment memory thresholds shift.
Has anyone here dealt with comparable socket termination issues when running customized Java environments on modern mobile devices, and did you resolve it through OS-level battery exemptions or specific socket timeout flags in your configuration? Any troubleshooting tips or insights would be greatly appreciated.