860726 - [Bluetooth][Certification]HFP PTS test case TC_AG_OCM_BV_02_I failed

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Bluetooth, defect)

Description

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

When testing TC_AG_OCM_BV_02, it is requested to clear all call history.
If call history is empty, we need to reply "ERROR" to hfp role.
Otherwise, test case failed

Comment 1

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Nominate as a leo+ since we got inquiry from leo.

Comment 2

[Alex Keybl [:akeybl]]

This needs more context - what's the user impact if left unfixed?

Comment 3

[Wayne Chang [:wchang]]

Triage 4/12 - Leo+ for certification

Comment 4

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Hi Wayne,
This required to change dialer app to support memory dialing. Please help to check this is required to have leo+ in the triage meeting.

Comment 5

[Peter Dolanjski [:pdol]]

Shawn, could you describe this further?  Why is supporting memory dialing related to clearing the call history? (and does this refer to call history in the call log?)

Comment 6

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

TC_AG_OCM_BV_01_I, TC_AG_OCM_BV_02_I are test cases to verify handsfree memory dialing protocol. They are somehow mandatory.
The reason why I mentioned "call history" is because we're trying to workaround this test case via replacing memory-dial as last number redial. So Bug 860663 (TC_AG_OCM_BV_01_I) with comments points out why we took redial as memory dialing as workaround. But this is not proper thing to do.

The TC_AG_OCM_BV_02_I purpose is to verify that phone can respond with an error message when headset attempts to access invalid or empty memory location, which means it is possible that memory location (such as memory location '1' referred to number '123'). TC_AG_OCM_BV_02_I depends on TC_AG_OCM_BV_01_I.

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

If this blocks certification, then we should block on it.

Comment 8

[Lukas Blakk [:lsblakk] use ?needinfo]

Sorry, spoke too soon - https://bugzilla.mozilla.org/show_bug.cgi?id=860663#c11 suggests that this might not be in scope for v1.1.

Comment 9

[Alex Keybl [:akeybl]]

Same as https://bugzilla.mozilla.org/show_bug.cgi?id=860663#c12

Comment 10

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Hi Joe,
As Alex mentioned, please raise for tef.

Comment 11

[Kai-Chih Hu [:khu]]

It looks like a tef+ case.

Comment 12

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

We moved patch to Bug 869296. Once Bug 869296 fixed, this bug also get fixed. Bug 869296 is going to review process.

Comment 13

[Alex Keybl [:akeybl]]

Can we dupe then?

Comment 14

[Johnny Stenback (:jst)]

Bug 869296 is fixed now, marking this one fixed as well.

Comment 15

[Mila Davydova]

Unable to verify. Lack of resources. Need Bluetooth PTS tool to verify.
Marking as QARegressExclude.