Closed
Bug 911138
Opened 12 years ago
Closed 12 years ago
[Bluetooth] [File Transfer] Try L2CAP first and then RFCOMM for outbound connection
Categories
(Firefox OS Graveyard :: Bluetooth, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ben.tian, Assigned: ben.tian)
Details
Attachments
(1 obsolete file)
L2CAP connection has faster transfer speed than RFCOMM one but not all OPP devices support L2CAP connection, so current b2g OPP implements only RFCOMM outbound connection. We should try L2CAP connection first and then RFCOMM one to cover both transfer speed and compatibility.
|
Assignee | |
Updated•12 years ago
|
Component: Bluetooth → Gaia::Bluetooth File Transfer
|
|
Assignee | |
Updated•12 years ago
|
Component: Gaia::Bluetooth File Transfer → Bluetooth
|
|
Assignee | |
Comment 1•12 years ago
|
||
Changes
- add a parameter in GetServiceChannel() function to indicate L2CAP channel
- for OPP manager outbound connection, get L2CAP channel first and then RFCOMM channel if no L2CAP channel exists
- fix some warnings
Attachment #802134 -
Flags: review?(echou)
|
|
Assignee | |
Updated•12 years ago
|
Attachment #802134 -
Attachment is obsolete: true
Attachment #802134 -
Flags: review?(echou)
|
|
Assignee | |
Comment 2•12 years ago
|
||
After testing we found l2cap and rfcomm sockets have similar speed limited by the max MTU size of l2cap, so we'd like to keep current rfcomm-only outbound connection.
Mark as resolved.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•12 years ago
|
Resolution: FIXED → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•