In that nobody would use it on mobile without continued development from Google (Android development can easily pause after say a 5-10 year transition period) and without Google apps and services on it.
At best, you'd have Samsung or some Chinese company keeping the flame alive for a short while.
After that everything now Android will be Fucscia based.
They aren't going to be interested in supporting Linux after Android.
Google hasn't extinguished anything. Linux just didn't offer a compelling reason for companies to support it.
Logically it's very strong. It's also neither here, nor there.
The "extinguish" part refers to the transition from Linux on mobile being a thing thanks to Android (on billions of devices) to Linux on mobile not being a thing anymore (or being a small niche) in a post-Android/Fucscia world.
It doesn't matter if Linux on mobile wasn't a thing before Android, the same way when defending a murder "Well, the victim wasn't alive before it was born either, judge" is not an argument.
What you are describing is what happens when an inferior technology is replaced by a better one.
I'll agree with that.
It still is "use X when convenient, profit off X, build your own replacement piecemeal, throw X away and let it die" though.
Pretty sure doing that falls under the essential software freedoms, though, doesn't it.
This largely depends on them having the goodwill of the phone manufacturers in not de-googling their distributions. How would Google feel about Samsung switching the default search engine to Bing?
And for what matters, non-techies love Samsung´s UI skin.
Google doesn't have an obligation to use Linux. Linux doesn't offer what they need, so they stopped using it.
However, I'm MAKING my own Android ROM. I actually do the job Google implied they would do when they announced Project Treble with Android 8.0 (which is actually providing working new Android versions on older Android vendors).
I'm guessing you don't know my project, so I'm making GSIs, which make Android's Project Treble actually usable to thousands of various devices. If you take Google's Project Treble as-is, you get /at best/ something that is not even a smartphone (you get no in-call audio, assuming you get calls at all, because it doesn't provide VoLTE support). I'm making it actually daily-drivable.
Many users are saying that I'm doing Google's job there, and even some Googlers said so. But of course, it's not in Google's nor the OEM's best interests to do that, which is way this job needs to be done by other people.
Also, I sent dozens of patches to AOSP, with very very small success rate. (While my contributions to Linux were pretty smooth)
But yes, I'm entitled to Google's work.
I'm pretty sure Google will disagree on that :P
No, I don't feel entitled to Google's work, the quote was sarcasm.
My point of showing my contributions is that I can do stuff on my own, that I'm happy that Android is opensource, and I do my best to contribute to it, in the opensource spirit. But if it stops being opensource, then so be it (it'd be a bigger shot in the foot for Google than for me anyway), I'm not simply leeching on Google's back, like previous comments assumed.
They did it because they wanted to be entitled to someone else's work (the free components they built it on). No one told them they couldn't be proprietary from the ground up.
Android phones don't have any semblance of FOSS/Linux/DIY sprint in them anyway...
Nowadays, Linux's realtime is pretty good. Steven Rostedt has extensive documentations on how to "debug" realtime on Linux. You know what's the number one source of non-realtime-ness in Linux? It's parts of hardware that Linux simply can't control. He found that on many PCs, the BIOS triggers SMI (to refresh the RAM IIRC), and said SMI blocks the CPU.
In case you're thinking "Surely this is an x86-only mess", well, sorry, but that's wrong. It's even worse for embedded systems with shared memory bus, where modem has higher priority over the bus, and can decides to stall any memory access made by the CPU.
Switching to Fuchsia won't change much wrt real-time. (Possibly with Fuchsia, it is harder for OEMs to footgun their drivers, which would still be an improvement)
I think the reason Android would switch to Fuchsia is simply that Google is too big to rely on the community, and most engineers there don't have an opensource mind, so overall it makes it more convenient for Google to get rid of 3rd parties. Yes, it is a technical reason.
I agree that extinguishing is not Google's goal (which is why I didn't add embrace/extend). It is just a side-effect.
Too little imagination applied here. They will find a way. They always do.
Three years ago, gregkh did a presentation about LTS in Android. Guess who was using latest LTS kernels. Google? Nope. Sony and Essential are who.
Guess who upstreamed support for their phones in Linux kernel? Google? Still nope, again it's Sony.
How long was Pixel 1 supported? Ah yes, a whopping 3 years. (Same for Pixel 2 I believe). Who does better? Fairphone (circa 100 overall employees, and not many are software engineers), and nVidia.
Guess who provides major kernel upgrades? Sony (but not Google-certified sadly), and nVidia.
So far, Google hasn't shown any sign they are more capable than average OEMs to upgrade my devices.
The one Qualcomm supports in their BSP package for Pixels SoC.
You seem to not understand who exactly provides kernels for Android and other embedded devices.
Oh, I perfectly understand how those things work, I've Google-certified more smartphones than I can count (which means more than 50), and that's merely one line of my resume.
In my comment, I mention Sony who upgraded their major kernel version. How does it fit your mental model of embedded system's BSPs?
I currently work in a company who provides software upgrades for a 10 years-old STB. This 10 years-old STB (that's older than the Nexus 4) is currently running Linux 5.4, and is planned to run Linux 5.14 in a few months, at millions of customers' home.
Are we bigger than Google? Gosh no, by orders of magnitude. Are we spending a lot of time on this? Well nope, we don't even need one person full-time to upgrade kernel version. Are we paying that person a lot? Nope, they could probably move to Google 500 meters away and have at the very least double salary.
Of course SoC-vendor stopped providing us with upgrades aeons ago.
But, contrary to Google, we actually have monetary incentives to keep supporting this device.
If they can't even wrangle this for their own phones, how is going to a more permissive license and embracing proprietary modules going to make the situation better?
Why are you so darn sure that they're wrong and the model that's been failing for the last 15+ years is really the right one?
And this stuff isn't like an http API. I gave examples above about how NT has fallen behind Linux because of their stable API and binary drivers.
Step 1: Require OEM's userspace drivers to use stable ABI (Android 8.0-9.0) exposed over a bus
Step 2: Require OEMs to use your way of doing secure boot chain (Android 10)
Step 3: Require OEM's kernel-space drivers to use stable ABI, and force the usage of Linux Kernel Modules (Android 11 -- we already lost the GPL here)
Step 3b: Start implementing VM support. Find a nifty marketing reason to have VMs ("Privacy Core")
Step 4: Require OEMs to use your own signed kernel (Android 12)
Step 5: Have said micro-kernel load/exec original kernel's executables
Step 5: Say that for security's-sake, it will be better of the nifty VM if its OS is a micro-kernel
Step 6: Require OEMs that your own signed kernel also runs as hypervisor
Step 7: Expose bus defined at step 1 across the VM. Use it to move various components from original kernel to the new micro-kernel, "for security reasons"
Step 8: Have said micro-kernel load/exec original kernel's kernel-space drivers (stable thanks to step 3)
Step 9: OTA kernel defined at step 4 to new micro-kernel
Step 10: Extinguished.