A customer updated the firmware of some of their Oculus Go headsets and data files on the /sdcard partition lost their timestamps. A query of the file timestamp returns 30/06/1970 08:17:34. This is a problem for our app because we check the timestamps of files to know if they are up-to-date or need to be downloaded again.
Q1: Why are file timestamps being corrupted?
Q2: Can anyone make any sense of that timestamp? It's not the UNIX epoch, but it's almost exactly 1/99th of the current UNIX epoch in seconds!
We think the customer went from firmware version 3.47 to 3.53, but their were probably a few versions along the way as the patches appear to applied sequentially.