Closed Bug 860726 Opened 7 years ago Closed 7 years ago

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


(Firefox OS Graveyard :: Bluetooth, defect)

Not set


(blocking-b2g:tef+, firefox21 wontfix, firefox22 wontfix, firefox23 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)

1.0.1 IOT1 (10may)
blocking-b2g tef+
Tracking Status
firefox21 --- wontfix
firefox22 --- wontfix
firefox23 --- fixed
b2g18 --- fixed
b2g18-v1.0.0 --- wontfix
b2g18-v1.0.1 --- fixed


(Reporter: shawnjohnjr, Assigned: shawnjohnjr)



(Whiteboard: [status: will be fixed by bug 869296] QARegressExclude)

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
blocking-b2g: --- → leo?
Nominate as a leo+ since we got inquiry from leo.
Assignee: nobody → shuang
This needs more context - what's the user impact if left unfixed?
Triage 4/12 - Leo+ for certification
blocking-b2g: leo? → leo+
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.
blocking-b2g: leo+ → leo?
Flags: needinfo?(ffos-product)
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?)
Flags: needinfo?(shuang)
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.
Flags: needinfo?(shuang)
Flags: needinfo?(ffos-product)
If this blocks certification, then we should block on it.
blocking-b2g: leo? → leo+
Sorry, spoke too soon - suggests that this might not be in scope for v1.1.
blocking-b2g: leo+ → leo?
Hi Joe,
As Alex mentioned, please raise for tef.
It looks like a tef+ case.
blocking-b2g: - → tef?
blocking-b2g: tef? → tef+
Depends on: 869296
Target Milestone: --- → 1.0.1 IOT1 (10may)
We moved patch to Bug 869296. Once Bug 869296 fixed, this bug also get fixed. Bug 869296 is going to review process.
Can we dupe then?
Whiteboard: [status: will be fixed by bug 869296]
Bug 869296 is fixed now, marking this one fixed as well.
Closed: 7 years ago
Resolution: --- → FIXED
Unable to verify. Lack of resources. Need Bluetooth PTS tool to verify.
Marking as QARegressExclude.
Whiteboard: [status: will be fixed by bug 869296] → [status: will be fixed by bug 869296] QARegressExclude
You need to log in before you can comment on or make changes to this bug.