Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms.
-
For Motorola devices, we plan to prepare our releases early and have everything ready for major Android updates at launch. We should be able to simply push the code to our own repositories for major Android releases. We'll need to host all the AOSP Git repositories ourselves.
@GrapheneOS are there some members of the grapheneos-team who like the born-again trend of upcomming qwerty phones? — as some of the hype also got its shape from ppl and ultimately clicks adding a keyboard to a closed flip-foldable, it seems like there could be some human engineering and convincing some peaple at certain phone manufacturer that it would be so so great to have a graphene qwerty phone
And...
a 3.5" screen does visualize less of your private information than a 6" screen XD -
Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms. It's completely ridiculous and they've gradually become very slow at handling requests. They're in clear violation of the GPLv2 now.
@GrapheneOS wait it's real??? sounds like a joke ._. -
@GrapheneOS if the paper contains many inaccuracies, maybe it's a good idea to contact the authors and editors to get it retracted?
@danieldk @GrapheneOS I think that this kind of inaccuracies are intentional. This "work" looks like a slop that was made with premeditaion. I have also doubt if there was any review before publishing this slop.
-
@xyhhx @vrtrahan @GrapheneOS plus vendor buy-in. It's very hard to make a driver without documentation on the hardware and that's usually not freely available
-
@eatham @GrapheneOS The GPLv2 does not place any stipulation on schedules and deadlines.
@lattera @eatham It doesn't have to explicitly specify any time constraint for it to be required to provide it in a reasonable amount of time. Law is not code and doesn't depend on everything being explicitly written down. Google is a massive tech company with enormous resources. They clearly made these changes to make it a hassle to obtain the sources. By not quickly responding to the requests and dealing with it, they're artificially delaying access and that's a violation of the license.
-
@lattera @eatham It doesn't have to explicitly specify any time constraint for it to be required to provide it in a reasonable amount of time. Law is not code and doesn't depend on everything being explicitly written down. Google is a massive tech company with enormous resources. They clearly made these changes to make it a hassle to obtain the sources. By not quickly responding to the requests and dealing with it, they're artificially delaying access and that's a violation of the license.
@lattera @eatham Aside from that, not providing it in the form of Git repositories is not providing it in the preferred form for modifying the source code. Android's tooling is based around dealing with Git repositories. Even if they strip all the history, it should still be tags in Git repositories so stuff works properly and it's split up into separate repositories in the way they did themselves. The build system uses Git revisions. It has a fallback to use a metadata file which they provide.
-
@danieldk @GrapheneOS I think that this kind of inaccuracies are intentional. This "work" looks like a slop that was made with premeditaion. I have also doubt if there was any review before publishing this slop.
@wod0bow @danieldk It was funded by a grant from Google, one of the authors is from Google and it lists 4 reviewers from Google. It fits neatly into Google defending banning GrapheneOS with the Play Integrity API in Europe. There's going to be a lot more of a response from us than what we already did if they don't retract or correct it soon.
-
For Motorola devices, we plan to prepare our releases early and have everything ready for major Android updates at launch. We should be able to simply push the code to our own repositories for major Android releases. We'll need to host all the AOSP Git repositories ourselves.
@GrapheneOS i'm so unbelievably hype for the motorola devices
-
@GrapheneOS since when?
@idkrn They started doing this for Pixel kernel drivers after the initial release of Android 16.
-
For Motorola devices, we plan to prepare our releases early and have everything ready for major Android updates at launch. We should be able to simply push the code to our own repositories for major Android releases. We'll need to host all the AOSP Git repositories ourselves.
@GrapheneOS when do you change the recommendation for devices on your website?
-
Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms. It's completely ridiculous and they've gradually become very slow at handling requests. They're in clear violation of the GPLv2 now.
@GrapheneOS I get the feeling it's not an easy feat to be in violation of GPL2
-
@wod0bow @danieldk It was funded by a grant from Google, one of the authors is from Google and it lists 4 reviewers from Google. It fits neatly into Google defending banning GrapheneOS with the Play Integrity API in Europe. There's going to be a lot more of a response from us than what we already did if they don't retract or correct it soon.
@GrapheneOS @danieldk Almost all banking apps in EU are based on GMS. Govs apps require GMS. MasterCard Visa removed simcentric payments and also their own HCE payments and replace that with GooglePay. EU dosn't give a F about that... And right now Google is takimg narration in EU about Android security. More over false narration.
-
P pelle@veganism.social shared this topic
