I can't say I've had these problems with my code - I have the alarmmanager set to wake my app up every 'x' minutes (the pending intent kicks off a service) and from there I open an HTTP connection to a server. The server holds a PARTIAL wake lock so the phone doesn't go back to sleep immediately. Usually the phone will use the cellular network to make the connection as WiFi has probably gone to sleep and it takes a few seconds to wake- up/connect.
In fact, my problem has actually been different, in that the HTTP request is dispatched via the cellular network, then (because it can) WiFi may come into service before the response has been received. Depending on timing, I've seen this situation "break" the cellular data connection, forcing my app to re-run the query. Doug On Mar 24, 8:51 pm, AuxOne <tyler.thack...@gmail.com> wrote: > Just to let you know, I experimented with FULL_WAKE_LOCK. Not only did > it not turn on the screen as it said it would, which is a good thing I > guess, but it also doesn't seem to lock as effectively as the > PARTIAL_WAKE_LOCK. Both seem to go into a deep sleep around 15-20 min > of use and then WiFi connectivity is gone. > > When testing on the emulator faking a cellular network (and no Wifi), > it works fine with PARTIAL so I didn't try FULL. -- 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 To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
