Grrrrr.

[edent@mastodon.social]

@henryk aha! Thanks. For some reason, my laptop won't let me use usbmon. Trying to add it just gives
modprobe: ERROR: could not insert 'usbmon': Invalid argument

Will bash my head against the keyboard until it works

[henryk@chaos.social]

@Edent Check dmesg, there should be a more verbose kernel error. (Most likely: Your distribution did not install the module by default.)

[edent@mastodon.social]

@henryk thanks! A reboot did the trick.

[edent@mastodon.social]

Well, I've sniffed the USB connection, and I'm pretty sure I've found the individual packets which send the image to the eInk screen via NFC.

No idea how to actually decode them. So I guess I'll stick with the shitty Android app.

If anyone fancies doing some decompiling, let me know

[edent@mastodon.social]

And, yes, I got it to run DOOM!

(Obviously not. I can stream Doom to it at 2 frames per *minute*.)

[meyerweb@mastodon.social]

@Edent Bad Apple when?

[ge0rg@chaos.social]

@tswsl
The Android developer menu Bluetooth HCI snoop log will store all Bluetooth traffic (both directions, including BTLE) in a PCAP format file called btsnoop_hci.log in a model dependent location, cf. https://stackoverflow.com/a/43046823
@Edent

[edent@mastodon.social]

@ge0rg @tswsl
Ah! Perfect, thanks. I can see the packets it is sending now!

(Still don't fully understand them, but it is a start )

[ge0rg@chaos.social]

@Edent
Yeah, the BTLE layer 2 protocol isn't very exciting, and the fragmentation and indirection between UUIDs and handles doesn't make it easy to follow. You should also query the device with https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp to get a map of the UUIDs and which ones are read/write. Maybe googling the device ID will yield prior work as well.
@tswsl

[edent@mastodon.social]

@ge0rg oooh! That's useful. It shows me that the BLE isn't active until it receives an NFC message.

Thanks