Closed Bug 914461 Opened 11 years ago Closed 11 years ago

[B2G][Helix][SD][fengximing]Set the "Default media location" for SD Card, but the picture is stored in internal_SD after capture picture. Set the "Default media location" for Internal, but the picture is stored in external_SD card after capture picture.

Categories

(Firefox OS Graveyard :: General, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:hd+)

RESOLVED WORKSFORME
blocking-b2g hd+

People

(Reporter: lecky.wanglei, Unassigned)

Details

(Whiteboard: [POVB])

Attachments

(2 files)

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba; .NET4.0E; .NET4.0C)

Steps to reproduce:

Test 1:
1, Use camera to take pictures (Note: no external SD card).
2, Insert the SD card.
3, Settings->Media storage, set the "Default media location" for SD Card.
4, Use the camera to take pictures, view the photo storage location.

Test 2:
1, Insert the SD card.
2, Restart the phone.
3, Settings->Media storage, set the "Default media location" for Internal.
4, Use the camera to take pictures, view the photo storage location.





Actual results:

Test 1:
Set the "Default media location" for SD Card, but the picture is stored in internal_SD.

Test 2:
Set the "Default media location" for Internal, but the picture is stored in external_SD card.


Expected results:

Test 1:
Set the "Default media location" for SD Card, the picture should be stored in the external_SD card.

Test 2:
Set the "Default media location" for Internal, the picture should be stored in the internal_SD card.
Severity: normal → blocker
blocking-b2g: --- → hd?
OS: All → Gonk (Firefox OS)
Priority: -- → P1
Hardware: All → ARM
Alan,
Can you check this, it seems the references to the storage devices are mixed up?
Flags: needinfo?(ahuang)
Hi,

I have chosen a solution to modify this issue, please help us check it,
pealse give me a call as soon as possible.

phone: 027-59599479.

Thanks.
Hi Wayne,

I have uploaded the patch file.

pleaes see in gecko-dom-devicestorage-patch.

Thanks.
I cannot reproduce this bug on my helix.

To clarify this bug, I suggest using the device storage test app under gaia/test_apps/ds-test ot know with part is wrong. You will see the expected location and result with absolute path. You can test on the device you found this bug.

Or, you can attach gdb and call mozilla::Preferences::GetString("device.storage.writable.name") to see what's wrong
Flags: needinfo?(ahuang)
Hi Alan,

Please refer to the following steps, it's very easy to reproduce, you can see storeage file at this time.
1, Use camera to take pictures (Note: no external SD card).
2, Insert the SD card.
3, Settings->Media storage, set the "Default media location" for SD Card(external).
4, Use the camera to take pictures, view the photo storage location.

Test 1:
1, Use camera to take pictures (Note: no external SD card).
2, Insert the SD card.
3, Settings->Media storage, set the "Default media location" for SD Card.
4, Use the camera to take pictures, view the photo storage location.

You can see that the picture is not stored in the external sdcard. 

Test 2:
1, Insert the SD card.
2, Restart the phone.
3, Settings->Media storage, set the "Default media location" for Internal.
4, Use the camera to take pictures, view the photo storage location.

You can see that the picture is not stored in the internal sdcard. 


Are you understand this mean?

Thanks.
Hi Alan,

I have two questions.
1,How to build and use gaia/test_apps/ds-test?

2,This modification can solve this issue, but I was worried whether it meets your design thought.
Because I will get default devicestoragename in AddNamed() function, and then the picture is storage in the default devicestoragename.
Whether it meets your design thought?
Whether This would create a bad effect?
What counts is determination and confidence in this modification.

Thanks.
fengximing.
027-59599479.
Please provide unlocked bootloader ROM so I can test on latest PVT build
Hi Alan,

I can't understand what you mean, can you call me?
phone: 027-59599479.

kindly,
Thanks.
We don't have this in our build. I think this is POVB. Please check your device's vold.fstab or init.rc
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Lecky,

I understand from Alan that your modification in vold created this problem, you will need to fix this on your build.

It's also noted that your latest release (0924) has already corrected this. Please, it would be appreciated if you can update such findings and fixes you made on your build so we better utilize our time on other bugs.

Thanks.
blocking-b2g: hd? → hd+
Whiteboard: [POVB]
(In reply to Wayne Chang [:wchang] from comment #12)
> It's also noted that your latest release (0924) has already corrected this.
> Please, it would be appreciated if you can update such findings and fixes
> you made on your build so we better utilize our time on other bugs.
0924 build fixed some of this bug ...
Now images always saved in internal storage, no matter what preferred storage we chose.
Hi Alan,

(In reply to Alan Huang [:ahuang] from comment #13)
> (In reply to Wayne Chang [:wchang] from comment #12)
> It's also noted that
> your latest release (0924) has already corrected this.
> Please, it would be
> appreciated if you can update such findings and fixes
> you made on your
> build so we better utilize our time on other bugs.
0924 build fixed some of
> this bug ...
Now images always saved in internal storage, no matter what
> preferred storage we chose.

I don't understand what you mean, this issue has been solved on hd1.1, is it right?
Which patch is used to fix this bug?

Thanks.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: