This routinely happens to assorted built in apps on the emulator for me, especially if I unlock the screen before its done churning through all of its "morning ritual", so it might not be your fault. But then again it might.
Would be interesting to find out what happens on a device, and what happens if you let the emulator sit for a while before unlocking the screen (or go in with adb or ddms and wait until nothing is using cpu) On Sep 20, 3:02 am, Samuh <[email protected]> wrote: > That is exactly what I thought when I saw ANR, but I am just setting > an Alarm in it. No network calls. -- 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
