Hi everyone,
I’ve been working on integrating LiveKit into a mobile-first project, and while the performance on desktop is flawless, I’ve run into a bit of a technical hurdle regarding connection persistence on handheld devices when the system is under heavy load.
I’ve noticed that whenever the device environment is pushed to its limits—specifically when testing how my app handles simultaneous data streams or while I’m experimenting with an ios roblox executor to see how the OS manages background multitasking—the LiveKit signal connection tends to drop. The most frustrating part is that the WebSocket seems to hit a timeout, and I’m seeing “ICE connection failed” errors more frequently than I’d like. While I was chatting with some other developers about these resource bottlenecks, it seemed like the mobile OS might be deprioritizing the network worker thread when other high-concurrency tasks are active, leading to these silent disconnections.
Has anyone else noticed their mobile clients hitting persistent “Signal connection closed” alerts or experiencing significant media lag if there are other high-performance tasks running in the background? I’m seeing occasional packet loss spikes in my logs that only trigger during these heavy load periods, which makes me think the hardware is struggling to manage the real-time encrypted stream alongside other background operations.
I’m trying to figure out if there’s a way to make the connection more resilient—perhaps by tweaking the adaptive bitrate settings or if there’s a way to prioritize the LiveKit worker thread to ensure it stays fluid in “noisy” multitasking environments on mobile. If you’ve dealt with stabilizing real-time communication while the system is working hard in the background, I’d really appreciate your insights!
Best regards!