I bet a number of instances are due to HTC devices with Fast Boot enabled in the Settings. BOOT_COMPLETED isn't broadcast when Fast Boot is enabled.
HTC added Fast Boot to the Evo 4G with the Gingerbread update. I think the Thunderbolt also has this feature. Try asking your users to turn Fast Boot off. On Aug 12, 11:45 pm, keyeslabs <[email protected]> wrote: > I'm looking for ideas on this one, as I've been unable to reproduce no > matter how hard I try in any of my local evironements. > > As users are getting upgraded to 2.3+, a small but significant number are > reporting that my app (Screebl) is failing to start on phone reboot. The > app has had a receiver for BOOT_COMPLETED for a long time now, and it seems > to be something new to 2.3 that is causing it to fail for some users. > > What I know: > - The app does not allow users to move to SD, so that isn't the problem. > - It works for the majority of users. > - It happens on stock and custom roms. > > My best working theory is that the new "smart" battery saver and > optimization features in 2.3 are deciding the receiver is taking too long to > boot and throttling it somehow, but I haven't been able to validate this. > If this is indeed the problem, is there any way to deal with the startup of > a service in a more friendly way? The service is threaded properly, and > notifications are registered to make the service less likely to be killed. > The onStart method is reading preferences, registering to receive about a > half-dozen broadcast events (screen on/off, dock events, etc.), and then > starting a thread. That's about it. > > Any ideas on how I can nail this one down? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
