Re: external bluetooth keyboard / mouse paired but not used
Il 15/07/20 10:39, deloptes ha scritto: Andrea Borgia wrote: Devices are connected and show up in logs, that is where it gets weird. Next week I'm home and I'll be able to try a physical kbd / touchpad combo. You may have a look at the X server configuration. I don't use BT inputs, but I recall there could be some additional settings in the following sections, or needed to add those. I'm sure you can find instructions. I have plugged in a dongle for a wireless keyboard (non BT) and that worked out of the box without restarting. A proper BT kbd / touchpad combo also works as expected, so the Linux configuration seems to be just fine, without any changes. I'll give feedback to the author of the app, we'll see if it can be fixed. Thanks, Andrea.
Re: external bluetooth keyboard / mouse paired but not used
Il 15/07/20 10:39, deloptes ha scritto: You may have a look at the X server configuration. I don't use BT inputs, but I recall there could be some additional settings in the following sections, or needed to add those. I'm sure you can find instructions. I don't have a server config file, only a snippet which I have added to force taptoclick for the internal touchpad. I'll try adding another one as you suggested and report back once I have also tried a real BT mouse / kbd combo. In the meanwhile, this is an excerpt from Xorg.log: [ 5691.217] (II) config/udev: Adding input device abo-motog5splus Keyboard (/dev/input/event21) [ 5691.217] (**) abo-motog5splus Keyboard: Applying InputClass "libinput keyboard catchall" [ 5691.217] (II) Using input driver 'libinput' for 'abo-motog5splus Keyboard' [ 5691.217] (**) abo-motog5splus Keyboard: always reports core events [ 5691.217] (**) Option "Device" "/dev/input/event21" [ 5691.217] (**) Option "_source" "server/udev" [ 5691.220] (II) event21 - abo-motog5splus Keyboard: is tagged by udev as: Keyboard [ 5691.220] (II) event21 - abo-motog5splus Keyboard: device is a keyboard [ 5691.221] (II) event21 - abo-motog5splus Keyboard: device removed [ 5691.237] (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:001D:1200.0009/input/input33/event21" [ 5691.237] (II) XINPUT: Adding extended input device "abo-motog5splus Keyboard" (type: KEYBOARD, id 17) [ 5691.237] (**) Option "xkb_model" "pc102" [ 5691.237] (**) Option "xkb_layout" "us" [ 5691.237] (WW) Option "xkb_variant" requires a string value [ 5691.237] (**) Option "xkb_options" "compose:ralt,terminate:ctrl_alt_bksp" [ 5691.242] (II) event21 - abo-motog5splus Keyboard: is tagged by udev as: Keyboard [ 5691.243] (II) event21 - abo-motog5splus Keyboard: device is a keyboard [ 5691.247] (II) config/udev: Adding input device abo-motog5splus Mouse (/dev/input/event22) [ 5691.247] (**) abo-motog5splus Mouse: Applying InputClass "libinput pointer catchall" [ 5691.247] (II) Using input driver 'libinput' for 'abo-motog5splus Mouse' [ 5691.247] (**) abo-motog5splus Mouse: always reports core events [ 5691.247] (**) Option "Device" "/dev/input/event22" [ 5691.247] (**) Option "_source" "server/udev" [ 5691.249] (II) event22 - abo-motog5splus Mouse: is tagged by udev as: Mouse [ 5691.250] (II) event22 - abo-motog5splus Mouse: device is a pointer [ 5691.250] (II) event22 - abo-motog5splus Mouse: device removed [ 5691.285] (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:001D:1200.0009/input/input34/event22" [ 5691.285] (II) XINPUT: Adding extended input device "abo-motog5splus Mouse" (type: MOUSE, id 18) [ 5691.290] (**) Option "AccelerationScheme" "none" [ 5691.293] (**) abo-motog5splus Mouse: (accel) selected scheme none/0 [ 5691.293] (**) abo-motog5splus Mouse: (accel) acceleration factor: 2.000 [ 5691.293] (**) abo-motog5splus Mouse: (accel) acceleration threshold: 4 [ 5691.296] (II) event22 - abo-motog5splus Mouse: is tagged by udev as: Mouse [ 5691.297] (II) event22 - abo-motog5splus Mouse: device is a pointer [ 5691.299] (II) config/udev: Adding input device abo-motog5splus Consumer Control (/dev/input/event23) [ 5691.299] (**) abo-motog5splus Consumer Control: Applying InputClass "libinput keyboard catchall" [ 5691.299] (II) Using input driver 'libinput' for 'abo-motog5splus Consumer Control' [ 5691.299] (**) abo-motog5splus Consumer Control: always reports core events [ 5691.299] (**) Option "Device" "/dev/input/event23" [ 5691.299] (**) Option "_source" "server/udev" [ 5691.301] (II) event23 - abo-motog5splus Consumer Control: is tagged by udev as: Keyboard [ 5691.301] (II) event23 - abo-motog5splus Consumer Control: device is a keyboard [ 5691.302] (II) event23 - abo-motog5splus Consumer Control: device removed [ 5691.321] (II) libinput: abo-motog5splus Consumer Control: needs a virtual subdevice [ 5691.321] (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:001D:1200.0009/input/input35/event23" [ 5691.321] (II) XINPUT: Adding extended input device "abo-motog5splus Consumer Control" (type: MOUSE, id 19) [ 5691.324] (**) Option "AccelerationScheme" "none" [ 5691.328] (**) abo-motog5splus Consumer Control: (accel) selected scheme none/0 [ 5691.328] (**) abo-motog5splus Consumer Control: (accel) acceleration factor: 2.000 [ 5691.328] (**) abo-motog5splus Consumer Control: (accel) acceleration threshold: 4 [ 5691.331] (II) event23 - abo-motog5splus Consumer Control: is tagged by udev as: Keyboard [ 5691.332] (II) event23 - abo-motog5splus Consumer Control: device is a keyboard [ 5691.334] (**) abo-motog5splus Consumer Control: Applying InputClass "libinput keyboard catchall" [ 5691.334] (II) Using input driver 'libinput' for 'abo-motog5splus Consumer Control' [ 5691.334] (**) abo-motog5splus Consumer Control: always reports core events [ 5691.334] (**) Option
Re: external bluetooth keyboard / mouse paired but not used
Andrea Borgia wrote: > Devices are connected and show up in logs, that is where it gets weird. > Next week I'm home and I'll be able to try a physical kbd / touchpad > combo. You may have a look at the X server configuration. I don't use BT inputs, but I recall there could be some additional settings in the following sections, or needed to add those. I'm sure you can find instructions. Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection
Re: external bluetooth keyboard / mouse paired but not used
Il 14/07/20 23:56, Bob Weber ha scritto: On 7/14/20 1:11 PM, Andrea Borgia wrote: I bought a bluetooth keyboard with the intention to use it with our Samsung tablets. It just worked in KDE to my surprise. Is the mouse a part of the keyboard or a separate device? It is in an app which emulates multiple devices at the same time. Also, the bt adapter is embedded in the laptop, no need to have an external adapter in my case. Have you gotten audio through to a bt device? Not my use case and at the moment I don't have a headset to test it anyway. If there no bt widget in the tray click on the up arrow to bring up the "Status and Notifications" panel and see if bt is there. If so click on bt and enable bt for the system. Devices are connected and show up in logs, that is where it gets weird. Next week I'm home and I'll be able to try a physical kbd / touchpad combo. Regards, Andrea.
Re: external bluetooth keyboard / mouse paired but not used
On 7/14/20 1:11 PM, Andrea Borgia wrote: Il 12/07/20 20:17, Andrea Borgia ha scritto: After the pairing, I can see in the logs that there are 3 new devices (keyboard, mouse, multimedia controls) as input devices but that's it: it doesn't work in parallel with the internal touchpad and keyboard. I've tried both with KDE and on console, no go. Are there any special settings I have to make? No ideas? I bought a bluetooth keyboard with the intention to use it with our Samsung tablets. It just worked in KDE to my surprise. Is the mouse a part of the keyboard or a separate device? These comments are for KDE. I use bluetooth all the time to play audio on bt headphones and through a bt gateway to my HIFI for audio. I've been able to connect a bt headphone and the bt gateway at the same time but I don't think audio worked after that until I disconnected both and then reconnected to just one. So try using just ONE bt device (like the keyboard) and see if that works. If so you may need to get another usb bt device (plugs into your computer) for the mouse. Have you gotten audio through to a bt device? Do you have the bt tray widget visible ... a bt symbol in the tray. If so then you should be able to see what is connected. Make sure only one device is connected. Some devices tend to auto connect after pairing so turn off all bt devices except the one your are testing. You might have to reboot after you are sure just one device is on. There is also an application bluetoothctl that can restart bt devices but it is just as easy to reboot. If there no bt widget in the tray click on the up arrow to bring up the "Status and Notifications" panel and see if bt is there. If so click on bt and enable bt for the system. -- *...Bob*
Re: external bluetooth keyboard / mouse paired but not used
Il 12/07/20 20:17, Andrea Borgia ha scritto: After the pairing, I can see in the logs that there are 3 new devices (keyboard, mouse, multimedia controls) as input devices but that's it: it doesn't work in parallel with the internal touchpad and keyboard. I've tried both with KDE and on console, no go. Are there any special settings I have to make? No ideas?
external bluetooth keyboard / mouse paired but not used
Hello. I'm trying to use this app on my phone to have a spare BT mouse / keyboard combo: https://play.google.com/store/apps/details?id=io.appground.blek Tested with WIndows on my laptop, it works out of the box, no special settings required beyond pairing. When running Linux on the same system, I can perform the pairing... well, actually, I have to: unless you copy the BT keys from Windows to Linux or viceversa, you'll have to anyway. After the pairing, I can see in the logs that there are 3 new devices (keyboard, mouse, multimedia controls) as input devices but that's it: it doesn't work in parallel with the internal touchpad and keyboard. I've tried both with KDE and on console, no go. Are there any special settings I have to make? Thanks, Andrea.
