Adam - K3CANMar 1
@robyn @alphapuggle I concur, but I don't think it's a matter of processing power. I believe the "fancy" UI works by essentially hijacking the Bluetooth API. In other words, the UI is not fully built into the firmware; I think it sort of sits on top and pretends to be a Bluetooth connection.
Show threadNate Metzger

@me @robyn Yup was able to track down the docs page. This is the case

> MUI functions as a client, similar to the Android and Apple apps. It runs on one core of the MCU, while the regular Meshtastic firmware runs on the other. MUI communicates with the firmware using the Client API, the same interface used by other Meshtastic clients.

> The Client API supports only one active connection at a time, which means other clients cannot be used while MUI is running. Since not all settings can be configured within MUI, you may wish to boot into Bluetooth Programming Mode or BaseUI. This frees up the API so client apps can use the Bluetooth or serial connection.

https://meshtastic.org/docs/configuration/device-uis/meshtasticui/

Meshtastic UI | Meshtastic

Meshtastic UI (MUI) is a standalone interface for supported Meshtastic devices, enabling direct interaction without requiring a phone for most functions. It runs alongside the firmware, providing messaging, mapping, and configuration tools.

Mar 1 at 7:04pmWeb
Show threadAdam - K3CANMar 1
@alphapuggle @robyn ah! Okay, so I was partially correct, at least as far as the fancy UI goes. It's not pretending to be a Bluetooth client specifically, it's just a client, which prevents the other options from working.