Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: [email protected]
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: [email protected]
For fresh communities, lemmy apps, and instance updates: [email protected]
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
view the rest of the comments
I agree, but it's more complicated than that: They have removed the device tree for pixel devices from AOSP and using the device tree of the basic virtual phone in android studio instead. That brings the pixel 10 family (as well as future android pixel devices) to the same level as many other phonemaker's devices as far as making roms is concerned. So not all hardware will be documented, many drivers will need to be rebuilt. The pixel line up to the 9a is not affected because older device trees can be used (until Google wants to mod the way drivers load or add API's).
Graphene OS posted that having the device trees is not a strict requirement.
They are correct. It only means more work for future devices, makes the initial port to a device slower. But then, once things have been figured out. It becomes just as fast and reliable as it was (unless what I said earlier: Google setting things in a very different way in a major update (for example, moving to Fushia, which has been abandoned)
Ah. I read "closing the source" and thought AOSP as a whole, not the device tree for pixels. I did hear about that, and I'm honestly kind of hoping it opens up the space for PostMarketOS to support more Pixels if the drivers need to be written from scratch. I am not a big fan of the direction Google has been going either regarding AOSP& device trees so, another player in the mobile OS space that isnt DOA would be cool. Wishful thinking.