Alex313031 / ThoriumOS

ChromiumOS fork with Thorium Browser, x264/x265 codecs, Widevine, Kernel 5.15, Linux firmware/modules support, Nouveau, Intel microcode, and extra packages.
https://thorium.rocks/thoriumos
Other
341 stars 28 forks source link

android support #6

Open crocer211 opened 2 years ago

crocer211 commented 2 years ago

now i know this probably will never happen but i know its possible as fydeos has it and its not licensed by google i know fydeos is commercial but its probably impossible for one person to do

Alex313031 commented 2 years ago

@crocer211 They actually have it open source it's called archero. I also used some things from their raspberry pi and vmware chromiumos overlays to enable widevine and to disable cros-pd (updates chromebook specific firmware)

crocer211 commented 2 years ago

ah well would it even be possible to add it

Renkoto commented 2 years ago

@Alex313031 There is an open source project called Waydroid which is a compatibility layer for Android apps, but only works on Wayland (as the name suggests) and Chromium OS doesn't use Wayland as far i known. Waydroid is a Anbox fork that improves a lot of things from the original project. Archeros should rebase their Anbox implementation to Waydroid. I would recommend you check it out, i don't know how difficult it would be to implement it on Chromium OS.

Alex313031 commented 2 years ago

@Renkoto Quite difficult. Because chromiumos doesn't use wayland anywhere, packages actually specifically disable it. And there are alot of dbus restrictions. And anbox/waydroid use ashmem and binder kernel modules, which are out of tree, and the kernel config for chromiumos disallows out of tree modules, so they would have to be compiled into the kernel.

Renkoto commented 2 years ago

@Alex313031 Waydroid latest builds no longer requires ashmen module, it still requires binderfs to satisfy binder needs tho. So there seem to be efforts to get Waydroid run on a mainline kernel. Waydroid is still in active development, the biggest hurdle now is ARM emulation, because the existing translation layers are proprietary and there are no alternatives.

yavko commented 8 months ago

@Renkoto Quite difficult. Because chromiumos doesn't use wayland anywhere, packages actually specifically disable it. And there are alot of dbus restrictions. And anbox/waydroid use ashmem and binder kernel modules, which are out of tree, and the kernel config for chromiumos disallows out of tree modules, so they would have to be compiled into the kernel.

Isn't wayland used now that lacros is used by default? https://chromium.googlesource.com/chromium/src/+/main/docs/lacros.md