[android-developers] Re: } catch (OutOfMemoryError E) {

I think I'm a little confused about how bitmap scaling is working with
Android 2.0. We have an activity with a ListView which displays a
small image (let's say 65x90sp) in each list item. The image source
is just an image from the camera but we have specified that 65x90sp
size for the ImageView and specified it to scale using fitXY. This
code works on all current phones except the Droid. We've tested with
over 20 items in the list and no memory issues occur whatsoever on any
phones except the Droid where it fails as soon as there are more than
1 entry in the list (OutOfMemoryException).

I assumed that when you specified fitXY in the layout, that under the
covers the bitmap was being scaled to that size before display and
thus greatly reducing the amount of heap memory required to display
it. This does not seem to be happening on the Droid/Android 2.0.

Is there something about how ListView works that I'm unaware of (with
regard to how memory is allocated per list item) or is something
working differently with regard to memory usage and fitXY scaling with
Android 2.0?

Thanks,
Derek

--
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