TOHKBD2 still supported or dead? [answered]
asked 2018-04-22 02:05:09 +0300
Dear sailors,
I own a TOHKBD2 and used it until the connectivity killer bug appeared. I read some long time later that the TOH issues were solved, so I searched my house for my KBD and attached it. The NFC and tohd-service successfully identified it, the EEPROM values are valid, and the TOHKBD application was downloaded and installed, BUT I cannot save any changed settings or assign any F-button shortcuts (I can choose any app to assign to that but it isn't saved, leaving me with empty F-buttons no matter what) and nothing happens when I attach the keyboard part (normally it would switch to landscape mode and light up the keyboard keys, but none of that happens now). Is this just my J1, or can the whole special-TOH chapter be considered closed? Any ideas I could try before locking the great keyboard TOH away forever?
Cheers - Lutwolf
I have one TOHKB2, which works well with my two Jolla 1 phones under SFOS 2.1.4 (and 2.1.3 before): Automatic keyboard background lighting & landscape orientation lock work fine and so does altering the settings in the TOHKBD setup app (I haven't tried assigning function keys, yet).
Initial set up of the TOHKB2 was a hassle, though (unfortunately, I forgot the details, but they are documented at various places).
BTW, I never experienced the "connectivity killer bug" (under SFOS 2.1.3 & 2.1.4), but hesitated long to install the TOHKB2 due to it, as I did not find a clear statement that it is resolved.
olf ( 2018-04-22 03:24:33 +0300 )edit