BOOT_COMPLETED intent not received on all devices

I created an application that gets BOOT_COMPLETED in the receiver using the following filter:

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

I get this on one device, but I have another device that does not receive it, despite using the same APK. What problems with a particular device can prevent a particular device from getting this intention? Is there a way to test this and create a tool?

+2
source share
2 answers

Make sure that you perform a complete full reboot.

Some HTC devices, for example, have a β€œfast boot” mode that does not start BOOT_COMPLETED , but instead broadcasts android.intent.action.QUICKBOOT_POWERON . As I understand it, the "fast boot" mode basically does sleep mode instead of a true power outage, so they do not send BOOT_COMPLETED as a result.

(why is the Intent action not com.htc.action.QUICKBOOT_POWERON - this is the whole problem) ...

+2
source

Some devices after Android 3.1 will not receive application control after the BOOT_COMPLETED receiver.

Google has long stated that users must first launch an event from the launch bar before this application can go do a lot. Preventing BOOT_COMPLETED from before the start of the first action is a logical continuation of the same argument.

I don't know which devices matter, though.

+2
source

Source: https://habr.com/ru/post/1487522/


All Articles