zhanghai / zhanghai/MaterialFiles

Timestamp "modified time" is not the same after copying files or folders

Open
#335 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
9k
Forks
736
PR merge metrics
No merged PRs in 30d

Description

Hello,

the timestamp "modified time" is not the same.

  1. When files and folders (without sub folder and files) are copied from internal storage to external storage such as an SD card in the SD card slot or to a USB flash drive (OTG). When files and folders are copied from external storage (SD card or USB flash drive) to internal storage (Android device).

For point 1 there is another file manager app (without root) on Android which does not have this problem. This means that the timestamp for "modified time" remains the same after copying as the source file or folder. Should I say the name of the app or is it not allowed to say it?

  1. When folders (with sub folders and files) in the same internal storage of the Android device are copied e.g. the folder Download (/storage/emulated/0/Download) is copied again to a new path in the same internal storage e.g. to (/storage/emulated/0/Backup).

  2. When accessing external storage on the Android device e.g. the SD card to copy files or folders (with sub folders and files) only within the same external storage.

  3. When files and folders (with sub folders and files) are copied from internal storage (Android device 1) to another internal storage (Android device 2).

For point 3 and 4 the Android system must support it? How do I do that? How can the Android developers get this information to fix the problem?

Tested with Material Files (1.1.2)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Reproduce the four copy scenarios described in the issue with Material Files 1.1.2, comparing modified timestamps before and after each operation. Done means determining whether the timestamp is lost by the app or Android storage APIs and documenting a specific, reproducible fix scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.