Thank you for sharing!
I think this thread may provide more info for you about the display driver that we made: OledDisplay::Init with Daisy Submodule help
And yes, the pins connected to the OLED will be slightly different between Seed (what Patch and Field are powered by) and Patch SM.
I don’t know if this directly relates to your issue, but I have heard from another community member who used the bootloader + OLED + Patch SM before (thanks Danyl!) that display init in the bootloader may cause problem with OLED. SPI displays can be very particular about resets and inits. If you didn’t properly clear the screen sometimes, it could “stay stuck”. So that’s something to look out for in your code.