The arm64 version of Google Chrome has finally arrived on Linux, a development that will be of particular interest to users of Raspberry Pi and similar architectures. This new version brings a long-awaited feature: native support for Widevine, essential for streaming platforms. This significant step demonstrates Google’s stronger commitment to open source and alternative ecosystems.
Historically, Chromium offered a solid foundation but didn’t allow for seamless synchronization of Google accounts or access to DRM modules. This new version partially addresses this shortcoming, enriching the user experience on arm64. This is a game-changer for online video enthusiasts on Linux.
Google Chrome arm64: a true revolution for streaming under Linux
Until recently, Chrome’s official download page favored the amd64 package, which is incompatible with ARM-based machines like the Raspberry Pi. By simply modifying the URL and replacing “amd64” with “arm64”, it becomes possible to obtain a .deb package that can be installed perfectly via apt, without any issues.
The browser offered here is Chrome 150 on the stable channel. This is a great opportunity to dust off that old Raspberry Pi 5 from the attic, because while Chromium doesn’t offer built-in Google account synchronization, this version provides that convenience. For Linux system administrators, it’s like giving modest machines a new lease on life, with all the best features Chrome has to offer.
Widevine: the key to DRM finally natively on ARM64
Widevine, this digital rights management technology, is vital for unlocking access to protected content on Netflix, Disney+, or Amazon Prime Video. Until now, its integration on ARM64 remained cobbled together, often clumsily extracted from ChromeOS. This time, Google delivers a module compiled natively for aarch64, installed in /opt/google/chrome/WidevineCdm/_platform_specific/linux_arm64/.
It’s a bit like lubricating an engine before dismantling it: a clean build ensures increased stability and performance. As a result, this Chrome version stands out from derivative browsers that cannot offer this exclusive DRM compatibility.
Limitations remain despite a significant technical boost.
However, Widevine integration doesn’t open all doors. Google applies a “Software Secure” security restriction to Linux. In short, this limits video resolution to around 720p or 1080p. 4K playback and HDR remain out of reach due to the lack of a TEE environment, a secure hardware execution environment absent on these machines.
This limitation isn’t unique to Raspberry Pi; it also affects Linux PCs running Intel or AMD processors. Testing 2K YouTube playback on a Raspberry Pi 5 yielded good results, even without dedicated hardware decoding. The performance was stable, significantly better than that offered by Firefox Snap on the same configuration.
The promises not highlighted by Google
As the announcements progressed, Google promised a Chrome arm64 port including Google Pay, improved Safe Browsing protection, and features related to Gemini. This stable version has been available for several months, but remains discreet, not officially promoted by Google.
The port is clearly aimed at Raspberry Pi enthusiasts and Snapdragon PC users. The browser gains fluidity and reliability, paving the way for new uses of low-power machines with a full Chrome experience.
How to install Google Chrome arm64 on Raspberry Pi?
Simply modify the download URL by replacing ‘amd64’ with ‘arm64’ to retrieve the .deb package. Then, install it with apt, which adds the Google repository for updates.
Does Widevine allow 4K playback on Linux ARM64?
No, playback is limited to 720p or 1080p primarily due to the absence of TEE, a secure hardware execution environment. This restricts the maximum resolution even if the video is compatible.
Chromium does not support Google synchronization, what changes with Chrome arm64?
Chrome arm64 brings native synchronization of Google accounts, including passwords, extensions and bookmarks, which Chromium does not offer by default.
Is this version of Chrome arm64 stable?
Yes, it is based on the stable channel and features native compilation for ARM64, thus ensuring stability and decent performance.
Why isn’t Chrome arm64 given more prominence?
Despite its existence, Google remains discreet about this port, probably to focus on future improvements or targeted uses such as Raspberry Pi and Snapdragon processors.
Source: www.clubic.com