android-wake-lock

I am using GCM for push notifications for my project, but am stuck at acquiring wake lock. Log message: 09-03 17:04:05.003: V/GCMBroadcastReceiver(5772): onReceive:com.google.android.c2dm.intent.REGISTRATION 09-03 17:04:05.003: V/GCMBroadcastReceiver(5772): GCM IntentService class: example.pro.GCMIntentService 09-03 17:04:05.049: V/GCMBaseIntentService(5772): Acquiring wakelock Below is my manifest file: <?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="example.pro" android:versionCode="1" android:versionName="1.0" > <uses-sdk

My audio streaming app is working correctly with only WifiLock. But some devices report that when they turn off the screen, connection is cut and audio streaming is topped. (They say this does not happen on 3G) So, I thought maybe I can also use a Partial WakeLock. I am not sure if this fixes the issue but I think it is an option. At the same time, adding a WakeLock while a basic WifiLock is working may deplete the battery faster and may not fix the issue. What do you think about adding a WakeLock too for this kind of issue and app? private static WifiLock wifiLock = ((WifiManager) appInstance

Disclaimer: this is not duplicate of Activity Recognition stops receiving updates when phone goes to standby(screen off state) because I'm already using that approach and it does not help. Problem: It seems that Activity Recognition service stops working and is not sending any updates when device goes asleep. It works OK (recognized activities are stored to sqlite) when device is not asleep but as soon as I press power button on HTC M8, nothing is stored from this moment until I wake up the device but pressing power button again. Some details how I'm doing activity recognition: Requesting

I want that when my application is running the power button (which upon pressing locks the screen & screen goes BLACK), should be disabled. So that the user cannot lock the screen. I have noticed this thing in Samsung Galaxy S phone's Default Camera App. That's the same reason I am trying to do the same. I have also a Camera related App. try this one int val=android.provider.Settings.System.getInt(getContentResolver(), SCREEN_OFF_TIMEOUT); android.provider.Settings.System.putInt(getContentResolver(), SCREEN_OFF_TIMEOUT, -1); Toast.makeText(this, "Disabled Screen Timeout", Toast.LENGTH_LONG)

My requirement is: after a GCM message arrives, the device should wake up to display a high-priority notification. The device should turn the screen on . Currently I'm using WakeLock to achieve this. The newWakeLock() method expects a lock level AND a flag to be passed (as the 1st param, bitwise or'd). I'm using PowerManager.ACQUIRE_CAUSES_WAKEUP flag since it does exactly what I need. However, I'm a bit frustrated about the lock level. So according to the docs , I got the following options: PARTIAL_WAKE_LOCK - not compatible with ACQUIRE_CAUSES_WAKEUP / doesn't turn the screen on SCREEN_DIM

I have question about wakelock. In cases shown below, does android OS release wakelock ( PARTIAL_WAKE_LOCK if you need to specify) to prevent wakelock was left acquired and wasting battery until turning power off (not sleep). Case 1-a: App has acquired wakelock (w/o timeout option) in one of its threads (please think it is reasonable in this case) and it was designed to release wakelock when critical task was finished. App can be killed by taskmanager or notorious taskkiller, and app has no chance to let its thread release wakelock. What happens to that wakelock? Case 1-b: (If answer to case 1