All of
 help / color / mirror / Atom feed
From: Miguel Sancho <>
Subject: Re: BlueZ 5:50: First key sent from Ble device lost after initing bluetoothd
Date: Fri, 22 Mar 2019 12:41:47 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

I think, this behavior has to do with the fact that  Hog Report Map
needs to be requested and processed by bluetoothd in the fist
connection to the device after bluetoothd is restarted as stated here:

El jue., 21 mar. 2019 a las 10:41, Miguel Sancho
(<>) escribió:
> Hi,
> using BlueZ 5.50, I observe that if bluetoothd is re-initialized, the
> first key from a previously BLE paired device is not being processed.
> Looking into bluetoothd log, upon first key pressed in the device
> after bluetoothd re-init, bluetoothd connects to the device and
> creates the uHID device:
> bluetoothd[9023]: profiles/input/hog-lib.c:report_map_read_cb() HoG
> created uHID device
> In the second and further connections, key works fine, this is the
> only output related to HoG:
>     Line 401: bluetoothd[9023]: src/service.c:change_state() 0xd0b98:
> device profile input-hog state changed: disconnected -> connected (0)
>     Line 402: bluetoothd[9023]: plugins/policy.c:service_cb() Added
> input-hog reconnect 0
> Is this expected behavior? Can it be avoided? I wonder whether the
> uHID device can be created upon bluetoothd initialization instead of
> waiting to first connection.
> Thanks in advance
> Miguel

      reply	other threads:[~2019-03-22 11:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  9:41 BlueZ 5:50: First key sent from Ble device lost after initing bluetoothd Miguel Sancho
2019-03-22 11:41 ` Miguel Sancho [this message]

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:

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

  git send-email \
    --in-reply-to='' \ \ \

* 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.