receiver

I wrote a widget for Android and I'm trying to get the battery level. I've tried using Intent batteryIntent = context.registerReceiver(null, new IntentFilter(Intent.ACTION_BATTERY_CHANGED)); but I get the error: "IntentReceiver components are not allowed to register to receive intents" Why? the ACTION_BATTERY_CHANGED is a sticky intent and I don't register a receiver (null in the first parameter). Any workaround? Thanks. hackbod gave the solution at the comments: " use getApplicationContext().registerReciever() " Ummmm...that feels like a bug. They must be doing the is-a- BroadcastRecevier

For creating a receiver I'm extended WakefulBroadcastReceiver in my old project. But now it's deprecated . Instead of WakefulBroadcastReceiver which Receiver I should use now and how to convert below code with new method? Here is my code: public class TaskFinishReceiver extends WakefulBroadcastReceiver { private PowerManager mPowerManager; private PowerManager.WakeLock mWakeLock; @Override public void onReceive(Context context, Intent intent) { mPowerManager = (PowerManager) context.getSystemService(Context.POWER_SERVICE); turnOnScreen(); Intent wakeIntent = new Intent(); wakeIntent

I'm currently working on a little app to get started with the services that the Bluetooth Android API can provide. Edit -> Answer: It seems that the issue was due to the specific Nexus 5 devices. Seems like their bluetooth receiver doesn't work well. Solution below should work for other devices Remark: I’ve read the documentation here: http://developer.android.com/guide/topics/connectivity/bluetooth.html as well as the following source code of this tutorial http://www.londatiga.net/it/programming/android/how-to-programmatically-scan-or-discover-android-bluetooth-device/ located on github under

I have a very weird problem, and none of the questions already on the website have an answer or the same problem. I have an app that receives BOOT_COMPLETED. I made sure it could receive the intent by setting android:installLocation to internalOnly. I have a Log.Debug in my OnBoot class, confirming wether or not it was called. I have two devices, an Android 2.2, and a Honeycomb. On android 2.2, it works fine, but Honeycomb... If I install the application on the honeycomb tablet with eclipse's "run" button, onBoot is called when the tablet boots. If I install the application on the honeycomb

I m currently learning how create and use services on android. I looked on the android SDK for further help and i found the android:enable=[true | false] . in the SDK is said that: The and attributes must both be "true" (as they both are by default) for the service to be enabled. If either is "false", the service is disabled; it cannot be instantiated. So i would like to know what is the interest of/ why (in general) setting the application enables as "false". setting the service enable as "false". I say that if we put service enable as false there is no way to call that service, so why we

django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet. Exception appeared when I added: import signals in init .py file (apps/application/init.py) from models import Review in signals.py file (apps/application/signals.py) I want to send an http request when there is an insert in the model Review. So I need to import Review model (in the __init.py__ file) to execute the following code: @receiver (pre_save, sender = Review) def my_handler (sender, ** kwargs): .... In the Django's source , this is where the exception is comming from: def check_apps_ready(self): """Raise an exception