Google plans to migrate installations of the company's Chrome web browser on Android from 32-bit to 64-bit in the near future. While the migration is limited to devices running Android 10 or newer, it should have a positive effect on the performance of the browser and security.
Chrome users on Android may wonder whether their version of the web browser is a 32-bit or a 64-bit application to find out whether their version of Chrome has been migrated already.
Good news is that the process of finding out is relatively easy. All you need to do is load chrome://version in the mobile browser's address bar to get information about the architecture and related information.
Check the first line of the output on the page to find out whether the installed version of Chrome is 32-bit or 64-bit. The browser has been upgraded to the 64-bit version already if you see 64-bit listed in that line; if it still states 32-bit, you are still using a 32-bit version and need to wait for the migration to happen on the device.
The following screenshot shows a 32-bit version of Google Chrome Stable, currently at version 83, and a 64-bit version of Google Chrome Dev, currently at version 85, running on the same device.
Google Play, the official store for Android applications on most devices, does not provide options to download 32-bit or 64-bit versions of applications. There is no official option to migrate manually to the 64-bit version of Chrome if the 32-bit version is still installed or offered. Third-party sites that provide downloads for Android APK files may offer 64-bit versions of Google Chrome that users with Android 10 or newer versions of the operating system may install. While that may make sense in some cases, it is safer to wait for the official rollout of the feature.
Now You: which browser do you use on your mobile devices?
Thank you for being a Ghacks reader. The post How to check whether your Chrome on Android is 32-bit or 64-bit appeared first on gHacks Technology News.
from gHacks Technology News https://ift.tt/3gqYrqx
No comments:
Post a Comment