tizianomattei

Thank you!

Hi @Gunjan Gupta, so I edited the file you mentioned with "After=...", rebooted and there was no bt running (no warning), then I put "Before=..." and rebooted again. The first time everything was ok, the second time the dialog I transcribed above popped up again and there was no bt, then third reboot was ok again.

I've rebooted again now and this time there is no bt icon in the tray and a new error dialog appears, with this content: Failed to apply network settings You might not be able to connect to the Bluetooth network via this machine Exception g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.23 was not provided by any .service files (2) Edit: now I've rebooted again and it seems there's no problem

Hi @Gunjan Gupta! I've replaced the binary you linked, then I rebooted 5 times in a row and the bluetooth was working each time, so I'm pretty sure it solved my issue. Thank you so much! Edit: I'd like to mark your post as the solution, but I can't find the button...

Hi all, I'm using an OrangePi 3 LTS with Armbian 23.11.1 bookworm current 6.1.63 xfce installed on a microsd card. Unlike some previous version I tried, now the wifi works correctly. As for the bluetooth, it works... every other time. That is, on one boot it will load, in the subsequent one it will fail, and so forth consistently. I'm not an expert, so if you need some output from some program, please tell me which. By now I can say that when it doesn't work, the bt icon in the systray doesn't appear, however if I try ps aux | grep blue* I find that obexd and blueman-applet are running. And if I launch blueman-manager I get an error dialog saying that the bluez daemon is not running, and that it probably means that no bluetooth adapter was found or that the bluetooth daemon wasn't started (I'm translating back from Italian). But, at the subsequent reboot, it works again, and over and over... I've found this post which might be related, as the issue seems similar, but it's on a different board and with a different iso, so I really don't know. Can anyone help please? Thank you Tiziano

It worked! Thank you so much! I'll mark this as solved 😃 Now, for the broken wifi... (just kidding... there are plenty of threads already about that and as of now there seem to be no solution...)

Found /sys/class/rc/rc0/ with: Name: sunxi-ir Driver: sunxi-ir Default keymap: rc-empty Input device: /dev/input/event3 LIRC device: /dev/lirc0 Attached BPF protocols: Operazione non permessa Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm Enabled kernel protocols: lirc nec bus: 25, vendor/product: 0001:0001, version: 0x0100 Repeat delay = 500 ms, repeat period = 125 ms This is ir-keytable without arguments...

SORRY, I forgot I had rebooted and lost my config. Now I've redone the last steps and ir-keytable -t gives the following: Testing events. Please, press CTRL-C to abort. 18634.316865: lirc protocol(nec): scancode = 0x41c 18634.316925: event type EV_MSC(0x04): scancode = 0x41c 18634.316925: event type EV_KEY(0x01) key_down: KEY_LEFT(0x0069) 18634.316925: event type EV_SYN(0x00). 18634.452052: event type EV_KEY(0x01) key_up: KEY_LEFT(0x0069) 18634.452052: event type EV_SYN(0x00). 18635.535743: lirc protocol(nec): scancode = 0x444 18635.535795: event type EV_MSC(0x04): scancode = 0x444 18635.535795: event type EV_KEY(0x01) key_down: KEY_UP(0x0067) 18635.535795: event type EV_SYN(0x00). 18635.668038: event type EV_KEY(0x01) key_up: KEY_UP(0x0067) 18635.668038: event type EV_SYN(0x00). 18636.345104: lirc protocol(nec): scancode = 0x448 18636.345149: event type EV_MSC(0x04): scancode = 0x448 18636.345149: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a) 18636.345149: event type EV_SYN(0x00). 18636.480079: event type EV_KEY(0x01) key_up: KEY_RIGHT(0x006a) 18636.480079: event type EV_SYN(0x00). 18637.155758: lirc protocol(nec): scancode = 0x41d 18637.155803: event type EV_MSC(0x04): scancode = 0x41d 18637.155803: event type EV_KEY(0x01) key_down: KEY_DOWN(0x006c) 18637.155803: event type EV_SYN(0x00). 18637.288043: event type EV_KEY(0x01) key_up: KEY_DOWN(0x006c) 18637.288043: event type EV_SYN(0x00). Anyway, the buttons still don't work in the desktop environment or the apps.

WRONG OUTPUTS SORRY... please refer to next post Ok, here they are. ir-keytable: Found /sys/class/rc/rc0/ with: Name: sunxi-ir Driver: sunxi-ir Default keymap: rc-empty Input device: /dev/input/event3 LIRC device: /dev/lirc0 Attached BPF protocols: Operazione non permessa Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm Enabled kernel protocols: lirc bus: 25, vendor/product: 0001:0001, version: 0x0100 Repeat delay = 500 ms, repeat period = 125 ms ir-keytable -t doesn't print anything on button pressed neither does ir-keytable -t -p nec, and it complains that it has no access to /sys/class/rc/rc0//protocols however, sudo ir-keytable -t -p nec finally gives this output while pressing the buttons: Protocols changed to nec Testing events. Please, press CTRL-C to abort. 17366.585270: lirc protocol(nec): scancode = 0x444 17366.585303: event type EV_MSC(0x04): scancode = 0x444 17366.585303: event type EV_SYN(0x00). 17368.295701: lirc protocol(nec): scancode = 0x41c 17368.295735: event type EV_MSC(0x04): scancode = 0x41c 17368.295735: event type EV_SYN(0x00). 17369.768642: lirc protocol(nec): scancode = 0x448 17369.768688: event type EV_MSC(0x04): scancode = 0x448 17369.768688: event type EV_SYN(0x00). 17371.271205: lirc protocol(nec): scancode = 0x41d 17371.271237: event type EV_MSC(0x04): scancode = 0x41d 17371.271237: event type EV_SYN(0x00). Thank you so much for helping!

For now, I've only mapped the four arrow buttons in the remote to the four arrow keys: KEY_UP, KEY_LEFT, KEY_RIGHT and KEY_DOWN. I'm in xfce. If I press the down arrow on my keyboard, the first icon in the desktop gets selected, and then I can move around using the arrow keys on the keyboard; however, pressing the arrow buttons on the remote has no effect. Similarly, if I open the applications menu, I can navigate using the arrow keys on my keyboard, while pressing the arrow buttons on the remote has no effect. This is what I mean. I suspect the applications aren't getting the events? Please tell me if you need more information, and which. Thank you

Hi all, I've just installed Armbian on my OPi3-lts and I'm trying to get the IR remote working (the iDroid included in the kit from aliexpress). I've followed this guide (from "Second attempt" on), using only the kernel driver without intalling lirc. Found out the protocol (nec), wrote the rc_keymap file mapping the key codes to the button names and everything seems to work fine, down to the last command (sudo ir-keytable -v -t -p nec), which correctly gives me the codes and the button names associated with them. Now, the guide says it's all and I should be able to use the remote as I use my keyboard, but... the desktop and the apps seem not to be aware of it, since nothing happens when I press the buttons... What am I missing? Thank you in advance