Android Nexus One Update is causing problems!

by Bob Kerns » Sun, 07 Feb 2010 03:23:01 GMT

Sponsored Links
 Is the entire application disappearing, or is it just this activity?
onDestroy() doesn't necessarily get called in the former case.


Android Nexus One Update is causing problems!

by Alex » Thu, 11 Mar 2010 01:08:31 GMT

 I posted in another thread, but I'll try here as well:

I'm having a similar lifecycle issue on the Nexus One.

Start the app ->OnCreate
Hit back -> no OnDestroy is called
Run app again ->OnCreate, followed by OnDestroy

The wierd thing is that it doesn't actually kill our application, so
it is left in a broken state since we are tearing things down in



Sponsored Links

Android Nexus One Update is causing problems!

by Streets Of Boston » Thu, 11 Mar 2010 04:58:06 GMT

 I guess the 'this' value of the activity of the second onCreate is
different than the 'this' value of the onDestroy after that. It looks
like a new activity is created first and then the old one is
destroyed. The fact that onDestroy is not called when you hit Back
could be OK (when you show the activity again, onResume could be
called), but the fact that a new one is generated and then the old
one's onDestroy is called does not look good. I'm going to check this
out on my apps.


Other Threads

1. SEND Intent similar to Gallery


I'm trying to set up a SEND intent so that my app can share images in
a similar way to the gallery app. The only difference is that my
images are in memory rather than on the sdcard. This seems to present
a conundrum with file system permissions. Any advice appreciated.

This is how I set up the send intent. All seems to be fine:

            Uri u = Uri.fromFile(local_file);
            Intent intent = new Intent();
            String mimeType = "image/jpeg";
            intent.putExtra(Intent.EXTRA_STREAM, u);

The JPEG I want to send is in memory. In order to construct a URI to
pass to the send intent, it seems I have to write the JPEG to disk.
However, if I write the file to the local files directory of my app


then the activity that accepts the send request has an error when it
tries to fetch this image. I think this is because it doesn't have
read permissions on my local storage. And there is no apparent way to
give it the necessary permissions.

So that seems to leave writing the image to the sdcard. Is this
correct, or did I miss a trick somewhere? Using the sdcard as temp
storage seems like a messy solution.



2. ImageButton handling of transparent src pngs

ImageButton doesn't honor the transparency of my android:src png. My
src image is a rounded rectangle, with the remaining portion of the
bounding rectangle set to be transparent. When the button is
displayed, what should be transparent is a dark shadowy color. The
images I'm using are OK, and display the proper transparency when
shown in a browser. android:background="@android:color/transparent"
doesn't have any effect. Or do I need to subclass ImageView directly
to get the desired handling of the src image transparency?


3. What is the name of the built-in android round loading drawable

4. splash screen and low memory

5. single-line text horizontal scroller

6. Can I update my Motoblur firmware 1.5 to the 2.0?

7. Javadoc missing in Eclipse for 2.0, API 5