Yes, but ai gives a lot of false positives. And when you see articles like this its hard to know if its a verified vurnebility or a potential vurnebility.

It was kind of the same with the old vurnebility test tools

The problem I would guess is moving everything to new hardware. I know that many people that are working with VMs tries to ignore this, but software behaves different on different hardware. And this can cause some really hard to catch bugs and performance issues.

Also my guess is that these machine have some custom built hardware that would be hard to emulate

Yes I agree. I have a different reason for it but it would be good with more phone os;s.

But some other in this thread recommended Jolla. And I guess that’s an alternative. I think a android emulator is included but otherwise i think its based on Nokias old megoo OS. The new phone was announced after i bought my fairphone otherwise i probably had bought that.

Yes of course. And now google have made it a bit harder to. Because they only release the source code when they release the new version.

But you are less dependent on google/manufacturer with an open source version of android, Then a closed version. And as far as I know fairphone also release drivers open source when possible ( sometimes its not allowed from the chip manufacturer side )

So atleast in theory you don’t need google for updates to your phone. But in reality much code will come from google.

So its stills matter that you can install an open source variant on your device.

You write them yourself

If its only uses the Foss part of android you really don’t need google for updates. But it helps.

I guess its depends on what you think is important. I went with fairphone and e/os and I’m happy with it. Nothing 3 seems to have a lot higher specs. But for me repairability is important and my old fairphone 4 I was able to keep for atleast a couple of years longer because it was easy to replace USB port and battery.