Pointing device doesn't work with Android

[ionic cape]

I recently added a Cirque trackpad to my FFKB. It's working over USB and Bluetooth with my Linux PC, and works over Bluetooth with an iPad, but when I connect it to my Android phone or tablet, the Cirque does not work, only the keyboard. I've tried forgetting and re-pairing a few times, no luck. I have an old Motorola keyboard with a pointing stick that does work with the tablet, although I think it's Bluetooth classic and not BLE.

What can I do to troubleshoot further? My guesses at this point are either that Android caches the old HID descriptor from before I added the Cirque, and it's cached in a way that just forgetting the pairing doesn't clear it. Or possibly there's something about the descriptor that Android doesn't like, but other devices can parse fine.

For reference my config is here: https://github.com/DeltaWhy/zmk-config/tree/main/config
west.yml is not correct because I've been building it locally with west build -p -b nice_nano_v2 -- -DSHIELD=ffkb_v3 -DZMK_CONFIG="/home/michael/code/zmk-config/config" -DZMK_EXTRA_MODULES="/home/michael/code/zmk-config/cirque-input-module;/home/michael/code/zmk-config/zmk-fingerpunch-keyboards;/home/michael/code/zmk-config/zmk-fingerpunch-controllers;/home/michael/code/zmk-config/zmk-fingerpunch-vik"

[potent forge]

just a wild guess... seems like that android doesn't like 16bit min-max descriptors in current PR.

[ionic cape]

hmm, is it possible to change that to test that theory?

or to look at HID descriptors from other devices to see if they also use that?

[potent forge]

hmm, no harm to change the zmk header in your copy to test the theory. it should be HID_LOGICAL_MIN8(-0x7F), iirc.

[ionic cape]

🤦 I just pulled the latest commit and now it works without changing anything else. good news I guess!

[broken dove]

if you have an iphone, would woul mind testing if cirque works on iphone via bluetooth?

[ionic cape]

I don't have an iPhone but it works on iPad.

[daring coral]

@potent forge would you recommend pairing your fork of the cirque driver with your point+scroll feature branch and vice versa wit Pete's? I've been trying to get a cirque working with this config with yesterday: https://github.com/HumanComputingInc/zmk_uno_config_cirque/blob/main/boards/shields/cirque_dev_kit/cirque_dev_kit.overlay and so far I only got it working over USB once, then it stopped working and when I try the to use it over BT it just disconnects 🫠

I'm using an nRF52840 dev kit and put together that shield with a one key matrix for easy testing

[daring coral]

For anyone looking at this in the future, I increased the BLE thread stack size to 2048 and that seemed to do the trick

[potent forge]

seems like that you already tried it.

[daring coral]

Yup, I tried both, I don't think my issues are due to firmware (though I might be wrong) and could be related to my hardware setup (nordic dk jumped to a cirque dk) sometimes the cirque doesn't start sensing until I physically disconnect the SS and DR pins from the board and perform a hard reset

[potent forge]

my personal experience teach me to not to touch it for few seconds after power up, let it finish self-calibration

[daring coral]

Very interesting....

Wondering if that can be modeled in code somehow, for me it seems like if it doesn't start correctly it just won't work until I disonnect/hard-reset