I'm sorry for what must be a really dumb question... my app is a
client, the server is a linux box in a colo.  I use android Sockets to
connect to the server.  It works great.

that is, it works great when the phone is on wifi.

But when the phone is on 3G, the socket connection times out.

---

The ONLY permission my app is asking for is 'INTERNET' (which is
apparently enough for it to work on wifi).

What am I missing?

My app also uses a URLConnection to discover the server address (by
asking a second server, whose address is well known).  That works both
in wifi and 3G, but is a port 80 http request, so probably is
considered pretty inoffensive.  Still, it makes me feel like this is
not some subtle radio startup issue.

---

It smells like a permission issue, but reading through the
permissions, I don't see any that scream out 'enable sockets on 3G'

Note, the phone is always a client.  this is not about incoming
connections.  This is an outbound TCP connection from the phone to a
remote server (which is not a phone).

It also works in the emulator, even when you tell the emulator to
disable wifi, but I'm not sure that proves anything.

Is there another permission I am missing?

- Dan



-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to