T1 resets device when in 1/2/3.cfg?

datacyclist

I have another odd issue. I have my own layouts in the device, in 1,2,3.cfg. There is nothing defined in either of those layouts for when only the T1 thumb button is pressed. However, if I'm in one of those layouts and just press and release the T1 button (nothing else), the twiddler resets completely (red-green-blue LED simultaneously), loses bluetooth connection and also reverts to the default layout.

This does not happen in the default layout. Also, all chords that actually involve the T1 button work fine and do not reset anything. It's only when the button is hit all alone (which can happen accidentally).

I even tried with an empty config (except for the SYS standard buttons that get added automatically), same result.

And even if I over-define it with something else (e.g. T1 = <NumLock>, it still resets the twiddler, so the definition doesn't even get picked up).

datacyclist

Just now I saw that the definition of a chord that consists only of "T1" is not even possible in the tuner. So no chance of solving this problem on my own, I guess. And yes, it's really annoying.

Geoff

I'm seeing the same behaviour when I press T1. It would be less of an issue if the Twiddler didn't reset to the default layout every time.

datacyclist

Ah good, then it's not my configurations that cause the problem. I hope this gets picked up here -- can't be that hard to fix, but shouldn't have occurred in the first place. Even if it did keep the currently active layout, it would still reset the bluetooth and the input method and cause funny things on my android apps with changing focus and such.

datacyclist

Something that makes it slightly better: you can enable the "sticky" key for NUM (which is T1 on my device), so it doesn't reset the whole device every time you hit that button. But it has a drawback:

Variant 1:
T1 (nothing happens, device goes to NUM mode)
...type anything in NUM mode...
T1 (return to normal mode, everything fine)

Variant 2:
T1 (e.g. accidental press, goes to NUM mode)
...nothing in between, no other key presses...
T1 (to return to normal mode) --> resetting the device, as mentioned before

So that doesn't really solve the problem, but if you realise that you've accidentally hit the T1 button and are in NUM mode, you may be able to return safely to normal mode. Maybe insert a specific chord in NUM mode that does nothing.

datacyclist

Hehe, but with this sticky setting for NUM, I run into another problem: I activate the twiddler, change to the first custom config (which contains the NUM sticky setting) and then the twiddler gets stuck, I can't change configs any longer, cannot cycle through them with T04M as it's specified. I can type, though.

I had this problem before, but didn't bother to find out which of my key settings caused it, I just reverted to another CFG version. Smells even more like a firmware issue. I'm still happy to try out other things and encircle the problem, if anyone's got other ideas.

Geoff

datacyclist if you had both the time and the inclination, you could try mapping a chord to cfg rotation that doesn't require a thumb button. You could also test the other chords that require T0 to see if anything else is affected.

Tony

Please create a support ticket and include a copy of your config so we can try an replicate the issue.

Are these configs that you generated from Tuner?

datacyclist

Tony Thanks, I sent the ticket, and thanks for looking into this.

And yes, the configurations come from the tuner.