Somehow, the Avov remote for the box only makes red lights flash on my RCA LED TV and does nothing. I tried pressing a few buttons, but it didn't work.
It will happen in the log, and I would specifically expect these lines:
kernel: remote: Wrong custom code is 0xHEXACODEPlease follow my instructions, because without it we will only run unnecessary loops and will not make any progress in solving the problem.
I also need help with the remote control configuration for the box's remote to configure.
If the image was successfully booted on the box, please press a few buttons on the remote control, then run the pastekodi command via SSH and copy the generated link here.
the 4th one, philips small remote control
Certainly not, because Philips does not use NEC code. If you actually tried that, I'm not surprised it didn't work at all.
I also found out that this TV box had an Amlogic S805 SoC, which would be perfect for a LibreELEC Legacy v9.2 build.
It may work, although you will probably have to find the remote control configuration or make it a new one yourself.
First try to boot from SD card, using the toothpick method. You can find the description in the opening post of this topic.
today I try my 4 remote control by remote.conf, and get root cause why some remote no event in log
It's nice that you suddenly show 4 remote controls here, but which one is the one whose code I tried to implement for you under amremote?
This results in segfaults, likely glibc incompatibility? Is docker supported for minix x8h-plus? As that's basically the only thing I need on it (tailscale+homeassistant+zigbee; it was previously working before updating it after a ~year)
You guessed it perfectly well:
Due to the switch to GLIBC v2.34, all binary addons have been rebuilt. The main version of the add-ons has been changed from v9.2.0 to v9.2.1, so after the system update, the binary add-ons will also be updated. In addition, the default transfer protocol in the repository has also changed from HTTP to HTTPS.
All addons should update automatically, but it seems that your system attempted to query the repo hash file before your network connection was established. At least, this is evidenced by the fact that the RTC date still shows 2019 at that time, because the NTP sync did not occur either.
2019-04-11 16:29:01.220 T:2891973376 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 16:29:01.221 T:2891973376 ERROR: CCurlFile::Open failed with code 0 for https://libreelec.dtech.hu/packages/9.2.1/S8X2/arm/addons.xml.gz.sha256:
2019-04-11 16:29:01.221 T:2891973376 ERROR: Open - failed to open source <https://libreelec.dtech.hu/packages/9.2.1/S8X2/arm/addons.xml.gz.sha256>
2019-04-11 16:29:01.221 T:2883580672 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 16:29:01.221 T:2891973376 ERROR: CRepository: failed read 'https://libreelec.dtech.hu/packages/9.2.1/S8X2/arm/addons.xml.gz.sha256'You can manually trigger the repo update: Settings -> Add-ons -> Install from repository and select the LibreELEC Add-ons repository, and after pressing the menu button, select the Check for updates option.
After that, the updates will appear and all binary addon versions should have a 9.2.1 version prefix.
Is there a sticky / walkthrough for how I upload this device from its current version (6.0) to the latest available?
Now I'm in a bit of a dilemma because from the information I found, the T8 Plus is equipped with the S812 SoC, and the T8 Plus 2 is the one with the S912. So which one do you have?
Edit: I assume that you really have a T8Plus-2 with S912, since Android 6 was not released for the previous model.
The opening post of this topic contains all the important information, from which I have highlighted the installation part. Otherwise, I highly recommend reading the entire post.
- Create bootable media (SD card or USB flash drive):
To create bootable media you need to download the LibreELEC-AML USB-SD Creator tool. Select the file you want to download and click the Download button, or click the Select file button and browse the previously downloaded disk image (*.img.gz).- Boot LibreELEC from your previously prepared bootable media:
If you want to boot the device from your bootable media, you need to perform the toothpick method first:
Disconnect the power plug, insert the prepared boot media, and then press and hold the reset button. Reconnect the power jack while holding down the reset button, then release it after about 3-5 seconds*.
* If the Android recovery menu appeared, you pressed the button for too long.
The RESET (Restore) button is on the right side of this box, near the WiFi antenna, based on the photos I found.
This would be good because it loads the config, but according to the log you didn't press any button on your remote.
Now I don't see the most important thing, because if there was a problem with the config, there should be a line like this:
kernel: remote: Wrong custom code is 0xHEXACODESo I need a pastekodi that also shows the event that occurs when the buttons are pressed.
Sorry, but without this information I can't do much.
try many methods got from google, and found that, evey "key map editor" also cannot response with key event, as if there have some thing block IR remote control code
Please answer the question I asked: I created remote.conf for you a week ago, did you try it? If not, please do that first.
And if it doesn't work, please run a pastekodi and copy the generated link in your answer. Thanks.
A week after my last reply and the holidays, I would like to ask that you managed to try the remote control config I posted?
You didn't interpret the description correctly, so the factory_code is not correct either.
I made a new one based on the remote code above, please try it:
#amlogic NEC remote
factory_code = 0x9f000001
work_mode = 0
repeat_enable = 1
repeat_delay = 40
repeat_peroid = 39
release_delay = 121
debug_enable = 1
key_begin
0x57 116 # Power
0x43 103 # Up
0x06 105 # Left
0x0e 106 # Right
0x0a 108 # Down
0x47 172 # Homescreen
0x16 46 # Menu
0x02 28 # Enter
0x4f 14 # Backspace
0xff 115 # Volume +
0x5d 114 # Volume -
0x8a 113 # Mute
key_endThis file should be copied to /storage/.config/remote.conf.
when I try to config remote, it report following error:
LibreELEC:~ # ir-keytable
/sys/class/rc/: No such file or directory
No devices foundhow to fix it ?
In my images meson-ir is not supported, only amremote, so all you need is the appropriate remote.conf file.
If you could identify what box you have, I could help you find the correct remote control config.
Well no voltage error in your case but are you using LibreELEC-WeTek_Play_2.arm-9.2.8.18.img.gz or LibreELEC-Generic_S905.arm-9.2.8.18.img.gz with gxbb_p200_2G_wetek_play_2.dtb is it same thing ?
Since it is not DVB-S, there is no LNB to be powered (13-18V DC), so there is obviously no such problem with this tuner. Regardless, there is a 5V DC output for possible antenna signal amplifiers, but for terrestrial signal reception (DVB-T/T2) a passive antenna is basically sufficient, and for cable TV (DVB-C) this is not even necessary.
For WP2, I strongly recommend using the WP2 image, because it is optimized for it (different boot method, remote control codes, kernel drivers, etc.), and between the base modules, only this one contains the wetekdvb driver.
The abdroid box os uses kernel 3.14.29 so drivers should be compatible but I have no idea how to proceed.
I extracted your stock ROM image with AMLogicTools and unfortunately the driver is not included as a module, so it is impossible to extract and use it from its original environment.
If you have access to the wetek play 2 it has a built in DVB-S2 tuner you don't need LNB to be connected to the tuner ...
No, WeTek Play 2 has a removable tuner, mine has DVB-T2/C and I don't have a DVB-S/S2 modular tuner for it at all.
WP2:~ # dvb-fe-tool -a 0 --verbose
Found dvb demux device: dvb0.demux0
path: /dev/dvb/adapter0/demux0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.demux0
bus addr: platform:dvb.50
Found dvb demux device: dvb0.demux1
path: /dev/dvb/adapter0/demux1
sysfs path: /sys/devices/dvb.50/dvb/dvb0.demux1
bus addr: platform:dvb.50
Found dvb demux device: dvb0.demux2
path: /dev/dvb/adapter0/demux2
sysfs path: /sys/devices/dvb.50/dvb/dvb0.demux2
bus addr: platform:dvb.50
Found dvb dvr device: dvb0.dvr0
path: /dev/dvb/adapter0/dvr0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.dvr0
bus addr: platform:dvb.50
Found dvb dvr device: dvb0.dvr1
path: /dev/dvb/adapter0/dvr1
sysfs path: /sys/devices/dvb.50/dvb/dvb0.dvr1
bus addr: platform:dvb.50
Found dvb dvr device: dvb0.dvr2
path: /dev/dvb/adapter0/dvr2
sysfs path: /sys/devices/dvb.50/dvb/dvb0.dvr2
bus addr: platform:dvb.50
Found dvb frontend device: dvb0.frontend0
path: /dev/dvb/adapter0/frontend0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.frontend0
bus addr: platform:dvb.50
Found dvb net device: dvb0.net0
path: /dev/dvb/adapter0/net0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.net0
bus addr: platform:dvb.50
Found dvb net device: dvb0.net1
path: /dev/dvb/adapter0/net1
sysfs path: /sys/devices/dvb.50/dvb/dvb0.net1
bus addr: platform:dvb.50
Found dvb net device: dvb0.net2
path: /dev/dvb/adapter0/net2
sysfs path: /sys/devices/dvb.50/dvb/dvb0.net2
bus addr: platform:dvb.50
Selected dvb frontend device: dvb0.frontend0
path: /dev/dvb/adapter0/frontend0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.frontend0
bus addr: platform:dvb.50
Device Sony CXD2837ER DVB-T/T2/C demodulator (/dev/dvb/adapter0/frontend0) capabilities:
CAN_2G_MODULATION
CAN_FEC_1_2
CAN_FEC_2_3
CAN_FEC_3_4
CAN_FEC_5_6
CAN_FEC_7_8
CAN_FEC_AUTO
CAN_GUARD_INTERVAL_AUTO
CAN_HIERARCHY_AUTO
CAN_INVERSION_AUTO
CAN_MUTE_TS
CAN_QAM_16
CAN_QAM_32
CAN_QAM_64
CAN_QAM_128
CAN_QAM_256
CAN_QAM_AUTO
CAN_QPSK
CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.11, Current v5 delivery system: DVBT
Supported delivery systems:
[DVBT]
DVBT2
DVBC/ANNEX_A1. If it was built with kernel 3.14, it might work. But generally, its stability is questionable due to the different build environment.
2. What do you mean on "generic build"? The Availink drivers are tightly built into the Amlogic BSP kernels, so it's unlikely that they could be easily ported to the mainline kernel.
I was hoping that the driver would be able to start the demod chip like the WP2, but it seems that the WP2 dtb doesn't have a dvbfe entry because all the necessary parameters are fixed in the driver. (This is just a suspicion, not confirmed.)
However, if the above is true, then the driver is not truly universal, but only works with the WeTek factory wiring solution, and not with a different configuration. This is too deep water for me, unfortunately I am not that knowledgeable, I am mostly just experimenting. Unfortunately, I do not have any DVB-S capable accessories, neither LNB nor dish.
I think I will give up at this point, I'm just guessing blindly due to the lack of devices. 
Really sorry about the confusion — here is the exact S905D DTB pulled directly from the OS :
I compared it and the modified parts are the same, only the order of the lines was different. I'm afraid that the dvbfe section contains a misleading configuration, so I modified the dtb again based on a different approach. If this doesn't get us any closer to the solution, then I have no more ideas for now.
I modified it a bit based on the original Android device tree, please try the attached file.
The dvb-latest and crazycat_aml only load the AVL6211 demodulator driver if ...
I don't see any of them active:
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: setup base modules
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/base/lib/modules/3.14.29
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: added firmware from /usr/lib/kernel-overlays/base/lib/firmware
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: adding overlays from /storage/.cache/kernel-overlays
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: done
Apr 11 16:28:37 LibreELEC systemd[1]: kernel-overlays.service: Succeeded.Please enable one of them, because only avl6862 is present among the base modules in the Generic_S905 image.