Closed Bug 868347 Opened 12 years ago Closed 12 years ago

[Buri][PTS][HFP][Certification]Need to support Enhanced Call Status

Categories

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

Product:
Firefox OS Graveyard
Component:
Bluetooth
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: sync-1, Assigned: gyeh)

References

Details

CONTACT INFO (Name,Phone number): yuanying 021-61460640 DEFECT DESCRIPTION: Need to support Enhanced Call Status REPRODUCING PROCEDURES: Regarding PICS enhanced call status (HFP_2_21a, HFP_2_21c) set to false which creates test case failure. So need to support Enhanced Call Status , because it is mandatory and blocks reset of HFP tests. EXPECTED BEHAVIOUR: For KO,please refer to mozilla PR list: 01. bug 827204 02. bug 827255 03. bug 823346 04. bug 827230 05. bug 828798 06. bug 827266 07. bug 828175 08. bug 846647 09. bug 825861 10. bug 825851 11. bug 835740 12. bug 828837 13. bug 827212, patch 1 14. bug 827212, patch 2 ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:
block BT certification
blocking-b2g: --- → tef?
Component: Gaia::Bluetooth File Transfer → Bluetooth
Summary: [Buri][PTS][HFP]Need to support Enhanced Call Status → [Buri][PTS][HFP][Certification]Need to support Enhanced Call Status
This seems to be asking we need to support a new feature (Enhanced cAll Status). HOw complex is adding support for that?
Flags: needinfo?
Flags: needinfo?(gyeh)
Flags: needinfo?
adding ni? echou as well
Flags: needinfo?(echou)
Please also consider list: 830213 860663 860726 828160 828804 828837 828882 857795 which described in meta bug 861047, and judge they are certification blocking bugs. Thanks.
We had started to implement these "small" features on m-c since last December, and all of them were uplifted to branch b2g18 in the end of March. It's pretty stable and works well on both b2g18 and m-c. Most important of all, we need these patches to pass BT certification.
Flags: needinfo?(gyeh)
Bluetooth profile certification could not be passed by using current v1.0.1 branch. I can confirm this becuase we had done in-house PTS testing. Patches of those bugs mentioned in comment 1 have landed on m-c and b2g18 and worked well. For BT certification, we should have them landed on v1.0.1 as well.
Flags: needinfo?(echou)
I've marked all those bugs in comment 1 as tef+. But... are we sure we are passing BT certification with those patches applied to 1.0.1? Are more patches coming (e.g. the ones listed in comment 4)?
Flags: needinfo?(sync-1)
Flags: needinfo?(gyeh)
By the way, marking tef- as this is a meta and hence not actionable.
blocking-b2g: tef? → ---
(In reply to Daniel Coloma:dcoloma from comment #7) > I've marked all those bugs in comment 1 as tef+. > > But... are we sure we are passing BT certification with those patches > applied to 1.0.1? Are more patches coming (e.g. the ones listed in comment > 4)? Since those are also certification-related bugs, I would say yes. Our goal is to make Bluetooth more complete. Of course we don't want to break original functions because of merging these patches, but these are patches working well in both m-c and b2g18. Moreover, they do fix cerfification issues reported by partners(or by us since now we are able to do in-house tests). I can't see any reason why we shouldn't have them merged into v1.0.1.
(In reply to Shawn Huang from comment #4) > Please also consider list: 830213 860663 860726 828160 828804 828837 828882 > 857795 which described in meta bug 861047, and judge they are certification > blocking bugs. Thanks. These are also must-have to pass Bluetooth Hfp certification, and some updates as following: Bug 828804 is a dup of bug 828798, so no need to a tef+. Bug 828837 has been listed in comment 1 and is tef+ now. These are what we found so far. Shawn helps to go on all certification tests. He'll report new bugs if he find a new one and marked them as blockers of bt-certi-blocking (bug 861047).
Flags: needinfo?(gyeh)
I've tested with today's v1.0.1 build, and AG_ECS test cases can be all passed. So I'm going to close this bug. Thanks for everybody helped.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
(In reply to Daniel Coloma:dcoloma from comment #7) > I've marked all those bugs in comment 1 as tef+. > > But... are we sure we are passing BT certification with those patches > applied to 1.0.1? Are more patches coming (e.g. the ones listed in comment > 4)? according to Shawn's comment, yes.
Flags: needinfo?(sync-1) → needinfo?(shuang)
which patch fixed the bug? thanks~
(In reply to sync-1 from comment #13) > which patch fixed the bug? > thanks~ Mainly bug 827212, and so does bug 869306.
mark tef?, please uplift patch to v1.0.1
blocking-b2g: --- → tef?
(In reply to buri.blff from comment #15) > mark tef?, please uplift patch to v1.0.1 I think patches mentioned in comment 14 which fixed problems of 'Enhanced Call Status' test items are all in v1.0.1 already.
clear blocking-b2g flag per comment 16. fixes are already in v1.0.1 with bug 827212, and bug 869306.
blocking-b2g: tef? → ---
You need to log in before you can comment on or make changes to this bug.