What do you mean proper colors?
The colours displayed on screen were not correct … not sure how else to describe it.
That config option is there specifically to correct the problem.
I expect if you want to see the effect yourself you can change that option in your install, reboot, and see if the colours change.
Changing it back to where it is now should fix it again.
I want to know. What different in X96Air S905x3_P3 and X96Air S905x3_P2
WiFi chip seems to be the only practical difference. Its currently not working on the P3
Wifi is working here … I have no idea how well as I do not use it for streaming.
Bluetooth is not yet working.
No sound from A/V 3.5mm socket.
As I do not do UHD, HDR or HQ audio I have no information on those.
Hello,
My X96 Air 4/32 arrived. Its P3. Guides for P2 are valid for P3 as well.
I didnt bother with finding woodstick for button, I just tried Reboot to LibreELEC_v1.1_apkpure.com.apk and it works very nice.
I am happy to confirm, it boots from USB. I just used back USB port with CE nightly-ng image, + .apk for android there. Boot normally, then install app in stock Android 9, Run it, and then CE from USB booted correctly.
I will buy another USB stick to final setup, as I use my USB just for test I can confirm that in nightly ng 16.1.2020:
- BL301 injection - works (at least wake up by remote)
- IR receiver - works
- VFD works - works
- Wifi works (2.4 tested) - works
- LAN works - works
- 4K content - works
- Automatic Frame switching - works
- Boot from USB flashdrive - works, used back USB port and Android .APK method to booting CE
- Bluetooth - doesnt work
Not tested yet
- HDR content
- DVB-T2 driver for MN88973 Panasonic
- HDMI passthrough DTS(HD)/DD/Atmos
- included remote - I am using own remote.
From HW perspective, before I plugged in I look into a box, as I was worried about temperature reports here. First thing is, board is upside down (ie. heatsing on the bottom of the box). So I drilled some holes (give some air to Air), and also prepare one bigger, if I would want to add external heatsink (propably I will and put box upside down to 4 stands sticked to the “top”).
After 15minutes 1980/23,976Hz (TV) temperature is around 53°C, with heatsing a bit warm. Thats 17°C more (!!) than I am used to be with Rpi2/C2 in idle, so I maybe I will look around for some piece of allumunium I guess. Hopefully this will be just 905x3 problem, and not some issue within NG… On the 3.14 C2 Ive got 36 in idle, with Rpi2 35 idle.
Pictures for those who are interested:
Did you check if BT is working or what chip it has?
I wrote it in my post… It doesnt… I mean, I just briefly went to the sethings, turn on BT and BT page shows no device found or something like that.
Was having a re-think about using this … but IIRC the phono out has a fixed level requiring volume adjustments to be made after it.
If that is the case then it would be unsuitable for my purpose.
Can you, or anyone else confirm this?
Thanks.
Jan 20 12:03:24 Test systemd[1]: Condition check resulted in Bluetooth defaults being skipped.
Jan 20 12:03:24 Test systemd[1]: Started Bluetooth service.
Jan 20 12:03:24 Test kernel: Bluetooth: Core ver 2.22
Jan 20 12:03:24 Test kernel: Bluetooth: Starting self testing
Jan 20 12:03:24 Test kernel: Bluetooth: ECDH test passed in 13068 usecs
Jan 20 12:03:24 Test bluetoothd[4296]: Bluetooth daemon 5.50
Jan 20 12:03:24 Test kernel: Bluetooth: SMP test passed in 26 usecs
Jan 20 12:03:24 Test kernel: Bluetooth: Finished self testing
Jan 20 12:03:24 Test kernel: NET: Registered protocol family 31
Jan 20 12:03:24 Test kernel: Bluetooth: HCI device and connection manager initialized
Jan 20 12:03:24 Test kernel: Bluetooth: HCI socket layer initialized
Jan 20 12:03:24 Test kernel: Bluetooth: L2CAP socket layer initialized
Jan 20 12:03:24 Test kernel: Bluetooth: SCO socket layer initialized
Jan 20 12:03:24 Test bluetoothd[4296]: Starting SDP server
Jan 20 12:03:24 Test kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 20 12:03:24 Test kernel: Bluetooth: BNEP filters: protocol multicast
Jan 20 12:03:24 Test kernel: Bluetooth: BNEP socket layer initialized
Jan 20 12:03:24 Test dbus-daemon[3408]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop
Jan 20 12:03:24 Test bluetoothd[4296]: Bluetooth management interface 1.14 initialized
Test:~ # journalctl -xe | grep blue
Jan 20 12:08:20 Test pulseaudio[3459]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
CE shows Bluetooth adapter not found.
dmesg
journal
kodi.log
lsmod
rfkill
I would like to help devs with BT chip/driver find, but so far no other ideas…
In the CE Config System Services, disable and renable Bluetooth.
Then via ssh do
dmesg | grep -i blue
lsmod | grep -i blue
and you should get some indication of the module loaded as well as seeing the dmesg out showing BT start self testing etc.
Thats what I already done and its again in my previous post 
Unfortunatelly, I dont think this helps identify BT chip driver 
[ 1867.691018@0] Bluetooth: Core ver 2.22
[ 1867.691024@0] Bluetooth: Starting self testing
[ 1867.705412@0] Bluetooth: ECDH test passed in 14042 usecs
[ 1867.712347@3] Bluetooth: SMP test passed in 26 usecs
[ 1867.712384@3] Bluetooth: Finished self testing
[ 1867.712484@3] Bluetooth: HCI device and connection manager initialized
[ 1867.712498@3] Bluetooth: HCI socket layer initialized
[ 1867.712504@3] Bluetooth: L2CAP socket layer initialized
[ 1867.712530@3] Bluetooth: SCO socket layer initialized
[ 1867.747546@1] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1867.747551@1] Bluetooth: BNEP filters: protocol multicast
[ 1867.747566@1] Bluetooth: BNEP socket layer initializedTest:~ # lsmod | grep blue
bluetooth 446464 7 bnep
My experience is that it tracks Kodi’s volume.
Shoog
Thanks … I will look into it further so when I get the chance.
In the meantime I have ordered a couple of cheap USB audio ‘cards’ which should do the job if all else fails.
I have tested a speaker connected via USB and it functions correctly, so I am hopeful that a fairly simple solution is available.
Thanks.
CoreELEC:~ # lsmod | grep -i 88
8822cs 2703360 0
amvdec_h264 122880 0
This is what is in mine.
But we do not have firmware for it yet.
rtw8822c_fw.bin file is available out there.
ls -la /usr/lib/kernel-overlays/base/lib/firmware/rtl_bt/
shows a rtl8822cu_fw.bin but not a rtl8822c_fw.bin so I guess the firmware is not present and the BT does not work.
Also
CoreELEC:~ # udevadm info /sys/bus/sdio/devices/sdio* | grep -i driver
E: DRIVER=rtl88x2cs
CoreELEC:~ #Can you find original remote.conf file on Android system?
I am using a computer speaker to plug the 3.5mm cable to the x96 air the sound from the coreelec is not output but I using kodi from rom x96 air the sound is output,How to set up?
The 3.5 jack is not yet working.
Shoog
1 Like