1169811 - When a Firefox OS device is mounted over USB via MTP, files are shown with bogus datestamps from mid-twentieth century e.g. 1940, 1950, 1965

Status: RESOLVED DUPLICATE of bug 1167090

(Firefox OS Graveyard :: MTP/UMS, defect)

Description

[Daniel Holbert [:dholbert]]

STR:
 1. Take some photos / screenshots on a B2G phone, so you have a DCIM directory at least.
 2. In Settings, enable USB Storage, and in USB storage's settings, tap "Media transfer protocol (MTP)"
 3. Connect your phone to a computer over USB. (I'm connected to a laptop running Ubuntu 15.04)
 4. Browse the device in your computer's file viewer, and look at the timestamps.

ACTUAL RESULTS: The timestamps are randomly distributed in the 1940's, 50's, and 60's.

EXPECTED RESULTS: Meaningful timestamps.


If I connect to the device using "adb shell" and use "ls -l" to inspect timestamps on the device locally, they look reasonable -- so I think this is specifically a bug with MTP and/or USB.

Comment 1

[Daniel Holbert [:dholbert]]

Attachment: screenshot, showing both "adb shell" w/ reasonable timestamps, & file browser w/ 1900's timestamps

Comment 2

[Daniel Holbert [:dholbert]]

Testing on a Sony Xperia Z3, with a Firefox OS 3.0 build on it.
  Build Identifier: 20150528210322
  Update channel: dogfood
  Git commit info: 2015-05-28 19:50:18   18f7c340


My OnePlus One phone (running CyanogenMod Android lollipop) gives EXPECTED REUSLTS, when I browse photos on it from the same laptop (also with a USB/MTP connection). So I think that means it's an issue with the phone/b2g, not with my laptop.

Comment 3

[Daniel Holbert [:dholbert]]

I see this same issue on a Flame device which I just updated to the latest b2g 3.0 nightly, too.

(The flame previously had a 2.1 nightly on it, and with that build, the flame simply wouldn't mount with MTP. With 3.0, it mounts & exhibits this bug.)

So, this doesn't seem to be device-specific.

Comment 5

[Marcia Knous [:marcia]]

I think this is a dupe of Bug 1146900 - at least that is what my bug got duped to me.

Comment 6

[Daniel Holbert [:dholbert]]

Thanks. I don't really understand what's going on there, but I'll trust aosmond's duping of your bug & follow suit.  (I also extended the summary of that bug to hopefully make it more discoverable & reduce the number of dupes that are filed.)