Closed
Bug 850760
Opened 11 years ago
Closed 6 years ago
[Flame][Camera] EXIF header Digitized Date Time field can't be set, stuck at "2002:12:08 12:00:00"
Categories
(Firefox OS Graveyard :: Vendcom, defect)
Tracking
(blocking-b2g:-)
RESOLVED
WONTFIX
blocking-b2g | - |
People
(Reporter: mikeh, Unassigned)
References
Details
(Whiteboard: [POVB])
[This behaviour is observed on Unagi; it may apply to other handsets as well.] Bug 819835 added the capability to set the EXIF Original Date Time header field by calling SetParameter("exif-datetime"); but there doesn't appear to be any parameter key that can be used to set the Digitized Date Time. As a result, this field is always populated with "2002:12:08 12:00:00".
Comment 1•11 years ago
|
||
Is this not a dup of bug 850629 at this point?
Reporter | ||
Comment 2•11 years ago
|
||
Not exactly. Bug 850629 is because camera.js is just not setting 'dateTime' in the takePicture() config parameter object. That's a fairly easy fix, which will cause the Original Date Time field to be populated. We can fix that. This bug is because libcamera is writing a value into the EXIF header that we can't seem to modify. Either the vendor has to fix this, or tell us what magic frob we can twiddle to override the default value. I've poked into libcamera with strings and don't see anything obvious.
Comment 3•11 years ago
|
||
Got it, thanks. tef- for now, until another partner raises this as blocking.
blocking-b2g: tef? → -
Comment 5•11 years ago
|
||
This bug happen for me also on Geeksphone Peak.
Comment 7•10 years ago
|
||
This behavior is shown in JB (v123) and KK (v165) Flame as well. Captured image displays exif data as follows: Date Time Original 2014:08:22 14:33:04 Create Date 2002:12:08 12:00:00
Keywords: unagi
Summary: Camera - EXIF header Digitized Date Time field can't be set, stuck at "2002:12:08 12:00:00" → [Flame][Camera] EXIF header Digitized Date Time field can't be set, stuck at "2002:12:08 12:00:00"
Updated•10 years ago
|
Component: General → Vendcom
Whiteboard: [POVB]
Comment 10•9 years ago
|
||
And it is not a problem on Aries.
Comment 11•9 years ago
|
||
Workaround on flame/geeksphone would be to rewrite the exif tag. We'll have Exif write support soon.
Comment 12•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•