On Thu, Jun 30, 2011 at 2:01 PM, Thomas Economous <econ0...@gmail.com> wrote: > I am currently working on an app that receives the BOOT_COMPLETED > action using a Broadcast Receiver. The receiver is statically > registered in the AndroidManifest.xml. > > It works on the next boot after installation for android 2.2 but not > 3.1. With 3.1 I have to start the app once before the broadcast > receiver gets the BOOT_COMPLETED action when booting. > > I suspect that something changed in 3.1 that is causing my receiver to > be inactive until the app is started once. > > Has anyone ever seen this before or know how to stop this behavior?
I can confirm the behavior, new to 3.1 (3.0 does not exhibit this behavior). I suspect it cannot be stopped. This feels like a security-related change. Anyway, I filed an issue on it: http://code.google.com/p/android/issues/detail?id=18225 -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in London: http://bit.ly/smand1, http://bit.ly/smand2 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
