Closed Bug 883335 Opened 13 years ago Closed 8 years ago

Need to figure out UI for settings when volume can't be shared with PC

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: dhylands, Unassigned)

References

Details

Currently, when you enable USB Mass Storage in the Settings app, there are 2 reasons why the volume can fail to be shared with the PC. In either of these scenarios, there is currently no user feedback, and the user won't know why the volume didn't appear in the PC. One of the reasons that sharing can fail is if there is a volume lock. Currently, volume locks are obtained while storing an update to an sdcard, or while transferring a file to the sdcard via bluetooth. The current behaviour (at least with bug 876782) is that if a volume lock is held, then the Automounter puts the following message in logcat: UpdateState: Mounted volume XXX is locked, not sharing With bug 876782 sharing can fail if there are any open files on the volume (perhaps the music player is currently playing a song). In this case, logs like the following will show up: The following files are open under '/mnt/sdcard' PID: 2697 file: '/mnt/sdcard/foo' app: '' comm: 'sh' exe: '/system/bin/mksh' PID: 2702 file: '/mnt/sdcard/foo' app: '' comm: 'cat' exe: '/system/bin/toolbox' PID: 3352 file: '/mnt/sdcard/Music/01_-_Love Who You Love.mp3' app: 'Music' comm: 'Music' exe: '/system/b2g/plugin-container' UpdateState: Mounted volume sdcard has open files, leaving However, this is not really discoverable by the user. So I think we need some mechanism to communicate to the user that files are open, and perhaps a way to find out what files are open.
blocking-b2g: --- → leo?
Does this actually block bug 876782? This doesn't seem like a regression in 1.1. Please renominate with that justification, if it is a regression or a blocker for a leo+ bug.
blocking-b2g: leo? → -
Flags: needinfo?(dhylands)
If its acceptable to have the USB Mass Storage appear to 'not work' while there are open files, then this bug doesn't need to block.
blocking-b2g: - → leo?
Flags: needinfo?(dhylands)
Triage- not blocking release for - not a likely scenario for users to be transferring via BT and attempting to connect via UMS at the same time. Chances are the users would use the PC to do whatever transfer they wish to do. - new strings are required if we take this to create a prompt to inform the user of the situation.
blocking-b2g: leo? → ---
BT isn't the only thing that can old files open. If you're playing Music or Watching a video, then these operations hold files open as well.
Blocks: 912609
blocking-b2g: --- → koi?
I'm really confused by all of the threads on this, so I'm asking for QA Wanted to confirm the following: On the latest 1.1 build on any shipping production device, is there a warning message that appears when you try to enable USB mass storage when you are playing a music file in the background?
Keywords: qawanted
(In reply to Jason Smith [:jsmith] from comment #6) > I'm really confused by all of the threads on this, so I'm asking for QA > Wanted to confirm the following: > > On the latest 1.1 build on any shipping production device, is there a > warning message that appears when you try to enable USB mass storage when > you are playing a music file in the background? To the best of my knowledge, no release has ever included a warning message that appears when you are playing a music file. The only warning that I'm aware of is one that shows up the very first time that you enable UMS (irrespective of whether music is playing or not). My understanding of the various behaviours is: In 1.1, If you enable UMS while music is playing, then UMS just appears to not work, until the music stops. In pre-1.1, If you enable UMS while while music is playing, then the music app is immediatly killed, and UMS is enabled. Sometimes the mediaserver would also crash. In recent 1,2, if you enable UMS while music is playing, then the music app exits (typically within a second) and UMS is enabled.
Okay. Moving to 1.3? then.
blocking-b2g: koi? → 1.3?
Keywords: qawanted
SystemPlatform triage: plus for 1.3
blocking-b2g: 1.3? → 1.3+
(In reply to Bruce Huang (:bhuang) from comment #9) > SystemPlatform triage: plus for 1.3 This is not a committed feature for 1.3, so this should not block the release.
blocking-b2g: 1.3+ → 1.3?
Adding to System-Platform backlog
Blocks: 908549
blocking-b2g: 1.3? → ---
blocking-b2g: --- → backlog
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.