heavyharmonies
New member
Well, after a few more hours of using the Redfly and Touch Pro, it's definitely usable via USB cable, but currently not usable at all via BlueTooth. In addition to the continuous stream of "Invalid Sequence" errors, the combination of Bluetooth and S2U2 is just not workable.
If you connect the Touch Pro to the Redfly (or a computer) via USB, S2U2 is disabled automatically (which is what you want), but when you connect via Bluetooth, S2U2 is still active, so you end up with the Redfly screen seemingly locking up, when in fact S2U2 is kicking in (in fact you can see "S2U2" in the upper left corner). S2U2 is waiting for you to swipe the screen on the Touch, but since the touchscreen is turned off when connected to the Redfly, you cannot get past the swipe screen; you have to kill the Bluetooth connection with the Redfly... lather, rinse, repeat.
In the same way that the Redfly driver knows how to disable Touchflo3D when connecting, and then re-enabling upon exit, it needs to do the same with S2U2.
If you connect the Touch Pro to the Redfly (or a computer) via USB, S2U2 is disabled automatically (which is what you want), but when you connect via Bluetooth, S2U2 is still active, so you end up with the Redfly screen seemingly locking up, when in fact S2U2 is kicking in (in fact you can see "S2U2" in the upper left corner). S2U2 is waiting for you to swipe the screen on the Touch, but since the touchscreen is turned off when connected to the Redfly, you cannot get past the swipe screen; you have to kill the Bluetooth connection with the Redfly... lather, rinse, repeat.
In the same way that the Redfly driver knows how to disable Touchflo3D when connecting, and then re-enabling upon exit, it needs to do the same with S2U2.