All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Sathish Narasimman <nsathish41@gmail.com>
Cc: Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: OPP File Transfer From Settings always uses L2cap Conf as BASIC_MODE- OS: Ubuntu 18.04
Date: Thu, 14 May 2020 10:47:03 -0700	[thread overview]
Message-ID: <CABBYNZLVKHVbHXc5=uem1JtKa=eSBi=nc92eaKWgT-kCWj552Q@mail.gmail.com> (raw)
In-Reply-To: <CAOVXEJL_zq0_-KTh2HEBT1VvSCCkuwdecXLaEGFquMi30oH6Eg@mail.gmail.com>

Hi Sathish,

On Wed, May 13, 2020 at 12:14 AM Sathish Narasimman
<nsathish41@gmail.com> wrote:
>
> Hi
>
> In Ubuntu when trying to do OPP File transfer using Bluetooth settings
> the L2cap Configuration  uses BASIC_MODE
>
> whereas obexctl it is using ERTM_MODE mode.
>
> Once the initial connection made from obexctl.later any transfer of
> files from setting UI also used ERTM mode.
>
> How to change the MODE to ERTM for the transfer of file using settings?

Is ubuntu setting really using obexd? Or perhaps they are setting a
Channel on CreateSession which is then forcing to use RFCOMM instead
of L2CAP ERTM, when you use obexctl and don't set any Channel it will
attempt to discover the record using SDP and if there is an entry for
L2CAP channel it will use to connect using ERTM.

-- 
Luiz Augusto von Dentz

  reply	other threads:[~2020-05-14 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13  7:09 OPP File Transfer From Settings always uses L2cap Conf as BASIC_MODE- OS: Ubuntu 18.04 Sathish Narasimman
2020-05-14 17:47 ` Luiz Augusto von Dentz [this message]
     [not found]   ` <CAOVXEJKf5dAv5eriZf04PLABLhPU9uW5CLAnzKf8ePEJRq-GGg@mail.gmail.com>
2020-05-15 17:26     ` Luiz Augusto von Dentz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABBYNZLVKHVbHXc5=uem1JtKa=eSBi=nc92eaKWgT-kCWj552Q@mail.gmail.com' \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=nsathish41@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.