Closed Bug 1050079 Opened 10 years ago Closed 9 years ago

[Clock] No preview for adjusting the volume on System Alarm Volume.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: vishnubiaora, Unassigned)

References

Details

(Whiteboard: [LibGLA,TD84038,WW, B])

No preview for adjusting the volume on System Alarm Volume.
STR:
1.Clock > New alarm > No preview for adjusting the volume on System Alarm Volume.

Actual:No preview for adjusting the volume on System Alarm Volume.
Expected:Should be able to enter preview at System Alarm Volume Adjust the volume.
when we are in Edit alarm Screen then we can change the Alarm volume using "Volume" button then whats the use of this separate "System Alarm Volume" in Edit Alarm screen.
Flags: needinfo?(m)
I believe if there is music playing (e.g. from the music app), the hardware volume buttons will change the music, not the alarm volume. We received a lot of complaints in the past from the volume being hard to discover.

Can you explain what you mean by "preview"? Do you mean the alarm should play a sample preview of how loud it would sound when the user drags the slider?
Flags: needinfo?(m) → needinfo?(vishnubiaora)
it means when we move slider in Setting>sound>Alarm or Setting>sound>Media then selected rings sound is coming but in case of Clock > New alarm > System Alarm Volume  when move slider selected ringtone sound did not come.
Flags: needinfo?(vishnubiaora)
Whiteboard: [LibGLA,TD84038,WW, B]
Hi Alive

Test 1:
1. Go to settings
2. GO to sound
3. <input type = "range"> element Alarm

Test 2:
1. Go to clock
2. GO to new alarm
3. <input type = "range"> element System alarm volume

a.> Firstly, In both the Tests, step 3 refers to the same volume. First of all there name should be same instead of (System alarm volume it should/may be alarm volume). As a developer I myself gets confused what somebody mean by 'system alarm volume'.

b.> Secondly, Test2(step 3) is not synchronized with Test1(step 3) i.e. I have seen this many times. I don't have an exact scenario. May be this should work for you.
    i.> Do Test1 as indicated above & reduce the alarm volume to half.
    ii.> Now, do Test2. The Volume shown there is Full.
    Or, (if this doesn't work)
    i.> Go to settings->sound->Alarm volume slider
   ii.> Press home button
  iii.> Go to clock->New Alarm->Alarm volume slider
   iv.> Press home button.
    v.> Long press home button go to settings & change the alarm volume
   vi.> Press home button
  vii.> Long press home button go to clock & see the sound didn't change
     or, (if this also didn't work - do steps i to iv as it is)
    v.> Long press home button go to clock & change the alarm volume
   vi.> Press home button
  vii.> Long press home button go to settings & see the sound didn't change
  In either of this it will fail.
 
c.> Thirdly, We can press hardware volume keys up/down to reduce/add volume of alarm in alarm app. Thereby, I don't feel the need of <input type = "range"> element System alarm volume in alarm app.
d.> Fourth, We don't give any sound feedback on changing the <input type = "range"> element System alarm volume unlike as we do it in Test 1 above.

With these all I feel that these Test2(Step 3) element shouldn't be there. May be it should be removed or hidden.

We might need to talk with UI guy's as well.

thanks!
Flags: needinfo?(m)
Hi mcav 

TO add to the list further Comment#4- 

e.> Fifth, Let's take the user go to clock->new alarm->system alarm volume max-> set an alarm. Alarm is set. Go to settings -> sound-> Reduce the alarm volume. When the alarm comes, it comes with the reduced volume. Henceforth I don't find any need of system alarm volume there.

Mike -> Please read comment #4 & Comment#5.

thanks!
Flags: needinfo?(mike)
Hi Arthur

Please read comemnt # 4 & comment # 5.

Please if you can ping some one from clock app, it would be great. Past 14 days I have been waiting.

Thanks.
Flags: needinfo?(arthur.chen)
Juwei (needinfoed) is the UX owner for Clock. It sounds like there are two separate requests here, one requesting that we get rid of the "System Alarm Volume" slider, and one saying that it doesn't work as expected. In any case, Juwei can weigh in on the requests in Comment 4 and Comment 5.
Flags: needinfo?(mike)
Flags: needinfo?(m)
Flags: needinfo?(jhuang)
Flags: needinfo?(arthur.chen)
The history of this design can be rolled back to bug 939197 when we were still working on 1.4. At that time there's no way to adjust alarm volume in clock app because hardware key cannot adjust alarm volume yet.

Although the alarm volume can control by HW key now, the design still have benefit to stay in the alarm edit view. One user case is as Marcus said: users cannot adjust alarm volume while music is playing in the background. The volume slider also can indicate that how loud the alarm sound is now in case users accidentally adjust the volume to very low in elsewhere but they forgot it totally. 

Of course, in order to fulfil this design, the alarm volume from setting app + alarm settings view + hardware alarm volume key should be consistent at all time, including the preview sound.
And I think "System alarm volume" would be helpful to indicate that the value would be apply to all alarms not just one.

So I prefer keeping the volume slider on alarm edit view, as long as the behaviour of system alarm sound is consistency with it.
Flags: needinfo?(jhuang)
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.