Android

30762 readers

160 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]

295

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]

82 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] 2 points 2 days ago* (last edited 2 days ago) (2 children)

The FairPhone is expensive and I'm not sure it can run Android Auto properly. If I can't run my own OS anymore, Android will be an ugly alternative to the iPhone and I'd have to go back to iOS, it's absolutely stupid from Google to do this.

[–] [email protected] 5 points 2 days ago

Fairphone is not expensive. All the other phone are too cheap due to slave like labor both in the raw materials and production of the phones. Fairphone pays every one along the production chain fairly.

[–] [email protected] -2 points 2 days ago (1 children)

Why can't you run your own OS anymore? You don't have to buy a Pixel. This news is about Pixel phones, one of the many many many Android phones...

Anti Commercial-AI license

[–] [email protected] 1 points 1 day ago

The discussion is about this being the first step to Google closing the source more broadly