Troubles with SurfaceView's surfaceCreated/Destroyed

by Dianne Hackborn » Wed, 01 Apr 2009 10:17:26 GMT

Sponsored Links
  don't think you've included enough code.  Where is this 'thread' variable
defined? Where do you clear it after finishing the thread?

I am also confused by the comment saying you "exiting" the activity in
rollDice -- you aren't calling finish, you are just starting another
activity, so the original activity is still there, and its window will just
be re-displayed when it is shown again.

The only thing I can think of is that you aren't handling the case where
your window is hidden and then shown again, causing surfaceCreated to be
called a second time on the same SurfaceView, but again there isn't enough
code here to really tell what is happening.

Also you do know that you can only call Thread.start() once on a particular
thread object, right?

On Tue, Mar 31, 2009 at 6:46 PM, kbeal10 <> wrote:

Dianne Hackborn
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.


Other Threads

1. Dynamic class loading - how?

Is it possible to dynamically load classes from a URL into your
application in the same way as a desktop application can? For example,
can you do a simple boot-strap application which you install onto the
device, that boots up loads the main jars required for the
applications from a server, or from a local jar on the SD for example?


2. Is it possible for an app to replace the NotificationManager?

Or extend it in some way to allow for pre/post-processing of all
notifications and additional workflow?


3. Always running all the processes as ROOT in Android.

4. Opening /dev/SOMETHING from Register buffer in gralloc.

5. LVL advice in the Android Developer Blog

6. Samsung Tab Emulator

7. Sqlite busy timeout - [was error code 5: database is locked]