Application fails "unexpectedly" with no errors apparent.

by Justin Anderson » Thu, 03 Dec 2009 00:38:57 GMT

Sponsored Links
 Look at the logcat info (without actually being in the debugger so you get
the crash).  That should give you the information you need

There are only 10 types of people in the world...
Those who know binary and those who don't.


Application fails "unexpectedly" with no errors apparent.

by Trip » Mon, 07 Dec 2009 13:54:52 GMT

 Bingo.  The logcat showed very clearly that I was blowing up because
my activity "did not call through to super.onCreate()". In copying
snippets from the example program I either omitted or copied over the
super.onCreate() call.  The most important thing is that I learned
about logcat.  Thanks.

> >

Sponsored Links

Other Threads

1. A suggested way to deal with long running tasks across context switches.

Like Dianne said, an AsyncTask doesn't take a Context. If you are
careful about what references you keep in the AsyncTask, there will be
no problem at all.

The implementation you link to has two issues in my opinion: it is not
as easy and straightforward as AsyncTask, and you lose the ability to
post progress on the UI thread from doInBackground().

Romain Guy
Android framework engineer

Note: please don't send private questions to me, as I don't have time
to provide private support.  All such questions should be posted on
public forums, where I and others can see and answer them


2. android kernel vs linux 2.6 kernel

Hi everyone,
I'm just trying to hack Android kernel source code.

Although, android is based on linux 2.6 kernel, google claimed that it
was not linux. Does anyone know the differences between android kernel
and linux kernel?

Thanks a lot,

3. Fastest way to load images

4. Accessing a resource

5. A suggested way to deal with long running tasks across context switches.

6. Support for newer kernel versions...

7. EditText for App.Widget