Closed
Bug 919834
Opened 11 years ago
Closed 6 years ago
[Buri] Unable to toggle Default Media Location
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:-)
RESOLVED
WONTFIX
blocking-b2g | - |
People
(Reporter: marcia, Unassigned, Mentored)
References
Details
(Keywords: regression, Whiteboard: , burirun2)
Attachments
(1 file, 1 obsolete file)
125.49 KB,
text/plain
|
Details |
Buri, while using: Gaia 3408cc3f6b190c8cd31832fbb8cd2ae571041f29 SourceStamp f97307cb4c95 BuildID 20130923040214 Version 27.0a1 STR: 1. Download some content to test forward lock. 2. Go to Settings | Media Storage. Observe that the default media location is set to SD card. 3. In the advanced section try to toggle the default media location Expected: I could toggle between SD card and Internal Memory Actual: It remains as the default - SD Card and I cannot change to internal memory Logcat attached. I checked on 1.2 and the issue exists as well there. Works fine using the latest 1.1 build. On Mozilla Central even if I reset the phone the issue still persists.
Reporter | ||
Comment 1•11 years ago
|
||
Although maybe I am hitting Bug 873247?
Comment 2•11 years ago
|
||
Currently, the only devices which have multiple storage areas are the leo and helix. All of the other devices only have a single storage area (which is either the external sdcard (unagi/buri/inari) or internal storage (nexus s/nexus 4). I think that for the case where there is only a single storage area that it might make sense to not show the control which allows the default storage area to be selected, but that's really a UX decision.
Comment 3•11 years ago
|
||
I closed bug 873247 as invalid since there is only one storage area. I left this one open in case we'd like to persue having the settings changed.
Comment 4•11 years ago
|
||
Tested as far back as 6/21 1.2 build and the issue still occurs. "Default media location" option appears even though there is only one storage location. - Issue occurs 6/21 1.2 - Build ID: 20130621031231 Gecko: http://hg.mozilla.org/mozilla-central/rev/7ba8c86f1a56 Gaia: e2f19420fa6a26c4287588701efaec09a750dba1 Platform Version: 24.0a1
Keywords: regressionwindow-wanted
Comment 5•11 years ago
|
||
Hi CJ, Do you know which team is working on the forward lock gaia part?
Flags: needinfo?(cku)
Comment 6•11 years ago
|
||
Hi Ivan, I believe djf is working on that (media team).
(In reply to Dave Hylands [:dhylands] from comment #6) > Hi Ivan, > > I believe djf is working on that (media team). Yes, that's what I know as well
Flags: needinfo?(cku)
Comment 8•11 years ago
|
||
David, could you comment the bug and judge it's blocking status?
Flags: needinfo?(dflanagan)
Comment 9•11 years ago
|
||
It is bad to make the user think that there is internal memory available when there isn't. On devices that have only one storage area, the settings app shouldn't show an option to change. If I was in in a triage meeting about this, I'd want to make it koi+.
Flags: needinfo?(dflanagan)
Comment 10•11 years ago
|
||
Who we should assign this bug to?
blocking-b2g: koi? → koi+
Flags: needinfo?(dflanagan)
Comment 11•11 years ago
|
||
(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) from comment #10) > Who we should assign this bug to? Evelyn and Kaze are the modules owners. Maybe then can take it or assign it.
Flags: needinfo?(kaze)
Flags: needinfo?(ehung)
Flags: needinfo?(dflanagan)
Comment 12•11 years ago
|
||
Kaze, do you know how worked on forward lock and touched this part of code recently? Thanks.
Comment 13•11 years ago
|
||
I don't think the issue is related to forward lock (I don't know it though), and agree with comment 2: it's a UX decision, and we (as engineer) have a discussion before (bug 874313 comment 47), need UX input now.
Comment 14•11 years ago
|
||
BTW, I can mentor someone to fix the issue after having UX input.
Whiteboard: [mentor=evelyn]
Comment 16•11 years ago
|
||
Per talked with Arthur, My suggestion is to remove "Advanced" whole category when the user doesn't have any choice. (Only internal memory or only SD card) And also change 4 related App's (Video,Music,Camera,Gallery) pop up the message wording, remove pop-up messages' button (Go to Advanced). Does it make sense to you ? Any comments are welcome.
Flags: needinfo?(nhsieh)
Updated•11 years ago
|
Assignee: nobody → tzhuang
Updated•11 years ago
|
Whiteboard: [mentor=evelyn] → [mentor=evelyn], burirun2
Updated•11 years ago
|
Flags: needinfo?(rmacdonald)
Flags: needinfo?(kaze)
Comment 19•11 years ago
|
||
Hi Evelyn, Please kindly help to review the settings part. Thanks Hi David, Please kindly help to review the apps part(Camera, Gallery, Video, and Music). Thanks
Attachment #817714 -
Flags: review?(ehung)
Attachment #817714 -
Flags: review?(dflanagan)
Comment 20•11 years ago
|
||
Comment on attachment 817714 [details]
pull request
r- because the change (in Settings app) is not on a correct direction. Please see my comment on Github. Thanks.
Attachment #817714 -
Flags: review?(ehung) → review-
Comment 21•11 years ago
|
||
Comment on attachment 817714 [details]
pull request
Hi Evelyn,
I've updated pull request as your comments.
Please help to review it again.
Thanks
Attachment #817714 -
Flags: review- → review?(ehung)
Comment 22•11 years ago
|
||
Comment on attachment 817714 [details]
pull request
r+ on Settings part with two nits be addressed. Thanks!
Attachment #817714 -
Flags: review?(ehung) → review+
Comment 23•11 years ago
|
||
Comment on attachment 817714 [details]
pull request
I left a couple of comments on github.
I'd slightly prefer that you don't define a new variable in the media apps and just do
if (navigator.getDeviceStorage(type).length <= 1)
Also, I'd prefer if you used "nocard-nointmem" or something like that instead of "nochoice".
In fact, I wonder if we need two separate cases at all. On devices that have internal memory, I didn't think we could ever get into the "nocard" state. Would we ever actually see the "nocard" message and button on those devices? If not, then we don't need separate "nocard" and "nochoice" overlays. Making that change now might be too risky if you hope to uplift this, however.
Attachment #817714 -
Flags: review?(dflanagan) → review+
Comment 24•11 years ago
|
||
Hi David, Thanks for the review. For media apps which depends on MediaDB (Gallery, Video, and Music), I agree with your point that we will never be in 'nocard' state since no volume is available when MediaDB says it is in MediaDB.NOCARD state. But I cannot be sure of this would ever happen in Camera app. I'll fix the Gallery, Video, Music app with only one 'nocard' stat and investigate if this also works on Camera app.
Comment 25•11 years ago
|
||
(In reply to Tzu-Lin Huang [:dwi2] from comment #24) > Hi David, > > Thanks for the review. > For media apps which depends on MediaDB (Gallery, Video, and Music), I agree > with your point that we will never be in 'nocard' state since no volume is > available when MediaDB says it is in MediaDB.NOCARD state. But I cannot be > sure of this would ever happen in Camera app. > > I'll fix the Gallery, Video, Music app with only one 'nocard' stat and > investigate if this also works on Camera app. I think we can open a follow-up bug because it's another issue. :)
Comment 26•11 years ago
|
||
I just tried this patch on Helix (which has enough large internal storage and sdcard slot) Steps: 1. Set default media storage location to SD card while SD card is inserted 2. Remove SD card 3. Open Camera/Gallery/Music/Video app In Gallery, Music, and Video apps, it automatically search content from internal storage. (Though its default media location is SD card ) However in Camera app, it did enter 'nocard' state and poped up message 'Insert a memory card to take pictures or select an alternate default media location in settings.' So I think separation of 'nocard-nointmem' state from 'nocard' state in Camera app is necessary, but no necessary in three other apps. I'll fix this part in the patch because the inaccessible state is cause by this patch.
Comment 27•11 years ago
|
||
Comment on attachment 817714 [details]
pull request
Hi David,
I've update the patch.
Now there is one 'nocard' state in Gallery, Music, and Video app. (No 'nocard-nointmem' state anymore in these three apps)
Only Camera app has both 'nocard' and 'nocard-nointmem' state.
Please kindly help to review it again. Thanks
Attachment #817714 -
Flags: review+ → review?(dflanagan)
Assignee | ||
Updated•10 years ago
|
Mentor: ehung
Whiteboard: [mentor=evelyn], burirun2 → , burirun2
Updated•9 years ago
|
Attachment #817714 -
Attachment is obsolete: true
Attachment #817714 -
Flags: review?(dflanagan)
Updated•9 years ago
|
Assignee: tzhuang → nobody
Comment 28•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•