wakelock

Hеllo guуs, I want to unlock the phone with service. I'm using alarm manager. Receiver and Service were added to manifest and also permissions for RECEIVE_BOOT_COMPLETE and WAKE_LOCK AlarmReceiver public class AlarmReceiver extends BroadcastReceiver { @Override public void onReceive(Context context, Intent intent) { setAlarms(context); } public static void setAlarms(Context context) { cancelAlarms(context); PendingIntent pIntent = createPendingIntent(context); Calendar calendar = Calendar.getInstance(); setAlarm(context, calendar, pIntent); } @SuppressLint("NewApi") private static void

Question I am wondering if we need to aquire the WakeLock or if the service.startForeground() command does that anyway for us? I didn't find anything in the documentation. Goal We want to remove unnesessary stuff which might slow down the service start as we want to start capturing the sensor data as soon as possible and as the service might be restarted frequently. Context We're developing an Android library to capture sensor data with ~ 200 Hz for up to a couple of hours (research environment). Right now we aquire a WakeLock and start the capturing service as ForegroundService to make sure

im receiving an intent in broadcast receiver and then i start service to do more work. now what if the device is sleep and this happen, do i have to get Wakelock (AlarmManger?), and why do i need it? does my service will stop running if the device goes to sleep without getting a wakelock. now what if the device is sleep and this happen, do i have to get Wakelock (AlarmManger?), and why do i need it? If the device is asleep to begin with, you will not be "receiving an intent in broadcast receiver", because the device is asleep. do i have to get Wakelock (AlarmManger?), and why do i need it? You

I'm developing a small utility app that scans 2D barcodes, and then submits each barcode to an IntentService where a longer task is performed. When the activity is shown, it should prevent the device from sleeping, until the barcode is processed in the service. If the service finishes the processing, it stops itself, but the activity should still be visible. I'd like to hold a SCREEN_DIM_WAKE_LOCK WakeLock during the activity lifecycle, but as this type doesn't prevent the CPU from sleeping, I'd also need to acquire a PARTIAL_WAKE_LOCK in the activity when a new 2D code is scanned, and release

I want an Android service, which is listening for data (I have tried TCP and UDP) to wake up the service/phone when data arrives. Currently the phone stays asleep when IP data arrives and that data is lost. Is this normal for Android? I see sleeps of 2+ hours several times a day, and 7+ hour sleeps when I am asleep. Does GCM provided a solution which wakes up a service/phone when a message arrives. I need messages to be displayed within a few seconds of them being sent from the server. Can this only be achieved by keeping the CPU running all day long? Is there no interrupt from the GSM modem

I have been stuck in this situation for a long time... I want to use the alarm manager to show notification at the specific time, and now it worked in the situation listed below: when the app runs in the background, notification will be shown at the correct time, and no matter the device is locked or not. after the app has been killed in the background, i will still get correct notification when device is not locked, but things turn wrong when the device is locked, i can't receive any notification. Here's the code AlarmReceiver.java, all the needed permission has been added into