this post was submitted on 07 Jul 2025
13 points (81.0% liked)

Android

19706 readers
239 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: [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]

πŸ’¬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 [email protected].

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].

  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 2 years ago
MODERATORS
 

cross-posted from: https://lemmy.world/post/32606497

why is unzipping on android so slow compared to Windows? I've tried ZipXtract, MaterialFile... All took 10+minutes to unizip a zip file that only took 30 seconds to unzip on Windows.

Why is this the case and i s there any way to speed it up?

Thanks a lot

EDIT:

I am using google pixel 9a so this issue looks like it might not be the issue of storage speed

Windows is not running in a virtual machine, just a normal laptop

Typo in the post fixed

EDIT AGAIN:

Solved!

yes it the archive does contains thousands of small files! I think that could be the reason of low performance on android mobile!

thanks a lot @[email protected]

top 14 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 4 days ago (1 children)

Can you share a test file so we can compare the results and rule out a bottleneck with your device?

[–] [email protected] 1 points 4 days ago (1 children)

What should I use to do the test?

[–] [email protected] 1 points 4 days ago

Check the difference on other phones. Try different file manager apps to see which can do the task faster. Try turning on battery saver mode – sometimes background processes can slow foreground apps.

To be consistent test 3 times in flight mode. Also, when your phone is warn/hot it can slow down drastically compared to when its cold to the touch.

[–] [email protected] 5 points 4 days ago

might have something to do with SAF, idk why but android file operation especially with the default file manager is pretty weird. I tend to just use unzip on termux or total commander and it generally seems to work better..

[–] [email protected] 4 points 4 days ago (1 children)

EDIT AGAIN:

Solved!

yes it the archive does contains thousands of small files! I think that could be the reason of low performance on android mobile!

thanks a lot @[email protected]

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

hey, i just run in the issue again today where an file would have taken several hours. instead i tried the app zarchiver and it was done in under a minute. idk if its the best app for that matter. but it worked for me.

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

thank you, I will try that!

[–] [email protected] 8 points 5 days ago (2 children)

In my experience the unzipping speed roughly matches my expectations of a phone unless the archive contains thousands of small files. I have a phone with a Snapdragon 870 SOC, 8GB RAM und UFS 3.1 storage and a Pixel 7 with Tensor G2, 8GB RAM and also UFS 3.1 storage. Performancewise they're roughly the same. On both decompression is fairly speedy for phone hardware. But when i tried to decompress texture packs for PS2 games with thousands of small texture files time to complete exploded up to several hours. I uneducatedely believe UFS3.1 is the bottleneck here? Decompression scales pretty well with multithreading so i dont expect the SOCs to be a problem. Maybe something something how android handles blocks of data, idk?

[–] [email protected] 3 points 4 days ago (1 children)

UFS 3.1 is not necessarily bottleneck here. It also depends on the optimization by OEM.

According to this youtuber some brands UFS 2.2 storage outperforms UFS 3.1 storage used by other brands solely due to their software optimization. Skip the video to 04:54s to see the zip uncompression test and a few mins back to see the results of other tests.

https://youtu.be/mOm4RbC5qxc

[–] [email protected] 1 points 4 days ago

Thanks a lot!

[–] [email protected] 2 points 4 days ago

yes it the archive does contains thousands of small files! I think that could be the reason of low performance on android mobile!

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

I am NOT in any way well known in this topic, so take it as source? my ass answer, but if I'd have to guess it would be

  1. Poorer singlethread performance of ARM CPUs
  2. Missing instruction sets
  3. Android algorithms written in Java/Kotlin where as Windows (WinRAR, 7zip) are written in C/C++
[–] [email protected] 8 points 5 days ago (1 children)

Most of the file browsers I've looked at use a native tool to unzip (sometimes literally invoking unzip).

Even the native/optimised byte code difference shouldn't make the process that much slower unless OP is just using a phone that's not very powerful.

[–] [email protected] 1 points 4 days ago* (last edited 4 days ago)

Sry, I should state my device model in the post

Post updated

I am using google pixel 9a so this issue looks like it might not be the issue of storage speed? But I reckon it could be the issue of ARM CPUs