I had a similar problem. I have mostly solved it by switching to a cache of softreferences to the actual compressed image bytes (not the bitmap). And then I use bitmapfactory to create the fully exploded bitmap as needed.
The phones have very little memory for how big their screens are. Do some basic map using the bits-per-pixel and the width and heights of your images. You might be surprised how large your bitmaps are given the size of the compressed images. -E On Aug 10, 1:28 pm, Davide <[email protected]> wrote: > 2010/8/10 Streets Of Boston <[email protected]>: > > > The raw binary data of your image (e.g. RGB_565 or ARGB_8888) is not > > part of the java heap. The dalvik-vm does not 'see' this heap. But the > > raw binary is counted towards the total heap allowed for your app's > > linux-process. That's where you see the discrepancy. > > > And yes, i would cache your images on your file-system. > > Many thanks for the response. You explaination is the same as: > > http://stackoverflow.com/questions/2131947/android-memory-allocation > > So i will try to download the bytes of the image and save they on the > external memory. Then when necessary I convert it on the fly in bitmap > and set on the image view! > > But was is strange is that I have copied the code from internet. > My starting problem was to lazy loading images in a listview. > Examples in internet use ArrayList of Bitmaps! > > Where can I write the downloaded images to be quickly readed after? > I think sd card i slow ... or? > > -- > _| _. o _| _ > (_| (_| \/ | (_| (/_ -- 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
