[android-developers] Re: Giving up wake up lock / Idle timeout for HistoryRecord: Always

The problem you describe is certainly peculiar. But in any case, in
order for anyone to help you, we need more information.

So, for example, when you say "i try to debug with Eclipse", are you
setting a breakpoint? Where are you setting it? Are you getting the
error message before or after hitting the breakpoint?

Also, where are you seeing the message? In logcat, this is a warning,
not an error message. I see it frequently, but it is not always
associated with an error.

On Dec 13, 1:49 pm, ferostar <erosta...@gmail.com> wrote:
> Hi people,
>
> i've been working on Android for a couple of weeks, no big issues...
> untill now.
>
> No matter what app i try to debug with Eclipse, even my first "Hello,
> World", everything, ends up with a:
>
> Launch timeout has  expired, giving up wake lock!
> Activity idle timeout for HistoryRecord
>
> First i thought (d'oh) it was lock related but actually it isn't,
> given that it prompts me with this warning even if ì'm debugging a
> Hello World with just a TextView, one thread, nothing to worry about,
> an app that worked just great a couple of days ago.
>
> Any ideas?
>
> I can't do -anything right now, debugging is my life at this very
> moment.

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en