Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@codecoup.pl>
To: "Gabriel A. Zorrilla" <gabriel@zorrilla.me>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: lescan stops after 10-15 minutes (bluez 5.48)
Date: Mon, 29 Jan 2018 10:16:45 +0100	[thread overview]
Message-ID: <5325267.NxmNQnImGX@ix> (raw)
In-Reply-To: <CAOwdT4=_T4zXX-S0c5h+siL9Pa2DoNAAFB+fK4gTaPqKnP5N5w@mail.gmail.com>

Hi Gabriel,

On Sunday, 28 January 2018 20:22:47 CET Gabriel A. Zorrilla wrote:
> Hello there. I'm really desperate here. I'm trying to work with BLE in
> my Pi3. When i do:
> 
> sudo hcitools lescan (with or without -duplicates) the Pi scans
> normally then stops after about 10-15 minutes.
> 
> Here I made some btmon dumps:
> without duplicates: http://termbin.com/ox3z
> with duplicates: http://termbin.com/6nnn
> 
> * Pi3
> * Raspbian with 4.9.66-v7+ kernel.
> * Embedded bluetooth.
> * Compilled bluez 5.48
> 
> Don't know what extra info you would need to diagnose this. Perhaps
> it's a common bug in the Pi3 Raspbian distro, but cant find
> information about this on the web. Been googling for a week.
> 
> I really want to make this work, so dont hesitate in asking me some
> tests and such.
> 
> Thanks and regards,

You don't want to mix using HCI directly and bluetoothd. Bluetoothd will 
interfere with you accessing controller and this is most likely what you are 
seeing.

Is there a reason for you to use hcitool lescan instead of D-Bus APIs?

-- 
pozdrawiam
Szymon Janc



  parent reply	other threads:[~2018-01-29  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28 19:22 lescan stops after 10-15 minutes (bluez 5.48) Gabriel A. Zorrilla
2018-01-28 19:44 ` Fwd: " Gabriel A. Zorrilla
     [not found]   ` <CAAu3APZCzOMRWR1fLO2LmOPBbYRfCvRUfra5O2XYvtibSwY9Tw@mail.gmail.com>
2018-01-28 22:27     ` Gabriel A. Zorrilla
2018-01-29  9:16 ` Szymon Janc [this message]
2018-01-29 13:16   ` Gabriel A. Zorrilla
2018-01-30  0:52     ` Gabriel A. Zorrilla
2018-01-30  7:22     ` Szymon Janc

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=5325267.NxmNQnImGX@ix \
    --to=szymon.janc@codecoup.pl \
    --cc=gabriel@zorrilla.me \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox