Dekkia

That's a bold move.

They'd better make sure the phone holds up and doesn't break within half a year or something.

They both implemented ways to detect each others tags and warn their users.

Afaik that's as far as it goes.

I had a motorola z3 play a few years ago.

Software quality was pretty good. Security updates were sometimes 3-4 months behind and would combine a few monts when they did get released. When I contacted them about it I was told that not all security patches google issues apply to them. I don't have a way of verifying that.

With "normal" updates to different Android versions they where also slow, but I guess that's normal with most Android vendors.

The biggest bummer with that phone was that they killed the module-feature halfway trough it's livecycle in some regions. (You could snap modules to the back that would add additional stuff like a 360° Camera or a bigger Speaker)

There is an official lineageos build for the z3 play which still gets updated I believe. Even very recent motorola phones get lineageos pretty soon after release. (Not shure tho if that includes all or just the flagships)

Oh, I see. I had it on different disks with one efi partition at the start of each. Windows didn't like that.

Why do we need 24GB of RAM in a Phone again?

Windows will leave your EFi linux boot alone.

I wish that was True. Windows loves to overwrite boot partitions during major updates in my experience.

OP was asking about the Fairphone. So opening it up to fix or replace something is clearly not off the table.

I'd say "very slow" is overstating it a bit.

It's not a gaming phone of course, but besides that it's more than enough for everything else.

X is old and very hard to maintain. A lot of rules about how displays work have changed drastically since X became a thing. X went along with most of those changes, which meant the introduction of more and more hacks to keep it running.

Over time X became worse and worse to work on and people realized that it's easier to write something new from scratch instead of trying to fix the decade-old technical debt in X.

That new thing was Wayland and over time most if not all people that where interested in working on desktop compositing pivoted away from X.

Wayland (as it is always the case with new software of that size) didn't hit the ground running. It had various issues at the beginning and also follows a different desig philosophy than X.

Despite a lot of issues being fixed some people are still very vocal about not wanting to use wayland for one reason or another. While some of those reasons are valid, most come from ignorance or laziness to adapt.

Anything that isn't debian-like. I'm just very used to It and can't make myself learn anything else.

Wayland break games

The Steam Deck uses wayland so I guess that's not true (anymore?)