Quack Doc

most android apps are architecure agnostic “java, kotlin etc” and even apps that are often ship “Universal binaries” which include x86, or split builds for arm and x86

as far as I know the SELinux container is configured, whether or not the distro uses it isn’t up to waydroid but the packaging and host configuration. If there are issues with the SELinux implementation they need to be brought up.

Waydroid also supports apparmor for some protections when SELinux is not available. OFC it’s not as good as selinux (and currently it’s set in warning mode so it doesn’t actually offer protections out of box, please we need people testing this) https://github.com/waydroid/waydroid/pull/906

If you want to use a VM, and anyone who needs a highish level of security should. Bliss OS is a much better option. Though it doesnt offer “native integration” with the host.

It is true that Waydroid isn’t super secure. that being said, it is still just a mostly stock android (unless you download gapps). Root is not exposed to the container so unless an exploit is found it is reasonably secure. There are measures waydroid can take to make it more secure. but as it stands it’s “not bad”

There is an unofficial script that ads arm emulation. Note before anyone asks, it will not become officially supported by waydroid.

I did have some scripts to do this more properly but the shift to A11 broke a lot of stuff, I plan on revisting it when the A13 (or was it A12) work is done and released as stable.

That’s actually horrid. My router is android only and I thought that was bad.

Waydroid works inside of Avian perfectly fine, but I would still generally recommend either just using Bliss OS or the native host. You can run Waydroid using something like Cage or Weston if you’re on X11.

If you are running on something like VirtualBox, you may need to disable hardware acceleration for GPUs. QEMU has working GPU acceleration.

This would be a really nice change

I did and quite frankly it’s trash, XDG portals are a clunky and quite frankly terrible and poorly thought out api. I’m not the only one that disagrees with this sentiment as multiple people are trying to get protocols like ext-screencopy-v1 for screen recording and ext-foreign-toplevel-* for window management upstreamed into wayland so that xdg portals aren’t necessary for these use cases. I don’t mind the reliance on pipewire too much, but I too think that It shouldn’t be necessary for screen capture.

IMO It is one of nate’s worst takes of all time if not the worst. Usually I agree with most things he writes, but not this, xdg-portals is a travesty, pipewire is nice and all, but I don’t see why we should need an entire media system for basic screen capture capabilities. and clearly im not alone on this sentiment

woops my bad, I mean to link this https://github.com/probonopd/wayland-x11-compat-protocols it’s a repo of going to be protocols, to fill in the gap instead of pretending the issue doesn’t exist

Really glad probonopd is doing this, X11 is dying but wayland isnt ready to replace it, so it’s nice to have this

EDIT, paste didn’t work https://github.com/probonopd/wayland-x11-compat-protocols

I use mpvpaper on sway and cosmic

not to mention the totally bogus comparison they preformed which is an insult to anyone who has a even an inkling into how image metrics and comparisons work and more then 30sec to compare

Google has been trying to clamp down on people daring to run software they don’t approve on their devices.

“Google” isn’t. ChromeOS is actually providing more and more flexibility then ever. Android however is the exact opposite. One must keep in mind that google isn’t some monolithic company, it’s very fractured and has many independent teams, the best showcase of this is JXL. 3/4 top contributors to libjxl are google employees, and yet chromium decided to remove JXL support citing bogus reasons generated by obviously flawed testing and analysis.

crostini is pretty damn great but it’s important to know what it IS and it’s actually really simple. Crostini is two things combined into one

Firstly A VMM

Crostini uses the crosvm VMM which is can be thought of kinda like an inhouse version of qemu but designed to explicitly run natively integrated and high performance VMs safely instead of being a swiss army knife (KVM acceleration, virtio peripherals etc) (PS. it’s written in rust too) They use it for chromeOS to integrate android support (on select newer devices) and linux. It runs a supervisor distro which can run containers inside of it.

ChromeOS calls the VM termina. Im not sure what distro is running in the VM, or if its a specialized one. I forget

Next is the containerization

It is a lot like distrobox, It can run a myriad of distros but the key part of it is sommelier. A wayland compositor designed to render windows through virtio-wayland, an extension of virtio-gpu. In practice very similar waypipe which rendering wayland windows to a remote wayland client using network/sockets (Yes, it does support AV_VSOCK so it can work with qemu.)

Sommelier is run in the containerized Distro, running on the TerminaVM. Using termina provides excelent security and performance, and then using LXD inside of termina provides excellent flexibility

The guts of “crostini” crosvm, virtio-wayland, sommelieris all open source, you can actually (with some degree of hassle) set this up entirely yourself, or do what I do, and run qemu + waypipe for a similar experience. Waypipe is much easier to setup however it comes at a preformance detriment since qemu virtio-gpu perf is worse then crosvm (no vulkan support in qemu yet still)

EDIT: s/Architecturally/in practice/ I have no idea why I said Architecturally. they are quite different things. I must have had a brain fart

I just get any windows tablet that has good linux support and throw bliss on it, Linux tablet situation is bad right now

I am aware of that, but even with it there’s still a decent amount of waste.

I fell for the lie of flatpak not being bloated, I just nuked flatpak from my PC since I just run arch anyways. Im not sure if repo is safe to remove. You might be able to run rmlint -g and see how much data can be deduplicated on an FS level, I never checked myself since I run f2fs, but if you run an FS with dedupe capabilities it may work for you.

For sure try out olive You can’t do automatic stabilization but manual works fine, However I will always use gyroflow whenever possible anyways. If needed you can easily script motion tracking data from 3rd party sources.

but it is properly color managed throughout the entire editor so doing color correction works properly and accurately. the node system is really powerful despite it’s early nature, and as far as I know olive is the only FOSS editor with proper OCIO integration, which means you get industry standard color management tooling including things like ACES support. You also have OTIO support for importing and exporting editorial cutting information.

i’ve been using sonobus lately and it’s been pretty good, I had latency issues when I tested the android app a long time ago, ill have to test it again