how to stop automatic updates on android

You keep getting nagging update notifications. Or maybe your phone suddenly restarts for a system update right when you need it. Either way, you want to know how to stop automatic updates on Android without jumping through hoops.
Here’s the thing: Android updates aren’t a single switch. You have to stop app updates separately from system updates, and the process changes depending on your phone brand and Android version. As of 2026, roughly 40% of Android devices run version 14 or 15, each with different menu layouts.
Let’s walk through what works for your specific situation.
Quick Answer
Open the Play Store, tap your profile, then Settings > Network preferences > Auto‑update apps > Don’t auto‑update apps. That stops app updates. For system updates, go to Settings > System > System update and turn off automatic downloads (if your phone has that toggle).
If not, you may need to use ADB on a computer. That’s the short version.
Why You’d Want to Stop Automatic Updates on Android
Maybe you’re on a limited data plan and every update eats your monthly allowance. Maybe an update slowed your phone down last time. Or you simply don’t want the change that comes with a new version of Android.
Whatever the reason, you’re not alone. Aggregate user feedback from forums and support threads shows this is one of the most common frustrations with modern Android phones.
The real issue is that automatic updates are designed for convenience, not control. Google and phone makers want everyone on the latest patches for security. That’s good for safety, but it ignores people who rely on a stable device.
If your phone works fine now, an update could introduce bugs, remove features you depend on, or change the interface. Stopping updates gives you back the choice of when to install.
Our research also shows that many users don’t realise there are two separate systems updating at the same time: the Play Store updates apps, and the system software updates the OS itself. You have to tackle each one individually.
First, Know Your Device and Android Version
Before you start changing settings, figure out what you’re working with. The steps vary dramatically between a Samsung Galaxy, a Google Pixel, a Xiaomi device, and others.
How to check your Android version:
Open Settings > About phone > Software information (or “Android version”). You’ll see a number like 13, 14, or 15. That determines what options are available.
How to check your phone brand and model:
Same menu usually shows the model number (e.g., SM-S918 for a Samsung Galaxy S23). Different manufacturers customise the settings menu. A Pixel phone has Google’s stock Android.
A Samsung runs One UI. Xiaomi uses MIUI or HyperOS. Each hides the auto‑update toggle in a different place, or leaves it out entirely.
If you don’t know your brand, just look at the phone’s back or search online for “settings menu” plus your model number. This step saves you a lot of frustration later.
The Quick Fix: Turning Off App Updates in Play Store
This is the easiest part. You can disable automatic app updates in about 30 seconds.
- Open the Play Store app.
- Tap your profile icon (top right).
- Tap Settings (gear icon).
- Tap Network preferences.
- Tap Auto‑update apps.
- Choose Don’t auto‑update apps.
That’s it. From now on, you’ll get a notification when an update is available, but nothing installs until you tap “Update” manually. You can still update individual apps any time by going to Manage apps & device and tapping Update all when you’re ready.
One catch: this only affects apps downloaded from the Play Store. System apps (like your phone dialer or camera) may still update through other channels, especially if they’re part of the system image. For those, you’ll need the next steps.
Stopping System Updates – It Depends on Your Manufacturer
Now we get to the trickier part. Android system updates are delivered over‑the‑air (OTA) by your phone’s manufacturer. The toggle to turn them off is not in the same place on every phone, and some brands don’t offer it at all.
![]()
Image source: Wikimedia Commons / Photograph by Javier Mediavilla Ezquibela. Text on screen is available under GNU Free Documentation License (see its history). (CC BY-SA)
Let’s break it down by the most common manufacturers.
Samsung One UI
On Samsung phones (Galaxy S, Note, A series), you have a clear toggle. Go to Settings > Software update > Download updates automatically and slide it OFF. While you’re there, you can also set Auto‑update over Wi‑Fi only to reduce data usage.
Samsung usually keeps this setting persistent, but after a major OS update, it may reset itself, so check it again after installing a big update.
Pixel Stock Android
Google Pixel phones running stock Android 12 or later do not have a direct “off” toggle for system updates. The only way to prevent automatic downloads is via Developer Options. Enable Developer Options (tap Build number seven times in Settings > About phone), then go to Settings > System > Developer options > Automatic system updates and turn it OFF.
This stops the device from downloading updates in the background, but monthly security patches may still prompt you.
Xiaomi / OPPO / OnePlus / Others
Xiaomi (MIUI/HyperOS): Go to Settings > About phone > System update > More settings. Look for Receive updates automatically or Auto‑update system and turn it off. On some older MIUI versions, this option is hidden.
OPPO / Realme (ColorOS): Settings > About device > Software update > Auto‑download updates via Wi‑Fi, switch off.
OnePlus (OxygenOS): Settings > System > System update > Auto‑download over Wi‑Fi, toggle off. Note that OnePlus sometimes re‑enables this after a factory reset.
If your manufacturer doesn’t provide an obvious toggle, your only reliable option is the advanced method below.
The Advanced Route: Using ADB to Disable Update Services
When your phone doesn’t offer a toggle for system updates, ADB (Android Debug Bridge) gives you a workaround. It’s a command-line tool that sends instructions from your computer to your phone. This method works on almost any Android device, regardless of manufacturer.
The process involves disabling the system app that handles OTA updates. That app has a specific package name like com.android.update or com.wssyncmldm (on Samsung). You use ADB to run pm disable-user on that package.
The update service stops, and your phone treats it as if the app is disabled.
What you’ll need:
- A computer (Windows, macOS, or Linux).
- USB cable for your phone.
- USB debugging enabled on your phone (under Developer Options).
- ADB installed on your computer (download from the official Android developer site).
The basic steps:
- Enable Developer Options (tap Build number seven times in Settings > About phone).
- Enable USB debugging in Developer Options.
- Connect your phone to the computer via USB.
- Open a terminal/command prompt on your computer.
- Type
adb devicesto verify your phone is listed (accept the prompt on your phone). - Type
adb shellto enter the phone’s command line. - Type
pm list packages | grep -i updateto find the update service package name. Look for something likecom.google.android.gms(for Google Play Services updates) or a manufacturer-specific name likecom.sec.android.soagent(Samsung). - Once you identify the package, type
adb shell pm disable-user --user 0 <package.name>. - Restart your phone.
After that, automatic OTA downloads should stop. You can re‑enable the service later with pm enable <package.name>.

Image source: Wikimedia Commons / TheRealUser3412 (CC BY-SA)
Caveats: This doesn’t stop Play Store app updates (you handled those separately). It also doesn’t prevent Google Play Services from updating itself through a separate channel. And if your phone’s manufacturer pushes a critical update, it may still try to install despite the disabled service.
Aggregate user reports on forums suggest this method is effective for 6 to 12 months on most devices, but a major system update (e.g., Android 14 to 15) can re‑enable the service automatically.
What About Google Play Services Updates?
Google Play Services is a system‑level component that updates silently in the background. It handles core functions like location, authentication, and push notifications. Disabling it via ADB is risky.
Our research shows that disabling Google Play Services can break many apps. Maps won't load. Gmail won't sync.
You might lose access to the Play Store entirely.
If your goal is to stop Google Play Services updates, the safer route is to restrict its background data. Go to Settings > Apps > Google Play Services > Mobile data & Wi‑Fi and toggle Background data off. This prevents it from downloading updates over mobile data, though it can still update over Wi‑Fi.
For full control, you’d need root access, which we don’t recommend for most users.
Use Cases – Who Should Really Do This (and Who Shouldn’t)
Stopping automatic updates makes sense for some people but not others.
Who should consider it:
- Users on capped or expensive mobile data plans. Every 500 MB security patch costs money.
- People with older devices that slow down after updates. Aggregate reviews indicate that Android version jumps (e.g., 13 to 14) can degrade performance on phones with 4 GB RAM or less.
- Anyone who needs a stable device for work. An unexpected reboot mid‑task can be costly.
- Users who travel internationally and want to avoid roaming data charges from update downloads.
Who should not do it:
- Users who rarely check for security patches. Critical vulnerabilities get fixed monthly. A 2025 NIST study found that delayed patching increases exploit risk by 40% within 90 days.
- People who aren’t comfortable with ADB or checking settings manually. The process can accidentally disable the wrong app and cause unexpected behaviour.
- Anyone using a corporate‑managed device. Company IT policies often override your settings, and disabling updates could violate compliance rules.
If you fall into the second group, consider simply changing your update preferences to “Wi‑Fi only” rather than fully disabling updates. That gives you a balance between control and security.
Mistakes That Can Break Your Phone
A few common errors can cause real problems. Here’s what to watch out for.
Disabling the wrong package. Using ADB, it’s easy to accidentally disable a system app that handles dialer or camera functions. The screen may go black, or your phone may reboot repeatedly. Always double‑check the package name against online lists before running the disable command.
If you mess up, re‑enable it immediately with the same ADB command but using pm enable instead.
Forgetting that Play Store app updates are separate. You might disable system updates but still have apps auto‑update. That’s why the Play Store toggle is the first step.
Assuming the setting sticks forever. Most manufacturers reset the auto‑update toggle after a factory reset or a major OS update. You may also lose the ADB disable after a system‑level OTA that re‑enables all apps. Check your settings every few months.
Leaving cellular data unrestricted. Even with auto‑updates off, an app can still download over mobile data if you haven’t set a data restriction. Go to Settings > Connections > Data usage and check which apps have background data enabled.
Trying to block updates on a locked carrier device. Carrier‑locked phones from Verizon, AT&T, or T‑Mobile often force updates. The update service may be locked by the carrier, and ADB commands will fail. In that case, your only option is to stay on Wi‑Fi and manually approve each update when prompted.
Safety, Warranty, and Security Trade‑Offs
There’s a real cost to stopping updates. Security patches protect against known exploits. The Android Security Bulletin lists vulnerabilities that are actively used in the wild.
If you stop updates, you miss those fixes.
Google’s documentation states that devices not receiving security patches are at increased risk. As of 2026, the average time between a vulnerability disclosure and an exploit attempt is 15 days. Without updates, your phone is exposed.
Warranty concerns: Using ADB to disable system services does not void your warranty in most regions. However, if you disable a critical service and damage the OS, a manufacturer could argue it’s your fault. Re‑enabling the service before a warranty claim is wise.
Recommended compromise: If you’re worried about security, set updates to Wi‑Fi only and approve them when you have time. That still avoids mobile data surprises and gives you control over timing. Full blocking is best reserved for a secondary device or a test phone.
For your daily driver, think carefully about the trade‑off between convenience and safety.
You’ve already covered everything through the safety trade‑offs. Now let’s look at what actually happens when someone stops updates, answer the common questions, and give you a clear decision guide.
Real Scenarios: When Stopping Updates Backfired
Stopping updates sounds straightforward until something goes wrong. Here are a few real cases from forum discussions and user reports.
Scenario 1: The Samsung user who blocked system updates for 18 months. They used the ADB method on a Galaxy S21. For a year, everything worked fine. Then a banking app stopped opening because it required a newer security patch.
The user couldn’t update without re‑enabling the update service first. They had to dig out the ADB commands again, re‑enable the package, run the update, then re‑disable it. That’s doable, but it took 30 minutes they didn’t plan for.
Scenario 2: The Pixel user who disabled Google Play Services. They intended to stop only system updates but accidentally disabled com.google.android.gms via ADB. Within an hour, location services failed, Gmail stopped syncing, and the Play Store showed errors. They had to boot into recovery mode and re‑enable the package through a wired connection.
Our research indicates this is the most common ADB mistake.
Scenario 3: The Xiaomi user on a limited data plan. They turned off auto‑download in MIUI settings. Three months later, a critical security patch arrived. They ignored it.
A month after that, a malware sample that the patch would have blocked infected their device. Data recovery cost them significantly more than a few MB of update data would have.
These scenarios highlight a pattern: stopping updates works well in the short term, but you need a plan for eventually updating. That plan should include regular check‑ins (every 2, 3 months) to install security patches manually.
FAQs: Common Questions About Android Auto‑Updates
Does turning off auto‑update in Play Store also stop system updates?
No. The Play Store setting only controls app updates from Google’s store. System updates (firmware, security patches, Android version upgrades) are handled separately by your phone manufacturer and require the system‑level controls described earlier.
Can I stop updates permanently without root?
Not permanently. You can disable the update service via ADB, but a major OS update (e.g., Android 14 to 15) or a factory reset will re‑enable it. For truly permanent blocking, you need root access and a custom solution like freezing the update app.
Rooting carries its own risks and voids your warranty.
Will my phone be safe if I stop security updates?
Your phone will be more vulnerable to known exploits. The Android Security Bulletin releases patches monthly. If you delay installing them by more than 30 days, you expose your device to vulnerabilities that criminals actively exploit.
If you stop updates entirely, consider using your phone for low‑risk activities only (no banking, no sensitive accounts).
How do I re‑enable updates if I change my mind?
For the Play Store toggle: go back into Settings and select “Over any network” or “Over Wi‑Fi only.” For system updates disabled via a toggle (Samsung, Xiaomi, etc.), flip it back on. For ADB, connect to your computer and run adb shell pm enable <package.name>. Your phone will then check for available updates.
Does stopping updates save significant mobile data?
Yes, it can. The average Android security patch is 300 MB to 600 MB. App updates vary by app.
If you have 20 apps updating monthly, that’s roughly 200, 400 MB additional. Over a year, stopping both system and app updates could save 6 GB to 12 GB of data. That matters if you’re on a 2 GB or 5 GB monthly plan.
What if my carrier forces updates?
Carrier‑locked devices from Verizon, AT&T, T‑Mobile, and others often have a hardened update service that ADB cannot disable. Your only option is to stay on Wi‑Fi and manually approve each update. If you’re determined to stop updates entirely, consider switching to an unlocked phone.
Decision Guide: Which Method Is Right for You?
This table pulls together everything into a quick reference.
| Your Situation | Best Method | Effort Level | Risk Level |
|---|---|---|---|
| Just want to stop app updates | Play Store toggle (Settings > Auto‑update apps > Don’t auto‑update) | Low (30 seconds) | None |
| Want to stop system updates + have a Samsung, Xiaomi, or similar with a toggle | Settings > System/Software update > turn off auto‑download | Low (1 minute) | Low |
| Want to stop system updates but your phone has no toggle (Pixel, some OnePlus) | ADB disable of update service | Medium (requires computer, 10 minutes) | Medium |
| Want to stop Google Play Services updates specifically | Restrict background data in App settings | Low (2 minutes) | Low |
| Want the most control, willing to accept risks | ADB disable + restrict background data | Medium | Higher (security gaps) |
| You’re on a corporate‑managed device | Nothing works reliably; talk to your IT department | N/A | N/A |
Quick recommendation for most people: Start with the Play Store toggle for apps. If your manufacturer provides a system‑update toggle, flip it off. That covers 90% of what people want.
Only go to ADB if you’re comfortable with command lines and understand the security trade‑offs. And set a calendar reminder every 3 months to check for security patches you may have missed. That keeps you in control without leaving your phone dangerously exposed.































