SF8008 and Logitech K250 Bluetooth keyboard

[eastof111]

EB, using the Bluetooth devices manager to scan for the K250 keyboard and can't get it to pair. Checked with my Samsung phone and it finds the keyboard.
Do I need to install a driver for this keyboard? Using the 10-23 version.
Thanks.

 

[el bandido]

I do not know what Bluetooth does or does not do. Try OpenAtv image and see if it works in it. That will tell us something. OpenATV 8.x

 

[ArloG]

That's kind of been my interest for some time. There are many E2 installs that include an on screen keyboard. And bluetooth capable receivers. I believe the drivers for USB bt dongles are also available in plugins.
Pretty painless when you pair a bt kb and mouse in an Android (Firestick, Fire TV) and an Apple streamer. Even my Sony TV.
You get a bit of a pause after pairing and then the cursor just appears. Keyboard is usable in searches and settings, etc.
3 devices can be paired with just a flick of a switch or button push on them.
E2? Not so much. If the Linux kernel is always updating. Yet bt hid's always worked with older kernel versions. What's up with that?
Left, Right, Up., Down, OK. I mean. Why use YouTube on a receiver if you got spoiled using the other way to search and select.
Man. When pairing the kb & mouse to my Amazon stuff and Sony. Night and day. Not griping, just wondering.

 

[eastof111]

It doesn't work in ATV, but the Vix 03-21-2026 works very well. It's a nice quality, inexpensive keyboard to have by your side when renaming things and not have to punch keys on the rc.

 

[eastof111]

EB, I was going to copy the Bluetooth files from Vix to Tnap but I asked the 'copy" question in Opencode and GLM-5.3 and received an answer. Might help for future builds?

 

[el bandido]

That is garbage because the model does not seem to fully understand or grasp your question. That model has not looked at the TNAP enigma2 and the openvix enigma2. It is hallucinating. Basically that output is garbage.

---

Fix for Logitech K250 / Bluetooth keyboards not detected on TNAP 7 (SF8008)
The SF8008’s built-in Bluetooth chip was missing its firmware in the TNAP 7 image. These steps install it from the TNAP feed. A permanent fix will be in a future image update.


1. Install the Bluetooth firmware. Telnet into the receiver and enter these one line at a time:
opkg update
opkg install linux-firmware-rtl8822
ln -sf rtl_bt/rtl8822cu_fw.bin /lib/firmware/rtl8822cu_fw
ln -sf rtl_bt/rtl8822cu_config.bin /lib/firmware/rtl8822cu_config

2. Turn on Bluetooth:
hciconfig hci0 up
/etc/init.d/bluetooth start

Check that it worked:
hciconfig
You should see UP RUNNING in the output.


3. Pair the keyboard
Turn the K250 on and press its connect/pairing button.
On the receiver, go to Menu → Plugins → Bluetooth Devices Manager → Scan.
When the keyboard appears, select it and choose Connect.
Test by typing in any text field, such as the EPG search or the virtual keyboard screens.

4. Reboot and test again
Restart the receiver and check that the keyboard still works without repeating any steps.


If something doesn’t work, please post the output of:
hciconfig
ps | grep bluetoothd
dmesg | tail -30

Also say which step it stopped working at: the scan didn’t find the keyboard, it found it but wouldn’t connect, it connected but typing does nothing, or it stopped working after the reboot.

 

[eastof111]

Thanks for the clarification...... will give it a shot.

 

[eastof111]

After the scan found the keyboard but won't pair. Reboot, same thing.

login as: root
root@sf8008:~# hciconfig
hci0: Type: Primary Bus: USB
BD Address: 40:9C:A7:48:B7:0B ACL MTU: 1021:6 SCO MTU: 255:12
UP RUNNING
RX bytes:1338 acl:0 sco:0 events:82 errors:0
TX bytes:2606 acl:0 sco:0 commands:82 errors:0

root@sf8008:~# ps | grep bluetoothd
root@sf8008:~# dmesg | tail -30
[ 81.861540] vtunerc0: allocated buffer of 6768 bytes
[ 81.885704] vtunerc0: allocated buffer of 7144 bytes
[ 81.910014] vtunerc0: allocated buffer of 8460 bytes
[ 81.934129] vtunerc0: allocated buffer of 9588 bytes
[ 81.967292] [20:48:50:368 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]ort = 0 RelPortFrame 0 Failed
[ 82.006749] vtunerc0: allocated buffer of 10528 bytes
[ 82.079281] vtunerc0: allocated buffer of 10904 bytes
[ 82.103488] vtunerc0: allocated buffer of 11656 bytes
[ 82.127819] vtunerc0: allocated buffer of 12032 bytes
[ 82.151923] vtunerc0: allocated buffer of 12596 bytes
[ 82.485758] \x1b[1;32mdvb video add event 1 - 0 0 1280 720
\x1b[m
[ 82.489938] \x1b[1;32mdvb video add event 2 - 0 0 30 0
\x1b[m
[ 82.493957] \x1b[1;32mdvb video add event 16 - 0 1
\x1b[m
[ 82.539025] vtunerc0: allocated buffer of 12784 bytes
[ 82.805528] [20:48:51:207 ERROR-HI_DEMUX]MX_OsiReleaseReadData[11989]:channel 16 is not open yet or not play channel
[ 82.814980] [20:48:51:216 ERROR-HI_DEMUX]mxSharedChanCbFunc[560]:release cb data failed(0x80150018).
[ 110.148598] vtunerc0: allocated buffer of 12972 bytes
[ 151.792753] [20:50:00:198 ERROR-HI_DEMUX]MX_OsiReleaseReadData[11989]:channel 13 is not open yet or not play channel
[ 151.802193] [20:50:00:207 ERROR-HI_DEMUX]mxSharedChanCbFunc[560]:release cb data failed(0x80150018).
[ 172.820472] [20:50:21:227 ERROR-HI_DEMUX]MX_OsiReleaseReadData[11989]:channel 14 is not open yet or not play channel
[ 172.829942] [20:50:21:236 ERROR-HI_DEMUX]mxSharedChanCbFunc[560]:release cb data failed(0x80150018).
[ 191.888235] [20:50:40:296 ERROR-HI_DEMUX]MX_OsiReleaseReadData[11989]:channel 13 is not open yet or not play channel
[ 191.897687] [20:50:40:305 ERROR-HI_DEMUX]mxSharedChanCbFunc[560]:release cb data failed(0x80150018).
[ 192.928779] [20:50:41:336 ERROR-HI_DEMUX]MX_OsiReleaseReadData[11989]:channel 14 is not open yet or not play channel
[ 192.938245] [20:50:41:346 ERROR-HI_DEMUX]mxSharedChanCbFunc[560]:release cb data failed(0x80150018).
[ 213.012526] [20:51:01:421 ERROR-HI_DEMUX]MX_OsiReleaseReadData[11989]:channel 14 is not open yet or not play channel
[ 213.021964] [20:51:01:431 ERROR-HI_DEMUX]mxSharedChanCbFunc[560]:release cb data failed(0x80150018).
root@sf8008:~#

 

[el bandido]

opkg update
opkg install kernel-module-hidp

Then reboot, and straight after the reboot run:

ps | grep bluetoothd
lsmod | grep hidp

Then turn the keyboard’s pairing mode on, go to Bluetooth Devices Manager, and choose Scan → Connect.

If bluetoothd isn’t listed after the reboot, post cat /etc/image-version (or the TNAP build date) and ls /etc/rc*.d | grep -iE "blue|dbus". That shows whether your image is simply older than mine.

 

[eastof111]

Shows as connected after scanning but will not pair. Upon reboot their is nothing listed in the Bluetooth device manager.

login as: root
root@sf8008:~# cat /etc/image-version
cat: can't open '/etc/image-version': No such file or directory
root@sf8008:~# ls /etc/rc*.d | grep -iE "blue|dbus"
K20bluetooth
K20dbus-1
K20bluetooth
K20dbus-1
S02dbus-1
S20bluetooth
S02dbus-1
S20bluetooth
S02dbus-1
S20bluetooth
S02dbus-1
S20bluetooth
K20bluetooth
K20dbus-1
root@sf8008:~#

 

[eastof111]

I noticed when comparing the var/lib/bluetooth directory of Vix next to Tnap, there is a folder C0_48 in vix which is not in Tnap. Does that mean anything?

 

[el bandido]

Ahh ... Hard to tell without looking at what they did and why. Let's try a new image build that supposedly includes everything needed.

 

[el bandido]

Try the 1102 image and see if it helps. An online update may not contain everything needed.

 

[eastof111]

Still problems. Sometimes it will scan correctly and the keyboard shows up. Then while still in scan mode it will delete the keyboard from the list. Again, during the same scan mode, the keyboard will pop up again and enter a key will display. Entering the key code will sometimes be accepted and other times will not.

Reboot and the keyboard is in the list. Hit connect and the key code will popup and sometimes will be accepted most times it won't accept. Once it is accepted, the list will display as connected. Exit the devices manager and the keyboard does not work. Return to the devices manager and the keyboard is gone from the list. A rescan again and it displays on the list, the cannot pair error pops up.

Reboot again and start from scratch with the same results.

 

[eastof111]

Forgot to mention. Everything matches as in post #11, except the C0_48 is missing in the Tnap dir.

 

[eastof111]

As mentioned, some quirks still exist, but it does work when once bluetooth decides to accept the keyboard. Bluetooth is slow reacting, so patience is the word to use. Wait for a while between prompts before pressing the connect , scan, ok or exit keys. Not waiting before pressing keys will create errors.