this post was submitted on 25 Jun 2024
28 points (88.9% liked)

Android

17623 readers
82 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.

🔗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

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. 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.

  5. 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.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More

founded 1 year ago
MODERATORS
ijeff@lemdro.id
ladfrombrad@lemdro.id
Paradox@lemdro.id
multimoon@lemdro.id
mikestevens@lemdro.id
Devgard@lemmy.world
limerod@reddthat.com
Netrunner@lemdro.id
28
Android still doesn't support many compression types (lemmy.world)
submitted 4 months ago by ByteMe@lemmy.world to c/android@lemdro.id
17 comments fedilink hide all child comments
 

When w11 announced that they were adding native support for rar, 7z, etc, it occurred to me that android also doesn't support these and I found it really weird

you are viewing a single comment's thread
view the rest of the comments
[–] ByteMe@lemmy.world 1 points 4 months ago (1 children)

I'm using a Samsung tablet that doesn't support rar for example.

[–] 9point6@lemmy.world 19 points 4 months ago (1 children)

I suppose you'd fall into my "you'd install a file manager app if you actually needed it" category

[–] ByteMe@lemmy.world -1 points 4 months ago (1 children)

Yeah but it's still weird that there is no native support

[–] 9point6@lemmy.world 14 points 4 months ago* (last edited 4 months ago) (1 children)

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

[–] woelkchen@lemmy.world 0 points 4 months ago (1 children)

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

Unrar is free enough.

[–] 9point6@lemmy.world 4 points 4 months ago* (last edited 4 months ago) (1 children)

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.

[–] woelkchen@lemmy.world 2 points 4 months ago (1 children)

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.

[–] 9point6@lemmy.world 4 points 4 months ago (1 children)

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

[–] woelkchen@lemmy.world 2 points 4 months ago* (last edited 4 months ago) (1 children)

We’re talking about Android, unrar doesn’t have anything to do with this really.

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.

RAR is and will continue to be a proprietary format with an owner who can seek royalties.

Nope, unrar's source code is free, released by RAR's developer.

It’s like saying Google should stop licensing MPEG because ffmpeg exists—it simply doesn’t work like that

Nope, it absolutely isn't like that. You just have no clue at all.

   Unrar source may be used in any software to handle RAR archives
   without limitations free of charge, but cannot be used to re-create
   the RAR compression algorithm, which is proprietary. Distribution
   of modified Unrar source in separate form or as a part of other
   software is permitted, provided that it is clearly stated in
   the documentation and source comments that the code may not be used
   to develop a RAR (WinRAR) compatible archiver.

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.

[–] 9point6@lemmy.world 2 points 4 months ago

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:

  • The licence could still be an issue as it's not FOSS and parts of android are, so I guess that could prevent its inclusion if it's incompatible with existing licences
  • The licence could also be an issue in terms of wanting feature parity with zip support, which would include creation of archives.
  • As I mentioned before, the percentage of users who are interacting with non-zip archives locally on their devices is a pretty small percentage. It may be on the backlog, but it's not going to be far from the bottom in priority.
  • How many of the use cases are not served by the third party app ecosystem sufficiently that it would benefit inclusion in the actual OS and the extra maintenance that would entail
  • RAR is an outdated format and in decline at this point, there are better options to add before getting to it
  • Let's also address the elephant in the room regarding the last point—I don't think I've seen RARs used regularly outside of piracy in quite some time. If that's the main use case, Google is not going to be bothered about supporting it.

There's probably other reasons I've not thought of, but just a couple of the above are enough to explain it IMO