Android

17818 readers

446 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

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

💬Matrix Chat

💬Telegram channels / chats

📰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

Lemmy App List

See thread

Chat and More

founded 2 years ago

MODERATORS

[email protected]

Devgard

[email protected]

Report: Arm cancels Qualcomm’s instruction set, IP license for chip design (9to5google.com)

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

8 comments fedilink hide all child comments

The dispute between Qualcomm and Arm has escalated with the latter canceling Qualcomm’s ability to use the instruction set for designing chips.

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

[–] [email protected] 3 points 2 months ago (1 children)

I wouldn't be surprised if they started working on it, but even if they had a design ready, it wouldn't happen overnight. Apps, and Android itself, don't yet have support for RISC-V (though I believe Android 15 has preliminary support).

At the moment, Qualcomm likely has to bend over and take it

[–] [email protected] 3 points 2 months ago

I mean, sure, but this could be the push to open architecture. Half the apps wouldn't need recompiling anyway, only those containing native code.

Realistically it could take 2-3 years for Qualcomm to switch to RISC-V (so 5 years because we all know how smooth such huge transitions are). That's enough time for Google to fully support Android on RISC-V.

IMO it's now in Google's hands, once they add support, interesting things are gonna happen. I could even see Arm going out of business, I'm sure Qualcomm would happily help others transition for a very fair fee to help get them out of business.

I think with RISC-V being as supported as it is (meaning it's nothing obscure, but has strong open source toolchain support), this might potentially be a very bad move for Arm.

Anyway, I love it when corporate greed destroys corporations instead of humans for a change. And if open architecture gains traction thanks to that, well, all the better.