An additional clue I just caught on DDMS just before the first connection failure:
12-14 19:00:23.164: VERBOSE/WifiMonitor(60): Event [CTRL-EVENT- DISCONNECTED - Disconnect event - remove keys] 12-14 19:00:23.164: VERBOSE/WifiMonitor(60): Event [CTRL-EVENT-STATE- CHANGE id=-1 state=8] In looking through other message boards it appears this might be related to the phone going to sleep. Any ideas on how to get around this? On Dec 14, 9:06 am, Ron <[email protected]> wrote: > I am able to connect to aSocketon my PC from my HTC 1 phone, via IP > and successfully transfer data in a thread that gets rescheduled every > few seconds. The problem is that after 15 minutes or so, the > connection drops and my debug traces give me the "Network > unreachable". A further clue is that if I plug in or replug in the > USB cable I get reconnected. > > I'm wondering what programmatic function will reconnect to the PC > without having to fiddle with the USB cable. I've tried > Wifimanger.reconnect and reassociate, neither did the trick. Perhaps > if I knew what actions were peformmed when the usb cable is plugged in > (which shouldn't have anything to do with my connection) I would be > able to program them into my exception path. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
