zhanghai / zhanghai/MaterialFiles
0B File Size after copying files to USB (using Paragon NTFS)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 9k
- Forks
- 736
- PR merge metrics
- No merged PRs in 30d
Description
I'm using Material Files 1.7.4 and Paragon NTFS 5.0.0.3. Weirdly when I rename the file the file size is fixed but disconnecting and reconnecting my USB dosen't fix the 0B bug. I can still open and see the files though. This didn't happen with version 3.6.1.19 of Paragon NTFS & so I also reported this to them.
Contributor guide
No contributing guide indexed for this repository
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
No source file, test, or entry point is named. Reproduce the 0B size after copying to USB with Material Files 1.7.4 and Paragon NTFS 5.0.0.3, then compare behavior after renaming, reconnecting the USB, and using Paragon NTFS 3.6.1.19; done means identifying whether Material Files or Paragon causes the discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100