It's a background service which must remain connected, and also cannot
be overridden by the user, so I need a programmatic solution to keep
wifi on. I'm trying:
wl = wifiManager.createWifiLock(tag);
wl.acquire()
but that doesn't seem to be working.
I don't want to get too far
Ron wrote:
It's a background service which must remain connected, and also cannot
be overridden by the user, so I need a programmatic solution to keep
wifi on. I'm trying:
wl = wifiManager.createWifiLock(tag);
wl.acquire()
but that doesn't seem to be working.
That will only
You might try closing the socket and trying to connect it again, the
same way it was opened before the disconnect.
15 minutes is a relatively long time... does the socket live in an
activity? It should probably live in a service so its resources don't
get reclaimed like an activity would.
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
Sounds like wifi is going to sleep. Go to wifi settings, hit menu,
tell the wifi to never go to sleep. Understand the battery
implications.
On Dec 14, 8:52 pm, Ron ronbruck...@comcast.net wrote:
An additional clue I just caught on DDMS just before the first
connection failure:
12-14
Can I ask why you're keeping a connection open for 15 minutes? That
must be killing the battery.
--
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
6 matches
Mail list logo
