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
Not without directions as I know nothing of Android, only that it is present.
Checking things that might help with the heat generation I notice that the CPU governor is set to performance.
I would like to reduce that to interactive which should help somewhat.
I also notice that the set min frequency is nowhere near as low as it could be so would like to try reducing that also.
CoreELEC:~ # cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
1908000
CoreELEC:~ # cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
1908000
CoreELEC:~ # cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
100000
CoreELEC:~ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
100000 250000 500000 667000 1000000 1200000 1404000 1500000 1608000 1704000 1800000 1908000
My intention for testing would be the following
CoreELEC:~ # echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
CoreELEC:~ # echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
CoreELEC:~ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
500000
How is this best achieved?
I expect I can do this, at least temporarily, in an autostart file, but what would be best?
Thanks
Altering governors is generally performed in autostart.sh
Anything else would require an in depth knowledge of systemd
Shoog
1 Like
Thanks Shoog.
Well initial results are somewhat positive.
The idle temp has dropped to 48 C (from about 54 C).
So I have put it playing a UHD channel into a FHD monitor to see what happens to temp over about an hour.
From what I can observe the cur_freq is varying from 500000 to max as required. I expect this to help a lot in temps, and hopefully have no adverse effect on display.
EDIT: I played UHD onto FHD monitor and the temp hit max 63 C at times, down to 59 C. It generally sat ~61 C.
This is a considerable improvement over the 74 C previously experienced.
I dropped the lowest frequency to 100,000 but was able to discern an odd frame drop (or similar glitch) so put it to 500,000, where all seems fine. I was doubtful about the 250,000 setting, so took the prudent level. There was not a lot of difference in temp when running anyway. I have yet to check idle with 500,000 set and booted from cold.
I will apply these settings through an autostart file.
echo 500000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governoras you propably know, I talking about this topic on the NG thread (as I think it is right thing to do considering governor difference NG vs previous kernel).
I conclude similiar results as you (difference is I believe UHD vs FHD video, and I have also a bit vented box.
Compiling ng will took my old good PC 1.5-2 days, but hopefully ondemand mode would be working as good as on previous kernel.
1 Like
I’ve been playing around with this, I’ve tried the following schedules “schedutil” & “interactive”, I’ve created this autostart file that goes into the root of config
#!/bin/sh
(
#available governors - interactive performance schedutil - the default for coreelec is performance
echo 'interactive' > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
# Supported CPU frequencies 100000 250000 500000 667000 1000000 1200000 1404000 1500000 1608000 1704000 1800000 1908000
# Default min freq is 667000 Default max is 1908000
echo '667000' > /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq
echo '1908000' > /sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq
) &
It just changes the default governor from performance to interactive (as people seem to like that)… And sets min/max frequencies to the default and allows others to easily change for test etc
I’m new to linux, what do you think about “schedutil” - it seems to work okay for me?
FYI One other item that does not work on this box it that after suspend the display does not work (blank screen) but the box boots fineautostart.sh (546 Bytes)
I look forward to seeing the results of the on-demand governor.
Suspend works correctly here … pressing the power button brings it back up again.