Closed Bug 860575 Opened 12 years ago Closed 12 years ago

[Bluetooth] Caller number is not displayed on Carkit

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME
1.1 QE1 (5may)

People

(Reporter: leo.bugzilla.gecko, Assigned: shawnjohnjr)

Details

(Whiteboard: [TD-11434])

Attachments

(1 file)

GENERAL Defect Description 1. Title : [BT/ BT CAR KIT] - Caller number is not displayed on CK 2. Precondition : Pair and connect DUT to CK 3. Tester's Action : Make or receive call. 4. Detailed Symptom (ENG.) : Caller number is not displayed on CK (Unknown number, ****, unknown) despite HFP is supported. 6. Expected : Caller number is displayed on CK 7.Reproducibility: y 1)Frequency Rate : 100%
Dear Mozilla Team, I upload the air log and images. Please check it. Thanks.
Assignee: nobody → shuang
It looks like both PCM and Conti CK with the same CLIP problem. Do you see the same problem on other CK? Just want to know this IOT bug be general case or not.
Flags: needinfo?(leo.bugzilla.gecko)
This could be resulted from CLCC support missing, can you use the latest Gecko b2g18 v1.1 to verify again?
Dear Mozilla Team, Our tester seems to use the old version. Did not have this problem in the car kit you are using? I'll update again after the re-test this bug. Thanks.
Flags: needinfo?(leo.bugzilla.gecko)
Whiteboard: [TD-11434]
Dear Mozilla Team, Root cause of this bug is that CLIP is sent to CK late. It is fixed in latest version, so I'll close this case. Thanks.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Resolution: WONTFIX → WORKSFORME
Target Milestone: --- → Leo QE1 (5may)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: