当安装GO短信SMS的BroadcastReceiver不叫 [英] SMS Broadcastreceiver not called when GO SMS Pro installed

问题描述

我已经实现了短信接收器，它拦截收到的短信没有任何问题。 然而，当我安装GO短信，并设置禁用其他消息通知，然后我的应用程序 不接收即使我已经设置意图过滤器的优先级的任何广播消息 很高。有没有办法克服，使我的应用程序总是收到一个短信广播无关 哪些用户做对GO短信的应用程序，特别是因为我的应用程序不显示任何用户界面弹出 通知？当我卸载GO短信，我的应用程序开始变得接收到的SMS广播 并能正常工作。

下面是当收到一个来电短信和GO短信安装日志。有一些 魔由GO短信做了，我不明白。有人能解释都是在这里完成，以及如何 我可以确保我的应用程序不会每次都获得订购的广播通知。

  07-02 19：52：21.674：信息/合子（25209）：受精卵：PID 25209有INTERNET权限，为CAP_NET_RAW接盘能力

07-02 19：52：21.820：信息/ ActivityThread（25209）：发布商去短信：com.jb.gosms.provider.GoSmsProvider

07-02 19：52：21.830：信息/ ActivityThread（25209）：发布商请即MMS短信：com.jb.gosms.provider.GoMmsSmsProvider

07-02 19：52：21.834：信息/ ActivityThread（25209）发布提供com.jb.gosms.im; com.jb.gosms.chat：
com.jb.gosms.im.database.ImContentProvider

07-02 19：52：21.842：信息/ ActivityThread（25209）发布提供com.jb.gosms.schedule.Schedule：com.jb.gosms.schedule.ScheduleProvider

07-02 19：52：21.846：信息/ ActivityThread（25209）：发布商去-MMS：com.jb.gosms.provider.GoMmsProvider

07-02 19：52：21.959：DEBUG / dalvikvm（25209）：GC_FOR_MALLOC释放2657对象/ 173112字节30毫秒

07-02 19：52：22.182：DEBUG / dalvikvm（25209）：试图加载LIB /data/data/com.jb.gosms/lib/libHanzi2Pinyin.so 0x47d4cf70

07-02 19：52：22.182：DEBUG / dalvikvm（25209）：新增LIB /data/data/com.jb.gosms/lib/libHanzi2Pinyin.so 0x47d4cf70共享

07-02 19：52：22.182：DEBUG / dalvikvm（25209）：没有JNI_OnLoad在/data/data/com.jb.gosms/lib/libHanzi2Pinyin.so 0x47d4cf70发现，跳绳的init

07-02 19：52：22.186：信息/ Hanzi2Pinyin_Native（25209）：InitLib的版本= 3141000

07-02 19：52：22.186：信息/ Hanzi2Pinyin_Native（25209）：初始化中

07-02 19：52：22.186：信息/ Hanzi2Pinyin_Native（25209）：文件大小= 155203

07-02 19：52：22.186：信息/ Hanzi2Pinyin_Native（25209）：初始化了

07-02 19：52：22.186：信息/ Hanzi2Pinyin_Native（25209）：实例初始化出来= 21

07-02 19：52：22.186：信息/ Hanzi2Pinyin_Native（25209）：InitLib出

07-02 19：52：22.467：DEBUG / dalvikvm（25209）：GC_FOR_MALLOC释放5960对象/ 376104字节29ms

07-02 19：52：22.815：DEBUG / IMS / Ims3GPP2SmsMessage（25209）：IMSLogcreateFromPdu：调用parsePdu

07-02 19：52：22.815：DEBUG / IMS / Ims3GPP2SmsMessage（25209）：IMSLogpdu解析：000002100202070292A106A85A0008150003100730010610254E9D3A000306110702195220

07-02 19：52：22.815：DEBUG / IMS / Ims3GPP2SmsMessage（25209）：IMSLogparseAddress

07-02 19：52：22.815：DEBUG / IMS / Ims3GPP2SmsMessage（25209）：IMSLogaddress接受：3233292992

收到IM​​SLogbearer数据：07-02 19：52：22.815：DEBUG / IMS / Ims3GPP2SmsMessage（25209）0003100730010610254E9D3A000306110702195220

07-02 19：52：22.815：ERROR /承载数据（25209）：承载获得的数据1

07-02 19：52：22.815：DEBUG / EMS（25209）：为messageType为1 MESSAGEID是115 hasUserDataHeader是假的

07-02 19：52：22.858：DEBUG / IMS / Ims3GPP2SmsMessage（25209）：IMSLogcreateFromPdu：调用parsePdu
 

解决方案

pretty的高价值优先级是不够的，当涉及到GO短信，因为他们已经将他们的绝对最大2147483647（ 2 ^ 31-1）。所以，如果你把这个值你会没事的，只要你的应用程序在安装之前，GO短信是因为当相同优先级的Andr​​oid操作系统将通过广播给老的应用程序（这是我的经验，而不是官方资料） 。如果GO短信先于您的应用程序安装，您应该提醒你一下情况的用户。他们可以配置GO短信不同或卸载它，然后再重新安装它，以便您的应用程序可以工作了。

I have implemented an SMS receiver which intercepts incoming SMS messages without any issues. However, when I install GO SMS Pro and set "Disable other message notification", then my app does not receive any broadcast message even though I have set the priority on intent filter very high. Is there a way to overcome so that my app always receive a SMS broadcast irrespective of what user does on Go SMS Pro's app, especially since my app does not show any UI pop-up notification? As soon as I uninstall GO SMS Pro, my app starts getting incoming SMS broadcasts and works fine.

Here is the log when an incoming SMS is received and GO SMS Pro is installed. There is some magic done by GO SMS Pro which I don't understand. Can someone explain what is done here and how can I make sure my app does get ordered broadcast notification every time.

07-02 19:52:21.674: INFO/Zygote(25209): Zygote: pid 25209 has INTERNET permission, then set capability for CAP_NET_RAW

07-02 19:52:21.820: INFO/ActivityThread(25209): Publishing provider go-sms: com.jb.gosms.provider.GoSmsProvider

07-02 19:52:21.830: INFO/ActivityThread(25209): Publishing provider go-mms-sms: com.jb.gosms.provider.GoMmsSmsProvider

07-02 19:52:21.834: INFO/ActivityThread(25209): Publishing provider com.jb.gosms.im;com.jb.gosms.chat: 
com.jb.gosms.im.database.ImContentProvider

07-02 19:52:21.842: INFO/ActivityThread(25209): Publishing provider com.jb.gosms.schedule.Schedule: com.jb.gosms.schedule.ScheduleProvider

07-02 19:52:21.846: INFO/ActivityThread(25209): Publishing provider go-mms: com.jb.gosms.provider.GoMmsProvider

07-02 19:52:21.959: DEBUG/dalvikvm(25209): GC_FOR_MALLOC freed 2657 objects / 173112 bytes in 30ms

07-02 19:52:22.182: DEBUG/dalvikvm(25209): Trying to load lib /data/data/com.jb.gosms/lib/libHanzi2Pinyin.so 0x47d4cf70

07-02 19:52:22.182: DEBUG/dalvikvm(25209): Added shared lib /data/data/com.jb.gosms/lib/libHanzi2Pinyin.so 0x47d4cf70

07-02 19:52:22.182: DEBUG/dalvikvm(25209): No JNI_OnLoad found in /data/data/com.jb.gosms/lib/libHanzi2Pinyin.so 0x47d4cf70, skipping init

07-02 19:52:22.186: INFO/Hanzi2Pinyin_Native(25209): InitLib in ver=3141000

07-02 19:52:22.186: INFO/Hanzi2Pinyin_Native(25209): Init in

07-02 19:52:22.186: INFO/Hanzi2Pinyin_Native(25209): file size=155203 

07-02 19:52:22.186: INFO/Hanzi2Pinyin_Native(25209): Init out

07-02 19:52:22.186: INFO/Hanzi2Pinyin_Native(25209): Instance out Init = 21

07-02 19:52:22.186: INFO/Hanzi2Pinyin_Native(25209): InitLib out

07-02 19:52:22.467: DEBUG/dalvikvm(25209): GC_FOR_MALLOC freed 5960 objects / 376104 bytes in 29ms

07-02 19:52:22.815: DEBUG/IMS/Ims3GPP2SmsMessage(25209): IMSLogcreateFromPdu : calling parsePdu

07-02 19:52:22.815: DEBUG/IMS/Ims3GPP2SmsMessage(25209): IMSLogpdu to parse : 000002100202070292A106A85A0008150003100730010610254E9D3A000306110702195220

07-02 19:52:22.815: DEBUG/IMS/Ims3GPP2SmsMessage(25209): IMSLogparseAddress

07-02 19:52:22.815: DEBUG/IMS/Ims3GPP2SmsMessage(25209): IMSLogaddress received :3233292992

07-02 19:52:22.815: DEBUG/IMS/Ims3GPP2SmsMessage(25209): IMSLogbearer data received : 0003100730010610254E9D3A000306110702195220

07-02 19:52:22.815: ERROR/bearer data(25209): bearer data obtained 1

07-02 19:52:22.815: DEBUG/EMS(25209):  messageType is 1 messageId is 115 hasUserDataHeader is false

07-02 19:52:22.858: DEBUG/IMS/Ims3GPP2SmsMessage(25209): IMSLogcreateFromPdu : calling parsePdu

解决方案

"Pretty high" value for priority is just not enough when it comes to Go SMS Pro because they've set their on absolute maximum of 2147483647 (2^31-1). So if you put that value you'll be fine as long as your app is installed before Go SMS Pro is because when on same priority Android OS will pass broadcast to "older" app (This is from my experience, not an official information). If Go SMS Pro is installed prior to your app you should warn your users about the situation. They could configure Go SMS Pro differently or uninstall it and then re install it again so your app can work too.

这篇关于当安装GO短信SMS的BroadcastReceiver不叫的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！