Skip to content Skip to sidebar Skip to footer

Launch Timeout Has Expired, Giving Up Wake Lock! Activity Idle Timeout For Historyrecord. Is This Something To Worry About?

In my application I use AsyncTask in oncreate. Sometimes I get 'Launch timeout has expired, giving up wake lock! Activity idle timeout for HistoryRecord' in the logs. Can this caus

Solution 1:

Finally Found the answer. This can be ignored.

This means that your main thread is continually running, pumping message through its message queue without ever going idle. If that is what you want, there is nothing to fix. This is why the log message is a warning, not an error.

Source : Google Groups

Post a Comment for "Launch Timeout Has Expired, Giving Up Wake Lock! Activity Idle Timeout For Historyrecord. Is This Something To Worry About?"