I think you are going to have to be more informative than that to be helpful. Not that it is your fault: the suggestion of 'wakelock' was a good one. It is just that the online documentation for PowerManager.WakeLock is not as thorough as that for, say for example, Activity.
Why, as one example of a major omission, the documentation for the acquire() method says, "Makes sure the device is on at the level you asked when you created the wake lock", but no Constructor is documented. Nor is there any mention of a Factory method. So how is the user supposed to figure out HOW to ask for the level??? So since the documentation didn't mention it, I will mention it here: the answer is in the class WakeLock is nested in(PowerManager), which has the method 'newWakeLock()'. This is what does the creation referred to so obliquely in the doc for 'acquire()'. On Jun 2, 2:23 pm, Mike dg <[email protected]> wrote: > Are you using a wakelock? > > On Jun 2, 4:10 pm, Daniel Lew <[email protected]> wrote:> I've run into a > bizarre situation and I'm not sure how to solve it. > > > The app I'm working on has a regular pull update that occurs every so > > often in the background. When the phone is on, it works. When the > > phone is using wifi, it works. However, if the phone is sleeping and > > connected only to 3G, it only *sometimes* works. Other times, > > HttpUrlConnection.getInputStream() returns null (after a lengthy > > timeout, though it's not based on any timeout setting... it just > > seems to randomly time out at some point). There are no exceptions > > thrown and no logs indicate any trouble, except that my connection > > goes completely ignored. > > > Does anyone know why this might be happening? -- 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
