Users of smartphones running Android often face a situation where the next browser update Google Chrome brings more problems than benefits. This could be increased consumption of RAM, the appearance of unwanted functions, or a banal change in the interface that is difficult to get used to. Unlike desktop versions, mobile applications are updated forcibly through the store Google Play, which deprives the user of the ability to choose when to install the patch.
However, there are working ways to block this process. It is impossible to completely prevent the system from downloading updates for a specific application using standard means, but you can create conditions under which the update simply will not happen. In this article, we'll look at methods to disable auto-updates - from simple settings to using debugging tools ADB for advanced users.
Keep in mind that refusing updates means not having the latest security patches. This is critical for a browser that processes sensitive data. Before making a decision, weigh the risks: the stability of the current version versus protection from new vulnerabilities.
Limiting updates through the Google Play Store
The most obvious, but not always effective, way is to change the settings in the application store itself. Default Google Play is configured to automatically download and install updates when connected to Wi-Fi. You can try to disable this feature globally or for a specific application.
Go to the store settings and find the “Auto-update applications” item. There are three options available here: always, only via Wi-Fi and never. Selecting the “Never” mode will stop updating all apps on the device, including Chrome. However, this is a radical solution that will lead to other important applications no longer receiving fixes.
⚠️ Attention: Globally disabling auto-updates in the Play Store settings may lead to some banking applications or instant messengers eventually stopping working due to an outdated software version.
A more targeted method involves checking the settings of a specific application. Open the page Google Chrome in the store, click on the three dots in the upper corner and uncheck the “Auto-update” item, if such an option is available for your version of the store. Unfortunately, in the latest versions of the interface Google Play this function for individual applications is often hidden or removed altogether.
If the “Auto-update” checkbox is missing on the application page in the Play Store, it means that the developer or store policy forcibly enables this function, and deeper intervention methods are required.
Using traffic saving mode
One of the non-standard, but often working methods is emulation of network restrictions. The browser and app store respect the data saving settings set by the user. If you limit background data transfer for Google Play, it will not be able to download the update installation file without your direct participation.
To do this, go to your smartphone settings in the "Applications" section and find Google Play Store. In the Mobile Data or Data Usage menu, turn on the Data Saver or Limit Background Switch. This will prevent APK files from being automatically downloaded in the background.
Similar steps can be done for the browser itself Chrome. Limiting background activity will prevent Google services from checking for a new version and initiating the download process until you manually allow the application to access the network.
- 📱 Go to
Settings → Applications → Google Play Market. - 📉 Find the section
Mobile data and Wi-Fi. - 🚫 Activate the toggle switch
Saving trafficorBackground limitation.
This method is effective if you primarily use mobile data. When connected to Wi-Fi, restrictions may be removed, so this method requires control over the type of connection used.
Disabling updates via ADB (for advanced users)
The most reliable way to completely block the update of a specific package is to use USB debugging and utility ADB (Android Debug Bridge). This method requires connecting the smartphone to the computer and having the drivers installed. It allows you to send commands to the system directly, bypassing the user interface.
The essence of the method is to change the settings of the global or local update repository. The command prevents the package manager from checking for new versions of the specified application. This does not remove the application, but only “freezes” its current state.
adb shell pm disable-user --user 0 com.android.chrome
The above command disables the browser completely, which is not our goal. We just need to disable the update. For this, a more specific setting is used through settings or blocking the update component if it is allocated to a separate process. However, there is no universal “disable update” command, so they often resort to a trick: disabling the component Google Play, responsible for installation, or change priorities.
A safer option via ADB is to revoke rights to install applications for the store. This will prevent the Play Store from silently installing a new version of Chrome.
adb shell pm revoke com.android.vending android.permission.INSTALL_PACKAGES
⚠️ Attention: Using ADB commands requires caution. Incorrect entry of commands can lead to unstable operation of the system or loss of access to important functions of the smartphone.
After performing such manipulations, the application store will no longer have the technical ability to install any updates, including Chrome. To return everything as it was, you will need to grant permission back.
How to return rights to the application store?
To restore functionality, enter the command: adb shell pm grant com.android.vending android.permission.INSTALL_PACKAGES. This will return the ability to install applications manually and automatically.
Comparison of update blocking methods
The choice of method depends on your technical skills and goals. Simple settings in the interface are often bypassed by the system, while using ADB gives a guaranteed result, but is difficult to implement. Below is a table comparing the effectiveness and risks of various approaches.
| Method | Complexity | Efficiency | Risks |
|---|---|---|---|
| Play Store Settings | Low | Low | No updates for other applications |
| Traffic limitation | Medium | Medium | Problems with applications running in the background |
| ADB commands | High | High | Possible system instability |
| Disable auto updates Wi-Fi | Low | Low | Update via mobile network |
As can be seen from the table, the most reliable method is to use ADB, but it requires preparation. Traffic limiting methods are good as a temporary measure, but do not provide a 100% guarantee when changing networks.
A combination of methods (for example, limiting traffic + unchecking the Play Store) increases the chances of success, but does not guarantee complete blocking in the long term.
Managing notifications about available updates
Even if you manage to prevent automatic installation, the system may continue to persistently notify you that a new version is available. Constant pop-ups can be annoying and encourage you to update.
To get rid of visual noise, you can turn off notifications from the app store. Go to Settings → Applications → Google Play Store → Notifications. Here you can disable the notification channel associated with “App Updates” or “Completed Downloads”.
This will not stop the process of checking versions on Google servers, but will make it invisible to the user. You can safely use the current version Chromewithout seeing reminders that the software is outdated.
- 🔔 Open notification settings for Play Market.
- 🙈 Find a category
Application updates. - ❌ Turn the switch to the "Off" position.
This approach is a compromise: technically the update is possible if you go to the store yourself and press the button, but the system will not do this without your knowledge and will not bother you.
Return to the old version of the browser (Rollback)
If the update has already occurred and the new version does not suit you, the question arises: how to go back? On Android, there is the ability to remove updates, which returns the application to the factory version preinstalled in the firmware.
To do this, go to Settings → Applications → Chrome. In the menu (three dots), select “Uninstall updates”. The system will warn that all data will be saved, but the functionality will return to its original state. This is the only legal way to roll back without root access.
After rolling back, immediately apply the blocking methods described above to prevent the system from updating the browser to the latest version again. Keep in mind that the factory version may be very old and may not support modern web standards.
⚠️ Attention: After rolling back to the factory version, some modern sites may not display correctly or not open at all due to lack of support for new security protocols in the old browser engine.
There are also third-party directories of APK files from which you can download specific old version of Chrome and install it manually. However, this requires first uninstalling the new version and carries security risks, since files from unverified sources may contain malicious code.
☑️ Checklist before rolling back the version
Frequently asked questions (FAQ)
Is it possible to completely prohibit updating Chrome without root access?
It is difficult to completely and permanently prohibit updating without root access, since Google services have high priority. However, the combination of disabling auto-updates in the Play Store, limiting background traffic and revoking installation rights via ADB allows you to achieve a result close to 100% blocking.
Is it safe to use an old version of the browser?
This carries certain risks. Older versions do not receive security patches that address vulnerabilities. If you only use your browser to read news from trusted sites, the risk is minimal. But for online banking or entering passwords, it is better to use the current version.
What to do if the “Uninstall updates” button is inactive?
If the button is inactive (gray), it means that the current version of the browser is the factory version built into the system. It is impossible to roll back below this version without flashing the device or obtaining root access and using special system tweets.
Does disabling updates affect the operation of other Google applications?
Globally disabling updates in the Play Store affects all applications. Point restriction via ADB or traffic settings only affects selected components. Google Play Services are usually updated separately and are critical to the operation of the system; it is not recommended to block them.
How to find out which version of Chrome is installed now?
Open the browser, click on the three dots in the upper right corner, select Settings, scroll down and click About the Chrome browser. The current version number and the status of checking for updates will be indicated there.