261–270 of 350 posts
They stopped pushing tags for any of the Pixel kernel or userspace driver repositories to AOSP. They also stopped pushing AOSP releases specific to Pixels which is why AOSP now only gets yearly releases, QPR2 releases and security backports to both of those. Other OEMs use the yearly and theoretically also the QPR2 releases. Both the yearly and QPR2 releases get monthly security backports. Since they dropped Pixel su…
Was considering a Pixel 11 Pro, just cancelled it. Will wait for the Moto release. Thanks for your work!
Earlier quoted context omitted.
In the US? Under the current political and economic circumstances? Against Google's legal department? I wouldn't get my hopes up...
No, it would be in Canada.
Earlier quoted context omitted.
Infinite money in the pursuit of profit or an ego trip of an exec. No money for the benefit of community or society.
"Society" (whomever that is) uses Google services constantly, to society's constant benefit.
They stopped pushing tags for any of the Pixel kernel or userspace driver repositories to AOSP. They also stopped pushing AOSP releases specific to Pixels which is why AOSP now only gets yearly releases, QPR2 releases and security backports to both of those. Other OEMs use the yearly and theoretically also the QPR2 releases. Both the yearly and QPR2 releases get monthly security backports. Since they dropped Pixel su…
I really cross my fingers your partnership with Motorola will be successful
We need something other than Android, and we need the government to make sure we can run Android apps (like government ID and banking apps) without being spied on. They've been doing whatever the f they like for long enough if you ask me.
EU can have their own counter part but no one footing the bill
Classical not being evil stuff by Google.
Yeah, this is a total dick move.
Earlier quoted context omitted.
Well Google is becoming worse every year, but AOSP is way ahead of Linux on Mobile, for many reasons. The thing is, AOSP is open source. Just like Linux is not controlled by one of the TooBigTechs, I could imagine a fork of AOSP becoming a viable alternative without depending on Google anymore. And supporting alternative Android OSes (like GrapheneOS and LineageOS) is one way to support that vision. Linux on Mobile i…
> but unfortunately I think it's an uphill battle because of all the proprietary firmwares? In my GNU/Linux phone, all drivers are FLOSS and all pieces of firmware are backed into the replaceable peripherals (modem M.2 card and WiFi M.2 card).
"It's good enough for me" is not the same as "it is comparable to Android".
Earlier quoted context omitted.
Non-sequitor? They're not providing a (sha-1) hash, they're providing source code to integration partners using their business channels, not public git providers. Those business channels include contracts etc to "secure their supply chain". You and I aren't in those business channels, and we're not being given anything with a hash. There's simply no hash to collide with?
A git hash is cryptographically secure. It doesn't matter how you distribute it. That is the entire point you're missing.
Earlier quoted context omitted.
> Google refusing to do so means Google wants to violate the GPLv2 Not an expert in GPL, but does it say that the source code needs to be provided by a url?
As far as I understand, they could send it to you printed and bound and charge you for the paper and postage if they want to.
I doubt Google is distributing the Android code to third party OEMs that way.