In that case unsupported means not tested and that I can't provide support. Nothing removed.
Posts by kszaq
-
-
There is no need to create 2 threads with the very same question and there's no harm in doing some reading:
HOW TO:Update LibreELEC - LibreELEC
HOW TO:Update LibreELEC - LibreELEC -
kszaq:
I take it a box that won't work after update reboot isn't a problem ?
Or is it because I did something wrong ?
The problem is that I'm not a mind reader and the only information from you is a box name which means nothing due to ever-changing hardware in the same models and that update did not work. I am preparing some fixes in update and booting process thanks to more detailed information form other users and you can hope that an updated version will work fine. -
Unfortunately I don't. I solely rely on code released to the public that anyone can find on the internet.
-
Simply don't turn the box off.
-
It's not a device tree issue. You have "SCI 9082" chip that is not supported because there are no drivers available for it.
-
It's not running LibreELEC. Contact your seller for support, we don't provide Android support here.
-
The free command says it is 775 MB total...I will always be less than 1/2GB because of RAM reserved for GPU and video decoder.
-
I have a S805 box that shows 1GB in Android and has 2x512MB RAM chips on board but in reality only 512MB of RAM works and Android firmware fakes logs and visible RAM amount. This is to show how far there factories can go to save a few $$ on RAM.
The "default" dtb contains 4 device trees: 1GB/2GB, S905/S905X. If you leave default device tree on SD card, it's bootloader that chooses device tree depending on RAM amount and device type. The most obvious sign that you have only 1GB RAM is that when you use default DTB, the u-boot picks device tree with 1GB RAM. So either you need to flash a proper firmware that initializes your 2GB properly or you have fake RAM.
-
Obviously your box has only 1GB of RAM.
-
A better solution: echo 1 > /sys/module/di/parameters/bypass_prog
This flag was set in Jarvis but I set it back to 0 because for some reason this was needed to make VC-1 playback work properly...
-
Yes, the overscan is normal and it's HW decoder bug.
-
I will check if I can reproduce and fix this but no promises.
-
Please login over SSH and execute these commands (root is the only user). After this do not reboot - open your test videos and tell us if they're Jarvis-good or still the same.
-
Yes, installtointernal wipes internal partition with user data. Running it will create a clean install.
-
You can provide a YouTube link.
-
I have no issues playing HD videos. Unless you post logs and a sample as instructed I won't be able to help.
-
You can try switching USB ports where you connect the drive you boot from and where you connect your external HDD. U-boot is told by a script to try to boot from a first USB drive but I don't know how it assigns numbers to drives, i.e. which drive is considered to be the first. Maybe switching ports can fix it.