Discussion
Chromium Blog: Bringing Chrome to ARM64 Linux Devices
samtheprogram: [delayed]
yjftsjthsd-h: Curious; given that ARM Chromebooks are nothing new, I'm surprised that it took them this long to ship it to other Linux distros.
eddythompson80: Chrome had no official arm64 build. There are distro specific builds from debian, fedora etc for arm64 chromium, but google had no official arm64 build.There were actually some paid services that provided a distro-agnostic chromium arm64 builds mostly targeting people running puppeteer on AWS ARM lambda. You can see some discussion here https://github.com/alixaxel/chrome-aws-lambda/issues/241
emilbratt: I have been waiting... so many years for this. Like, I figured it would never come. So happy to be wrong. Wonder if it will work well on Raspberry Pi and also if it will come with Hardware Video Acceleration out of the box.
westurner: What is necessary to run Linux ARM64 binaries on Android ARM64?To run conda-forge arm64 Linux binaries on Android in termux requires proot-distro because the ABIs are slightly different FWIU.What is necessary to run Android ARM64 binaries on Linux ARM64?Android Studio, LineageOS or BlissOS's outdated Android containers, a runtime like vinegarhq/sober that emulates just enough of Android.An Android binary that makes Linux compatible syscalls only (that doesn't require Android libraries that aren't compiled for Linux) won't work will it?
mort96: A fully statically compiled Linux ARM64 binary which only interacts with the kernel through syscalls should run no problem on ARM64 Android.Most programs want to interact with various system libraries and system services. Android and your typical desktop Linux system share pretty much nothing aside from the kernel.
mort96: I would have more faith in Raspberry Pi's own patched fork of Chromium to do hardware acceleration properly on the Pi than I would have in Google's generic Chrome build.
westurner: Why is it easier to run a Linux ARM64 binary on Android than to run an Android ARM64 binary on Linux?My guess is that the reason is the same reason that there aren't official updated Android containers
Hackbraten: Looking forward to no longer having to patch glibc on my Linux phone just so I can watch YouTube or use Spotify.
mort96: Wait what, how is glibc patching related to YouTube and Spotify? Could you not watch YouTube using an arm64 build of Chromium or Firefox?
Hackbraten: Spotify requires Widevine CDM to run, and Firefox doesn't come with Widevine on Debian-based distros. The .so hasn't been available on arm64 except for ChromeOS. You can rip the .so out of ChromeOS (that's what RaspberryPi OS did). But ChromeOS uses its own flavor of libc so a couple of patches to glibc are required.Same thing with YouTube. A few months ago, YouTube started to require Widevine CDM if one uses the m.youtube.com site. I can't use the non-mobile site on my phone for performance issues, so I'm essentially locked into Widevine for watching YouTube, too.
oofbaroomf: Wait... weren't there many ARM Chromebooks already?
cmrdporcupine: Sure, and when I worked at Google on Chromecast there was also that build of Chromium.All of that is very different from The G actually provided a packaged official Chrome build, though. Which for some reason they couldn't be bothered to do before (Firefox exists though)
