TeamAmaze / TeamAmaze/AmazeFileManager
Properly calculate the space usage of sparse files
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Currently Amaze uses the size of a file/folder to display its space usage. This creates misleading reports on sparse files (e.g. the infamous thumbdata files) since they typically look larger than they actually are. In worst case it could be off by several GBs. It would also be better if the properties window could display the actual space usage of a file/folder along with its displayed size.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Kotlin code that calculates file and folder sizes and the properties window that displays them. First inspect how sparse-file metadata can distinguish displayed size from actual space usage. Done means reports use actual space usage and the properties window shows it alongside the displayed size, including for sparse files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100