1222739 - Dialer showed keypad that didn't submit tones to active call

Status: RESOLVED INCOMPLETE

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

Description

[Ed Morley [:emorley]]

>> Feature Request Summary:
Dialer showed keypad that didn't submit tones to active call

>> Description of feature, or problem to be solved
Using the Z3C foxfooding device with the latest FOTA/OTA installed (build number: eng.naoki.20151007.074137, build identifier 20151023101519).

STR:
1) Open phone app
2) Select a contact to start a call (or maybe enter a phone number manually; can't remember which it was)
3) When in-call, move phone away from face so you can start entering numbers on the keypad (eg a customer service number that asks you to choose options)
4) Try pressing numbers on the keypad

Expected:
When in-call, after moving the phone away from your face, the UI should initally be the standard in-call UI with call duration etc shown. After pressing the keypad icon, the UI should change to the keypad (with the already dialed number showing in the "typed numbers" history line) and then after entering a number, you should hear the tone being made, and the customer service line should respond as though you'd chosen an option.

Actual:
When moved away from my face, the phone was already showing a keypad, but it was not the standard in-call keypad (ie it didn't show the already dialed digits in the history line above the keypad numbers) and when numbers were pressed, no tones were heard, and the service being called didn't respond as though I'd chosen eg "option 2".

I can't tell whether the dialer "got stuck" and didn't clear after the phone call was started, or if somehow I ended up on the "add another number/person to this call, making it a three-way call" feature.

Comment 1

[Johan Lorenzo [:jlorenzo] - PTO - Back August 24th]

I recall a similar comment in Bugzilla, but I haven't managed to find it.

At that time, I remember the main argument was: the in-call keypad is visually different enough from the regular keypad, so users won't be confused. Maybe we could revisit the flow? What's UX point of view?

Comment 2

[Ed Morley [:emorley]]

Since writing the comment above, I've also noticed that the "add a person to the call" button is right next to the keypad button - so it's possible I fat-fingered it. Maybe moving the icons so they aren't next to each other might help too?

Comment 3

[Gabriele Svelto [:gsvelto]]

This is bizarre, was the keypad you got the normal dialer keypad (light blue rectangle at the top, white keys)? If that's the case then it might be due to bug 1209536 or bug 1185709 which could both cause this behavior; however both of those bugs should have been fixed in your build. Could you check if you can still reproduce on a recent nightly build?

Comment 4

[Ed Morley [:emorley]]

I can't quite remember unfortunately - it was mid-call and I was hurrying since the number I'd dialed would only wait a few seconds for me to select the next option. Those bugs definitely sound like they might have helped fwiw.

> Could you check if you can still reproduce on a recent nightly build?

I don't believe we're supposed to flash custom builds on the foxfood devices, since they have usage-tracking-foo enabled. I also don't know how I reproduced before, so doing so again (particularly when it involved making phone calls) may be difficult.

Happy to call this INCOMPLETE at some point, but didn't want to just not file it, in case you'd had similar reports etc (or in case I hit it again later).

Comment 5

[Tiffanie Shakespeare [:tif]]

From UX triage: 

We aren't able to reproduce. Can you provide a video if you are still experiencing the issue?

Thanks for pinging the UX team!

Comment 6

[Ed Morley [:emorley]]

I'm not able to reproduce on-demand unfortunately (see comment 4)

Comment 7

[Tiffanie Shakespeare [:tif]]

Adding qawanted

Comment 8

[Pi Wei Cheng [:piwei] (inactive)]

Cannot reproduce this following STR at comment 0 on latest Aries, or the Aries OTA'd from RC4.

I think the reporter hit bug 1185709, which is still reproducible on the OTA build, as well as on latest Aries, which makes bug 1185709 fail for verification. I'll comment on that bug.

No repro for comment 0 STR, but does repro bug 1185709 on:

Device: Aries 2.6 Master
BuildID: 20151113123209
Gaia: e8c15ae4e5324a210000ee0a869a962aa542009f
Gecko: faf815a0fa9b052a38bce00c0c2aa1e2c9610936
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 45.0a1 (2.6 Master) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0

Device: Aries 2.5 Master (OTA'd from RC4)
BuildID: 20150619225606
Gaia: 4c06ed88ddccaba8dc941e5006bd2a9e57306f07
Gecko: 7c1a6b1151a1539186b950a144387e2d7f378d1b
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 41.0a1 (2.5 Master) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Comment 9

[Tiffanie Shakespeare [:tif]]

Ed - No one seems to be able to reproduce so I am closing the bug. Please re-open if you hit it again.