Even with root it’s not anywhere near trivial.

You can’t, for instance, make a backup of the userdata partition block device and expect to be able to restore it because it must be decrypted by a key in the phone’s security module that gets wiped when you boot a new ROM.

Well none, it clearly says to call your physicist ;)

Specifically this section:

Why is Magic Earth free? What is the business model?

Magic Earth is free for all our end-users but we also have a paid Magic Earth SDK for business partners. For instance Selectric.de (a supplier for navigation solutions for ambulances and fire trucks), Smarter AI (developing ADAS systems) or Absolute Cycling (using the platform on bicycles). For more info on the SDK, you can check magiclane.com.

it seems to me Android devices are too important to just let them be abandoned if Google goes full-proprietary

I wish it’d be that way.

It wouldn’t just be volunteers. Many companies have a huge stake in this OS and would continue to contribute.

If they don’t contribute now, I doubt they would then. They don’t have any incentive in making the AOSP better publicly because that also makes it better for their competitors.

I think all the OEMs would have individual contracts for source code access anyways. It’s not like open source is the only possible model for industry-wide code collaboration.

A majority of the code would/could be forked and maintained.

What makes you think that? If you’ve ever taken a look at the AOSP source code, you’ll know that it’s insanely huge. This isn’t something a small community of volunteers can reasonably maintain; just like a web browser.

Or a project like GrapheneOS that’s already based on Android code would be expanded to fill the void.

Again, who do you expect to take on that insane task?

GrapheneOS is regular-ass android with some modifications to make it more secure on top. It’s not “based on Android” it is (mostly) Android. It does some important modifications but that’s details, not basic functionality.
If Google were to cut updates to Android, GrapheneOS would (rightly) make a stink but ultimately have to cease because they cannot maintain the entire rest of the Android code to keep it secure. I suspect they’d rather (loudly) end the project than keep limping along without proper security patches.

You should worry about that in any case. The writing has been on the wall for quite some time now.

Google is only going to “respond” by doing things it’s explicitly ordered to comply with and of course extremely reluctantly; only doing the bare minimum that could be seen as complying.

They sure as hell aren’t going to open up the google surveillance services unless explicitly and specifically forced to do so by a court.

This is entirely untrue.

Any part that is already open source will eternally be open source.

Only in the state that it is right now. Google could at any point simply stop releasing the source code with no warning and make all further modifications proprietary.

there are rules about using open source code in projects that requires them to also be open source.

That is only true for copyleft licenses. Licenses that are merely “open source” (also called “permissive”) such as the Apache License 2.0 which the AOSP is licensed under do not give two hoots about what you do with the code as long as you give appropriate credit.

The only part of Android that has a copyleft license is the Linux kernel (GPLv2) and I wouldn’t really consider it part of the AOSP in practice.

If only there was a place where it’s written down what he did? Commenters have yet to discover this mystical record.

Your currently stated requirements would be fulfilled by anything with a general-purpose CPU made in the last decade and 2-4GB RAM. You could use almost literally anything that looks like a computer and isn’t ancient.

You’re going to need to go into more detail to get any advice worth following here.

What home servers differ most in is storage capacity, compute power and of course cost.

• Do you plan on running any services that require significant compute power?
• How much storage do you need?
• How much do you want it to cost to purchase?
• How much do you want it to cost to running?

Most home server services aren’t very heavy. I have like 8 of them running on my home server and it idles with next to no CPU utilisation.

For me, I can only see myself needing ~dozens of TiB and don’t forsee needing any services that require significant compute.

My home server is an 4 core 2.2GHz Intel J4105 single-board computer (mATX) in a super cheap small PC tower case that has space for a handful of hard drives. I’d estimate something on this order is more than enough for 90% of people’s home server needs. Unless you have specific needs where you know it’ll need significant compute power, it’s likely enough for you too.

It needs about 10-20W at idle which is about 30-60€ per year in energy costs.

I’ve already seen pre-built NAS with fancy hot-swap bays recommended here (without even asking what you even need of it, great). I think those are generally a waste of money because you easily can build a low-power PC for super cheap yourself and you don’t need to swap drives all that often in practice. The 1-2 times per decade where you actually need to do anything to your hard drives, you can open a panel, unplug two cables and unscrew 4 screws; it’s not that hard.

Someone will likely also recommend buying some old server but those are loud and draw so much power that you could buy multiple low power PCs every year for the electricity cost alone. Oh and did I mention they’re loud?

The problem wouldn’t be the developers but the reverse engineers.

Though there are of course ways to RE without looking at what the original system does.

It’d look exactly like Russia but bigger. Same corruption, same authoritarianism, same human rights abuse, same power imbalance etc.

That’s typical for plain-text email which this is.

It was being compared to another implementation.

I’m quite certain it was being compared to mainline WINE, so no esync or fsync which themselves usually double FPS in CPU-bound scenarios.

Hers is actually better

[citation needed]

From what I gather from the ntsync feedback thread where some users have tested the WIP patches, it’s not clearly better than esync/fsync but rather slightly worse. Though that isn’t very clear data as it’s still in development. Still, if it was very clearly better than the status quo, we should have already seen that.

can be fully implemented in Wine

It cannot, hence the kernel patch.

It’ll be better but no one really knows the full concrete extend of improvement until it lands

I see no reason to believe it should be “better”. If anything, I’d expect slightly worse performance than esync/fsync because upstream WINE primarily wants a correct solution while the out-of-tree esync/fsync patches trade some correctness for performance in games.

Ideally, I’d like to be proven wrong; that ntsync is both correct and performant but that’s not what you should expect going into this.

That’s just an ACK and Elizabeth replied that she’ll resend again with further changes.

Nothing is in any tree that is going to Linus yet AFAICT.

We could be reasonably sure that it’ll go to Linus if it’s in char-misc but that hasn’t happened yet. I’m also actually not sure whether Greg’s or Arnd’s tree is the canonical one there.

Fake news. It’s merely a re-send of the patches; nothing landed yet.

The Phoronix article and their title makes that clear; you editorialised it to state differently. (Also, that’s…cringe.)

If you have millions a year of free cash flowing around to pay the teams of developers to maintain it, sure.

At that point you could fork chromium too.

Webkit.

What exactly does she need the SD card for? If she just needs to transfer files to and from an SD card, an external reader (via USB) might be sufficient.

3.5mm jack can be substituted with an external adapter too and they’re not even half bad.

Both suboptimal of course but small phones that don’t suck are rare enough as is.

If size is the most important, get an a-variant Pixel.

TL;DR deny the permission via appops via ADB.