CoreELEC 22.0-Piers_alpha3 Discussion

Development Development & Testing
121

Thanks for the reply; I finally found the answer on a GitHub forum. Switching to a V2xxx shortcuts skin instead of V3xxx solved the problem.

122

I am having issues on my UGOOS X4 with Youtube video audio sounding like a chipmunk. Additionally, when I select the S/PDIF output in the audio settings, it does output to it, but the menu entry (HDMI) stays the same.

Youtube plugin is the latest, and so are all the dependencies (inputadaptive, etc…).

Thanks

123

My build has been stable until the 22.0-Piers_nightly_20260616. I’m on AM9 Pro with latest Android firmware. Two different movies, both FEL, played for a while before stuttering and then crashing back into Android. Used reboot to CoreELEC to get back to Kodi side. I turned logging on afterwards and will monitor again.

124

Permanent RF-kill soft block issue on RTL8822CU USB Wi-Fi/BT combo adapter

Hardware & System

  • Device: RTL8822CU USB 2-in-1 Wi-Fi + Bluetooth dongle
  • System: CoreELEC
  • Board DTS custom modifications:
&sd_emmc_a {
	status = "disabled";
};

&aml_wifi{
	status = "okay";
	/delete-property/ wifi_pwm_conf;
	/delete-property/ pwm_config;
	/delete-property/ irq_trigger_type;
	/delete-property/ dhd_static_buf;
	/delete-property/ interrupt-gpios;
	power_on-gpios = <&gpio GPIOY_14 GPIO_ACTIVE_HIGH>; /* 5V power */
};

&aml_bt {
	status = "okay";
	/delete-property/ reset-gpios;
	/delete-property/ hostwake-gpios;
};

&pwm_ef {
	status = "disabled";
};

dmesg | grep rtl confirms the USB Bluetooth hardware, firmware and config blob load successfully:dmesg | grep rtl confirms the USB Bluetooth hardware, firmware and config blob load successfully:

[   39.437171@2]  Bluetooth: btrtl_initialize: hci0: RTL: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822
[   39.439261@1]  Bluetooth: rtl_read_rom_version: hci0: RTL: rom_version status=0 version=3
[   39.439271@1]  Bluetooth: rtl_load_file: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[   39.553318@4]  Bluetooth: rtl_load_file: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[   39.746024@3]  Bluetooth: btrtl_setup_rtl8723b: hci0: RTL: cfg_sz 6, total sz 35990
[   39.914822@0]  Bluetooth: rtl_download_firmware: hci0: RTL: fw version 0x0cc6d2e3
[   40.136997@0]  usbcore: registered new interface driver rtl88x2cu

hciconfig -a shows USB hci0 exists but stays in DOWN state:hciconfig -a shows USB hci0 exists but stays in DOWN state:

hci0:   Type: Primary  Bus: USB
        BD Address: 78:66:9D:AC:7D:65  ACL MTU: 1021:6  SCO MTU: 255:12
        DOWN 
        RX bytes:1681 acl:0 sco:0 events:183 errors:0
        TX bytes:36968 acl:0 sco:0 commands:183 errors:0
        Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: PERIPHERAL ACCEPT

hciconfig hci0 up
Can’t init device hci0: Operation not possible due to RF-kill (132)

hciconfig hci0 up
Can't init device hci0: Operation not possible due to RF-kill (132)

rfkill list output shows both bluetooth nodes are soft blocked, no hardware lock present:rfkill list output shows both bluetooth nodes are soft blocked, no hardware lock present:

0: bt-dev: bluetooth
        Soft blocked: yes
        Hard blocked: no
1: hci0: bluetooth
        Soft blocked: yes
        Hard blocked: no
2: phy0: wlan
        Soft blocked: no
        Hard blocked: no

Running these SSH commands manually unlocks Bluetooth fully, and the Kodi Bluetooth GUI works normally afterward:

rfkill unblock bluetooth
hciconfig hci0 up

I can add these lines to autostart.sh as a temporary fix, but I want to find the root cause and eliminate this RF soft block entirely instead of relying on a boot script workaround.I can add these lines to autostart.sh as a temporary fix, but I want to find the root cause and eliminate this RF soft block entirely instead of relying on a boot script workaround.I can add these lines to autostart.sh as a temporary fix, but I want to find the root cause and eliminate this RF soft block entirely instead of relying on a boot script workaround.

Is this automatic rfkill soft block triggered by my DTS device tree configuration, or some other system component/service? What steps can I take to resolve this fundamentally?

125

There are few services which do that: CoreELEC/projects/Amlogic-ce/packages/linux-drivers/amlogic/aml_bt/system.d/aml_bt.service at d4af3cf301c1310bff68b7b6b2a8a5e46c6469a4 · CoreELEC/CoreELEC · GitHub
Maybe at that time the device is not yet ready?

1 Like
126

Thanks a lot vpeter for your hint about aml_bt.service! I changed status = "okay" to status = "disabled" under the &aml_bt node in DTS, and the RF-kill soft block problem is completely resolved now. No more automatic bluetooth lock after reboot.

2 Likes
127

4 posts were merged into an existing topic: Nightly builds (NEW)

128

Continue here: CoreELEC 22.0-Piers_beta1 Discussion

Closed