I found a similiar problem going from the Samsung Galaxy Tab on 2.2 with 48MB heap to a Motorola Xoom on 3.0.1 with 48MB heap.
You may notice that previously if you intentionally made an OutOfMemoryError, Honeycomb seems to try to allocate twice as much RAM. As it turns out, Honeycomb defaults to 32 bit bitmaps, so you might want to override it to 16-bit like: BitmapFactory.Options o2 = new BitmapFactory.Options(); if (compressColor) o2.inPreferredConfig = Bitmap.Config.RGB_565; o2.inPurgeable = true; o2.inInputShareable = true; o2.inSampleSize = (int) scale; bitmap = BitmapFactory.decodeStream(fis, null, o2); The app I am building also uses a big 1280x800 background drawable defined in XML - I wonder if this is also eating my heap space, and if so, whether it would be better if I loaded it as a 16-bit Bitmap and set the background in code! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
