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: https://marc.info/?l=linux-bluetooth&m=144793894016748&w=2 Regards El jue., 21 mar. 2019 a las 10:41, Miguel Sancho (<miguel.a.sancho@xxxxxxxxx>) 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
