I ask my question on programmers because:

  • no coding is really involved
  • this question is very conceptual concerning an exchange protocol.

Bit of context:

When you implement Bluetooth, like I do, you have to choose between multiple protocols, such as L2CAP and RFCOMM.

RFCOMM relies on L2CAP protocol.


Are there devices/applications out there that can be RFCOMM only (and only this, not supporting L2CAP exchanges)?

  • RFCOMM is build on top of L2CAP, how can there be RFCOMM without L2CAP?
    – yannis
    Commented Feb 6, 2016 at 16:03
  • This is exactly the point of my question: is it possible to restrict an app on that subset or not? I will not implement RFCOMM because I have very good l2cap implementation already. Will I have issues with my bluetooth experience if I totally bypass RFCOMM implementation?
    – Larry
    Commented Feb 6, 2016 at 16:06
  • I am okay with a downvote, but, more positively, the user could also have commented/answered that question. That could have lead to some fruitful thinking.
    – Larry
    Commented Feb 6, 2016 at 17:43
  • 1
    I don't think you should lose sleep over a single downvote.
    – yannis
    Commented Feb 6, 2016 at 18:24

1 Answer 1


If your intent is to communicate with smartphones, forget about that. Just use rfcomm as l2cap sockets are forbidden/locked down most of the time.

Otherwise, if you control the machines (which are not smartphones) do whatever you feel is best.

Even if you find some -older- smartphones accepting L2CAP sockets, it is definitely not a good strategy to rely on "luck" basically.

  • Thanks Amy. So I will use rfcomm for a broader audience.
    – Larry
    Commented Feb 6, 2016 at 19:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.