PocketMatrix

We're involved in a new effort on a constantly-connected mobile application. While we can open socket connections over an available WiFi connection, we can't open one across the (cellular phone user's) carrier data plan until some other application (such as a mobile web-browser) does so first.

E.g., the following flow fails:
+ disable WiFi connectivity
+ run our EdgeLib app requiring a socket connection

while this flow succeeds:
+ disable WiFi connectivity
+ start mobile browser (slow to initialize but eventually connects)
+ quit mobile browser
+ run our EdgeLib app requiring a socket connection

Have I missed something in EdgeLib's network-connectivity stack? Or is there some initialization my app needs to perform outside of EdgeLib's API?

Thanks in advance,
Dave

Hi Dave,

EDGELIB provides a simple sockets API for networking and doesn't access (private) carrier information. Can you tell me which platform you're testing on?