Android

30751 readers

237 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules

1. All posts must be relevant to Android devices/operating system.

2. Posts cannot be illegal or NSFW material.

3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.

4. Non-whitelisted bots will be banned.

5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.

6. Memes are not allowed to be posts, but are allowed in the comments.

7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.

8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.

Community Resources:

We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.

Our Partner Communities:

[email protected]

founded 2 years ago

MODERATORS

[email protected]

291

It appears Google has stopped publishing device-specific source code for Pixel phones (lemmy.world)

submitted 2 days ago by [email protected] to c/[email protected]

81 comments fedilink hide all child comments

As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 21 points 1 day ago (2 children)

I remember a couple of months ago it was reported here that Google was making Android closed-source and I commented that this will be the end of custom rom's and this was received by the community poorly as many stated that they would still be releasing the code but not their AOSP apps (or something like that) but I already see the writing on the wall. Google doesn't want to be open-source, they where in the past because that gave them free coders to fix their shit and make them more profitable, but now they just want our data and the open-source community is against that, so they are closing doors to the community in order to be able to truly make money with people's information. Wouldn't surprise me if the next Pixel in the works is going with a similar approach as the iPhone and only allow for an eSim as well.

[–] [email protected] -1 points 8 hours ago* (last edited 8 hours ago)

that Google was making Android closed-source

That's disinformation.

From reading the rest:

You released misinformation ( Google is just open sourcing the releases, but not the dev builds of AOSP. nothing about Apps, nothing about Closed sourcing)
You failed to read the comments on your post and imagined something here again
And now go on a rant about eSims.

To be honest, I think the problem here is not Google, but your inability to read.

[–] [email protected] 2 points 21 hours ago

theres more profit to be like apple.