They are but they won’t have the desired functionality. You won’t get push notifications for instance.

If this was over an hour, yes. Though you’d typically state it as 100W ;)

I was drawing an average of 2.5kWh after a week of monitoring my whole rack

That doesn’t seem right; that’s only ~18W. Each one of those systems alone will exceed that at idle running 24/7. I’d expect 1-2 orders of magnitude more.

I wouldn’t be so pessimistic. The Netherlands was also a car dependent place that bulldozed neighbourhoods for highways a few dozen years ago and look at where they are now. Change can happen, it just needs a critical mass of supporters and time, lots of time.

Journalism that has any tooth whatsoever would mostly fix this.

As long as no proper journalistic standards exists, populists can pour their BS down the media drain unquestioned, unchallenged. If that’s all you hear about a topic, that’s what you’ll believe.

I consider Beat Saber to be one part of the essentials pack of modern VR gaming. As a rhythm game fan, it’s what got me hooked on VR

I’m not a rhythm game fan; Beat Saber is the only one I play an it’s amazing. It’s worth getting VR for this game alone.

!beatsaber@lemmy.ml btw.

ADB running at boot never worked

Please ensure the props are set as I wrote them.

Also note that the props get reset on every system flash.

It’s weird to me that I could use ADB on recovery, with no issue, even to transfer files, which to me it means there were no authorization issues then, and it never worked on boot.

That’s not weird at all; those are two entirely different operating modes. The recovery isn’t even Android for the most part.

The recovery typically accepts any ADB connection while Android only accepts explicitly trusted ones. ADB also doesn’t typically run by default in regular Android execution.

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.

So what part doesn’t work now? Is ADB running at boot or not? If it is running, are you authorised or not?

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.