CODEWITHSUNDEEP
androidbroadcastreceiverandroid-sqlitewakelockandroid-wake-lock
M-Wajeeh
M-Wajeeh

Reputation: 17304

PowerManager.PARTIAL_WAKE_LOCK android

I am very confused whether to acquire this wakelock. E.g. I have this type of code that is called from onReceive() of a BroadcastReceiever (CONNECTIVITY_CHANGE, BOOT_COMPLETED etc) asynchronously i.e. I am launching an IntentService from onReceive() which performs heavy lifting.

private static void insertInDatabase(Context context /*, some data to be inserted in database*/) {
        Database helper = Database.getInstance(context);
        PowerManager pm = (PowerManager) context
            .getSystemService(Context.POWER_SERVICE);
        final WakeLock wakeLock = pm.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, wakelockName); 
        wakeLock.acquire();
        try { 
            SQLiteDatabase db = helper.getWritableDatabase();
            ContentValues cv = new ContentValues();
            // insert data in database here  
        } finally {
            wakeLock.release();
        }
    }

Is this scenario the right candidate to acquire PowerManager.PARTIAL_WAKE_LOCK?

Upvotes: 2

Views: 5348

Answers (2)

Mr_and_Mrs_D
Mr_and_Mrs_D

Reputation: 34076

The answer by @paha misses an important point : IntentService is not enough. Between onReceive() ends and the IntentService is started the phone might fall asleep again. You need a (static) lock to bridge this gap - this is implemented in Mark Murpphy's WakefulIntentService

So keep the AlarmManager and receiver but launch a WakefulIntentService from your onReceive().

See:

Upvotes: 3

Paha
Paha

Reputation: 863

Method onReceive() is running on the main application thread and you do not know how long insertInDatabase() will take. Use an IntentService for doing the database insert and scheduling your alarms. The IntentService will call your onHandleIntent() on a background thread, so you can take the time you need, and the service automatically goes away when onHandleIntent() completes.

public class MyIntentService extends IntentService {

    @Override
    protected void onHandleIntent(Intent intent) {
        PowerManager pm = (PowerManager) getSystemService(Context.POWER_SERVICE);
        final WakeLock wakeLock = pm.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, wakelockName); 
        wakeLock.acquire();
        wl.acquire();
        try { 
            SQLiteDatabase db = helper.getWritableDatabase();
            ContentValues cv = new ContentValues();
            // insert data in database here  
        } finally {
            wakeLock.release();
        }
    }
}

To start IntentService from BroadcastReceiver use AlarmManager. IntentService work as queue pattern and you don't need to worry about synchronicity of operations.

Added after discussion in comments:

Your code example does not say from what place you call PARTIAL_WAKE_LOCK. The short answer is PARTIAL_WAKE_LOCK is not needed in the BroadcastReciever and PARTIAL_WAKE_LOCK is needed in the IntentService. Maybe this will help BroadcastReceiver, Service and Wakelock

Upvotes: 2

Related Questions