Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app crashes on customers' cheap Android phones but not on mine

Short answer

Android gives every app a memory limit that depends on how much RAM the phone has, and an app that asks for more can crash with an out-of-memory error. Budget phones have the least, so heavy images or leaks show up there first. Google Play also watches crash rates per device model.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Reviews mention crashes and name cheap or old Android phones.
  • It never crashes on my own phone or on the test phones in the office.
  • The app crashes when opening a screen with many photos, or after being used for a while.
  • The crash rate is fine overall but bad for a few phone models.
  • The app restarts by itself when customers switch to another app and come back.

Why does this happen?

  1. Every app has a memory ceiling, and it is lower on cheap phones

    Android sets a hard limit on the memory an app may use, and the limit varies with how much RAM the device has. If the app reaches the limit and asks for more, it can get an out-of-memory error and crash.

  2. The system closes apps in the background when memory runs short

    Android keeps apps you have left in a cache, and when it runs low on memory it ends processes from that cache. An app that holds on to a lot of memory while in the background is more likely to be ended, so the customer returns to a restarted app.

  3. Low-RAM phones are where memory problems show up

    Android's documentation says memory stress is less common on higher-end devices but can cause problems on low-RAM devices, such as those running Android (Go edition). A test on a recent phone can therefore pass while a budget phone fails.

  4. Google Play measures crashes per phone model

    Play treats a user-perceived crash rate as a core quality measure, with a threshold across all devices and a separate, higher one for a single device model. Google says exceeding a threshold makes the app likely to be less discoverable, and that users on affected models may be steered to other apps.

What can I do about it today?

  1. Open the crash report for your appIn Google Play Console, Android vitals shows crashes by phone model. Write down the three worst models and the Android version on each.
  2. Borrow one of those phonesAsk staff or friends, or buy a second-hand one of the worst model. Use the app for ten minutes on its heaviest screens.
  3. Ask support for details, not just complaintsAsk affected customers which screen they were on, how long the app had been open and whether they had many other apps running.
  4. Hold back new image-heavy featuresUntil the cause is known, avoid adding more large photos, videos or animations to the screens that crash.
  5. Keep the crash report open for the developerDo not clear or ignore the crash groups. They show the exact error and the exact code line, which is the quickest way to the cause.

When should I bring someone in?

  • Android vitals shows a crash rate that Google Play flags, or the app is losing visibility.
  • Crashes are on only a few phone models and nobody can reproduce them.
  • Your developer has no crash reporting set up.

How do I handle it?

  1. Read the crash groups firstI sort crashes by error, screen and phone model. An out-of-memory error points to a different fix than a crash in a library.
  2. Reproduce it on a low-memory phoneI test on a low-RAM device or an emulator limited in memory, and watch memory use while moving through the app.
  3. Reduce what is held in memoryImages are loaded at the size they are shown, lists load a page at a time, and things the app keeps after a screen closes are released.
  4. Release it gradually and watch the numbersThe fix goes out as a staged rollout, and I compare the crash rate for the affected models before and after.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is this a Play Store problem or an app problem?

The app. Google Play only reports the crash rate and, per its policy page, may show the app less when a threshold is exceeded. The cause is in what the app does on that phone.

Can I just stop supporting old phones?

That is a business choice, and it cuts customers. It is usually cheaper to find why memory runs out, and I would check that first.

Will a fix get the app back in search?

Google evaluates recent data, and the page says it generally looks at the last 28 days. I cannot promise an outcome, but lower crash numbers are what Google asks for.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.