[Bluetooth] [File Transfer] Try L2CAP first and then RFCOMM for outbound connection

RESOLVED WONTFIX

Status

Firefox OS
Bluetooth
RESOLVED WONTFIX
5 years ago
5 years ago

People

(Reporter: Ben Tian (inactive), Assigned: Ben Tian (inactive))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 obsolete attachment)

(Assignee)

Description

5 years ago
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

5 years ago
Component: Bluetooth → Gaia::Bluetooth File Transfer
(Assignee)

Updated

5 years ago
Component: Gaia::Bluetooth File Transfer → Bluetooth
(Assignee)

Comment 1

5 years ago
Created attachment 802134 [details] [diff] [review]
Patch 1: OPP L2CAP outbound connection

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

5 years ago
Attachment #802134 - Attachment is obsolete: true
Attachment #802134 - Flags: review?(echou)
(Assignee)

Comment 2

5 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
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Resolution: FIXED → WONTFIX
You need to log in before you can comment on or make changes to this bug.