开发者

onReceive method doesn't get called

开发者 https://www.devze.com 2023-03-07 02:53 出处:网络
public class BroadcastTest extends Activity { BroadcastReceiver receiver; /** Called when the activity is first created. */
public class BroadcastTest extends Activity {
BroadcastReceiver receiver;

/** Called when the activity is first created. */

@Override
public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.main);
    try{
    rec开发者_如何学编程eiver=new Receiver(this);
    registerReceiver(receiver,new IntentFilter(Intent.ACTION_CALL_BUTTON));
    }catch(Exception e){
        Log.d("error",e.getMessage());
    }
  }
}

and another class

public class Receiver extends BroadcastReceiver{
public Receiver(BroadcastTest broadcastTest) {
    // TODO Auto-generated constructor stub
}

@Override
public void onReceive(Context arg0, Intent arg1) {
    // TODO Auto-generated method stub
    Log.d("Fired","Hi");
}
}

is onReceive method of receiver class supposed to be called when i press call button?if yes then it is not geting call.What i am doing wrong here.I am not seeing anything in logcat while pressing call button.Thanks in advance


This Blog post describes some common pitfalls with AlarmManager and BroadcastReceiver. Examples included! Hope that helps.

EDIT: Some common pitfalls:

  1. Receiver not declared in AndroidManifest.xml

    Declare the receiver in the Manifest-file:

    <receiver android:name="net.fusonic.testapp.receivers.TestAlarmReceiver"></receiver>
    
  2. Receiver in the Manifest xml is misspelled

    Always remember that the whole Android-System is case sensitive. So check your spelling is correct in the AndroidMainfest.xml. Remember that the eclipse refactoring functions do not change packagename correctly if you use the short form like “.receivers.TestAlarmReceiver“.

  3. PendingIntent requestCode missing?

    If you create a PendingIntent for your Receiver, please add a requestCode – even it is a random number! Without your “onReceive” code never get called!

  4. AVD running for a long time (very tricky)

    Be aware of using the AVDs especially if your working with “REALTIME_WAKEUP” and SystemClock… So if you try to test your alarm, please restart the AVD or test on a real device!

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号