Okay, I'd originally chimed in on the BT issues discussion since there was overlap, but apparently the BT issue is holding all the focus there (fair) so now I'm making a discussion of my own. Th BT thread can be found HERE, for reference. I'll also copy at the bottom what I'd already posted in the other discussion, but under a spoiler to avoid a worse wall-of-text than it already is.

When using a custom config- any custom config, including a manual copy of the default files- the T4 first loses connectivity to its host (any host), refuses to stay connected for more than a minute or two, and then eventually stops responding to commands at all. This problem has persisted through 2 devices now; the original purchase and the replacement for the original purchase.

The default config is not useable for me for any duration worth mentioning nor with acceptable speed (maxing out at around 12 wpm). I've still put in almost 10 hours of practice with the default despite this, but it's clear the problems cannot be resolved through continued practice. For that much practice, I had expected to acquire at least a 1-3 wpm increase by now, but since getting to 12wpm around hour 2, there's been no such improvement. My hand size, shape, finger length, etc. simply isn't compatible with the device's default. I have mimicked a custom config for comparison (T4 in one hand, using a standard keyboard with the other to type synchronously) and even that early testing shows a starting rate of about 15wpm (with only 30 minutes of practice).

Is there an experimental firmware that might help? Is there something I can do to the config files to trick the T4 into accepting them? How do we fix this?

I'm definitely invested in seeing this product do well. Besides wanting it to work for myself, I work in tech, frequently with people with disabilities. This is an awesome concept that I'd love to share with them, but not in its current state. If I could still buy a T3, I'd be willing to do that to get a currently working product, but that doesn't seem to be an option.

- - COPIED FROM BT DISCUSSION - - -

Posted Jan 17 -

I was having a very similar issue and, as it was doing it on both Windows 11 (Asus ROG Strix) and Android version 14 (Samsung Galaxy Z Fold 6), I think we can rule out an OS issue as the most likely culprit. Twiddler 4, freshly arrived and opened yesterday, btw.

On both devices, initial connection was fine. It was paired first with the phone and was fine yesterday and today. Today, after I turned the BT on my phone off and paired the Twiddler to my computer, it worked fine with the computer. I changed config file 1 to a file downloaded from Tuner (file naming adjusted appropriately) and re-paired the Twiddler to my phone.

After which point, it began to have issues - it would not output commands, would not stay connected, could not reconnect to either device, and removing the device from the computer's list of paired devices resulted in a "driver error" displaying briefly before deletion completed. The phone simply refused to acknowledge it as a legitimate BT device even though it showed up in the list for pairing. Then it would not connect to the phone at all and would not stay connected to the computer for more than approximately 1 second before disconnecting or displaying a driver error (both resulting in the Twiddler going back into pairing mode where it still failed to connect to anything else).

While plugged in via USB, it seemed to work mostly fine but still cut out. It appeared to go to sleep mid-key stroke and refuse to wake up for several seconds before it resumed functioning. Changing the config files back to default (which I had saved as such just in case) appeared to do nothing.

I tried resetting the pairing list on the computer and phone, restarting both, clearing the BT pairing list in the Twiddler via the T14F1R command, as well as putting the device to sleep with T023 and waking it back up. Nothing worked and sometimes the Twiddler didn't respond to any kind of input at all, refusing to even wake up regardless of whether it was put to sleep with the T023 command or by timing out.

Solution? -

What does appear to have worked for me, however, and I can't say for how long since it only just worked just now, was pushing the Twiddler into Bootloader mode via "Hold T14 then press T0" and then letting it time out back to sleep. Afterwards, it woke up immediately upon clicking T0. I cleared the BT list via T14F1R, which appeared to work this time, and it promptly connected upon request to both the computer and the phone. It also appears to stay connected (so far).

I'm going to attempt to change the config file again and see if the problem reappers. Wish me luck. :-) <

Posted Jan 18 -

Well, not only did that "solution" not work for very long, but it began losing connection within the hour and has reverted to a nonfunctional state for the last 24+ hours.

In short, it appears not to turn on, charge, or connect (by usb nor BT). When plugged in, LEDs 1 & 2 are faintly visible, but only from certain angles, and there is some kind of activity beneath T0 which is not visible to the human eye but is visible in the camera on my phone (IR, maybe?). I have a video here.

No amount of button pressing, commands, or "charging" make any difference. I've tried usb-a to usb-c via 3 different computers and 2 different wall plugs, as well as usb-c to usb-c the same, without any variance in responsiveness.

At this point, I'm ready to send it back, but am undecided whether I should bother with a replacement or just get a refund. 🫤 <

Posted Jan 25 -

I agree about the config issue. I did reach out to TekGear and Tony was awesome in sending me a replacement.

Upon receiving it, I hooked it up to a PC (before ever connecting a bluetooth host), backed up all the original files, printed the version etc to a word document, and saved it all. Then I spent about a half hour just typing the alphabet over and over. It remained connected and unproblematic throughout.

While the original device was down and I was waiting to hear back, I had recreated the config file I wanted from scratch. I made sure the reserved chords were present, nothing overlapped wrong (not that it'll let you save if it does), and adjusted settings to get rid of all the mouse buttons except the left click at T0 (I don't need them for my use right now).

Then, I uploaded the new config to slot 1, disconnected from the PC, and let it reboot.

Initially, it appeared to work fine when reconnected via cable to the PC. So I switched to config1. For about 2 minutes it was also fine. Then, spontaneously, it switched two chord results? Yeah, I don't know: "a" and "q" just suddenly returned on their opposite key presses. I don't know what to tell you. I disconnected, T023'd it to sleep, woke it up, reconnected (still via cable), and it had reverted back to correct settings.

Then, a few minutes later, it stopped working entirely. No amount of button pressing, connecting, or disconnecting would allow anything to work. The PC no longer even recognized it as a storage device, so I couldn't revert the config change.

So I disconnected, T014'd into bootloader mode, let it fall back to sleep on its own, and then plugged it back in. This time, it opened the folder on the PC and I reverted all files back to their original state. Then disconnected to confirm.

It seemed to work fine after that. I finally BT connected it to my phone (the primary device I expect to use it on) and it worked fine for over an hour of practice (a full set of Tuner practice + some Monkeytype).

So, for now, as long as all you want is the default config, the device seems to operate well, including BT connection. I find that unfortunate, but I'm willing to hold out for a firmware update that I hope will resolve the problem. <

Posted Jan 26 -

I submitted an NFO via support ticket the same day the request for it was made, but haven't recieved any confirmation that they even recieved it. I figure I'll give it a week before resubmitting, unless something progresses in the meantime.

I've only used the native BT/BLE connections so far, but this does make me curious whether a dedicated dongle might help the percieved config issue. I doubt it, but still...🤔 <