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

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
 

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] 14 points 1 day ago (1 children)

I'm using an Ubuntu touch device as my main driver these days (currently on volla Quintus)

It's good, but it's not there yet in terms of ease of use. If you're not a Linux enthusiast, you will likely have a bad time on UT (can't comment on sailfish, though I'd imagine it suffers in a similar way).

The largest problem is app support... By a mile. Most apps I use are just web apps I've had to manually setup. You can emulate an android and boot into it with waydroid, which will allow you to install apks; But honestly that feels like a cop out... which is why I try to make use of web apps where I can. (It also destroys your battery life... As you're essentially running two phones).

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

I figured it's not quite there yet. I hope market forces will solve this eventually. If Google manages to make android bad enough, demand for an alternative should arise. I'm already running Linux on my desktop quite happily, thanks to windows 11.

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

Yeah I think you're right. This will be the main drive behind adoption; even as an enthusiast I was sceptical to try a Linux phone; but google's predatory policies ultimately forced my hand; it's only a matter of time before more end up feeling like they have no choice.

Android isn't the bastion of open source freedom it once was. We need a new (or GNU heheh) approach.