this post was submitted on 12 Jun 2025
1 points (100.0% liked)

Android

31047 readers
5 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
 

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] 0 points 3 weeks ago (4 children)

Uhg then what? Samsung's got too much of their own shit data harvesting crap on top of the Google stuff. All other phones basically have shit cameras. Time to go to iPhone? Seems they're all the same at this point ๐Ÿ˜œ

[โ€“] [email protected] 0 points 3 weeks ago

So, hear me out, but what if we all go back to feature phones? Smart phones are convenient, but do the pro's weigh more than the cons at this point? I am also including mental health into this btw.

[โ€“] [email protected] 0 points 3 weeks ago (1 children)
[โ€“] [email protected] 0 points 3 weeks ago

No. It's not nearly as usable. I can't get a proper browser, can't get a wifi analyzer, can't even get a different dialer or keyboard. On top of that there is all their nonsense with imessage and attempted vendor lock in. I had to use one for my work. It was an awful, constrained experience.

[โ€“] [email protected] 0 points 3 weeks ago

Honestly if Google is going to close all their shit, then yeah, absolutely.

[โ€“] [email protected] 0 points 3 weeks ago (2 children)

If you're in Europe, Fairphone is an option. I'm pretty happy with mine.

[โ€“] [email protected] 0 points 3 weeks ago (3 children)

Graphene is centered around security. I've heard bad things about Fairphone in that regard - the Graphene team even talks about them in the replies on that thread.

[โ€“] [email protected] 0 points 3 weeks ago

Respectfully to the Graphene team, they say that about literally every other OS.

[โ€“] [email protected] 0 points 3 weeks ago

You heard stuff? What stuff specifically? Care to elaborate and provide sources?

Anti Commercial-AI license

[โ€“] [email protected] 0 points 3 weeks ago* (last edited 3 weeks ago)

Read their comment and I'm left scratching my head. Their role in security with the straight android phone (not the /e/OS version) is simply pushing security patches as/when they get them from the Android team, as they're using straight Android. Security is handled by Google for Android, not them. When it comes to /e/OS, no idea how good/bad it is, but apparently Graphene has some beef with Murena (the people who make it), at least according to their comment.

Not at all knowledgable about mobile kernels and drivers to comment on the rest of it. I do know Fairphone 5 uses an unusual CPU normally used for SoC as that was the only CPU that was both good enough to run Android reasonably while simultaneously providing very long-term driver updates (they're aiming for a minimum of 8 years of updates).

[โ€“] [email protected] 0 points 3 weeks ago* (last edited 3 weeks ago) (1 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] 0 points 3 weeks ago

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