"Canvas: trying to draw too large bitmap" when Android N Display Size set larger than Small

AndroidLayoutAndroid 7.0-Nougat

Android Problem Overview


I have a published app that is crashing at startup on Android N when the newly introduced Display size OS setting is set to too large a value.

When I look in logcat, I see the following message:

java.lang.RuntimeException: Canvas: trying to draw too large(106,975,232 bytes) bitmap.

I've traced the issue to an ImageView in my first Activity that shows a nice big background image. The image in question is 2048x1066 and is in my generic drawables directory, so no matter the density, this image will be used.

Everything works okay when the Display size setting is Small. But when I go up to Default, it stops working. If I then swap the image out with a smaller one, it works at Default, but if I go up to Large, it stops working again.

My guess is that adjusting Display size up causes your device to behave like a physically smaller device with a higher pixel density. But I don't understand what I'm supposed to do here. If I put in progressively smaller images for progressively higher resolutions, it won't look good on actually large displays. Or am I not understanding something?

Any pointers would be greatly appreciated.

Android Solutions


Solution 1 - Android

I my case, moving the (hi-res) splash bitmap from drawable to drawable-xxhdpi was the solution.

I had the same problem. I didn't suspect my splash screen to be the problem, since it is displayed when the app is started, but it turned out the splash screen is the problem.

The splash screen in my case has xxhdpi resolution, and it was mistakenly placed in the drawable folder, instead of drawable-xxhdpi. This made Android assume the splash screen had mdpi resolution and scale the image to 3*3 times it's required size and trying to create a bitmap.

Solution 2 - Android

I solved the problem after adding the below code into the Manifest file's application tag in between android: lines.

android:hardwareAccelerated="false"

Solution 3 - Android

I don't know would it help some one, but I'll just leave it here. In my case - problem was only on Sumsung devices with Android 7, and problem was in splash screen proportions. after changing height to 1024 px - everything works fine

Solution 4 - Android

Move your image in the drawable to mipmap-xxhdpi.Your image is in bitmap format so you should put your image in mipmap folder,then it will work

Solution 5 - Android

Try to use Bitmap.Factory class, this link will help you Loading Large Bitmaps Efficiently

Solution 6 - Android

There are some scenarios where Original Bitmap needs be Drawn into ImageViews, Photo Editing apps etc...,

as bay mentioned above setting

android:hardwareAccelerated="false"

will Cause bad UI experince, You can set hardwareAccelerated Only one selected Activity where high res image to be drawn

<application android:hardwareAccelerated="true">
    <activity ... />
    <activity android:hardwareAccelerated="false" />
</application>

Solution 7 - Android

if you use Picasso change to Glide like this.

Remove picasso

Picasso.get().load(Uri.parse("url")).into(imageView)

Change Glide

Glide.with(context).load("url").into(imageView)

More efficient

Solution 8 - Android

The icon files are too large for Android to efficiently and smoothly load. Android recognizes this with its smart algorithms.

You can resize the icon files using Final Android Resizer by asystat. Resize them to "xhdpi" or lower.

Place the resized photos in drawable or overwrite over the existing large icon files.

Then, you're done.

Solution 9 - Android

if you are using glide and you are loading 1k of images at a time or some images then it is issue of glide or whatever you are doing to use to set the image view. you can resolve it just by applying scale type in glide.

Solution 10 - Android

In my case, I just changed the canvas of image which is used in the background using Paint3d(or you can use any other). Here I am sharing a screenshot just go through it.

Solution 11 - Android

it is solved by resizing the images to a lower size.

Solution 12 - Android

Need to add Manifest file's application tag in between android: add below lines.

android:hardwareAccelerated="false"

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionBrian RakView Question on Stackoverflow
Solution 1 - AndroidJohan FranzénView Answer on Stackoverflow
Solution 2 - AndroidCHAMCHOUNView Answer on Stackoverflow
Solution 3 - AndroidkazimadView Answer on Stackoverflow
Solution 4 - Androidkalsara MagamageView Answer on Stackoverflow
Solution 5 - AndroidKhalid AliView Answer on Stackoverflow
Solution 6 - AndroidBalu mallisettyView Answer on Stackoverflow
Solution 7 - AndroidDenizView Answer on Stackoverflow
Solution 8 - Androidlloydyu24View Answer on Stackoverflow
Solution 9 - AndroidDeepak RajputView Answer on Stackoverflow
Solution 10 - AndroidVishaljoshi007View Answer on Stackoverflow
Solution 11 - AndroidHosseinRezaieView Answer on Stackoverflow
Solution 12 - AndroidmahendrenView Answer on Stackoverflow