Update device storage paths for Gaia (again)

RESOLVED FIXED in mozilla16

Status

()

Core
DOM: Device Interfaces
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: dougt, Assigned: dougt)

Tracking

Trunk
mozilla16
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Turn out that the picture directory might need to be /sdcard/DCIM/.
The DCF spec is at:

http://www.jeita.or.jp/cgi-bin/standard_e/pdf.cgi?jk_n=51&jk_pdf_file=CP%2D3461A_e%2Epdf

If we want to have the camera recognized as a camera on major OS (this includes Linux), then DCIM has to be at the root of that filesystem, and images stored in subdirectories following the right conventions as set in this spec.
This supports multiples vendor / device for the same storage (see 3rd party camera app)

Do be like these guys:
  http://code.google.com/p/android/issues/detail?id=2960
 
> Do be like these guys:
>   http://code.google.com/p/android/issues/detail?id=2960

Here I meant "do not be like these guys".
Where the breakage is propagated to other vendors like Samsung.
(Assignee)

Comment 3

5 years ago
Thanks.

it was like this before I was asked to change it to /sdcard/Pictures/  :(

We'll revert it back.
(Assignee)

Comment 4

5 years ago
Created attachment 634811 [details] [diff] [review]
patch v.1
Assignee: nobody → doug.turner
Attachment #634811 - Flags: review?(fabrice)
Comment on attachment 634811 [details] [diff] [review]
patch v.1

Review of attachment 634811 [details] [diff] [review]:
-----------------------------------------------------------------

I love the way you increase your commit log score ;)
Attachment #634811 - Flags: review?(fabrice) → review+
(Assignee)

Comment 6

5 years ago
i might be #19 now!

https://hg.mozilla.org/integration/mozilla-inbound/rev/d9e9f7ebe2a1

Comment 7

5 years ago
https://hg.mozilla.org/mozilla-central/rev/d9e9f7ebe2a1
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
You need to log in before you can comment on or make changes to this bug.