未在所有设备上收到 BOOT_COMPLETED 意图 [英] BOOT_COMPLETED intent not received on all devices

查看:43
本文介绍了未在所有设备上收到 BOOT_COMPLETED 意图的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我创建了一个应用程序,它使用以下过滤器在接收器中接收 BOOT_COMPLETED:

I have created an application that receives BOOT_COMPLETED within a receiver using the following filter:

<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED" />

我在一台设备上收到了这个,但我有另一台设备虽然使用了相同的 APK,但没有收到这个.哪些特定于设备的问题会阻止特定设备接收此意图?有没有办法对此进行测试并创建补救措施?

I receive this on one device but I have another device that does not receive this despite using the same APK. What device-specific issues could prevent a particular device from receiving this intent? Is there any way to test for this and create a remedy?

推荐答案

Android 3.1 之后的某些设备在 BOOT_COMPLETED 接收器后不会给予应用控制权.

Some devices after Android 3.1 will not give the app control after the BOOT_COMPLETED receiver.

谷歌早就说过,用户应该首先从启动器启动一个活动,在那个应用程序可以做很多事情之前.防止 BOOT_COMPLETED 被在第一个活动启动之前交付是相同的逻辑扩展争论.

Google has long said that users should launch an activity from the launcher first, before that application can go do much. Preventing BOOT_COMPLETED from being delivered until the first activity is launched is a logical extension of the same argument.

我不知道它对哪些设备有影响.

I do not know which devices it makes a difference on though.

这篇关于未在所有设备上收到 BOOT_COMPLETED 意图的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆