Closed Bug 869282 Opened 11 years ago Closed 11 years ago

[Bluetooth][Certification]HFP PTS test TC_AG_ACS_BV_04_I test case fail

Categories

(Firefox OS Graveyard :: Bluetooth, defect, P1)

x86
Windows XP
defect

Tracking

(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.1 fixed)

RESOLVED FIXED
1.0.1 Cert2 (21may)
blocking-b2g tef+
Tracking Status
b2g18 --- fixed
b2g18-v1.0.1 --- fixed

People

(Reporter: wu.xinxiang, Assigned: shawnjohnjr)

References

Details

(Whiteboard: [status: patch needed-depends on 870683][target:05/17] QARegressExclude)

what did you do?
We did our HFP PTS test by using Boot2Gecko/Firefox OS phone.TC_AG_ACS_BV_04_I,TC_AG_ACS_BV_08_I,TC_AG_ACS_BV_11_I,TC_AG_ACS_BI_14_I are all fail.

what happened?
When the PTS require we to do the Action as below:
"Click Ok,then close the audio connection(SCO) between the Implementation Under Test(IUT) and the PTS.Do not close the service level connection(SLC) or power-off the IUT".
We can not find a way to close the sco.When we try to hung up the call,we find both SCO and SLC will be close.
And this will made the TC_AG_ACS_BV_04_I Inconclusive.

what should have happened?
There's the Output of the PTS,please check it.Thanks.
Test case : TC_AG_ACS_BV_04_I started
	- SDP Service record for PTS: 'Handsfree HF' successfully registered
	- The IUT claims support for the following eSCO LMP packet types: EV3, 2-EV3, 
	- AT: SPP connect succeeded
	- AT: Service Level Connection established
	- AT: ERROR
	- AT: ERROR
	- AT: ERROR
	- AT: post SLC command sequence complete
	- AT: RING
	- AT: Received +CLIP: "13880281851",129
	- AT: Incoming call established
	- HCI: Audio Connection enabled
	- AT: Call terminated
	- unexpected call termination
	- HCI: Audio Connection disabled
	- AT: SPP disconnect succeeded
	- MTC: Test case ended
Final Verdict : Inconclusive
Priority: -- → P1
In order to pass these test cases, we need to be able to switch SCO. Just like the dependency set by Shawn, we're trying to solve this in bug 830213. Please retry after bug 830213 is fixed.
Dear Sir,
Thanks for your reply,we will follow the bug 830213 untill it is fixed.
If this is a Bluetooth certification blocker, it should be marked as tef+.
blocking-b2g: --- → tef?
After bug 830213 landing into v1.0.1, need to wait for bug 870683 change in Gaia Dialer app.
Depends on: 870683
It is a blocker but not sure if this is just a duplicated of bug 870683 or depends on it.
blocking-b2g: tef? → tef+
Flags: needinfo?(echou)
shuang - are you the right owner here to verify that bug 830213 and bug 870683 resolves this?
Assignee: nobody → shuang
Yes. I am the owner to verify it. I'm waiting for bug 870683.
Set target date as May 17 due to bug 870683's target date.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → 1.0.1 Cert2 (28may)
Whiteboard: [status: patch needed-depends on 870683][target:05/17]
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
I assume we can mark this as fixed in all the branches as bug 830213 and bug 870683 are fixed in all branches too. Please do change it if my assumption is wrong.
Clear ni since it's been fixed already.
Flags: needinfo?(echou)
Unable to verify. Lack of resources. Need Bluetooth PTS tool to verify.
Marking as QARegressExclude.
Whiteboard: [status: patch needed-depends on 870683][target:05/17] → [status: patch needed-depends on 870683][target:05/17] QARegressExclude
You need to log in before you can comment on or make changes to this bug.