Difference between BOOT_COMPLETED and QUICKBOOT_POWERON on Android

Question

I have created BroadcastReceiver to schedule my Service execution every 30 seconds. This is what I have in AndroidManifest.xml :

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

This is working great now, but only after I added QUICKBOOT_POWERON action. Before that I had only BOOT_COMPLETED and when I reboot emulator or phone while debugging, my service would never start. So my question is what is the difference between these two and when to use each?

Solution

Intent android.intent.action.BOOT_COMPLETED is received after a "cold" boot.

Intent android.intent.action.QUICKBOOT_POWERON is received after a "restart" or a "reboot".

Check here

Comments

[Mitulát báti]

I restarted my phone (Lenovo P2) an received a Boot_completed intent... didn't check the other one though.

[Dmytro Batyuk]

I think it's applicable only for Google emulator. Real devices always do "cold" boot

[android developer]

Is this still useful nowadays to use android.intent.action.QUICKBOOT_POWERON ? If not, from which API ?

[DADi590]

But that permission is not anywhere! Where actually did people heard of this permissio? Should it even be used if Android Studio doesn't find it?? I have internal/hidden APIs showing and it still doesn't exist, it seems.