Top
Best
New

Posted by Animux 18 hours ago

Google has stopped pushing Git tags for some Android source code(grapheneos.social)
631 points | 247 commentspage 3
dminik 13 hours ago|
I really don't understand the thought process here.

Judging by public statements, Google is one of the 3 big western AI companies. Surely they should be rolling in cash and working hard towards AGI.

And yet, for whatever reason, they can't help themselves from further restricting user freedoms on Android. Why?

I don't want to be conspiratorial, but surely it's not money, right? It has to be control. Someone high up at Google just seems to resent people having control over their own devices.

palata 3 hours ago||
I genuinely believe that any human getting enough power (e.g. by moving up in a big company) tends to become a toxic asshole (without even noticing themselves). So that's one explanation.

On top of that, I believe that the sum of the actions of well-meaning people doesn't always result in something good. In big companies like Google, I'm sure that many people are taking decisions that they think are well-meaning, but the result is that Google is a toxic entity.

In other words, because Google sucks doesn't mean that all Google employees are evil. Many of them just take their high salary and try to do well, conveniently ignoring that they contribute to a toxic entity.

KetoManx64 12 hours ago|||
Both. Google has plenty of government contracts, they are undoubtedly pushing for more surveillance, and also on the inverse side, we are now in an age where users can create their own apps to do whatever they want within a few hours, sothis risks their Google Play Store profits
gruez 12 hours ago||
>Both. Google has plenty of government contracts, they are undoubtedly pushing for more surveillance,

I don't get it, are the government contracts somehow contingent on them oppressing users and stifling open source?

>we are now in an age where users can create their own apps to do whatever they want within a few hours, sothis risks their Google Play Store profits

If that's the reason, they're doing a pretty poor job, since it's trivially bypassable by running "adb install".

tliltocatl 9 hours ago|||
[dead]
shalom1112 13 hours ago||
[dead]
shevy-java 14 hours ago||
Google needs to lose in court here. This company is getting more and more evil by the day.
Brian_K_White 5 hours ago||
RE satisfying GPL, the google drive thing is annoying, and I called it paying a bill in pennies in another comment, But RedHat is 100x worse.

They might actually be violating the gpl because of the attempt to set terms on redistribution and the retaliation (kill your account and block future access) if you do.

sunshine-o 14 hours ago||
The era of big tech cooperation around free software is obviously over.

Those kind of moves are petty but there are worst tricks they can pull unfortunately.

It seems Grapheneos is the rare actor willing to put up a fight nowadays, and their "partnership" with Motorola seems to be a first step. They need to ensure a hardware platform.

My guess is at some point they will have to fork AOSP, just because Google will take it in directions that go against Grapheneos principles.

palata 3 hours ago|
> My guess is at some point they will have to fork AOSP

I am still sad that Huawei didn't go this way, I thought they would with HarmonyOS.

I wonder if it could happen at some point that an alternative Android becomes so big that OEMs start supporting it. It feels like it may be interesting for the big Android manufacturers to support something like GrapheneOS?

I wonder: for those Motorola phones that will come with GrapheneOS, won't that make it cheaper for Motorola because they won't have to pay the Google licence (because those GrapheneOS-Motorola phone won't be Google-certified)?

sunshine-o 45 minutes ago||
> I wonder if it could happen at some point that an alternative Android becomes so big that OEMs start supporting it.

I think this is the huge battle GrapheneOS won with Motorola. There are probably a few manufacturers of phones unhappy or nervous regarding Google.

The next battle is really on the app front. Once a country says our government and bank apps need to run on the fork of AOSP then you will start to have a real alternative to the Google/Apple (and now Huawei) duopoly.

My guess is there are a lot of candidate countries for breaking out of the American/Chinese grab on every smartphones.

So in a way the future could look bright as long as we support GrapheneOS and Motorola.

el1s7 13 hours ago||
It's a bit unclear what this is about exactly. What releases are we talking about? How git tags come into play here?
zb3 13 hours ago|
Pixel kernel drivers which are GPLv2, you need them to build the kernel modules from source. Git tags in this case refer to beta versions, but it being "beta" doesn't mean they can delay the release.
a-dub 13 hours ago||
hanlon's razor comes to mind. which trees are these? weird device trees that have complicated third party licensing nonsense attached?

i remember jumping through crazy hoops to interact with a google open source project years ago. i wouldn't be surprised if it's just megacorp bureaucracy.

torgeros 14 hours ago||
That's like this fun fact where Microsoft needs to send you source code via post when you mail them a 5$ check. lol
QuantumNoodle 12 hours ago||
Yo Louis Rossmann, do your thing!
PunchyHamster 14 hours ago||
I have feeling that is related to their upcoming changes that make sideloading harder
izacus 16 hours ago|
Source code of which components is that? It's not very clear from the mastodon thread.
grapheneos 11 hours ago||
Pixel kernel drivers.

We mirror the source code on GitLab. We put the upstream 17 code in the 17-base branch and our code on top of it in the 17 branch:

https://gitlab.com/grapheneos/kernel_pixel/-/tree/17-base

https://gitlab.com/grapheneos/kernel_pixel_muzel/-/tree/17-b...

We also have mirrors of the QPR1 Beta and QPR2 Beta code there too.

hskimse 13 hours ago||
Maybe AOSP source code
grapheneos 11 hours ago||
It's not AOSP but rather Pixels. Pixels are no longer support by AOSP. They went out of the way to no longer push any of the Pixel specific repositories or releases to AOSP. The impact is mainly that Pixels are now harder to support than a lot of other devices rather than easier. They'll sell far fewer Pixels over time because of these decisions.

https://news.ycombinator.com/item?id=49369087

More comments...