At runtime, Android resize’s images based on need (based on the screen size and resolution). It uses Bitmap’s for doing the resizing internally. Which, obviously, is very memory intensive (kinda allocates memory like crazy). One quick way to fix such issues can be, that you copy all drawable files to drawable-ldpi, mdpi, hdpi folders. This … Read more
What is the maximum amount of memory (in Megabytes / as percentage of the total RAM) that an Android application (that is not a system app) can use? That varies by device. getMemoryClass() on ActivityManager will give you the value for the device your code is running upon. Are there any differences between the Android … Read more
You should probably have a look at Displaying Bitmaps Efficiently which includes several ways to handle large Bitmaps Efficiently, Loading Large Bitmaps Efficiently BitmapFactory.Options options = new BitmapFactory.Options(); options.inJustDecodeBounds = true; BitmapFactory.decodeResource(getResources(), R.id.myimage, options); int imageHeight = options.outHeight; int imageWidth = options.outWidth; This will give you the size of the image before downloading and on … Read more
Way too late for the party here, but i will offer my 0.02$ anyways. It’s not a good idea to use android:largeHeap=”true” here’s the extract from google that explains it, However, the ability to request a large heap is intended only for a small set of apps that can justify the need to consume more … Read more
largeHeap = “true” does not increase the heap size to or by 64 MB: Most apps should not need this and should instead focus on reducing their overall memory usage for improved performance. Enabling this also does not guarantee a fixed increase in available memory, because some devices are constrained by their total available memory. … Read more