Closed Bug 817159 Opened 12 years ago Closed 12 years ago

The status bar does not display a vibrate icon when the phone is set to vibrate only

Categories

(Firefox OS Graveyard :: Gaia::System, defect, P3)

defect

Tracking

(blocking-basecamp:+)

VERIFIED FIXED
B2G C3 (12dec-1jan)
blocking-basecamp +

People

(Reporter: ckreinbring, Assigned: vingtetun)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121024073032

Steps to reproduce:

1. From the home screen, select Settings then Sound.
2. Tap the Ring toggle off and the Vibrate toggle on.
3. Observe the status bar.  Look for a vibrate icon.
4. Tap the ring toggle back on and return to the home screen.
5. Press the volume hardkey down until the volume meter is empty and the vibrate icon is lit.
6. Observe the status bar.  Look for a vibrate icon.


Actual results:

No vibrate icon is visible during steps 3 and 6.


Expected results:

There is a vibrate icon visible in the status bar during steps 3 and 6.
There's also no indicator when you go into silent mode.

Every phone I've ever owned -- feature phone or not -- has this indicator.  I think it would be crazy for us to ship without it.
blocking-basecamp: --- → ?
Assignee: nobody → alive
blocking-basecamp: ? → ---
blocking-kilimanjaro: --- → +
Priority: -- → P3
Need UX input here:
On what situation shall we see the vibration icon?
How about if I am hearing music, and the vibration settings is on?
Flags: needinfo?(kyee)
I am confused what happened in triage on this bug. Uhh...why is k9o set? We aren't really actively consistently using that flag. Let's try again.
blocking-basecamp: --- → ?
blocking-kilimanjaro: + → ---
blocking-basecamp: ? → +
Target Milestone: --- → B2G C3 (12dec-1jan)
Not a sure it's a V1 blocker
blocking-basecamp: + → ?
Changed my mind, agree with triage
blocking-basecamp: ? → +
Will be fixed by bug 822318. Stealing.
Depends on: 822318
Fix verified in build 20121231070201.
Status: RESOLVED → VERIFIED
Flags: needinfo?(kyee)
You need to log in before you can comment on or make changes to this bug.