English please
You can try to re-flash the original firmware for your box using the amlogic windows tool.
(Am besten versuchst Du, die originale Firmware mit dem Amlogic Windows-Tool wieder zu schreiben)
English please
You can try to re-flash the original firmware for your box using the amlogic windows tool.
(Am besten versuchst Du, die originale Firmware mit dem Amlogic Windows-Tool wieder zu schreiben)
This is most likely a setting on you router / wireless access point. Mine disallows wireless clients to connect to each other by default as a security measure.
The maker is known and the libreelec project tried contacting them (also using a native speaker). See here: [S905X] Unknown WLAN chip
I do not use one, so I cannot recommend one. Some discussion was here: Support for USB Gigabit LAN/802.11ac adapter?
There are no S905x boxes with gigabit Ethernet. The SoC does not have the capability for it. S905 has it, this is why it works with your other box.
You can use a usb adapter if 100 Mbit are not sufficient for your use case.
You can click on any user icon and see all their posts and likes. We discussed it here: [8.1.2] LibreELEC 8.2 for S905/S905X
The latest libreelec versions use a new kernel, and the setting command changed - but as I and others have already reported, it currently does not work.
The device tree from jarvis will not work with the latest builds, as those use a newer kernel version. So I recommend copying both the tar file as well as the appropriate dtb file to the "update" folder using samba and then reboot the device to apply the update.
mmpp, here's a build with the old output_rgb sysfs interface back. Initially I know you had issues with it (when the other method worked), but at this point I think it's worth trying. LibreELEC-S905.arm-8.2-devel-20170729192828-r25998-gf65b5f2.tar
Tried it this morning; sadly screen went pink after ~30 minutes of TV programme. This is my .config/autostart.sh:
echo 'rgb,8bit' > /sys/class/amhdmitx/amhdmitx0/attr
echo 1 > /sys/class/amhdmitx/amhdmitx0/output_rgb
To be sure I also issued the commands manually and waited for the pink screen to appear again.
Hm, this is getting wierd. I cannot get the image from 10th of June to run (no matter which of my downloaded dtb's I try) and all others from that time period either still show the bug or still use the old interface for forceRGB (so they are experimental releases using the older kernel).
I am now completely perplexed which image used to work. It might be that I tested one of yours and it was just a lucky coincidence that the forceRGB seemed to work at that time and then installed one of the other series and continued to use it. Dang.
mmpp , here's a rgb test build (to be set in the same way).
Sadly, it did not work. Color change is still happening sporadically. I will test the versions in my download folder to find the one that worked.
- hopefully fix RGB output switch: echo 'rgb,8bit' > /sys/class/amhdmitx/amhdmitx0/attr
Problem persists with my Philips TV and S905X box. I did not let the box sit in the main menu, but played different videos, so that there was a refresh change. Pink colour happend during video playback.
My dmesg is full of framerate calculations, but I think this is unrelated.
Looking at my download folder, I most likely used either
LibreELEC-S905.arm-8.0-devel-20170616131101-r26045-g72d22cef3.img
or
LibreELEC-S905.arm-8.0-devel-20170624124730-r26097-g7f1536977.img
before testing the newer release this month. I used the S905X quite exensively in June and am quite sure I would have noticed the problem then.
I have more time this weekend, I can try to walk back my downloads and identify the last one that worked.
Did you try playing media for refresh change after? It doesn't change or reset mode, that's up to you (when set early enough in autostart.sh, this isn't needed). Could you get a log to see if it's taking effect? dmesg | pastebinit
Checked this evening, colors changed after several files were played. Dmesg:
No the pink screen appears directly in the menu. I did not know a refresh change was needed for the setting to take effect. On the other hand, I do set it in the autostart file.
The effect is not static, it comes and goes periodically, so testing for it can be frustrating. My solution was to boot the box and just let it sit in the main menu and have a look at the TV from time to time to see if the colors have flipped. I will retest if playing a few file helps later this week (will be very busy until Friday...)
mmpp I'll fix the rgb issue in the next build (know the issue).
kszaq tried your proposed solution of reversing that commit in 8.1.1 - I just tested with my affected Philips tv set and the problem persists.
It should work in 8.1.1, commit has been reverted as advised by johngalt.
Hi, updated my S905X to the version from July 23rd, but the "pink bug" is still there.
Force RGB:
If you have an older display and needed output_rgb, please use the following instead of the old interface:
echo 'rgb,8bit' > /sys/class/amhdmitx/amhdmitx0/attr
This no longer works. I am quite sure it worked after you first implemented it.
I did not use the box for some weeks, and updated to the version 8.0.2-testing8 today. My Philips got the "pink screen" almost immediatly.