Can MDS bypass the new version of the Keyboard / Mouse bluetooth screen in the 11.3+ installer with Automaton? The old spacebar trick does not seem to work anymore. Attached is a screenshot.
After a bunch of testing it looks like it requires that it sees both a physical mouse in addition to the Automaton. I was hoping to use this headless.
I have seen this as well and have tried switching the automaton to mouse mode but that doesn’t seem to work either. I have escalated with apple and am investigating workarounds.
tim
Thank you for the reply. Please keep me posted with what you find.
1 Like
@tperfitt I figured you would like to know. A friend of mine fixed this issue for the arduino library.
NicoHood:master ← mdevaev:master
opened 08:49PM - 13 Jul 21 UTC
Using HID-Project on Mac was associated with two very big problems. This patch s… olves both - for the boot mouse and the absolute mouse. I believe these fixes could be relevant for other devices, but I have only dealt with these two.
1. When using any HID-Project mouse in Recovery Mode, Mac does can see it at the kernel level (that is, the cursor moves), but at the same time it asks connecting the mouse (which is already connected). The fact is that checking for the connected mouse is performed in a very stupid way: by searching for `USAGE(Pointer)` in the descriptors. Hardware mouse always (or almost always) have this, so adding this to the descriptor solves the problem. Details [here](https://github.com/pikvm/pikvm/issues/289) and [here](https://community.twocanoes.com/t/mds-automaton-keyboard-mouse-bluetooth-screen-in-macos-11-3/6391/3). I added this for absolute and boot mouses and it generally improves compatibility. It probably makes sense to do this for all mouses.
2. Another problem is that Apple UEFI (it uses another driver) could not work with BootMouse at all because it did not see it. It turned out that he needed a response to the `HID_HID_DESCRIPTOR_TYPE` request (which is strange, since we are already passing this descriptor in the interface). This is really part of the HID standard, and hardware mouse respond to this. Usually the BIOS and other things do not require this, but Apple UEFI turned out to be finicky.
I also added a bit of protocol and idle processing. It is better to let it be than not to be.
This patch is the result of my work with the hardware USB protocol analyzer. To understand the subtleties of Apple drivers, I compared how the Arduino behaves and how a "live" mouse works. All this is tested, of course.
thanks! I’ll check it out.
tim
