Out of memory exception on setting wallpaper

by Romain Guy » Fri, 13 Mar 2009 00:27:02 GMT

Sponsored Links
 getWallpaper() is not leaking. The default Home app is using it and
does not experience out of memory errors because of that.

I am more than willing to fix any existing memory leak in the
framework (and I did several times) or in the default apps (and I did
several times) but developers should really stop assuming that out of
memory errors are always caused by the framework. It is *very* easy
for an application to leak or simply to use too much memory.

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


Other Threads

1. Query contact number with URI

HI Gurus,

I have used the action below to pick specific number from contacts:

Intent intent1 = new Intent(Intent.ACTION_PICK,
startActivityForResult(intent1, REQUEST_GET_PHONE);

which returns a "content://***/contact/3" type of URI to me. How do I
query the contact database using this URI to get the "tel://****" uri?



2. OpenGL screen saver issue

My OpenGL app behaves very oddly after the screen saver kicks in.  If
in continuous render mode, the rendering function keeps getting called
during the screen saver. After the user clicks menu twice to
get out of the screen saver, the acivity shows the last screen that
was rendered, but never updates
the display.  I still see the onDrawFrame function being called.  I
just don't see any updates making it to the screen.  This happens in
both continuous and when-dirty rendering modes.

What could I be doing wrong here?  Has anyone else seen something like
This is Android1.6 on ADP1.



3. TelephonyManager.getNetworkOperator() returning different values under same circumstances

4. How to check if the phone is in Standby from a service?

5. https weirdness

6. Using a permission that doesn't exist

7. UPnP