You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The readable timestamp conversion fails on some video entries. Tested with an S6 android 5.1.1. The timestamps for videos are stored the same as the image entries. There are no extra zeros at the end of the time stamp. Instead of dividing by 1000 to eliminate the extra numbers, why not take a substring of the variable "timestring". This way the "if" statement is removed completely. (No need to check for difference between video and pictures)
Thankyou for sharing your S6 testing observations / sample code for "imgcache-parse.py" (assuming its the UTF16LE Timestamp version).
While your solution looks good to me, it would also require redoing all my recent validation testing with multiple test devices and then test it with some S6 data. Unfortunately, I don't have the time to do this at the moment.
Instead, I will post your Github comments in the comments section of my blog post [ http://cheeky4n6monkey.blogspot.com/2016/07/a-timestamp-seeking-monkey-dives-into.html ] so others can make this change to the code should they need to.
I will also keep this issue open to document your suggestion.
The readable timestamp conversion fails on some video entries. Tested with an S6 android 5.1.1. The timestamps for videos are stored the same as the image entries. There are no extra zeros at the end of the time stamp. Instead of dividing by 1000 to eliminate the extra numbers, why not take a substring of the variable "timestring". This way the "if" statement is removed completely. (No need to check for difference between video and pictures)
suggested code would be
timestring = datetime.datetime.utcfromtimestamp(int(timestamp[0:10])).strftime("%Y-%m-%dT%H-%M-%S)
replace if statement with that code. Tested and works great!
The text was updated successfully, but these errors were encountered: