Closed
Bug 1066235
Opened 10 years ago
Closed 10 years ago
v2.1 BT issues
Categories
(Firefox OS Graveyard :: Bluetooth, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1065999
People
(Reporter: bhargavg1, Unassigned)
References
Details
(Whiteboard: [caf priority: p2][CR 716068])
I am seeing issues with BT operation after migrating to v2.1 Wondering are there any known issues, some of the issues i see are, - Not all the times its listing the devices which i keep in discovery mode - By default the Turn visibility is on (not sure if this was a UX decision) - When I try to connect to the device the remote side gives an indication that the device is connected but dont see anything on the phone. The bluedroid code is from, https://www.codeaurora.org/cgit/quic/la/platform/external/bluetooth/bluedroid/log/?h=LNX.LF.3.5.1_RB1.2
[Blocking Requested - why for this release]:
Blocks: CAF-v2.1-FC-metabug
blocking-b2g: --- → 2.1?
(In reply to bhargavg1 from comment #0) > I am seeing issues with BT operation after migrating to v2.1 > > Wondering are there any known issues, some of the issues i see are, > > - Not all the times its listing the devices which i keep in discovery mode > - By default the Turn visibility is on (not sure if this was a UX decision) > - When I try to connect to the device the remote side gives an indication > that the device is connected but dont see anything on the phone. > > The bluedroid code is from, > https://www.codeaurora.org/cgit/quic/la/platform/external/bluetooth/ > bluedroid/log/?h=LNX.LF.3.5.1_RB1.2 Is bug 1065999 on your radar?
Flags: needinfo?(bhargavg1)
Depends on: 1065999
(In reply to Shawn Huang [:shawnjohnjr] from comment #2) > (In reply to bhargavg1 from comment #0) > > I am seeing issues with BT operation after migrating to v2.1 > > > > Wondering are there any known issues, some of the issues i see are, > > > > - Not all the times its listing the devices which i keep in discovery mode > > - By default the Turn visibility is on (not sure if this was a UX decision) > > - When I try to connect to the device the remote side gives an indication > > that the device is connected but dont see anything on the phone. > > > > The bluedroid code is from, > > https://www.codeaurora.org/cgit/quic/la/platform/external/bluetooth/ > > bluedroid/log/?h=LNX.LF.3.5.1_RB1.2 > Is bug 1065999 on your radar? sorry havent seen that let me check this. Is this something new you are seeing or was there all along
Flags: needinfo?(bhargavg1)
Updated•10 years ago
|
Whiteboard: [CR 716068] → [caf priority: p2][CR 716068]
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
(In reply to bhargavg1 from comment #0) > I am seeing issues with BT operation after migrating to v2.1 > > Wondering are there any known issues, some of the issues i see are, > > - By default the Turn visibility is on (not sure if this was a UX decision) bug 989704, it's a Settings bug. So bug 989704 shall go 2.1 blocker.
Depends on: 989704
Comment 6•10 years ago
|
||
Bug 1065999 isn't a blocker and this was marked as a dupe of that so I'm removing the nom here.
blocking-b2g: 2.1? → ---
(In reply to Shawn Huang [:shawnjohnjr] from comment #5) > (In reply to bhargavg1 from comment #0) > > I am seeing issues with BT operation after migrating to v2.1 > > > > Wondering are there any known issues, some of the issues i see are, > > > > - By default the Turn visibility is on (not sure if this was a UX decision) > bug 989704, it's a Settings bug. So bug 989704 shall go 2.1 blocker. Sorry bug 989704 is different bug. I will open another bug for it.
(In reply to bhargavg1 from comment #0) > I am seeing issues with BT operation after migrating to v2.1 > > Wondering are there any known issues, some of the issues i see are, > > - Not all the times its listing the devices which i keep in discovery mode > - By default the Turn visibility is on (not sure if this was a UX decision) FYI, Visibility bug had been fixed in bug 1069868.
Updated•10 years ago
|
No longer blocks: CAF-v2.1-FC-metabug
You need to log in
before you can comment on or make changes to this bug.
Description
•