It looks like DateTime is being stored with a different time zone to DateTimeOriginal/DateTimeDigitized, which seems like a bug. For my arale, the 8 hour difference looks like DateTime is in UTC and the others in local time.
I'm not sure where the DateTime value from Kyle's krillin comes from: it isn't UTC and since local time is UTC, so it isn't that either.
Whatever is going on, the root cause appears to be the inconsistent dates that the camera is writing to the images it produces.
I was looking into this with Kyle at the sprint today. He had his krillin set to UTC time zone and took a photo which produced the following metadata:
$ exiv2 print -PE image20160122_ 182840970. jpg | grep Date Image.DateTime Ascii 20 2016:01:22 19:28:42 Photo.DateTimeO riginal Ascii 20 2016:01:22 18:28:42 Photo.DateTimeD igitized Ascii 20 2016:01:22 18:28:42
Exif.
Exif.
Exif.
My arale was set to Australia/Perth time zone (UTC+8), and took a photo:
$ exiv2 print -PE image20160123_ 030314442. jpg | grep Date Image.DateTime Ascii 20 2016:01:22 19:03:15 Photo.DateTimeO riginal Ascii 20 2016:01:23 03:03:15 Photo.DateTimeD igitized Ascii 20 2016:01:23 03:03:15
Exif.
Exif.
Exif.
It looks like DateTime is being stored with a different time zone to DateTimeOrigina l/DateTimeDigit ized, which seems like a bug. For my arale, the 8 hour difference looks like DateTime is in UTC and the others in local time.
I'm not sure where the DateTime value from Kyle's krillin comes from: it isn't UTC and since local time is UTC, so it isn't that either.
Whatever is going on, the root cause appears to be the inconsistent dates that the camera is writing to the images it produces.