-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Enhanced L2CAP mode to support GOEB #245
Comments
Note: I'm working on this issue and hope to have a PR soon. Feel free to assign it to me. |
FYI, we will likely soon do a bit of refactoring/cleanup in the way L2CAP is handled. I hope that won't conflict too much with your work. |
Will the interfaces to the class be changing? |
Hi, this topic is not updated since last year. Thank you for your work! |
I have a PoC prototype, but I found it's not very compatible with the original implementation, so I am still thinking how to resolve this. BTW, if you want to use GOEP, you may just use GOEP 1.1 which is based on RFCOMM. |
The refactor has completed. You may feel free to contribute. Thanks. |
For my use case, I would like to be able to use the Generic Object Exchange Profile (GOEP). According to the GOEP specification, the L2CAP channel must be configured for Enhanced Retransmission Mode:
The current l2cap implementation in Bumble only supports Basic flow/control mode and does not support Enhanced Retransmission Mode. Therefore will not support GOEP functions. Please update the l2cap implementation (and test cases) to support ERTM.
The text was updated successfully, but these errors were encountered: