TeamAmaze/AmazeFileManager

Fix creation timestamp for system files - currently shows 1969/1970

Open

#1,028 opened on Feb 16, 2018

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Java (4,883 stars) (1,529 forks)batch import
Issue-Bughelp wanted

Description

Hello,

First let me say thank you for the on going development of this great file manager for Android!

Would there be any benefits to having the /root system of Android to reflect a present date, like when you first turned your device on, instead of 1969/1970?

I've always considered from a security perspective, something like this as beneficial, having correct dates and times...

Thanks

Contributor guide

Tech stack
javaandroid
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Basic Android developmentUnderstanding of file system timestamps
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate how AmazeFileManager retrieves and displays file modification timestamps. The issue indicates that system files show epoch (1970) because they lack modification time. Consider whether to display a fallback timestamp (like device first boot time) or hide it. Look at the file utility classes in the codebase (e.g., Utils.java or FileInfo.java) to understand timestamp handling. Also check comments on issue #1028 for any maintainer guidance.