We\'ve got a tablet application for which we want to s开发者_JS百科creen to timeout after a certain period, but would like the user to re-enable it by touching the screen instead of the \'power\'-butt
I\'m creating a Service that will be set up to start using the AlarmManager (using ELAPSED_REALTIME_WAKEUP). I do all my processing inside the onStartCommand method mainly because:
I am developing an app in which i need to send and receive packets in background. But I\'ve discovered that when screen shut off also cpu and networking is disabled. So I\'ve found on Android Develope
Suppose I use BroadcastReceiver to receive events(intents) that awake the phone even if it is in deep sleep mode (such as incoming data packet on a socket, or incoming text message). Then I forward re
I\'m using a repeating alarm to trigger a BroadcastReceiver (OnAlarmReceiver) which in turn calls WakefulIntentService.sendWakefulWork(context, PmNotificationService.class);
The pm and keepScreenOn variables are globally defined. I grab the PowerManager.WakeLock in my OnCreate method:
I must not have implemented the wakelocks correctly. This is how I did it. Is this correct? private static final String LOCK_NAME_STATIC=\"domination.shredAssistant.locationService\";
For some reason my Android phone won\'t go to sleep. I assume that a wakelock is keeping it awake, but there is no way to tell which wakelocks are active. The running services doesn\'t list anything s
im receiving an intent in broadcast receiver and then i start service to do more work. now what if the devi开发者_开发百科ce is sleep and this happen, do i have to get Wakelock (AlarmManger?), and why
I am writing a Android client app which keeps receiving push notifications from a server using HTTP long-polling(Comet).
加载中,请稍侯......