Strange: got touch event, but current tool is not set! Defaulting to pen.

[Eeems]

Jan 10 03:13:39 reMarkable folly[26962]: Strange: got touch event, but current tool is not set! Defaulting to pen.
Jan 10 03:13:39 reMarkable folly[26962]: render-loop gesture=5.583µs update=88.081µs render_first=43.874µs render_full=2.458µs refresh=11.125µs

I'm getting this error when attempting to use folly in an in-progress version of Oxide. Handwritten input is then never processed. This version uses a ld preload library to handle input and framebuffer interaction, such that oxide has full control over if any events are being sent to the application. It also resolves two applications drawing on the screen at the same time by giving each application their own virtual window to draw to.

I must be missing something that the code is expecting while reconstituting events, but it's not entirely clear to me what I'm missing, as based on what the event code does, it should be providing everything the evdev spec requires, including specifying BTN_TOOL_PEN: https://github.com/Eeems-Org/oxide/blob/5e64f3d96835443b2b94b17e090925daf1f9d736/shared/preload/main.cpp#L400-L516

I haven't had time yet to look into folly's code to determine why it would be operating under the assumption that BTN_TOOL_PEN hasn't been sent. I would appreciate any pointers into what could be happening, and if it's something I'm missing in the preload logic, or something not being handled quite right with folly.

[Eeems]

This also appears to be an issue in sill, I'm guessing they are both using the same armrest library for handling pen input?