Tracking the "flash corruption" issue causing bluetooth reconnects to fail on the preonic

[obra]

I'd hoped 0.92.8 would resolve this, but it didn't.

meshtastic/Adafruit_nRF52_Arduino#1 is the same issue

[coggro]

I'm also experiencing this issue. In case it helps, I'm including the full bug report.

Describe the bug
Preonic keyboard is failing to reconnect to Bluetooth under varying circumstances, making the cause difficult to pin down.

To Reproduce

1. Connect Preonic to computer via Bluetooth.
2. Leave connected for an unknown period of time and/or put computer computer to sleep and/or restart computer, cause is currently unclear.
3. Attempt to use Preonic keyboard or reconnect to Bluetooth. Current result is that it will often fail to reconnect and the computer has to forget the device and/or the keyboard has to be restarted several times.

Expected behavior
Regardless of device sleep or extended connection, Bluetooth should easily re-pair to last connected device.

Environment (please complete the following information):

• OS: macOS
• Version: Sequoia 15.6
• Device: Keyboardio Preonic (Firmware 0.92.8+124) with 2021 MacBook Pro w/ M1 Max

Additional context
n/a

[obra]

Ok. This is a test build. You can install it by plugging in your preonic while holding in the Hyper key. you'll see a PREONICBOOT drive show up on your desktop. Drag this file onto it.

https://www.dropbox.com/scl/fi/9cr45cfglvsld3ecjhka6/Preonic-202508151955.uf2?rlkey=faj9215f82m4s2mhe7ohadtyb&dl=0

The preonic will install the firmware and then eject the "disk"

After that, run through https://shop.keyboard.io/preonic#recovery-mode

I'd love to know if this improves bluetooth reconnect issues for folks.

[jeroenleenarts]

I installed the firmware mentioned and proceeded with the factory reset. Keyboard is operational again. I'll report on any findings.

Is there any active testing I can do beyond just using the device over bluetooth?

[jeroenleenarts]

It already "dropped" off without reconnecting already. Recovery with a power cycle of the device using the power switvh did resolve it on 1st attempt.

[obra]

@jeroenleenarts Thanks so much for testing this out. After you powered it off and on, did you need to 'pair' again, or did it connect automatically after you turned the power switch off and on? When it "dropped", had the computer gone to sleep? When it failed to reconnect, did any of the LEDs light up? Next time that happens, can you test hitting Fun-2 (to switch to bluetooth slot 2) and then Fun-1 to switch back to the first slot?

…

On Sun, Aug 17, 2025 at 2:41 PM Jeroen Leenarts ***@***.***> wrote: *jeroenleenarts* left a comment (keyboardio/Kaleidoscope#1523) <#1523 (comment)> It already "dropped" off without reconnecting already. Recovery with a power cycle of the device using the power switvh did resolve it on 1st attempt. — Reply to this email directly, view it on GitHub <#1523 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALC2F7JR42BSFGSPQ3PVL3ODZJHAVCNFSM6AAAAACDQXPTA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJUGY3TAMRRHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jeroenleenarts]

I did the process of a factory reset after dragging the firmware onto the keyboard's drive.

Disconnected usb and did a fun+1 and repaired the device to my Mac, a 2024 MacBook Pro.

I went and watched some YouTube for like 2 minutes, not touching the keyboard. I wanted to search for another topic to watch. Keyboard was unresponsive.

A power cycle restored connection without a re-pair.

[jeroenleenarts]

Latest run of over an hour. No issues. I'll keep monitoring.

[ScriptingNose]

@obra
Hi Jesse,
I'm not quite sure whether I'm supposed to reply here or rather via email to [keyboard.io #20227].
Both of my preonics are running on this experimental build now. But while it partly fixes the butterfly boot animation on Bluetooth (it gets disturbed by the flickering red/blue wing signaling the BT connection now), it sadly doesn't do much connectivity wise in my case.
It enables me to use BT instead of a wired connection, but mostly acts like a USB cable:
Initial pairing ONE preonic to ONE device works and also seems to be quite stable and sturdy. The very moment I hit 'Fun-' the first one dies. Besides deleting the preonic from the first host and repairing it, I didn't find another way back to a working BT connection (powercycle, switching BT slots, switching BT on/off did not work).

The operating system on my computer is Win10, and my mobile phone runs Android 10, if that is of interest.

Please let me know if I can provide you with specific tests/details.

[obra]

@ScriptingNose Here's a great place to be discussing.

"Initial pairing ONE preonic to ONE device works and also seems to be quite stable and sturdy. The very moment I hit 'Fun-' the first one dies. "

Can you expand on the exact sequence of events you're running through here?

I think that you're saying:

• Pair the Preonic's Fun-1 slot with a computer.
• Everything works ok.
• You hit fun-2 to start to pair the preonic with a second computer.
• [Does the preonic pair successfully with that second computer?]
• You hit Fun-1 to switch back to being connected to the first computer.
• The preonic does not connect to the first computer.
  Is that right? If so, when the preonic fails to connect to the first computer the second time, what happens with the LEDs?

If that's not right, what's the full sequence of events?

[ScriptingNose]

@obra

I think that you're saying:
* Pair the Preonic's Fun-1 slot with a computer.
* Everything works ok.
* You hit fun-2 to start to pair the preonic with a second computer.

Exactly.

* [Does the preonic pair successfully with that second computer?]

Yes, pairs successfully and works as expected with the second device until next change of BT slot.

* You hit  Fun-1 to switch back to being connected to the first computer.

Yes

* The preonic does not connect to the first computer.

It does connect back to BT slot 1, upper left LED shows two flashes red and than turns blue. The first computer shows "Preonic (#1)" 'connected' - but doesn't register any keystrokes.

Same goes for afterwards switching back to slot 2 -> device shows "Preonic (#2)" 'connected' - but doesn't register any keystrokes.
While switched to BT1, the second device shows 'paired' and vice versa.

[obra]

@ScriptingNose just after you configure the preonic to be able to talk by bluetooth on device #1, if you plug it into a computer, does it switch to talking to the computer over usb? if you unplug it, does it successfully switch back to bluetooth?

[ScriptingNose]

@obra I guess I'm supposed to do these steps with no changes after my last reply?
If so, yes while switched to BT1 connecting via usb gets things working (computer shows "Preonic (#1)" as "paired" while connected via usb) and on unplugging it does get back to BT connection (computer shows "Preonic (#1)" as "connected"). Unfortunately it still doesn't register any keystrokes.
Strangely "Fun-2" got it talking to my mobile phone for once. Upon BT slot change this connection too got unresponsive.
Also repeating the whole sequence (plug-, unplug usb) didn't get BT1 or BT2 back to working state.

[vrenaville]

@obra
I have test the firmware, so far no crash, I don t have disconnection on BT , but I have a strange issue, that I have found. sometimes not everytimes, if i touch the rotary button to adjust volume on ubuntu 24.04 with i3, keys are unresponsive until I touch the rotary button again after that keyboard restart responding on keystroke.
I have switch back to official firmware and the problem was already there.

I don t know if you need more info or if I need to open an other issue