Closed
Bug 1001200
Opened 12 years ago
Closed 12 years ago
[B2G][Tarako][Camera]Tapping Camera while not plugged in with USB cable displays contradictory message of Camera can not be used while plugged in
Categories
(Firefox OS Graveyard :: Gaia::Camera, defect)
Tracking
(b2g-v1.3 unaffected, b2g-v1.3T affected)
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| b2g-v1.3 | --- | unaffected |
| b2g-v1.3T | --- | affected |
People
(Reporter: mclemmons, Unassigned)
References
()
Details
(Whiteboard: [tarako-exploratory])
Attachments
(2 files)
User taps Camera app without being connected to another device through a USB that states Camera can not be used while plugged in, Unplug the phone to view pictures. This message displays nearly 20 minutes after the last time the device was plugged in via USB to a computer for roughly 20 minutes with a battery level below 20 percent. Once device restarted, expected functionality returned but it's concerning behavior message appeared at all.
Prerequisites:
1. Enable USB Storage is enabled in Settings
Repro Steps:
1) Updated Tarako to BuildID: 20140424014003
2) Tap Camera App
Actual:
Camera can not be used while plugged in Unplug the phone to view pictures
Expected:
Camera App opens without error message
Notes:
Repro frequency: (5/5 100% before restart – 0/10 0% after restart)
See attached: Logcat, Firewatch, Video clip = https://www.youtube.com/watch?v=44SDNdBnTMc
Environmental Variables:
Device: Tarako 1.3T MOZ
BuildID: 20140424014003
Gaia: 706f474230432c8cb01e124aee2c055ec902aa1d
Gecko: 26ef3dded9ff
Version: 28.1
Firmware Version: sp6821a_gonk4.0_user.pac
| Reporter | ||
Comment 1•12 years ago
|
||
This issue does not reproduce on 1.3 Buri. Device does not demonstrate this message when clearly unplugged.
Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140424024004
Gaia: 32a9e3db738e0b3bc44a4d4d5c16512a2617a2cf
Gecko: 97ca2fdf3cf4
Version: 28.0
Firmware Version: v1.2-device.cfg
| Reporter | ||
Comment 2•12 years ago
|
||
I can't seem to get into this state with just the given STR.
I think there's some additional steps that are needed to get to that state...
I'm not sure what they might be.
Do you recall some of the things that you might have done before this occurred?
Does it happen once you reboot?
Flags: needinfo?(mclemmons)
| Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #3)
> I can't seem to get into this state with just the given STR.
> I think there's some additional steps that are needed to get to that state...
> I'm not sure what they might be.
>
> Do you recall some of the things that you might have done before this
> occurred?
> Does it happen once you reboot?
1. Tarako attached via USB cable to computer and charging with a very low Battery (less than 20%) for at least 20 consecutive minutes in a flat position. (prior to that, device was in constant use for nearly five consecutive hours). Device was being charged at the same time a Buri was being charged on the same computer using a different USB slot. Each device had the charging icon displaying in the status bar.
2. Disconnected both Buri and Tarako from USB and walked 10 feet to another location in same room.
3. Set Tarako on a special apparatus that holds device to take video without user holding device.
4. Placed Buri in separate part of apparatus to capture video from Tarako.
5. Tap Camera App
Bug encountered.
Note - the apparatus described in steps 3 and 4 above has metal ends attached to plastic straws atop a recyclable box but has been used in the past capturing video using a Buri without a problem. This was the first time placing this particular Tarako on this part of the apparatus.
Testing this morning (Friday, April 25 -using the same April 24 Tarako build) placing Tarako atop this apparatus with a low battery and recent charging simultaneously with a Buri and following above STR did not reproduce the issue reported in Comment 0.
Note - Passcode lock was enabled Thursday April 24 and Friday April 25.
The phone was not rebooted on Thursday April 24 prior to encountering the reported issue.
Flags: needinfo?(mclemmons)
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•