CoreELEC 20.1-Nexus Amlogic-ne Discussion

Amlogic-ne

Please use this thread for general CoreELEC 20.1-Nexus Amlogic-ne discussion

Before posting an error please follow these troubleshooting steps.

All good on Khadas Vim4. The results are amazing! I didn’t really find any bug yet, will keep testing.

2 Likes

everything is no issue but the same error of installation to emmc in dual boot mode w/ Android 11
any future plan or resolution to fix it out ?

thanks

As written multiple times, this will not be possible because Android data partition is encrypted.

For dual boot use µSD or USB boot media.

And this is no “issue”! This is fact…

1 Like

How do you think, any chance it will work on Vontar X4? VONTAR X4 Amlogic S905X4 Smart TV Box Android 11 4GB 128G 32GB 64GB Wifi BT AV1 media Player TVBOX 4K 1000M Set top box| | - AliExpress

Vontar X3 works just fine (19.5-Matrix version, 20 not tested yet)

Yes it will! You can get it in Europe and pay 65€ without waiting 2 months…

Apart from the fact that it is not HD Audio compatible. Indeed, it is a superb box. Very efficient for its size.

I am using an X96 Max+ Ultra S905X4 4GB RAM 100Mbps Ethernet device connected to a FHD TV directly.
I have CE-NE 20.1 nightly (20230317) installed on MicroSD with DTB sc2_s905x4_4g.dtb file.
I use it on WiFi and it connects and works nicely on 5GHz band.

Everything in my setup works correctly including VFD display, except for Bluetooth. I have the Bluetooth Service enabled in the CoreElec Services menu, but still in Bluetooth Menu it says Bluetooth Adapter is disabled.
Can you please advise how to get bluetooth working on this device, I use it for bluetooth headphones and keyboard and would be nice if this works on this device.
Please let me know what debug outputs are required and I will provide them. Looking through dmesg output I do not see any BT chipset being recognised at all.
I havent opened my device, but reviewers mention that this device has AM7256 wifi+bt chip.

It is running stock firmware X96Max_Plus_Ultra_20221026-0948 (I havent changed the firmware on the box) and can be downloaded from here

Thanks

Well that is better than
No adapter found

Make sure you are using default Estuary Skin
Set to Expert/Advanced

In CoreELEC
System/services/Bluetooth

Enable Bluetooth

Reboot to apply changes ** may not necessary
Iam creature of habit.

Then move to Bluetooth…

Happy Testing

Yes I do not use any 3rd party skin, run the default Estuary.
As mentioned above I already have Bluetooth services is enabled in the CoreElec Services menu, still in Bluetooth menu, it says disabled.



1 Like

i have the same box X96 Max+ Ultra with non working bt, which command should i use via ssh?

@Portisch already mentioned in this post that the chip used in this box does not have a linux driver for bluetooth
No solution for now until someone makes a driver for the aml-w1 chip

I am using the latest Coreelec 20.1-Nexus NE on a HK1 RBOX X4.

I normally turn the box off at the power source and turn both it and the TV on at the same time when I want to use it. I noticed that for both this and the previous version of Coreelec Nexus, when the box is powered up at the same time as the TV (and with the TV not turned on yet via remote), the TV would display a black screen with just a bright band of colour just at the top

However if I power up the TV and turn it on before I power up the coreelec box, the display is fine. In an attempt to fix this, I have done the following, none of which helps

  • In my /flash/config.ini file, I have uncommented and inserted the following line “vout=‘1080p60hz’”
  • I have added a autostart.sh file to /storage/.config/autostart.sh with the following 3 lines
  • fw_setenv hdmimode 1080p60hz
  • fw_setenv outputmode 1080p60hz
  • echo 1080p60hz > /sys/class/display/mode

The debug logs when I have booted correctly are at http://ix.io/4rLj

When the device does not display correctly, I have SSH into the device and used the “dmesg | paste” with the results in the following URL http://ix.io/4rLg

If it helps, I have tried to duplicate the debug logs and pasted here https://paste.kodi.tv/unidequgov.kodi. Both the dmesg and this paste are from the same boot up with no display

I have placed this in the coreelec release thread rather than a separate thread. Please advise if I should just start a separate thread

I know this is a minor annoyance rather than a major bug. And most people will not see this because they will not turn off the box and TV at the power source overnight

Hello ,i just make a frech install from 20.1on Beelink GT king 2 and try to make work a PS4 bluetooth controler, After bluetooth pairing and try to make work in controler settings…it not work…was it not longer suppoted in ce ? Never have problemes to make work this controller in older ce …i try with cable…not work …:thinking:

Hi @Portisch. I’ve just installed 20.1-Nexus (Stable), Amlogic-ne build.

I have a Lipa X96 X4 box and I understand that because it uses the aml-w1 chipset the internal bluetooth will not work. For some reason however, the USB bluetooth adapter I’ve been using successfully with the older 19.5/Amlogic-ng builds is not working.

lsusb results:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I do see these errors in dmesg, not sure whether it tells anything:

[  150.355551@3]  Hardware name: Amlogic (DT)
[  150.355565@3]  Workqueue: usb_hub_wq hub_event
[  150.355570@3]  Call trace:
[  150.355579@3]   dump_backtrace+0x0/0x154
[  150.355584@3]   show_stack+0x28/0x34
[  150.355591@3]   dump_stack+0xb8/0xe0
[  150.355598@3]   ___might_sleep+0x114/0x144
[  150.355603@3]   __might_sleep+0x5c/0x9c
[  150.355611@3]   lock_sock_nested+0x34/0x80
[  150.355668@3]   hci_sock_dev_event+0x17c/0x1e0 [bluetooth]
[  150.355680@3]   hci_unregister_dev+0xd0/0x360 [bluetooth]
[  150.355692@3]   btusb_disconnect+0x54/0x12c [btusb]
[  150.355698@3]   usb_unbind_interface+0x80/0x270
[  150.355705@3]   __device_release_driver+0x198/0x240
[  150.355711@3]   device_release_driver+0x34/0x50
[  150.355715@3]   bus_remove_device+0x118/0x124
[  150.355720@3]   device_del+0x15c/0x3f0
[  150.355724@3]   usb_disable_device+0xd8/0x1b0
[  150.355730@3]   usb_disconnect+0xfc/0x2ec
[  150.355734@3]   hub_event+0x820/0x15dc
[  150.355740@3]   process_one_work+0x214/0x560
[  150.355744@3]   worker_thread+0x7c/0x524
[  150.355748@3]   kthread+0x16c/0x170
[  150.355755@3]   ret_from_fork+0x10/0x20

Any ideas? I’ve tried plugging the adapter in another USB port, but no results :frowning:

Thanks for having a look!

Just to add to this: also in CoreELEC-Amlogic-ne.arm-20.1-Nexus_nightly_20230401-Generic.img.gz, my Bluetooth USB device is not detected in CoreELEC…

Hi guys

I have the same Problem on my Tox3.
I always turn off the power to my TV and TV box. As soon as I turn the power on again, the TV box starts diregtliy and the TV isn’t ready yet. This is how this error occurs. It would be nice if someone could take a closer look.
With Matrix (19.5 ng) this problem does not exist.
Otherwise everything run very stable. Big compliment to the coreelec-team.