On a normal unmodified phone you have to manually confirm each app you want to install. so no auto-updates in the background etc.

Background app updates are possible since Android 12, Fdroid just took two years to implement the new API (and you have to do a fresh install of the apps - apps already installed using the old API still require confirmation on each update). There is still friction on the initial install though.

This is the a model, it won't have optical zoom either way.

It's easy to dismiss as an ad. I did, too.

Well, Vivaldi's built-in in adblock apparently agrees with this categorization. The video shows up if I disable it. Lol

Then what's the meaning of this whole part?

On non-corpo linux syslog can be disabled if you want, though I'd prefer to just symlink/mount /var/log to a memory filesystem instead.

Is it just a random tidbit that could be replaced with a blueberry muffin recipe without any change of meaning of the whole comment? Because it sure won't help OP at all with their Arch-specific question, so it's either that, or it provides contrast to the "corpo Linux", which is how I interpreted it.

And here's the remaining part of your comment I left out, just to make sure people won't lose the context between two three sentence long comments (for those without any attention span, it comes before the previous quoted part):

If you're on arch you use redhat's garbage.

But it's a design for designs - it tells you how to design your own UIs, it doesn't dictate what for example a calculator app should look like. You can follow Material Design and still end up with a terrible UI design.

Surely that's enough for some distinction, right?

Vista's problem was just the terrible third party drivers and the fact that it was preinstalled on machines it had no business running on. 7 didn't improve much on it (except fixing the UAC prompt so that it no longer made you feel like you're using Linux with misconfigured sudo timeout), but it had the benefit of already having working drivers from Vista and proper hardware capable of running Vista/7.

The Quick Share option missing is weird - Nearby Share/Quick Share is supposed to be available on every Android 6 or newer device since roughly 2020. And it's supposed to be able to automatically figure out a reasonable way to connect the devices (LAN if they are in the same network, Bluetooth or WiFi Direct otherwise).

xrandr is Xorg only, it doesn't work with Wayland. You should be able to make SDDM use your Plasma display configuration - https://wiki.archlinux.org/title/SDDM#Match_Plasma_display_configuration

No clue if that's going to fix your issues, but at least it's supposed to work with Wayland.

Cool, so it's like two years ago

Oh...

Oh no

It is, and it's the reason Pixel 6 and 7 series had so many issues with poor battery life and weak modem. Although it appears that the third generation Tensor CPUs in Pixel 8 have major improvements on both of these pain points.

Still, that probably brings Pixel 8 only to the cheap-ish midrange standard when it comes to cell signal, as the Pixel 7 phones were atrocious and 6s were apparently even worse.

No, face unlock on Pixels doesn't do anything to illuminate your face, it simply refuses to work if the lighting's too dim. It's actually worse than the face unlock in Google Smart Lock in dealing with low light environments.

I'd love it too with my 7a, but there's no way Google does something nice just 'cause. They've already sold the phones with a shorter support window and they gain nothing by releasing more updates for those devices.