adb) installed, and free internal storage of at least twice the download size shown on the Gemini listing in Google Play.
adb (Android Debug Bridge) is a command-line tool that talks to your phone over USB and lets you read hardware data and install packages without the store./data. The installer needs room for the APK *and* the extracted native libraries, so a few hundred megabytes of headroom is the practical floor. Read the real download size from the Play listing.Pre-flight checklist — run through it before touching the phone:
adb devices shows your phone as device, not unauthorized./data.Example: on a Pixel-style device the menu path is Settings → System → Developer options → USB debugging; on Samsung firmware it is Settings → Developer options → USB debugging. The toggle name is identical.
What to do: connect the phone, authorise the debugging key, and dump the four values that decide whether Gemini can install and stay running: Android release, API level, total RAM, free space.
adb devices
Example output:
List of devices attached
R58M12ABCDE device
If the word is unauthorized, unlock the phone and tap Allow on the "Allow USB debugging?" dialog, then run the command again. If the list is empty, the cable is charge-only or the driver is missing.
Now read the profile:
adb shell getprop ro.build.version.release
adb shell getprop ro.build.version.sdk
adb shell getprop ro.product.cpu.abi
adb shell cat /proc/meminfo
adb shell df -h /data
Why: the installer rejects packages that do not match the API level or the CPU ABI (arm64-v8a vs armeabi-v7a), and the launcher gets killed by the low-memory killer when free RAM is thin. Reading the values first turns a vague "it won't install" into a specific mismatch.
How to check: the first three commands each print one line — an Android version such as 14, an integer API level, and an ABI string such as arm64-v8a. /proc/meminfo starts with a line of the form MemTotal: <value> kB. df -h /data prints a row where the Avail column is the usable free space.
| What you check | Command | Healthy result |
|---|---|---|
| Android version | `adb shell getprop ro.build.version.release` | Version is at or above the one named in the Play listing |
| CPU ABI | `adb shell getprop ro.product.cpu.abi` | Matches the APK variant you plan to install |
| Free space | `adb shell df -h /data` | At least 2× the download size |
| Live memory | `adb shell dumpsys meminfo` | `Free RAM:` line shows real headroom, not `0K` |

What to do: free memory first, then install from Play Store if the listing is compatible, or sideload the matching APK over ADB if it is not.
Close background apps and check what is actually free:
adb shell dumpsys meminfo
Look for the Total RAM:, Free RAM: and Used RAM: lines. On a small-RAM phone this is the number that decides whether the app survives its own first launch.
Install route A — Play Store. Open the Gemini listing and tap Install. Route B — ADB, when the store refuses:
adb install -r /path/to/<gemini-build>.apk
Example output:
Performing Streamed Install
Success
Then reduce the chance the system kills the app while you are using it:
adb shell settings put global always_finish_activities 1
Why: the low-memory killer (lmkd) terminates background processes when free RAM drops. Restricting the background process count gives the foreground app a larger share of the same physical RAM, which is the only lever you have on a device you cannot upgrade.
How to check: adb shell pm list packages | grep -i -E "bard|gemini" prints one line ending with your package name. If nothing prints, the install did not land. Revert the developer setting with adb shell settings put global always_finish_activities 0 when you are done testing.
The install flow looks like this end to end:
Phone ──USB──> Computer (adb)
├─ getprop → Android version, API level, ABI
├─ df /data → free space before download
├─ install → Play Store, or "adb install -r file.apk"
└─ settings → background process limit / always_finish_activities
If the store blocks you entirely, the same sideload route used for internally distributed builds applies — see How to Publish a Private App on Google Play and Install It on Android.

What to do: launch Gemini from the shell, then watch memory and the crash log while it runs.
Find the exact package name first:
adb shell pm list packages | grep -i -E "bard|gemini"
Launch it without knowing the activity name:
adb shell monkey -p <package> -c android.intent.category.LAUNCHER 1
Example output (last line):
Events injected: 1
Now attach to the log and take a memory reading while the app is in the foreground:
adb logcat -c
adb logcat | grep -i -E "FATAL|ANR|OutOfMemory"
adb shell dumpsys meminfo <package> | head -n 20
Why: a text prompt that gets an answer proves the app is alive, and the TOTAL PSS figure from dumpsys meminfo proves how much physical memory it actually holds. If PSS approaches the Free RAM figure from Step 2, the next backgrounding will kill it.
How to check: the app window appears, you can send one prompt and get a reply, and dumpsys meminfo prints a TOTAL PSS: line for the package. Leave it in the foreground for a few minutes: no "Gemini keeps stopping" dialog and no FATAL EXCEPTION in logcat means the run is stable.
Problem. The store page opens but the button says the app is incompatible.
Your device isn't compatible with this version.adb shell getprop ro.build.version.release and adb shell getprop ro.product.cpu.abi, compare them with the compatibility block on the listing, then install the APK variant that matches your ABI over ADB: adb install -r <file>-arm64-v8a.apk. If the Android version is below the listed minimum, no APK variant will help — check the documentation for the current minimum.Problem. ADB refuses the package during install.
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]/data filled up. The APK download is not the whole cost — the native libraries are extracted on install, so the real footprint is larger than the file you copied.adb shell df -h /data, then remove what you do not use: adb shell pm uninstall --user 0 <unused.package.name>. Re-run adb install -r <file>.apk and look for Success. A related variant, Failure [INSTALL_FAILED_OLDER_SDK], means the APK targets a newer API level than your phone reports — pick an older build or stop here.Problem. Gemini installs but closes the moment you open it.
FATAL EXCEPTION: main followed by java.lang.OutOfMemoryError, or ANR in <package> in logcat.lmkd kills it.adb shell monkey -p <package> -c android.intent.category.LAUNCHER 1 while adb logcat | grep -i -E "FATAL|ANR" runs in a second terminal. If the crash repeats, use Gemini through your mobile browser instead of the app on that device.Read the device profile over ADB before installing, because the API level, ABI and free space decide both whether the package installs and whether it survives launch. Once Gemini runs, extend the same setup to fully offline models with How to Run an AI Model Locally on Android: Apps and Setup.
How much RAM does the Gemini app need on Android?
The listing on Google Play is the authoritative source for your device and region; if the page does not state a figure, check the documentation. Measure your own headroom with adb shell dumpsys meminfo and compare the Free RAM: line against the app's TOTAL PSS: after launch.
Why does Google Play say my phone is not compatible with Gemini?
Either the Android version is below the listed minimum, the CPU ABI has no matching build, or the model is not on the supported list. Confirm with adb shell getprop ro.build.version.release and adb shell getprop ro.product.cpu.abi before trying a sideload.
Can I install Gemini on a phone without Google Play?
Yes, if you have the APK variant that matches your device ABI. Enable USB debugging, connect the cable, and run adb install -r <file>.apk; a Success line means the package landed. Without Play services the app may still refuse to sign in, so verify after launch.
Will Gemini keep working if I open other apps on a low-RAM phone?
Only within the memory you freed. Set Developer options → Background process limit to At most 2 processes and keep an eye on adb shell dumpsys meminfo; when free RAM drops, the system kills the backgrounded app and you get a cold start next time. For a fully local alternative that does not depend on a network round trip, see the local-model guide linked above.
Status: practical guide. Some statements come from vendors; verify in your environment.
Time to complete: about 25 minutes. You will need: an Android phone or tablet with Google Play, a Google account on the device, a USB cable, a computer with Android platform-tools (adb) installed, and free internal storage of at least twice the download size shown on the Gemini listing in Google Play.
Machine data: Citation Map JSON · JSON-LD · Semantic Embeddings — separate stage.
| Entity | Type | Role |
|---|---|---|
| gemini на старом android | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| gemini мало оперативной памяти | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| gemini не устанавливается на телефон | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| Android | платформа/технология | упоминается в заголовке, TL;DR или разделах гайда |
| компания | упоминается в заголовке, TL;DR или разделах гайда | |
| Gemini | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
No independent confirmation is provided; source claims and editorial conclusions are separated below.
| Source | Type | Role |
|---|---|---|
| No external links | — | — |
Cite as: AI Release. Как запустить Gemini на Android с малым объёмом памяти: требования, настройка и что делать, если приложение не устанавливается. ai-release.org.