Closed
Bug 1088335
Opened 10 years ago
Closed 7 years ago
[Flame] Unable to detect sd card after closing media storage app
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
b2g-v2.1 | --- | unaffected |
People
(Reporter: pensacola_m2000, Unassigned)
Details
(Keywords: regression, Whiteboard: [2.1-bug-bash] )
Attachments
(3 files)
Gaia f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1
SourceStamp ad497694e258
BuildID 20141013000205
Version 34.0a2
Steps to reproduce:
1. Go to Settings and enable USB Storage
2. Copy some pics from device and then disable USB Storage
3. Unplug USB cable.
4. Go to Settings->Media storage and choose SD card as default media location.
5. Close Settings (long tap on home button and close the app)
6. Open Camera and take some pictures.
Expected results:
User should be able to take pictures and all of them should be saved to SD card.
Actual results:
After closing Media storage, user is unable to detect SD card, so camera cannot be used. Going back in Settings->media storage, default storage is reset to Internal, please see the attached screenshot.
Reporter | ||
Updated•10 years ago
|
Whiteboard: [2.1-FC-bug-bash]
Whiteboard: [2.1-FC-bug-bash] → [2.1-bug-bash]
Comment 1•10 years ago
|
||
[Blocking Requested - why for this release]:
ni? dhylands, is there something missing in the steps above on why the user can't see the sdcard anymore? step 3 says to unplug the USB cable, so i would expect sdcard to appear as default
qawwanted to see if this can be reproduced as well with a regression window if so.
Comment 2•10 years ago
|
||
I tried the STR (running on master) and everything worked perfectly for me.
Flags: needinfo?(dhylands)
Comment 3•10 years ago
|
||
Unable to repro on Flame 2.2 or 2.1 on both nightly (full flash) or engineering (shallow flash) builds.
Actual result: After changing the default media location to the SD card, the user can still access it through apps like Camera.
Flame 2.2 engineering
BuildID: 20141028061150
Gaia: 75e10bb632b1e4a47493d0a66bc32fb74249c57f
Gecko: ab91b8407313
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Flame 2.2 nightly
BuildID: 20141028040202
Gaia: 6a7fb482a03c5083ef79b41e7b0dfab27527cd04
Gecko: a255a234946e
Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Flame 2.1 engineering
BuildID: 20141028051549
Gaia: d26ff7da07e910e55855db3d6e1583592e81e797
Gecko: 737ab5ff452c
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Flame 2.1 nightly
BuildID: 20141028001203
Gaia: a0174f7166745256aaca1cb3aa9f894033fbffa6
Gecko: 43bda3541f6b
Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Leaving qawanted tag for others to attempt.
Comment 4•10 years ago
|
||
(In reply to Marcela Oniga from comment #0)
> BuildID 20141013000205
I wasn't able to locate this exact build on the pvt website so I used a 10/13 2.1 nightly user build.
Issue is NOT reproducible with original STR. Device correctly switches to using SD card after closing media storage app. Repro rate: 0/5.
Device: Flame 2.1 (full flash, 512MB mem)
BuildID: 20141013161204
Gaia: d51956f84ebec0dd8998654f01f9f24fe8527f51
Gecko: a0647b2686eb
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0 (2.1)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1:
--- → unaffected
Flags: needinfo?(jmitchell)
Keywords: qawanted
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Reporter | ||
Comment 5•10 years ago
|
||
I was able to reproduce the issue using flame device on 2.2.0 nightly too:
Gaia 6a7fb482a03c5083ef79b41e7b0dfab27527cd04
SourceStamp a255a234946e
BuildID 20141028040202
Version 36.0a1
v188 base image
Please see attached video for steps.
Reporter | ||
Comment 6•10 years ago
|
||
(In reply to Marcela Oniga from comment #5)
> I was able to reproduce the issue using flame device on 2.2.0 nightly too:
> Gaia 6a7fb482a03c5083ef79b41e7b0dfab27527cd04
> SourceStamp a255a234946e
> BuildID 20141028040202
> Version 36.0a1
> v188 base image
>
>
> Please see attached video for steps.
Video uploaded to dropbox https://www.dropbox.com/s/cutemd7tycv4wh1/VID_20141028_224146.mp4?dl=0
Comment 8•10 years ago
|
||
At the start of the video, it looks like the sdcard was also not visible.
How many files are on the sdcard?
Whenever UMS is disabled, and the volume is remounted, the phone runs chkdsk. Is it possible that chkdsk is just taking a long time?
It would be really good to get a logcat.
Can you run the ds-test app, choose getDeviceStorages and click Doit?
I tried the 20141028040202 image (did a full flash) and I still can't reproduce it.
Flags: needinfo?(dhylands)
Comment 9•10 years ago
|
||
Triage group leaving nom'd for now.
Marcela, can you answer Dave's question in comment #8?
Flags: needinfo?(pensacola_m2000)
Keywords: regression
Reporter | ||
Comment 10•10 years ago
|
||
(In reply to Dave Hylands [:dhylands] from comment #8)
> At the start of the video, it looks like the sdcard was also not visible.
>
> How many files are on the sdcard?
>
> Whenever UMS is disabled, and the volume is remounted, the phone runs
> chkdsk. Is it possible that chkdsk is just taking a long time?
>
> It would be really good to get a logcat.
>
> Can you run the ds-test app, choose getDeviceStorages and click Doit?
>
> I tried the 20141028040202 image (did a full flash) and I still can't
> reproduce it.
I have just couple of photos on my sd card around 20 I think. I installed a production nightly build not engineering. I'm not sure I understand what does ds-test app do, but I will try to do what you've requested.
Regarding your question about chdisk taking a bit longer, I don;t think so. What I wanted to show in the video is that I can ONLY mount sd card afer connecting and disconnecting the USB storage, and that after closing the settings, SD card is being automatically unmounted and it remains unmounted.
Reporter | ||
Comment 11•10 years ago
|
||
(In reply to Marcela Oniga from comment #10)
> (In reply to Dave Hylands [:dhylands] from comment #8)
> > At the start of the video, it looks like the sdcard was also not visible.
> >
> > How many files are on the sdcard?
> >
> > Whenever UMS is disabled, and the volume is remounted, the phone runs
> > chkdsk. Is it possible that chkdsk is just taking a long time?
> >
> > It would be really good to get a logcat.
> >
> > Can you run the ds-test app, choose getDeviceStorages and click Doit?
> >
> > I tried the 20141028040202 image (did a full flash) and I still can't
> > reproduce it.
>
> I have just couple of photos on my sd card around 20 I think. I installed a
> production nightly build not engineering. I'm not sure I understand what
> does ds-test app do, but I will try to do what you've requested.
>
> Regarding your question about chdisk taking a bit longer, I don;t think so.
> What I wanted to show in the video is that I can ONLY mount sd card afer
> connecting and disconnecting the USB storage, and that after closing the
> settings, SD card is being automatically unmounted and it remains unmounted.
Re-tried with:
Gaia 35e87ac4324f0f3abd93dcc70d61c9f37256a0f5
SourceStamp 7e3c85754d32
BuildID 20141029040208
Version 36.0a1
v188
2.2.0 nightly
I was able to reproduce, please check logcat logs, before and after connecting/disconnecting USB storage.
Reporter | ||
Comment 12•10 years ago
|
||
Before connecting USB storage, so SD card not detected.
Reporter | ||
Comment 13•10 years ago
|
||
Logcat after connecting and disconnecting USB storage, so SD card was mounted and then unmounted when settings app was closed.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(pensacola_m2000)
Comment 14•10 years ago
|
||
According to the logs (both of them)
D/Vold ( 190): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
...
I/AutoMounter( 214): UpdateState: Volume sdcard1 is NoMedia and missing
So the bug appears to be that you shouldn't have even been allowed to select "SD Card" in the settings app, since the external "SD Card" wasn't present.
Updated•10 years ago
|
blocking-b2g: 2.1? → 2.1+
Comment 15•10 years ago
|
||
Oops, I forgot to add a comment. The triage group decided today that this should block since it's a regression and using the SD card in this way seems quite common.
Comment 16•10 years ago
|
||
Given, 2.1 is unaffected, I am removing the blocking nomination.
blocking-b2g: 2.1+ → 2.2?
Comment 17•10 years ago
|
||
Moving component based on comment 14
Component: Gaia::System → Gaia::Settings
Updated•10 years ago
|
Component: Gaia::Settings → DOM: Device Interfaces
Product: Firefox OS → Core
Comment 18•10 years ago
|
||
I'm not sure why this was moved to Core::Device Interfaces, when the bug appears to be a bug in Gaia.
Comment 19•10 years ago
|
||
removing nom and QAWANTED to check if it still happens in v2.2/master.
Comment 20•10 years ago
|
||
(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #19)
> removing nom and QAWANTED to check if it still happens in v2.2/master.
Unable to reproduce the issue on Flame 2.2 and on Flame 3.0. Following STR, device correctly switched to using SD card as default storage device. Repro rate: 0/3 on 2.2, 0/3 on 3.0.
Device: Flame 2.2
BuildID: 20150205002503
Gaia: c2047a46e29696238e9b4c9caaba47736421449a
Gecko: adfba0a07e9b
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0a2 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Device: Flame 3.0 Master
BuildID: 20150205010209
Gaia: 2b83a6d5d1185a438b5bbd287497ac2743b501db
Gecko: 34a66aaaca81
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 38.0a1 (3.0 Master)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0
-----
Please note that comment 2, comment 3, and comment 4 all indicated that nobody except reporter was able to reproduce the issue, so I think it's only suitable for bug reporter to follow up on this bug.
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 21•10 years ago
|
||
According to commen 20, wait for reporter's result, clear NI.
Flags: needinfo?(fan.luo)
Comment 22•7 years ago
|
||
Cleaning up Device Interfaces component, and mass-marking old FxOS bugs as incomplete.
If any of these bugs are still valid, please let me know.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•