view the rest of the comments
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: !android@lemdro.id
💡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: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰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 !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
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
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
I think a big part of it for RAR specifically is that it's a proprietary format that would technically require Google to license it, and for the tiny percentage of users that would benefit, they don't bother.
A seemingly random but relevant example is the Japanese travel card situation with Pixel phones—every pixel on the planet has the necessary hardware to support Japanese travel cards since the pixel 6, however only pixel phones bought in Japan can use the feature (locked by the OS) because it would mean Google would have to pay a per-device cost worldwide.
This is kinda a similar situation I'd bet, they've proven they would rather not include the feature than pay for licensing
Unrar is free enough.
And there's not really any money to be made charging licenses to open source projects—see ffmpeg/vlc
Google including it in android though means they can charge licenses as a per unit fee because, basically, Google (or phone manufacturers) is a company with money.
What? This has literally nothing to do with unrar's license terms.
We're talking about Android, unrar doesn't have anything to do with this really.
RAR is and will continue to be a proprietary format with an owner who can seek royalties.
It's like saying Google should stop licensing MPEG because ffmpeg exists—it simply doesn't work like that
The entire topic is about RAR archive support on Android, so of course the freely available source code of unrar, released by the RAR developer himself, has absolutely to do with everything here.
Nope, unrar's source code is free, released by RAR's developer.
Nope, it absolutely isn't like that. You just have no clue at all.
It's not FOSS, given that it comes with the provision that no RAR compressor can be created based on unrar source code but for browsing and extracting RAR archives, the unrar source code as is is absolutely fine.
Ah fair play, I didn't realise unrar was from the same guy, cheers for the extra context.
So I guess we go back to what else it could be:
There's probably other reasons I've not thought of, but just a couple of the above are enough to explain it IMO