Because Google is expert at making open source stuff become increasingly out of touch with their mainline, closed source releases, while remaining nominally open-source.

AOSP itself used to be 80% open-source Android, and 20% Google's proprietary shit on top of it made it Google's Android. Then slowly, over the years, Google quietly moved the open source stuff into their proprietary stack - or rather, they let the open source versions become stale and innovated only in their proprietary versions. As a result, AOSP is a shadow of its former self, and on the verge of becoming irrelevant in a world where apps all but require Google's stack to function.

They did that totally on purpose: the early days of open Android ensured its success, and now that the market is solidly entrenched, they're closing it and pushing the open players out.

The same will happen with this ChromiumOS-AOSP frankenmonster (I'm assuming they meant ChromiumOS will be merged into AOSP, not ChromeOS, obviously...): it'll be nominally open-source but practically unusable, or at least undesriable to use. And since both will be merged, Google will be able to deprecate both at the same time with no escape path for either of the former halves for the open-source players.

Google never does anything that doesn't serve their best interests. And at this point, usable, open AOSP or ChromiumOS ecosystems are not in their best interests.

they didn't announce they're stopping AOSP, only that Chrome OS is getting merged into it. unless you have conflicting sources?

how?

Which I read as:

Google deals the final blow to custom ROMs.

So basically the thing fans have been wanting them to do for about a decade now that Samsung tried doing with Dex. I recall in the mid 2010s people were speculating the super secret project “Fuchsia” was them combining the two. Only to learn it was their embedded OS for IOT things.

Google’s plan to merge Chrome OS into Android also comes as Android itself gains several features for large displays. These additions include a proper desktop mode, desktop windowing, improved external display management features, and improved app adaptability.

Honestly makes sense. They're definitely behind Samsungs Dex.

@askat expect to combine

Is this interesting for people who don't care about ios?

https://f-droid.org/packages/business.braid.f_wallet

Ah, sorry about that. It's a redirect from Google, of course. You've got the correct URL now.

Wtf is that link? What generated that? The site address is https://www.passsource.com/info/create.php

"AOSP isn't dead, but Google just landed a huge blow to custom ROM developers for Pixel devices"

FTFY

The news is about pixel phones. Somehow this article manages to paint pixel phones as the only android devices that matter.

Here's a site to create a pkpass file.

Create a Pass - PassSource - Create passes for Apple Wallet (formerly Passbook) and manage your own custom iOS passes for Pass Kit for your business for free for iPhone and Apple Watch using PassSource https://share.google/mwuRrccpzeUCCyziO

It sounded like your requirement could accommodate either Apple or Android wallet solutions. This runs on Android, add the pkpass file, you're done.

Took me about 30 seconds to install and add an old boarding pass. Maybe you be more specific in your requirements?

I've been happy with Catima.

FossWallet is only for Apple's Passbook files.

I guess you may need to use some google pay alternative? If yes, afaik there is no foss option. For contactless payment with my phone I use curve, it does not require google play services, so while it's closed source, it should work on a completely degoogled phone. If you can't find a foss solution, I recommend this: https://play.google.com/store/apps/details?id=com.imaginecurve.curve.prd

I have no experience but FossWallet looks interesting.

After battling my way through a samsung one, i can see why. Or could.

The "reference target" argument is kind of a joke. Other manufacturers don't publish everything for a reference device, so we can't have any real hardware one, including by Google. Sure. That was the entire appeal of Pixel devices for some people.

I never knew about the spaceship Easter egg, good fun.

Edit: it's the recent Android version easter egg that's mentioned in the DISALLOW_FUN section.

So like the majority of people that want this want to be able to do this on Linux, most people are not going to do that, who are normies inside of corporate ecosystem. Just one more... gimmick. Also, if I put a cell phone modem with a GPS tracker on your computer, would you be okay with that? Also, all the other apps that spy on you. Google is such a dog shit company.

Nice, that look useful. Sadly I can not try it, since Google has also stopped releasing the Pixel stuff and device trees, and now my Android ROM struggles to prepare an update to version 16 😖

DisplayPort support over USB-C.