Comment 5 for bug 1418639

Revision history for this message
Kyle Nitzsche (knitzsche) wrote :

The fundamental problem is that there is an off-by-one error in the hour of the timestamp in the db, as I initially stated.

For example, I just flashed with --wipe and have:
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 230
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-02-09 10:56:42
version version: 230
version ubuntu: 20150209
version device: 20150129-c75dcfb
version custom: 20150129-528-26-182

After the welcome wizard, I took a picture.

The db now has this:
sqlite> select * from media;
/home/phablet/Pictures/com.ubuntu.camera/image20150209_110013113.jpg|image/jpeg|1423479614:443753|image20150209 110013113|2015-02-09T12:00:14|||||0|0|0|2448|4352|0.0|0.0|0|3
sqlite>

HOWEVER, the hour on the timestamp (2015-02-09T12:00:1) is WRONG by one hour.

Here is the system date/time:
phablet@ubuntu-phablet:~$ date
Mon Feb 9 11:04:12 UTC 2015

This problem means my My Photos scope is unable to determine the correct time for the picture and displays the wrong time to the user and in some cases may put it in the wrong date range category.

Note that the off-by-one-hour persists after I set the timezone to my correct local timezone in settings.