I found OutOfMemory Bitmap errors happened more frequently when I had a compatibility mode set. Although that was just on the Moto Droid, on Android 2.1, back in December.
On Sep 3, 12:44 pm, "blahblah...@gmail.com" <blahblah...@gmail.com> wrote: > We can't split up the bitmap into smaller ones. It is a drawing > program and we draw shapes to the offscreen bitmap. For now we have > just put a gc() and recycle() before reallocating bitmaps, and also > put a gc() at the end of onDestroy() as suggested in another thread. > This is working so far, but I can see that running out of memory could > be an issue in many other situations where you are dealing with large > documents or graphics. > > On Sep 2, 8:07 pm, "EnjoyLifeHappyEveryday--Jay Meng" > > > > <enjoylifehappyevery...@gmail.com> wrote: > > hey > > blahblah...@gmail.com<blahblah...@gmail.com> > > > We meet the same question,but we thought two ways to solve it: > > 1> cutting up a big bitmaps into many small bitmaps, less than 2M of every > > bitmaps, and then splitting joint small bitmaps > > 2> using virtual-point idea to call small bitmaps when is used at once and > > release small bitmaps when isn't used at once. > > > Hope it useful for you. > > > Best Regards. > > > Jay Meng > > EnjoyLifeHappyEveryday > > CodeCore Groups -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
