I wanna add something else about the Windows share issue. I don't setup each box (Odroid C2) to access to Windows share, i use a SQL database to sync all devices, with advancedsettings.xml. The connection to the SQL DB is ok, I have my file list updated without problem, but i can't launch any video... Everything is ok with 8.0.2e.
Thanks !!!
Is that a screenshot or camera photo?
I have s905x and s905d device, and 4k ss are all mess up.
Greetings,
I connected with VNC and took pictures with CTRL - S.
Interface: Xonfluence.
But LE or KODI (because I'm not sure) provides SShot with a maximum resolution of 1080p.
I took these with the Tablet.
Without HDR.
With HDR.
Best regards...
Hi,
I am a S905X MXQPro+ TV box user. I use KODI for playing my music FLAC files. Music library of mine involves files with many different sampling rates (from 44.1 to 192 kHz). All version of LibreElec I have tried (7, 8, 8.2) do not play this files with sampling rates higher then 48.0 kHz. KODI activated on original Android firmware or e.g. Armbian does not show this issue.
Just tested my .flac - LE is playing all samplig rates from 44 to 192khz 16/24 bit
My Hardware is listed in signature
Thank You for Your support. Could You to specify, please, whether Your test have involved audio playing through HDMI? I have not mentioned above problems on analog and SPDIF output, only on HDMI.
Previously, the same issue I experienced using LE Generic x86 (64-bit) on Intel PC hardware platform. This problem vanished along with appearing of version 8.0.2.
Once again thank You for Your help.
Hello kszaq , I'm TVH + Kodi + TBS 6522 user and now I bought a KI Pro. My principal use is with DVB-C Annex B provider, I know is a "rare" standard but supported by your LibreELEC but with few issues.
When crazycat developed the TBS6522 support for annex B I found the some issues.
The first problem is the frontend, TVH detect my provider as ATSC-C, not DVB-C in consecuence I can't import my configuration from TVH (PC) to the KI Pro.
Second, TVH can't detect channel names.
Both problems were present in crazycat's drivers before he solve the frontend of it.
Here a log of the problem:
subscription: 0003: "scan" subscribing to mux "489MHz", w-eight: 5, adapter: "Availink avl6862 #0 : ATSC-C #0", network: "Provider ATSC-C", service: "Raw PID Subscription"
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - poll TIMEOUT
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 61 [e=Operation not permitted]
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 63 [e=Operation not permitted]
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 64 [e=Operation not permitted]
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 67 [e=Operation not permitted]
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 4385 [e=Operation not permitted]
inuxdvb: Availink avl6862 #0 : ATSC-C #0 - poll TIMEOUT
mpegts: 489MHz in Provider ATSC-C - scan complete (partial - 32/1 tables)
subscription: 0003: "scan" unsubscribing
Is possible solve it?
Thanks!
Thank You for Your support. Could You to specify, please, whether Your test have involved audio playing through HDMI?
Box is connected to Denon AVR using HDMI
Thank You so much.
Thank You so much.
Don´t use one of this creapy cheap HDMI cable
K1 Pro is S905D and Nougat. It should work.
Sorry kszaq I should be more clear.
The following are the specs:
Chip: S905D
Marshmallow 6.0.1
Board p231
Linux Version 3.14.29
1 gb Ram
8gb internal
Ethernet: 100 ? Not Sure But Guessing.
Wifi 2.4
Manufacturer: Winsat
Model: ModelCombo
I tried without a device tree. I tried the s905 device trees within spec and the K1 Pro but all freeze on the Devices Android Slash Screen.
I am pretty sure i will need to extract device tree from Android.
Outside of getting it from seller is there an ADB command i can issue ?
I cannot get LE to boot at all with the available device tree images.
When crazycat developed the TBS6522 support for annex B I found the some issues.
The first problem is the frontend, TVH detect my provider as ATSC-C, not DVB-C in consecuence I can't import my configuration from TVH (PC) to the KI Pro.
Second, TVH can't detect channel names.
Both problems were present in crazycat's drivers before he solve the frontend of it.
Is possible solve it?
Thanks!
When this is solved in a media_build release, it will be solved in my builds.
Display MoreSorry kszaq I should be more clear.
The following are the specs:
Chip: S905D
Marshmallow 6.0.1
Board p231
Linux Version 3.14.29
1 gb Ram
8gb internal
Ethernet: 100 ? Not Sure But Guessing.
Wifi 2.4
Manufacturer: Winsat
Model: ModelCombo
I tried without a device tree. I tried the s905 device trees within spec and the K1 Pro but all freeze on the Devices Android Slash Screen.
I am pretty sure i will need to extract device tree from Android.
Outside of getting it from seller is there an ADB command i can issue ?
I cannot get LE to boot at all with the available device tree images.
K1 Pro has 1Gbit Ethernet, that's probably why your box can't boot with K1 Pro device tree. You have to provide me with original device tree (or a link to firmware) so that I can prepare device tree for that board. Meanwhile you can try using one of S905X device trees - keep in mind that some of the pieces may not work, e.g. Ethernet.
Display MoreHello kszaq , I'm TVH + Kodi + TBS 6522 user and now I bought a KI Pro. My principal use is with DVB-C Annex B provider, I know is a "rare" standard but supported by your LibreELEC but with few issues.
When crazycat developed the TBS6522 support for annex B I found the some issues.
The first problem is the frontend, TVH detect my provider as ATSC-C, not DVB-C in consecuence I can't import my configuration from TVH (PC) to the KI Pro.
Second, TVH can't detect channel names.
Both problems were present in crazycat's drivers before he solve the frontend of it.
Here a log of the problem:
subscription: 0003: "scan" subscribing to mux "489MHz", w-eight: 5, adapter: "Availink avl6862 #0 : ATSC-C #0", network: "Provider ATSC-C", service: "Raw PID Subscription"
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - poll TIMEOUTlinuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 61 [e=Operation not permitted]
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 63 [e=Operation not permitted]
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 64 [e=Operation not permitted]
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 67 [e=Operation not permitted]
linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 4385 [e=Operation not permitted]
inuxdvb: Availink avl6862 #0 : ATSC-C #0 - poll TIMEOUT
mpegts: 489MHz in Provider ATSC-C - scan complete (partial - 32/1 tables)
subscription: 0003: "scan" unsubscribingIs possible solve it?
Thanks!
Tvheadend is different project, for principal issues you have to complain on tvheadend forum. But I had the same question on tvheadend forum and Jaroslav Kysela explain me: ATSC-C means DVB-C Annex B. BTW there is no standard ATSC-C, this is only introduced by tvheadend.
I am pretty sure i will need to extract device tree from Android.
Outside of getting it from seller is there an ADB command i can issue ?
Is there no root access in Android?
If so, there are several excellent root explorer & partition dumping Android apps available 
K1 Pro has 1Gbit Ethernet, that's probably why your box can't boot with K1 Pro device tree. You have to provide me with original device tree (or a link to firmware) so that I can prepare device tree for that board. Meanwhile you can try using one of S905X device trees - keep in mind that some of the pieces may not work, e.g. Ethernet.
Display MoreChip: S905D
Marshmallow 6.0.1
Board p231
Linux Version 3.14.29
1 gb Ram
8gb internal
Ethernet: 100 ? Not Sure But Guessing.
Wifi 2.4
Manufacturer: Winsat
Model: ModelCombo
Very good call on trying the S905x Device Tree for this S905D Chip.
I used (s905/8.2/device_trees/S905X) gxl_p212_1g.dtb
Tested everything , USB Ports , Ethernet , Wifi 8189, All working.
Remote Totally Inoperative.
I copied the remote.conf into .config folder , rebooted but nothing.
Not sure what you want to do in listing this S905D device tree ? I'm good with the above.
#*********************************************************************************************************
#this file is configuration for each factory remote device
# work_mode 0 :software mode 1 :hardware mode
# repeat_enable 0 :disable repeat 1 :enable repeat
#
# factory_code each device has it's unique factory code.
# pattern:custom_code(16bit)+index_code(16bit)
# examble: 0xff000001 = 0xff00(custom cod) 0001 (index)
#
# release_delay unit:ms.release will report from kernel to user layer after this period of time
# from press or repeat triggered.
#
# debug_enable 0 :debug disable 1 :debug disable
#
# SW MODE:
# bit_count how many bits in each frame
# tw_leader_act time window for leader active
# tw_bit0 time window for bit0 time.
# tw_bit1 time window for bit1 time
# tw_repeat_leader time window for repeat leader
# REG
# reg_base_gen set value for PREG_IR_DEC_BASE_GEN
# reg_control set value for PREG_IR_DEC_CONTROL
# reg_leader_act set value for PREG_IR_DEC_LEADER_ACTIVE
# reg_leader_idle set value for PREG_IR_DEC_LEADER_IDLE
# reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE
# reg_bit0_time set value for PREG_IR_DEC_BIT0_TIME
#*************************************************************************************************************
#amlogic NEC remote
work_mode = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay = 20
debug_enable = 1
fn_key_scancode = 0x03
left_key_scancode = 0x57
right_key_scancode = 0x53
up_key_scancode = 0x47
down_key_scancode = 0x4b
ok_key_scancode = 0x04
pageup_key_scancode = 0x08
pagedown_key_scancode = 0x5e
mouse_begin
0 0x57
1 0x53
2 0x47
3 0x4b
mouse_end
# WINSAT Remote keycode for Android Box
custom_begin
factory_infcode = 1
factory_code = 0xfc030001
key_begin
0x11 116 #KEYCODE_POWER
0x10 83 #KEYCODE_MUTE
0x5a 207 #KEYCODE_RED
0x07 208 #KEYCODE_GREEN
0x06 209 #KEYCODE_YELLOW
0x19 210 #KEYCODE_BLUE
0x5d 211 #KEYCODE_REC
0x5f 77 #KEYCODE_MEDIA_PLAY_PAUSE
0x17 84 #KEYCODE_MEDIA_STOP
0x0d 81 #KEYCODE_FB
0x4a 80 #KEYCODE_FF
0x44 78 #KEYCODE_MEDIA_PREVIOUS
0x12 79 #KEYCODE_MEDIA_NEXT
0x56 203 #KEYCODE_MEDIA_AUDIO_TRACK
0x16 204 #KEYCODE_TV_RADIO_SERVICE
0x55 205 #KEYCODE_TV_TELETEXT
0x42 206 #KEYCODE_TV_SUBTITLE
0x43 20 #KEYCODE_MENU
0x1a 318 #KEYCODE_FAV
0x52 17 #KEYCODE_EXIT
0x59 319 #KEYCODE_EPG
0x47 12 #KEYCODE_DPAD_UP
0x4b 13 #KEYCODE_DPAD_DOWN
0x57 14 #KEYCODE_DPAD_LEFT
0x53 15 #KEYCODE_DPAD_RIGHT
0x04 11 #KEYCODE_DPAD_CENTER
0x08 201 #KEYCODE_PAGE_UP
0x5e 202 #KEYCODE_PAGE_DOWN
0x4f 16 #KEYCODE_HOME
0x13 307 #KEYCODE_INFO
0x5b 18 #KEYCODE_VOLUME_UP
0x49 19 #KEYCODE_VOLUME_DOWN
0x1d 1 #KEYCODE_1
0x1c 2 #KEYCODE_2
0x46 3 #KEYCODE_3
0x15 4 #KEYCODE_4
0x14 5 #KEYCODE_5
0x45 6 #KEYCODE_6
0x00 7 #KEYCODE_7
0x1f 8 #KEYCODE_8
0x1b 9 #KEYCODE_9
0x1e 10 #KEYCODE_0
0x0f 250 #KEYCODE_TV_RECALL
0x4c 54 #KEYCODE_DEL
key_end
custom_end
custom_begin
factory_infcode = 2
factory_code = 0x3f800002
key_begin
0x44 116
0x0c 103
0x0e 108
0x0b 105
0x0d 106
0x11 97
#0x45 116
0xc5 133
0x14 113
0x10 15
0x12 125
0x48 102
0x52 104
0x05 109
0x89 131
0x9c 130
0x9a 120
0xcd 121
0x16 2 # 1
0x17 3 # 2
0x18 4 # 3
0x19 5 # 4
0x1a 6 # 5
0x1b 7 # 6
0x1c 8 # 7
0x1d 9 # 8
0x1e 10 # 9
0x1f 11 # 0
0x43 14 # DEL
0x42 46 # KEYCODE_RED_BUTTON == KEYCODE_C
0x41 32 # KEYCODE_YELLOW_TUTTON == KEYCODE_D
0x4d 75 # KEYCODE_BLUE_BUTTON == KEYCODE_F3
0x4e 76 # KEYCODE_GREEN_BUTTON == KEYCODE_F4
0x00 65 # KEYCODE_RECALL_BUTTON == KEYCODE_F7
0x4c 130 # KEYCODE_TTX == KEYCODE_ZOOM_IN
0x02 131 # KEYCODE_REC == KEYCODE_ZOOM_OUT
0x15 18 # KEYCODE_INFO == KEYCODE_E
0x47 119 # KEYCODE_FAV_BUTTON == KEYCODE_MEDIA_PLAY_PAUSE
0x4a 38 # KEYCODE_EPG == KEYCODE_L
0x4b 68 # KEYCODE_SUBTITLE == KEYCODE_F10
key_end
custom_endThe Android remote.conf is not compatible with the Libreelec Lirc
Follow this thread to create your own remote.conf: Create remote.conf from scratch
But please be aware that if you try to copy&paste the reference remote.conf file from this thread, it will not work since some non ANSI character are present and cause remotecfg to crash.
Instead download this one: remote.conf (I attach it also here, just remove the .txt extension)
Display MoreSorry kszaq I should be more clear.
The following are the specs:
Chip: S905D
Marshmallow 6.0.1
Board p231
Linux Version 3.14.29
1 gb Ram
8gb internal
Ethernet: 100 ? Not Sure But Guessing.
Wifi 2.4
Manufacturer: Winsat
Model: ModelCombo
I tried without a device tree. I tried the s905 device trees within spec and the K1 Pro but all freeze on the Devices Android Slash Screen.
I am pretty sure i will need to extract device tree from Android.
Outside of getting it from seller is there an ADB command i can issue ?
I cannot get LE to boot at all with the available device tree images.
Info from official site.
Best regards...
Are there any known issues with the S905D and temp sensor builds? I Flashed the regular version to my KI Pro and it occasionally hangs on the Mecool logo like builds would with the sensors enabled on my Mini MX III.
Info from official site.
Not the box I'm Testing. I've added this unknown box to my Signature.
Additionally to my C2 I bought a S905X-device (BeLink MiniMXIII II, 2GB) for 4K-HDR-support.
On both boxes I am running kszaq's LibreELEC-S905.arm-8.2-8.1.3.img.gz (with devicetree gxl_p212_2g.dtb on the MiniMXIII) and it works great so far.
There is only a problem with my Harmony remote on the MiniMXIII:
The original BeeLink-remote works out-of-the-box. But I want to use my Harmony, which works well with Lirc on the C2,
on the MininMXIII in the same way. I don't want to have an seperate Harmony-profile for the MiniMXIII.
I have enabled Lirc in LibreElec-config on both boxes.
I assume I have to create a new lirc.conf for the MiniMXII, because the IR-codes, which my Hamrmony sends are configured for the C2.
But irrecord does not work.
When I compare the C2 with MiniMXII, then there is no device /dev/lirc0 on the MiniMXIII, see below.
On the MiniMXIII there is also no lirc_dev-message as on the C2.
dmesg and processes on the C2:
Using username "root".
[email protected]'s password:
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (community): 8.1.3 (S905 arm)
LibreELEC:~ # dmesg|grep lirc
[ 13.549728@1] lirc_dev: IR Remote Control driver registered, major 231
[ 13.576276@2] rc rc0: lirc_dev: driver ir-lirc-codec (meson-ir) registered at minor = 0
[ 13.681545@0] input: lircd-uinput as /devices/virtual/input/input5
[ 14.132007@2] input: eventlircd as /devices/virtual/input/input8
LibreELEC:~ # ps|grep lirc
2488 root 0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd
2570 root 0:00 /usr/sbin/lircd --nodaemon --release /storage/.config/lircd.conf
2571 root 0:00 /usr/sbin/lircd-uinput
2794 root 0:00 {kodi.sh} /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs --lircdev /run/lirc/lircd
2818 root 0:11 /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd
2892 root 0:00 grep lirc
LibreELEC:~ # ls -l /dev/lirc*
crw------- 1 root root 231, 0 Jul 29 12:53 /dev/lirc0
LibreELEC:~ #dmesg and processes on the MiniMXIII:
Using username "root".
[email protected]'s password:
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (community): 8.1.3 (S905 arm)
LibreELEC:~ # dmesg|grep lirc
[ 14.427666@2] input: lircd-uinput as /devices/virtual/input/input3
[ 15.475733@3] input: eventlircd as /devices/virtual/input/input5
LibreELEC:~ # ps|grep lirc
2535 root 0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd
2626 root 0:00 /usr/sbin/lircd --nodaemon --release /storage/.config/lircd.conf
2628 root 0:00 /usr/sbin/lircd-uinput
2882 root 0:00 {kodi.sh} /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs --lircdev /run/lirc/lircd
2890 root 0:09 /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd
2966 root 0:00 grep lirc
LibreELEC:~ # ls -l /dev/lirc*
ls: /dev/lirc*: No such file or directory
LibreELEC:~ #Is this a problem with the devicetree on the MiniMXIII?
The device /dev/lirc0 seems not to be created on the MiniMXIII.
Is this a conflict with amremote?
Any ideas? And thanks for your help.
