If I remember correctly, my Venz-V10 box was booting fine with the 'BOX' image (no kernel panics), but ir-remote (and keyboard?) didn't work. Original discussion (but maybe not so relevant for your issue): Venz V10 (S905L) Bring Up
Extra info: actually I don't remember is wi-fi is working (I'm using wired connection).
Extra info2: I do run LE from the microSD card toothpick method), I never succeeded running LE from USB (however I could perform stock-firmware updates from USB).
I did create a device-tree for a "Venz V10" S905L box before but the user disappeared without providing feedback so I've dropped that from my kernels.
I guess I'm that user? I do remember you gave support for creating a keymap for my Venz V10. But I cannot remember you were waiting for feedback.
Situation is that I am currently running a LE on the box, but it's not stable in seeking through video streams, and sporadically I have freezes and network-issues in Kodi-UI as well. (But I guess that's what's meant in the initial post)
edit: to get a better Wife-Acceptance-factor (read: less crashes), I doubted to go back to CE, but I couldn't find time and I'ld like to replace the complete box as well because sometimes the navigation is slow - depending on the plugins
Hello, I attached my meson-gxl-s905l-venz-v10.zip (just zipped the dtb-file) if you want to test
System:
LibreELEC (official): 11.0.3 (AMLGX.arm)
uname -a => Linux LibreELEC 6.1.38 #1 SMP PREEMPT Sat Jul 15 08:59:46 UTC 2023 aarch64 GNU/Linux
No it's the opposite, in previous images the led came on with u-boot and stayed on (during boot&kodi) untill shutdown/poweroff.
in your last image, the led goes on with u-boot, and goes off once LE/Lodi is starting/running.
in previous images the LED always went on/off correctly except in the last image where it was off while LE/Kodi was running.
I never had issues with the LED (although only the blue color was used), but since you asked if it had an LED, I also described the behavior of the stock android FW with orange/blue)
I don't know what is the expected behavior of the LED in LibreELEC, but it seems you're right that u-boot is turning the led on and now you indeed reversed the polarity of the correct gpio. State of led (while running LE) is the opposite as previous images.
Behavior with previous image:
0) power on plug PSU / or press rc-pwr-btn => LED becomes Blue
1) after 3 seconds, LED goes off (just before the LE-boot logo shows)
2a) shutdown => showing LE-logo, followed by a very short blue flash (almost every time, sometimes it's not there/visible), an LED remains off
2b) reboot => showing LE-logo, followed by a very short blue flash, next LED becomes blue and (see step 0)
Personally, I prefer the LED on while running
The LED becomes blue as soon as de device starts booting (through power-cycle or powerbutton of remote)
It goes off as soon as the box is powered off (5-10 seconds after suspend/powerbutton).
It never gets orange (except in standby with the factory android image)
Attaching keyboard after boot doesn't make any difference, nothing happens on keypresses (tried with usb-wireless and wired keyboard)
No problem for the WIFI, I'm not using it anyway, but thought it might be useful for others, you've a reasonable explanation...
For the remote, if you're that good at guessing missing parts you should start playing the lottery/casino 
LED: well, actually it behaves like all the previous images of LE/CE i've ever used (but so did all your previous testbuilds, so I don't know what changed, might be nice maybe if we could control it's color (maybe orage when pauzed, of depending of the source/bandwith/buffer-level, ...) But just like the 1/2/3 buttons, I've never used it, and I don't need it
For the keyboard, I've downloaded the .img.gz because I messed up the storage on the previous SD and wanted to have a valid test.
kernel: Linux LibreELEC 5.18.0-rc2 #1 SMP PREEMPT Fri Apr 15 01:39:19 UTC 2022 aarch64 GNU/Linux
Still no keyboard 
Another thing I noticed on your recent images is that the smb-shares are not discoverable any more.
in 'Ubuntu-Files' I could browse to 'smb://libreelec/' and saw all shared folders, this doesn't work, but I can browse to 'smb://libreelec/backup'
dmesg:
Version with working keyboard is the image I have on my disk with name: LibreELEC-AMLGX.arm-10.85.0-box.img.gz
It has modification date 2022/03/28, and matches with my download manager address: https://chewitt.libreelec.tv/testing/LibreE…85.0-box.img.gz
according to 'uname -a', it's indeed a 5.17 kernel (don't remember any more where I downloaded it from), and indeed a python 3.8.12
Linux LibreELEC 5.17.0 #1 SMP PREEMPT Wed Mar 23 10:34:38 UTC 2022 aarch64 GNU/Linux
here the keyboard works (with generic p212 dtb) (rc doesn't work).
about the remote: I've cleaned/opened it twice, first time, I was able to see some IR-flashes in a cmos camera, but never successfully could capture the code, so my remote is partially broken I guess. (I see the keymap is compiled to a .ko-file, is there a guide somewhere on how to support custom remotes, probably I can find some spare remote)
LED (Blue when on, Off when off, but that's normal to me :-)) & Wifi (not working out-of-the-box) seem to behave as previous versions
dmesg: (At line 4 I do see a kernel image misalign error)
well, CE9.2.8 worked best for multiple years, now I'm trying to find some version which works 
I can confirm the remote now works, here's a dmesg:
Do you have any link/pointer to some architecture/commands on how to get wifi configured/tested/enabled? (I don't need it, but I'm willing to do an attempt for other people)
It's also very strange I've these issues with the keyboard/remote, because I think the first LE10.85 of your images I downloaded, also had a working Keyboard and remote (I think nightly of 20220403) (I used it a couple of days but it was slow an had some flickering issues, maybe because of the restore from my CE-backup in an attempt to keep all addons/settings, I'll retry the image if I can find it)
thanks for the clear instructions. see attached for the logfile of the keypresses.
I regularly double checked while annotating, and had to insert 1 key (hence a shifted timestamp).
Also, 2 rows didn't emit any signal (double checked with the camera on my phone), this was the 3rd row (with arrows up/down/left/right), and the first row of the numeric keypad (1/2/3).
I'm pretty sure they never worked... (Edit: My kid said nr3 sometimes works after pressing lot's of other numbers, I tried shaking/pressing, and indeed I've seen some response from the device, guess I'll need to open up the remote and clean some silicone juice)
About the LED:
In Libre/CoreELEC I only ever saw the blue light while powered on, off after shutdown.
I just booted the internal android: Blue while 'On', Red while in 'Standby', Purple for a short moment while transitioning from 'Stanby to On'
Probably you're correct about the BT, cannot find it either, but I remember now I once powered an edison-board from the usb-port of this player as a BT-gateway, and I also used a wireless headset (BT+RF), but I indeed plugged the USB-RF into the player.
So probably I was wrong assuming their was BT inside...
Does this IR-keymap also impact the keyboard?
Do you recommend LibreELEC of CoreELEC? for this device? (CE19 seems to get stuck in a freeze/reboot loop, CE20 with a 'slowemmc' does seem to keep running because the ping remains stable, but I cannot get any screen on it - tried on 720p TV, and 1440p 21:9 monitor, so I cannot get it configured)
bertiera please install (or update to) https://chewitt.libreelec.tv/testing/LibreE…85.0-box.img.gz for testing. I've added a device tree specifically for the box (meson-gxl-s905l-venz-v10.dtb) which should get WiFI working at least.
Does the box have power LEDs or power buttons on the case?
Is there an IR remote for the box? If yes, what keymap is used?
The box has 1 multi-color LED (I've seen blue and orange), no power buttons, only button is a reset button in the back (for getting the device into recovery)
The box came with IR remote (media remote only no full keyboard), no idea which keymap but in a previous nigthly build/dtb combo it did work properly. (I my current CE image, I've got lots of bmap-files in /usr/lib/keymaps, do you have any idea how te see which one is in use? dmesg says "Registered IR keymap rc-empty")
Tried this image with specific dtb, however still no WiFi, and now, also the keyboard/remote is broken (at least in Kodi). only mouse (on same RF-dongle as keyboard) was working.
Also, Kodi says BT-adapter not found.
dmesg output:
LibreELEC (10.85.0) dmesg (no wifi, no BT):
CoreELEC (9.2.8) dmesg (working wifi/BT):
I gave the latest stable coreELEC (amlogic-ng) another try, but currently without success. maybe because my Venz V10 (S905L) has only 1GB RAM?
I created new sd-card and configured with the 'gxl_p212_1g.dtb'.
During first boot I saw the partition resizing, after the next reboot I once received the 'setup wizard', but the device 'froze' before I could complete setup. additional attempts to boot, seem to fail. It kind of boots, but not successfully. While booting, I get a short period of ping-replies, but soon after that it's gone again. (Maybe that's a mention/questiong for the coreELEC forum)
bertiera What WiFi chip is in the box?
Just swapped the coreELEC 9.2.8 sdcard (with working wifi and BT) in and found this in the dmesg output:
RTL871X: rtl8189es v4.3.18.4_22798.20170620
RTL871X: rtw_ndev_init(wlan0) if1 mac_addr=a0:2c:36
Meanwhile I noticed some other issue with the LE-build: there is a lot of flickering for everything which is displayed (i.e. subtitles & volume indicator) as overlay while playing some media.
Hi,
I'm using currently using a Venz V10 (not the Pro) with AMLogic S905L 1G ram. I initially used the libreElec image which was delivered by the vendor, but the the last version was LibreElec 8, so I changed to CoreElec (running from microSD).
Since it looks like they drop support for this hardware, I checked LibreElec again, an found this thread and the 'AMLGX box image'.
So far, I was able to install a recent nightly from chewitt (using the meson-gxl-s905x-p212.dtb). thanks for the great work!
I did notice the WiFi and BT-adapter cannot be detected, (they worked in coreElec) could this be due to the dtb?
