Closed
Bug 870649
Opened 11 years ago
Closed 11 years ago
[Buri][IOT]Bluetooth is not able to connect at the time to connect it to MAC
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect, P1)
Tracking
(blocking-b2g:-)
RESOLVED
DUPLICATE
of bug 849365
blocking-b2g | - |
People
(Reporter: sync-1, Assigned: echou)
Details
(Whiteboard: Chile, IOT, )
+++ This bug was initially created as a clone of Bug #451773 +++ AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.094 Firefox os v1.0.1 Mozilla build ID:20130502070201 DEFECT DESCRIPTION: The bluetooth doesn't work well at the time to connect it to MAC, the device needs more than four digits to synchronize it with the MAC and it shows eight digits, as you can see we have to have the same digits in the device and MAC. REPRODUCING PROCEDURES: "1. On DuT main menu > Settings > Bluetooth > Turn On 2. In the ""device in the area"" section, select a MAC with discoverable Bluetooth 3. Check that parity codes match and make the connection EXPECTED BEHAVIOUR: The device have to have more digits to synchronize it with the MAC. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior: ++++++++++ end of initial bug #451773 description ++++++++++ CONTACT INFO (Name,Phone number): DEFECT DESCRIPTION: REPRODUCING PROCEDURES: EXPECTED BEHAVIOUR: ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:
Updated•11 years ago
|
Component: Gaia::Bluetooth File Transfer → Gaia::Settings
Updated•11 years ago
|
Whiteboard: Chile, IOT, buri
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → echou
Comment 1•11 years ago
|
||
Which MAC OS version are you using? The cod I see in both my MAC and my device is 6 digits long.
Flags: needinfo?(sync-1)
Updated•11 years ago
|
Whiteboard: Chile, IOT, buri → Chile, IOT, buri [tef-triage]
Comment 2•11 years ago
|
||
Are we talking about Mac OS X here? or MAC addresses?
Comment 3•11 years ago
|
||
Assuming it is a MAC address, can you comment with the specific device to which you are trying to connect?
Comment 4•11 years ago
|
||
per partner it's Mac OS
Comment 5•11 years ago
|
||
unable to reproduce the problem. i used a partner buri build (may 8th build) and can pair ok with my Mac OS X version 10.8.3. and i can share a picture from my phone to my Mac without a problem. same as comment 1, ni from reporter
Comment 6•11 years ago
|
||
(In reply to Joe Cheng [:jcheng] from comment #5) > unable to reproduce the problem. i used a partner buri build (may 8th build) > and can pair ok with my Mac OS X version 10.8.3. and i can share a picture > from my phone to my Mac without a problem. > > same as comment 1, ni from reporter The reporter's MAC OS version is MAC OS X 10.5.8,is this the point?
Flags: needinfo?(sync-1)
(In reply to comment #5) > Comment from Mozilla:per partner it's Mac OS > (In reply to comment #4) > Comment from Mozilla:unable to reproduce the problem. i used a partner buri > build (may 8th build) and can pair ok with my Mac OS X version 10.8.3. and i > can share a picture from my phone to my Mac without a problem. > > same as comment 1, ni from reporter > The reporter's MAC os version is MAC OS X 10.5.8,Is it the point?
Assignee | ||
Comment 8•11 years ago
|
||
We need hcidump log since we cannot reroduce. Please follow https://wiki.mozilla.org/B2G/Bluetooth#Helpful_Debugging_Information to generate hcidump log. Thank you.
Flags: needinfo?(sync-1)
Comment 9•11 years ago
|
||
It works for me with 10.6 and 10.7 (MAC OS X versions). I think we should not block on this one if it is only reproduced in 10.5.
Updated•11 years ago
|
blocking-b2g: tef? → -
Comment 10•11 years ago
|
||
(In reply to Eric Chou [:ericchou] [:echou] from comment #8) > We need hcidump log since we cannot reroduce. Please follow > > https://wiki.mozilla.org/B2G/Bluetooth#Helpful_Debugging_Information > > to generate hcidump log. Thank you. Hi, This issue dues to the version of Bluetooth on the reporter's PC is 2.0,Gaia limits the max pin length is 4 digits,actually more than 4 digits is needed,I think we need to change this logic,you can reproduce it easily when you use a V2.0 device,thanks.
Flags: needinfo?(sync-1)
Assignee | ||
Comment 11•11 years ago
|
||
(In reply to qingluo.wang from comment #10) > (In reply to Eric Chou [:ericchou] [:echou] from comment #8) > > We need hcidump log since we cannot reroduce. Please follow > > > > https://wiki.mozilla.org/B2G/Bluetooth#Helpful_Debugging_Information > > > > to generate hcidump log. Thank you. > > Hi, > This issue dues to the version of Bluetooth on the reporter's PC is > 2.0,Gaia limits the max pin length is 4 digits,actually more than 4 digits > is needed,I think we need to change this logic,you can reproduce it easily > when you use a V2.0 device,thanks. Hi qingluo, Thanks for your explanation. It's much more clear. We have fixed this in bug 849365, but not in v1-train/v1.0.1 branch. I just nominated that bug as tef+ and added you to the cc list of that issue. Let's see how it will go. Eric
Comment 12•11 years ago
|
||
(In reply to Eric Chou [:ericchou] [:echou] from comment #11) > (In reply to qingluo.wang from comment #10) > > (In reply to Eric Chou [:ericchou] [:echou] from comment #8) > > > We need hcidump log since we cannot reroduce. Please follow > > > > > > https://wiki.mozilla.org/B2G/Bluetooth#Helpful_Debugging_Information > > > > > > to generate hcidump log. Thank you. > > > > Hi, > > This issue dues to the version of Bluetooth on the reporter's PC is > > 2.0,Gaia limits the max pin length is 4 digits,actually more than 4 digits > > is needed,I think we need to change this logic,you can reproduce it easily > > when you use a V2.0 device,thanks. > > Hi qingluo, > > Thanks for your explanation. It's much more clear. > > We have fixed this in bug 849365, but not in v1-train/v1.0.1 branch. I just > nominated that bug as tef+ and added you to the cc list of that issue. Let's > see how it will go. > > Eric Hi Eric, Thanks for your support,I'll track it.
Assignee | ||
Comment 13•11 years ago
|
||
Bug 849365 has landed to v1-train/v1.0.1.
Updated•11 years ago
|
Whiteboard: Chile, IOT, buri [tef-triage] → Chile, IOT, buri
Updated•11 years ago
|
Whiteboard: Chile, IOT, buri → Chile, IOT,
Assignee | ||
Comment 14•11 years ago
|
||
Hi qingluo, Please check if it is already fixed. If it is, please leave a comment and I'll close the issue. Thank you.
Flags: needinfo?(qingluo.wang)
Comment 15•11 years ago
|
||
(In reply to Eric Chou [:ericchou] [:echou] from comment #14) > Hi qingluo, > > Please check if it is already fixed. If it is, please leave a comment and > I'll close the issue. > > Thank you. Hi Eric: Sorry for the delay to update the status,now we have not taken the patch from Qualcomm,but I have modified the related files and tested,it's OK now,so you can close it,thanks for your support.
Flags: needinfo?(qingluo.wang)
Assignee | ||
Comment 16•11 years ago
|
||
Close this issue based on comment 15, and mark as a dup of bug 849365 based on comment 11.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 17•11 years ago
|
||
Hi, This issue has been fixed,please help to recheck it,thanks.
You need to log in
before you can comment on or make changes to this bug.
Description
•