我需要检查Sim卡的状态，并根据其状态执行一些操作。 根据我对BroadcastReceiver的了解，当Sim状态更改时，将执行broadcastReceiver的onReceive方法。

这是BroadcastReceiver类：

public class SimStateListener extends BroadcastReceiver {

public SimStateListener() {

}

@Override

public void onReceive(Context context, Intent intent) {

// TODO: This method is called when the BroadcastReceiver is receiving

// an Intent broadcast.

// Checks Sim card State

TelephonyManager telephoneMgr = (TelephonyManager) context.getSystemService(Context.TELEPHONY_SERVICE);

int simState = telephoneMgr.getSimState();

switch (simState) {

case TelephonyManager.SIM_STATE_ABSENT:

Log.i("SimStateListener", "Sim State absent");

break;

case TelephonyManager.SIM_STATE_NETWORK_LOCKED:

Log.i("SimStateListener", "Sim State network locked");

break;

case TelephonyManager.SIM_STATE_PIN_REQUIRED:

Log.i("SimStateListener", "Sim State pin required");

break;

case TelephonyManager.SIM_STATE_PUK_REQUIRED:

Log.i("SimStateListener", "Sim State puk required");

break;

case TelephonyManager.SIM_STATE_UNKNOWN:

Log.i("SimStateListener", "Sim State unknown");

break;

case TelephonyManager.SIM_STATE_READY:

Log.i("SimStateListener", "Sim State ready");

String phoneNumber = telephoneMgr.getLine1Number();

Log.i("SimStateListener", phoneNumber);

Toast.makeText(context, phoneNumber, Toast.LENGTH_LONG).show();

if(phoneNumber.equals(myPhoneNumber)){

// do nothing

break;

}

else{

Log.i("SimStateListener", "Sim card is changed");

// do something

break;

}

}

}

}

这是我放在清单中的内容：

这是我在LogCat中得到的：

12-18 08:08:29.420: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

12-18 08:08:29.560: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

12-18 08:08:29.710: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

12-18 08:08:33.940: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

12-18 08:08:33.980: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

12-18 08:08:34.000: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

12-18 08:08:35.680: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

12-18 08:08:35.850: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

12-18 08:08:35.860: W/BroadcastQueue(1303): Failure sending broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x20000010 (has extras) }

堆栈跟踪 ：

12-18 10:53:18.850: E/ActivityManager(2170): ANR in com.android.systemui

12-18 10:53:18.850: E/ActivityManager(2170): PID: 2221

12-18 10:53:18.850: E/ActivityManager(2170): Reason: Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }

12-18 10:53:18.850: E/ActivityManager(2170): Load: 6.4 / 2.12 / 1.02

12-18 10:53:18.850: E/ActivityManager(2170): CPU usage from 3482ms to -8134ms ago:

12-18 10:53:18.850: E/ActivityManager(2170): 38% 2170/system_server: 25% user + 13% kernel / faults: 1455 minor 10 major

12-18 10:53:18.850: E/ActivityManager(2170): 15% 2330/com.android.launcher: 12% user + 3.3% kernel / faults: 2121 minor 10 major

12-18 10:53:18.850: E/ActivityManager(2170): 14% 2151/surfaceflinger: 6.2% user + 8% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 13% 2319/com.android.phone: 8.9% user + 4.8% kernel / faults: 831 minor 3 major

12-18 10:53:18.850: E/ActivityManager(2170): 6.6% 2221/com.android.systemui: 4.3% user + 2.2% kernel / faults: 639 minor 6 major

12-18 10:53:18.850: E/ActivityManager(2170): 2.8% 2161/bootanimation: 0.9% user + 1.9% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.2% 25/mtdblock0: 0% user + 1.2% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.5% 59/adbd: 0% user + 1.4% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1% 12/kswapd0: 0% user + 1% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0.7% 2300/com.android.settings: 0.5% user + 0.2% kernel / faults: 345 minor 1 major

12-18 10:53:18.850: E/ActivityManager(2170): 0.7% 2367/android.process.acore: 0.4% user + 0.3% kernel / faults: 80 minor 1 major

12-18 10:53:18.850: E/ActivityManager(2170): 0.3% 48/rild: 0.2% user + 0.1% kernel / faults: 16 minor

12-18 10:53:18.850: E/ActivityManager(2170): 0.5% 2347/com.android.printspooler: 0% user + 0.5% kernel / faults: 104 minor

12-18 10:53:18.850: E/ActivityManager(2170): 0.3% 284/logcat: 0.1% user + 0.1% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0.3% 1502/kworker/0:0: 0% user + 0.3% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0.2% 1//init: 0.1% user + 0% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0.1% 26/mtdblock1: 0% user + 0.1% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0% 3/ksoftirqd/0: 0% user + 0% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0% 43/servicemanager: 0% user + 0% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 100% TOTAL: 61% user + 38% kernel + 0% softirq

12-18 10:53:18.850: E/ActivityManager(2170): CPU usage from 6733ms to 7312ms later:

12-18 10:53:18.850: E/ActivityManager(2170): 31% 2170/system_server: 16% user + 15% kernel / faults: 65 minor

12-18 10:53:18.850: E/ActivityManager(2170): 11% 2185/ActivityManager: 3.7% user + 7.5% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 6.3% 2181/Binder_1: 5% user + 1.2% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 3.7% 2182/Binder_2: 2.5% user + 1.2% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 2.5% 2177/Compiler: 1.2% user + 1.2% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 2.5% 2345/Binder_5: 1.2% user + 1.2% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 2.5% 2346/Binder_6: 0% user + 2.5% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 2.5% 2362/Binder_8: 1.2% user + 1.2% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.2% 2251/Binder_3: 1.2% user + 0% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 15% 2319/com.android.phone: 11% user + 3.6% kernel / faults: 51 minor

12-18 10:53:18.850: E/ActivityManager(2170): 8% 2319/m.android.phone: 5.8% user + 2.2% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 2.9% 2326/Compiler: 2.2% user + 0.7% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 2.9% 2381/RILReceiver: 2.9% user + 0% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.4% 2380/RILSender: 0.7% user + 0.7% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 13% 2330/com.android.launcher: 8.4% user + 4.9% kernel / faults: 567 minor 8 major

12-18 10:53:18.850: E/ActivityManager(2170): 11% 2330/ndroid.launcher: 7.7% user + 3.5% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.4% 2334/GC: 0% user + 1.4% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0.7% 2339/Compiler: 0.7% user + 0% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 10% 2221/com.android.systemui: 9.1% user + 1.4% kernel / faults: 112 minor

12-18 10:53:18.850: E/ActivityManager(2170): 9.8% 2221/ndroid.systemui: 7.7% user + 2.1% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0.7% 2228/Compiler: 0.7% user + 0% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 2.8% 2151/surfaceflinger: 0.7% user + 2.1% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.4% 2156/DispSync: 0.7% user + 0.7% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0.7% 2151/surfaceflinger: 0% user + 0.7% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 0.7% 2166/Binder_4: 0% user + 0.7% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.3% 48/rild: 0.6% user + 0.6% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.3% 76/rild: 0.6% user + 0.6% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.7% 12/kswapd0: 0% user + 1.7% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.5% 59/adbd: 0% user + 1.5% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 1.5% 279/adbd: 0% user + 1.5% kernel

12-18 10:53:18.850: E/ActivityManager(2170): 100% TOTAL: 62% user + 37% kernel

12-18 10:53:21.560: E/InputDispatcher(2170): channel 'b3fdc490 StatusBar (server)' ~ Channel is unrecoverably broken and will be disposed!

12-18 10:53:21.570: E/InputDispatcher(2170): channel 'b40044f8 Keyguard (server)' ~ Channel is unrecoverably broken and will be disposed!

12-18 10:53:23.030: E/gralloc_goldfish(2151): gralloc_alloc: Mismatched usage flags: 480 x 800, usage b33

12-18 10:53:23.080: E/(2151): GraphicBufferAlloc::createGraphicBuffer(w=480, h=800) failed (Invalid argument), handle=0x0

12-18 10:53:23.140: E/BufferQueue(2151): [ScreenshotSurface] dequeueBuffer: SurfaceComposer::createGraphicBuffer failed

12-18 10:53:28.070: E/SoundPool(2424): error loading /system/media/audio/ui/Lock.ogg

12-18 10:53:28.110: E/SoundPool(2424): error loading /system/media/audio/ui/Unlock.ogg

12-18 10:53:29.420: E/BluetoothAdapter(2300): Bluetooth binder is null

12-18 10:53:35.860: E/NetdConnector(2170): NDC Command {12 bandwidth setiquota eth0 9223372036854775807} took too long (2654ms)

12-18 10:53:39.770: E/BluetoothAdapter(2424): Bluetooth binder is null

12-18 10:53:39.770: E/BluetoothAdapter(2424): Bluetooth binder is null

12-18 10:53:39.960: E/BluetoothAdapter(2424): Bluetooth binder is null

12-18 10:53:40.680: E/BluetoothAdapter(2424): Bluetooth binder is null

12-18 10:53:42.740: E/BluetoothAdapter(2424): Bluetooth binder is null

12-18 10:53:43.040: E/ConnectivityService(2170): startUsingNetworkFeature took too long: 8936ms

12-18 10:53:44.840: E/logwrapper(2487): executing /system/bin/ip failed: No such file or directory

12-18 10:53:45.260: E/NetdConnector(2170): NDC Command {18 interface fwmark exempt add 10.0.2.2/32} took too long (837ms)

12-18 10:53:45.360: E/JavaBinder(2424): *** Uncaught remote exception! (Exceptions are not yet supported across processes.)

12-18 10:53:45.360: E/JavaBinder(2424): java.lang.RuntimeException: android.os.DeadObjectException

12-18 10:53:45.360: E/JavaBinder(2424): at android.os.Parcel.writeException(Parcel.java:1362)

12-18 10:53:45.360: E/JavaBinder(2424): at android.os.Binder.execTransact(Binder.java:410)

12-18 10:53:45.360: E/JavaBinder(2424): at dalvik.system.NativeStart.run(Native Method)

12-18 10:53:45.360: E/JavaBinder(2424): Caused by: android.os.DeadObjectException

12-18 10:53:45.360: E/JavaBinder(2424): at android.os.BinderProxy.transact(Native Method)

12-18 10:53:45.360: E/JavaBinder(2424): at android.content.IIntentReceiver$Stub$Proxy.performReceive(IIntentReceiver.java:124)

12-18 10:53:45.360: E/JavaBinder(2424): at android.app.ActivityThread$ApplicationThread.scheduleRegisteredReceiver(ActivityThread.java:823)

12-18 10:53:45.360: E/JavaBinder(2424): at android.app.ApplicationThreadNative.onTransact(ApplicationThreadNative.java:394)

12-18 10:53:45.360: E/JavaBinder(2424): at android.os.Binder.execTransact(Binder.java:404)

12-18 10:53:45.360: E/JavaBinder(2424): ... 1 more

我无法在LogCat中打印任何内容，也看不到任何Toast出现。

你能告诉我我在做什么错。

android 广播失败,android - 发送广播Intent SIM_STATE_CHANGED失败 - 堆栈内存溢出相关推荐

  1. android requestmtu,android - 如何设置/获取/请求从Android到iOS或反之亦然BLE的MTU？ - 堆栈内存溢出...

    我们正在将MTU请求从Android发送到iOS Android-从此函数onServicesDiscovered回调请求MTU 但是我不知道如何确定对等设备支持是否请求了MTU,以及如何实际协商的M ...

  2. android sd卡挂载命令,android - 从android中的adb shell手动挂载SD卡 - 堆栈内存溢出

    我有一个Android 4.1手机(联想820). 经过一些旨在对内部SD ram进行分区的更改(更改后,手机将不再安装外部 SD卡.我很擅长Linux,但我从未见过Android shell. 我很 ...

  3. android 如何重载函数,android - 如何在Frida中使用“ int”重载函数 - 堆栈内存溢出...

    我有以下功能: public final int getState(@NotNull String str, int i) { Intrinsics.checkParameterIsNotNull(s ...

  4. android 415错误,java - Android Retrofit2无法添加标头（415错误代码） - 堆栈内存溢出...

    我正在尝试通过skyscanner api访问票证数据并将其传递到我的视图,但是我无法实现这一点,因为我收到415错误代码,我正在使用Retrofit2并以编程方式添加标头. 我的界面如下所示: pu ...

  5. Linux内存申请失败失败会怎样,linux - 转储失败，因为无法加载资产 - 堆栈内存溢出...

    我想在我的.bashrc Ubuntu 18.04上创建别名以构建和安装APK,但是在这样的终端中遇到问题 W/asset (22684): Asset path ./app/build/output ...

  6. android 按钮 叠加,android - 叠加层按钮在Android 4.3中不起作用 - 堆栈内存溢出

    我在WindowManager.LayoutParams.TYPE_TOAST级别层上有一个带按钮的覆盖视图. 该按钮在Android 4.2中可以正常工作,但是当我在Android 4.3中运行相同 ...

  7. android webview打印,javascript - 如何在Android Webview中使网站上的打印按钮工作？ - 堆栈内存溢出...

    我的网站上有一个模式按钮,在该按钮上附加了一个处理程序函数以打印模式. 该处理程序具有处理"仅打印模式"的代码,并最终运行window.print(). 该按钮的功能类似于浏览器中 ...

  8. android 无法添加帐户,android - Android SecurityException：uid xxxxx无法显式添加帐户 - 堆栈内存溢出...

    我收到错误消息 java.lang.SecurityException: uid 10178 cannot explicitly add accounts of type: net.roughdesi ...

  9. android alarm 的权限,android - Android权限被拒绝-com.android.alarm.permission.SET_ALARM - 堆栈内存溢出...

    我正在尝试通过我的应用设置闹钟,但是当我通过执行以下操作启动意图时,如下所述: 如何在Android中使用意图启动闹钟屏幕? public boolean onMenuItemSelected(int ...

  10. Android 找不到资源异常,cordova - 离子3错误：找不到资源xml / network_security_config - 堆栈内存溢出...

    当我尝试运行" ionic cordova build android"时,出现以下异常: 匿名资源链接失败J:\\ workspaces \\ APCO \\ App \\ ap ...

最新文章

  1. git 拉去merged 仓库的代码步骤
  2. freemarker.template.TemplateException: Expected string. column.nullable evaluated instead to freemar
  3. 2014 Multi-University Training Contest 1 Summary By Luke
  4. Java+MyEclipse+Tomcat (一)配置过程及jsp网站开发入门
  5. nmap结果导出html,nmap的简单使用 - osc_ijgldkz9的个人空间 - OSCHINA - 中文开源技术交流社区...
  6. mysql 优化之 is null ，is not null 索引使用测试
  7. c语言进制转换pdf下载,C语言 十六进制和十进制间的转换.pdf
  8. Win7系统打印机删除不掉的解决方法
  9. 【kafka】kafka record is corrupt（记录损坏）
  10. sqlite 中出现的database table is locked 解决办法
  11. 前端页面卡顿、也许是DOM操作惹的祸？
  12. Ubuntu之sshfs远程目录挂载到本地
  13. 计算机环境变量win10,Win10系统path环境变量怎么设置
  14. debian上虚拟机安装系统
  15. HTML5期末大作业：网上鲜花网站设计——网上鲜花网页设计(5页)HTML+CSS+JavaScript web期末作业设计网页
  16. 东南大学计算机考研面试题,东南大学复试常问问题今天的模拟面试总结
  17. 【VUE项目】VUE+ElementUI电商后台管理系统
  18. java poi_Java POI的学习（一）——Word
  19. 剑指offer2.1
  20. Unity 画折线图

热门文章

  1. C#实现删除自身程序
  2. matlab 算 cramer s v,基于Cramer’s V指数的遥感影像特征选择方法专利_专利查询 - 天眼查...
  3. 企业信息化整体解决方案
  4. CSS中如何让盒子里的文字自动换行
  5. $vjudge-$基本算法专题题解
  6. python读取pdf文档书签 bookmark_用Python为PDF文件批量添加书签
  7. 7-2 查找书籍 （20 分)
  8. php表单生成Excel,PHPExcel多表单数据导出
  9. 宏的录制——制作工资表
  10. 解决方案和产品经理的异与同