BOOT_COMPLETED not called on Honeycomb after export

Question

I have a very weird problem, and none of the questions already on the website have an answer or the same problem.

I have an app that receives BOOT_COMPLETED.

Answer 1

This works as intended, assuming you are using android 3.1. and later.

Applications installed on 3.1 and later are in the stopped state after installation. They have to be explicitly started by the user at least once to get out of that.

Applications in stopped state don't receive any broadcast intents, including BOOT_COMPLETED.

See Android 3.1. - API Overview - Launch controls on stopped applications