Android多图加载OOM问题求助：Manifest修改不生效及优化困惑

Hey there, let's break down your two problems step by step—these are super common hurdles in Android dev, so don't stress too much!

1. Manifest.xml Changes Not Taking Effect After Deleting Build Folder #

Deleting the build folder is a good first step, but sometimes the system holds onto cached data that's causing your changes to get ignored. Here are some fixes to try:

• Invalidate Android Studio Caches: Go to File > Invalidate Caches... > Invalidate and Restart. This clears out all cached build artifacts and forces AS to rebuild everything from scratch. I've lost count of how many times this fixed stubborn manifest issues.
• Check Build Variants/Product Flavors: If you're using multiple flavors or build variants (like debug/release), make sure you're modifying the correct manifest file for the variant you're running. Sometimes flavors have their own manifests that override the main one—double-check the src/[flavor]/AndroidManifest.xml files.
• Clear Gradle Cache: Delete the .gradle folder in your project's root directory, then run File > Sync Project with Gradle Files. Gradle sometimes caches old manifest data, so this forces a fresh sync.
• Verify Manifest Merging: Open the merged manifest (in Android Studio, go to Build > Analyze APK and pick your built APK, then look at the merged manifest) to confirm your changes are actually being included. If they're missing, you might have a merge conflict with another manifest file.

2. Out-of-Memory (OOM) When Loading 5 Images (Only Background Fixed) #

Great job fixing the background image—let's get those other four working without blowing up the memory. Here's how to optimize further:

• Align Loading Logic with Background Image: First, double-check that you're applying the same optimization tricks (like scaling down the bitmap) to the other four images as you did for the background. It's easy to miss a step when copying code or setting up loaders!
• Use a Image Loading Library (Glide/Coil): Trust me, this is the easiest way to avoid OOM. Libraries like Glide or Coil handle automatic bitmap resizing, memory/disk caching, and resource recycling out of the box. For example, with Glide:

  Glide.with(this)
      .load(R.drawable.your_image) // or a file/URL
      .into(your_image_view)
  

  It automatically scales the image to match your ImageView's size, so you never load a full-resolution bitmap into memory when you don't need it.
• Manual Bitmap Optimization (If You Can't Use Libraries): If you have to load bitmaps manually, make sure every image uses these settings:
  • Calculate the right inSampleSize: Use BitmapFactory.Options with inJustDecodeBounds = true to get the image's original dimensions, then compute a sample size that scales the image down to fit your ImageView. This reduces the bitmap's memory footprint drastically.
  • Use a memory-efficient bitmap config: Set inPreferredConfig = Bitmap.Config.RGB_565 (if your image doesn't need transparency) instead of the default ARGB_8888—this cuts memory usage in half.
  • Recycle bitmaps when done: In your Activity/Fragment's onDestroy method, recycle unused bitmaps and set their references to null to free up memory:

    if (bitmap != null && !bitmap.isRecycled()) {
        bitmap.recycle();
        bitmap = null;
    }
    

• Check for Memory Leaks: Use Android Studio's Memory Profiler to see if your bitmaps are being held in memory longer than they should be. Common culprits are static references to bitmaps, or not unregistering listeners that hold onto image views.
• Temporary Fix: Enable Large Heap: As a quick test, add android:largeHeap="true" to your <application> tag in the manifest. This gives your app more memory to work with, but it's not a long-term solution—use it to confirm OOM is caused by insufficient memory, then focus on proper optimization.
• Optimize Image Files: Convert PNGs to JPGs if you don't need transparency, and use tools like TinyPNG to compress the image files without losing quality. Smaller file sizes mean smaller bitmaps in memory.

内容的提问来源于stack exchange，提问作者IntFooBar