Closed
Bug 1071856
Opened 11 years ago
Closed 11 years ago
[Camera] User does not receive a no memory card message when removing SD card and attempting to save to SD card.
Categories
(Firefox OS Graveyard :: Gaia::Camera, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
WONTFIX
People
(Reporter: jthomas, Unassigned)
References
()
Details
(Whiteboard: [2.1-exploratory-2])
Attachments
(1 file)
|
995.44 KB,
text/plain
|
Details |
Description: After launching the camera app if the user sets the internal storage to SD card and then removes the SD card they are still able to access the camera app.
Memory card must be present at first.
Repro Steps:
1) Update a Flame to 20140923000204
2) From settings select Media storage > Default Media Location > SD Card
3) Open Camera app and then hit home button. (So that camera app is running in background.)
4) Remove SD card.
5) Open Camera App
6) Take a photo.
Actual: User does not receive a message indicating that an SD card must be present. Camera app opens. User is able to press the capture button with no results.
Expected: It is expected that the user will receive a message saying that an SD card must be present. User will not be able to open Camera app.
Flame 2.1 Jelly Bean Base (319mb)
Enviromental Variables:
Device: Flame 2.1
BuildID: 20140923000204
Gaia: 3742913e11f69e789dcb0aa0dedf2e5572da0129
Gecko: df42b05782aa
Version: 34.0a2 (2.1)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Notes: Logcat starts when camera app is already active and SD card has already been removed.
Repro frequency: 100%
See attached: Logcat
Video: https://www.youtube.com/watch?v=W4S2Adc1lRM&list=UUmFqEdAeIqIUaEnJuL7tNmg
| Reporter | ||
Comment 1•11 years ago
|
||
This issue DOES occur on the Flame 2.2 Kitkat Base (319mb), 2.1 Kitkat Base (512mb) and the 2.0 Kitkat Base (319mb)
Result: User does not receive the notification to indicate that there is no Memory card.
Flame 2.2 KitKat Base (319mb)
Environmental Variables:
Device: Flame 2.2 Master
BuildID: 20140923073003
Gaia: 37b8a812c642ca616bf9457cb9b71e45261cdfa8
Gecko: 9e193395b912
Version: 35.0a1 (2.2)
Firmware: v180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Flame 2.1 KitKat Base (319mb)
Environmental Variables:
Device: Flame 2.1
BuildID: 20140923003005
Gaia: 3742913e11f69e789dcb0aa0dedf2e5572da0129
Gecko: df42b05782aa
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Flame 2.0 KitKat Base (319mb)
Environmental Variables:
Device: Flame 2.0
Build ID: 20140923063014
Gaia: 6449cc35a8f0704d95acac374ba857bde4b86d6c
Gecko: b930730dba81
Version: 32.0 (2.0)
Firmware Version: v180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
This issue does NOT occur on the Flame 2.2 (319mb), Open_C 2.2, Flame 2.1 (512mb), 2.1 Open_C, Flame 2.0 (319mb), Open_C 2.0
Description: User receives a notification explaining that there is no memory card available and are unable to take photos.
Flame 2.2 Jelly Bean Base (319mb)
Enviromental Variables:
Device: Flame 2.2 Master
BuildID: 20140923040203
Gaia: 3c898380b47f298cd3b7a0dacb3a6529e94322d4
Gecko: 790f41c631cc
Version: 35.0a1 (2.2 Master)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
2.2 Open C
Environmental Variables:
Device: Open_C Master
Build ID: 20140923040203
Gaia: 3c898380b47f298cd3b7a0dacb3a6529e94322d4
Gecko: 790f41c631cc
Version: 35.0a1 (Master)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Flame 2.1 Jelly Bean Base (512mb)
Enviromental Variables:
Device: Flame 2.1
BuildID: 20140923000204
Gaia: 3742913e11f69e789dcb0aa0dedf2e5572da0129
Gecko: df42b05782aa
Version: 34.0a2 (2.1)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
2.1 Open C
Environmental Variables:
Device: Open_C 2.1
Build ID: 20140923000204
Gaia: 3742913e11f69e789dcb0aa0dedf2e5572da0129
Gecko: df42b05782aa
Version: 34.0a2
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Flame 2.0 Jelly Bean Base (319mb)
Environmental Variables:
Device: Flame 2.0
Build ID: 20140923000205
Gaia: 8d7f2ac85f3154bdb149d67e5c2f9b035f5e4105
Gecko: 6dd19beda1c2
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Open_C 2.0
Environmental Variables:
Device: Open_C 2.0
BuildID: 20140923000205
Gaia: 8d7f2ac85f3154bdb149d67e5c2f9b035f5e4105
Gecko: 6dd19beda1c2
Version: 32.0 (2.0)
Firmware: P821A10v1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → affected
Flags: needinfo?(ktucker)
Whiteboard: [2.1-exploratory-2]
| Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(dharris)
| Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(ktucker)
[Blocking Requested - why for this release]:
Although this is not a regression, this issue did not occur on devices with the Jellybean base.
Nominating this as a 2.0 Blocker. If the user were to enable media storage to SD, open the camera app, and then swap out their SD card, no photos would be saved to the newly inserted SD card until the user closed and opened the camera app again
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Comment 3•11 years ago
|
||
Removing the SD card while the flame is powered on is NOT supported.
The flame hardware has no card-inserted/card-removed signal at the HW level. The style of sdcard connector used on the flame doesn't support hot-swapping.
Comment 4•11 years ago
|
||
(In reply to Dave Hylands [:dhylands] from comment #3)
> Removing the SD card while the flame is powered on is NOT supported.
>
> The flame hardware has no card-inserted/card-removed signal at the HW level.
> The style of sdcard connector used on the flame doesn't support hot-swapping.
Unsupported. Dave says that it may or may not work on flame as it depends on what state the kernel driver is when card is removed. Marking as wont fix.
Thanks
hema
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Updated•11 years ago
|
blocking-b2g: 2.0? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•