Firefox OS/Comms/Dialer/Sprint/v2.1-S6/20141007-StandupNotes: Difference between revisions

From MozillaWiki
< Firefox OS‎ | Comms‎ | Dialer‎ | Sprint‎ | v2.1-S6
Jump to navigation Jump to search
mNo edit summary
Line 25: Line 25:
* 2.2? {{Bug|1077331}} - [System] If Vibrate is on, and a call is receive, it keeps vibrating
* 2.2? {{Bug|1077331}} - [System] If Vibrate is on, and a call is receive, it keeps vibrating
** Unassigned, new nom. Asking for branch checks.
** Unassigned, new nom. Asking for branch checks.
====drs====
====Rik====
====gtorodelvalle====
====thills====
====pacorampas====
====jpruden92====
====jlorenzo====

Revision as of 23:16, 6 October 2014

Blockers

  • 2.1+ bug 1070066 - [Dialer] The call screen does not display call info and shows a black background after repeatedly placing calls
    • Assigned to Tamara.
    • The patch in bug 1076597 will fix this.
    • We chose to dupe this to bug 1068109 as this effectively fixed the issue.
  • 2.1+ bug 1074379 - Dialer does not always show incoming call #
    • Assigned to Anthony for posterity. No work to be done.
    • This is related to bug 1070066.
    • The patch in bug 1076597 will fix this.
  • 2.1+ bug 1068109 - Restore 2s delay before callscreen is closed
    • Landed, needs to be uplifted to 2.1.
  • 2.1+ bug 1075699 - Calling voicemail by long-pressing the 1 button displays an error and then calls
    • Assigned to Tamara. Can only be repro'd on a T-Mobile SIM.
    • Tamara and Hsin-Yi have been digging, but this is still very much unknown. It should be possible to handle by the 2.1+ deadline.
  • 2.0+ bug 1074601 - The SIM 2 Voice mail displayed as a "Unknown contact" in dialer view and call log view
    • Assigned to Tzu-Lin, being reviewed by Doug. This is under control.
    • Will be ready to land soon.
  • 2.0? bug 1066874 - [Dialer] User can be put into a state where there is no one on the other line in a phone call and user is unable to end call
    • Assigned to Germán, new nom.
    • Looks like it could be bad, and is not a regression.
  • 2.0? bug 1077392 - The USSD interface shows "Session expired" when is sent a wrong USSD code.
    • Unassigned, new nom. This looks like a RIL issue, though it will need more investigation.
  • 2.0? bug 1078222 - USSD Notify response is not shown while USSD Request is working fine
  • 2.2? bug 1077331 - [System] If Vibrate is on, and a call is receive, it keeps vibrating
    • Unassigned, new nom. Asking for branch checks.

drs

Rik

gtorodelvalle

thills

pacorampas

jpruden92

jlorenzo