In one of my test devices, I am receiving this dreaded warning in LogCat:
07-20 09:57:02.093: W/ActivityManager(1159): Launch timeout has expired, giving up wake lock!
07-20 09:57:02.218: W/ActivityManager(1159): Activity idle timeout for HistoryRecord{4072b5e8 com.rero.myapp/.MyActivity}
My initial research revealed that this is a common eyebrow-raiser:
- "The app could have exceeded the VM budget and ran out of memory."
- "This can be ignored."
- Network problem?
- Activity is taking to long to start (too much processing on UI thread?)
- Services & Broadcasts involving HTTP.
- And on and on...
My questions are:
- What are the implications of "Launch timeout has expired"? What does the system do? (e.g. one source claims it kills my application, but I actually see my application proceeding normally after a 1-2 minutes of perceived freezing)
- Is there a way to get notified in my application about this warning?