Bug #2929

J3M timestamps vary by 19 hours within same image file

Added by wendy.betts almost 4 years ago. Updated almost 4 years ago.

Status:FeedbackStart date:01/31/2014
Priority:UrgentDue date:
Assignee:harlo% Done:


Target version:-


I took a photo yesterday morning (Jan. 30). In the Gallery view of the image history it says the photo was taken on Jan. 30 at 9:10 am. The J3M file on the device says "timestamp: 2014:01;30 09:10:04." The unix code timestamp for the user appended data is "1391102061903" which translates to Jan 30 at 9:14:21. So far so good. However, when I scroll down to the "sensor Capture" data in the J3M file, the timestamp changes to "1391171254883" which translates to Jan. 31 at 4:25:25. The remaining sensor data appears to continue from that timestamp. The dashboard displays the Created On time as Jan 31 at 4:27:38 am. The same problem occurred with another image that we took last week on a different device. I've marked the priority as urgent, because this type of inconsistency undermines the authenticity of all images collected by the app (not just this photo).

I'm attaching the J3M data from the dashboard from the image that I took. I've highlighted the two different timestamps, one in the beginning of the document and one at the end. I did not check every timestamp in between, but the half dozen I did check translated to Jan. 31.

Timestamp Problem - J3M file.docx (15 Bytes) wendy.betts, 01/31/2014 06:22 pm


#1 Updated by harlo almost 4 years ago

  • Status changed from New to Feedback
  • Assignee set to harlo

initial timezone and offset from initial GPS reading logged in J3M, but timestamps no longer re-adjusted around GPS: https://github.com/guardianproject/InformaCore/tree/harlo_bug_2929

Also available in: Atom PDF