Connecting to Bluetooth classic keyboards

[tockdev]

Originally Posted by Ruinemacil

Hi everyone! ace_bt_cli gets stuck here:




Any ideas?

I had similar output on my first try and I figured out it was because it's a BLE keyboard. I had to use another one.

[tockdev]

Originally Posted by tockdev

Hello.

I followed the instructions, and (I guess) paired by keyboard.

But now, while still in ace_bt_cli, every time I press any key on my keyboard, it shows:
"ACEBTCLI aceBtCli_aclStateChangedCallback() status:0 addr:22:66:08:C2:08:36 state:0, transport:0, reason:0
ACEBTCLI CLI callback : profile_state_callback() addr: 22:66:08:C2:08:36 profile:PROFILE_INPUT_DEVICE stateISCONNECTED
ACEBTCLI aceBtCli_aclStateChangedCallback() status:0 addr:22:66:08:C2:08:36 state:1, transport:0, reason:22"
22:66:08:C2:08:36 is my keyboard MAC address.

When I run the first step from debugging spoiler, it shows 0 connected devices.

What do I do to solve this? I have a Kindle Colorsoft with 5.18.6.

Sorry I don't have editing rights because I'm pretty new at MobileRead, so I have to reply to my own post.

I did "udevadm trigger" and it showed up in ace_bt_cli "connectedlist" and in Kindle interface.

But the typing doesn't work.

Debugging steps:
1. Shows up in "connectedlist".
2. /dev/uhid is owned by group bluetoot (LMAO).
3. "I: Bus=0005 Vendor=04e8 Product=7021 Version=0001
N: Name="BT3.0 Keyboard"
P: Phys=
S: Sysfs=/devices/virtual/misc/uhid/0005:04E8:7021.0002/input/input5
U: Uniq=36:08:C2:08:66:22
H: Handlers=sysrq leds event3 ktch
B: PROP=0
B: EV=12001f
B: KEY=3f 307ff 0 0 0 0 483ffff 17aff32d bfd44446 0 0 1 130ff3 8b17d007 ffff7bfa d9415fff ffbeffdf ffefffff ffffffff fffffffe
B: REL=1040
B: ABS=1 0
B: MSC=10
B: LED=1f

I: Bus=0005 Vendor=04e8 Product=7021 Version=0001
N: Name="BT3.0 Keyboard Mouse"
P: Phys=
S: Sysfs=/devices/virtual/misc/uhid/0005:04E8:7021.0002/input/input6
U: Uniq=36:08:C2:08:66:22
H; Handlers=event4 ktch
B: PROP=0
B: EV=17
B: KEY ff0000 0 0 0 0 0 0 0 0
B: REL=1943
B: MSC=10"
4. Events appear perfectly when I press keys.

/tmp/x.err has a line that says:
"feature=button,property=keypad.fsr,error=22, failed to get int"
Then a bunch of lines like: "W: awesome: xerror:370: X error: request=GrabKey, error=BadValue"
And after that bunch of lines another bunch of lines like this: "W: awesome: xerror:370: X error: request=(null), error=(null)"

No "ace" or permutations of my MAC address in /var/logs/messages.

There's a lot of stuff appearing in "udevadm monitor" when connecting the keyboard. Do I have to list it all here?
You say that there should be "IS_INPUT" and "IS_INPUT_KEY" set to 1 in there.
Is that what our dev_is_keyboard.sh script should set? Because the script you have in the first post echo-es "ID_INPUT" and "ID_INPUT_KEY". ID, not IS. Is that right?
But just in case I left the ID echo-s and added IS variants. It didn't help but the "udevadm info ..." Command still doesn't list "IS_INPUT".

...I guess I messed even more. I tried to unpair the device and then pair it again. But it didn't work and now it doesn't even connect...

[tockdev]

Another edit: IT INALLY WORKED!!! I'm typing this message right now on the keyboard.

Strange, big f letter isn't typing here in the browser. It's fine tho.

All I had to do to get it to type was to reboot! That's crazy. Wait, I actually did more. I added this to the second line to the udev rule:
"..., ENV{IS_INPUT}="1", ENV{IS_INPUT_KEY}="1""

I hope it can help to someone else with the same problem.

[tockdev]

Another addition.
Now it connects showing error message about generating a report (the resulting report files are starting with audiomgrd), types for some time, and then KTerm I was typing in closes and it stops typing.
Maybe the thing that helped at first was the reboot and its broken now again BECAUSE i added these ENV{…} parts.
Ima try now.