Hi All - thanks for the ping.
FYI - We're very focused on firmware revs for Bluetooth consistency related to host-side variations.
In theory, it shouldn't be our task to fix hiccups with host-side Bluetooth stack changes, But practically, we're obliged to deal with it.
The driver here is that once users get their TextBlade, they want to use it as their main keyboard. They jump across all their machines, and want that benefit of a consistent typing experience with all their hosts.
If they hit bumps with certain host configs, it gets in the way of enjoying all of what TextBlade can do for them.
The host Bluetooth hiccups aren't unique to us, but TextBlade is the only device to have all these new jump capabilities, so our users do things with 6 hosts and diverse maps that stress hosts in new ways.
We can provide certain firmware intelligence that helps fix host Bluetooth confusion. It's not simple to pull off, since there are many layers of defense needed to overcome host side confusion. But we do think it will really help eliminate most of the occasional link confusion.
Based on analysis of the most frequent requests for customer support, Bluetooth confusion is the biggest time hog. We think its important to make this as smooth as possible before we release the mass quantities.
Users really like the typing experience, so we need to harden the defenses to make sure new releases of host Bluetooth stacks don't distract. We want a great first experience, that just works, and is fun from the start.
We'll post more as we get these Bluetooth topics well settled.