Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #224711 > unrolled thread

external bluetooth keyboard / mouse paired but not used

Started byAndrea Borgia <andrea@borgia.bo.it>
First post2020-07-12 20:20 +0200
Last post2020-07-19 15:20 +0200
Articles 7 — 3 participants

Back to article view | Back to linux.debian.user


Contents

  external bluetooth keyboard / mouse paired but not used Andrea Borgia <andrea@borgia.bo.it> - 2020-07-12 20:20 +0200
    Re: external bluetooth keyboard / mouse paired but not used Andrea Borgia <andrea@borgia.bo.it> - 2020-07-14 19:20 +0200
      Re: external bluetooth keyboard / mouse paired but not used Bob Weber <bobrweber@gmail.com> - 2020-07-15 00:00 +0200
        Re: external bluetooth keyboard / mouse paired but not used Andrea Borgia <andrea@borgia.bo.it> - 2020-07-15 08:30 +0200
          Re: external bluetooth keyboard / mouse paired but not used deloptes <deloptes@gmail.com> - 2020-07-15 10:40 +0200
            Re: external bluetooth keyboard / mouse paired but not used Andrea Borgia <andrea@borgia.bo.it> - 2020-07-15 17:10 +0200
            Re: external bluetooth keyboard / mouse paired but not used Andrea Borgia <andrea@borgia.bo.it> - 2020-07-19 15:20 +0200

#224711 — external bluetooth keyboard / mouse paired but not used

FromAndrea Borgia <andrea@borgia.bo.it>
Date2020-07-12 20:20 +0200
Subjectexternal bluetooth keyboard / mouse paired but not used
Message-ID<ArOJX-6rJ-1@gated-at.bofh.it>
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.

[toc] | [next] | [standalone]


#224808

FromAndrea Borgia <andrea@borgia.bo.it>
Date2020-07-14 19:20 +0200
Message-ID<AswKZ-7Mj-13@gated-at.bofh.it>
In reply to#224711
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?

[toc] | [prev] | [next] | [standalone]


#224814

FromBob Weber <bobrweber@gmail.com>
Date2020-07-15 00:00 +0200
Message-ID<AsB7X-1MH-1@gated-at.bofh.it>
In reply to#224808

[Multipart message — attachments visible in raw view] — view raw

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*

[toc] | [prev] | [next] | [standalone]


#224824

FromAndrea Borgia <andrea@borgia.bo.it>
Date2020-07-15 08:30 +0200
Message-ID<AsJ5v-6J8-1@gated-at.bofh.it>
In reply to#224814

[Multipart message — attachments visible in raw view] — view raw

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.


[toc] | [prev] | [next] | [standalone]


#224829

Fromdeloptes <deloptes@gmail.com>
Date2020-07-15 10:40 +0200
Message-ID<AsL7k-7XH-5@gated-at.bofh.it>
In reply to#224824
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

[toc] | [prev] | [next] | [standalone]


#224855

FromAndrea Borgia <andrea@borgia.bo.it>
Date2020-07-15 17:10 +0200
Message-ID<AsRcJ-3kd-7@gated-at.bofh.it>
In reply to#224829
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 "Device" "/dev/input/event23"
[  5691.334] (**) Option "_source" "_driver/libinput"
[  5691.334] (II) libinput: abo-motog5splus Consumer Control: is a 
virtual subdevice
[  5691.334] (**) Option "config_info" 
"udev:/sys/devices/virtual/misc/uhid/0005:001D:1200.0009/input/input35/event23"
[  5691.334] (II) XINPUT: Adding extended input device "abo-motog5splus 
Consumer Control" (type: KEYBOARD, id 20)
[  5691.334] (**) Option "xkb_model" "pc102"
[  5691.334] (**) Option "xkb_layout" "us"
[  5691.334] (WW) Option "xkb_variant" requires a string value
[  5691.334] (**) Option "xkb_options" 
"compose:ralt,terminate:ctrl_alt_bksp"
[  5720.714] (II) config/udev: removing device abo-motog5splus Keyboard
[  5720.714] (II) event21 - abo-motog5splus Keyboard: device removed
[  5720.745] (II) UnloadModule: "libinput"
[  5720.762] (II) config/udev: removing device abo-motog5splus Mouse
[  5720.763] (II) event22 - abo-motog5splus Mouse: device removed
[  5720.803] (II) UnloadModule: "libinput"
[  5720.806] (II) config/udev: removing device abo-motog5splus Consumer 
Control
[  5720.815] (II) UnloadModule: "libinput"
[  5720.815] (II) config/udev: removing device abo-motog5splus Consumer 
Control
[  5720.815] (II) event23 - abo-motog5splus Consumer Control: device removed
[  5720.853] (II) UnloadModule: "libinput"


The insertion / removal events are either app startup / shutdown or the 
switching between functions.


I'll followup with new data when ready, thanks for the feedback.

[toc] | [prev] | [next] | [standalone]


#224973

FromAndrea Borgia <andrea@borgia.bo.it>
Date2020-07-19 15:20 +0200
Message-ID<Auhou-6KT-1@gated-at.bofh.it>
In reply to#224829
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.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web