LE injects/adds some additional bits into the boot flow but if those files are not found the box should default to Android. If you've used "install2internal" then you may have removed/overwritten some of the Android partitions. Amlogic (Android) ".img" files are normally for use with Amlogic Burning Tool and the USB OTG port not the Android on-box/OTA recovery process, so I'd try flashing with that first. Google will find you a few thousand HOWTO articles and the binaries if you're not familiar with it - it's not really an LE topic we handle. Forums like 4pda are probably more helpful.
Posts by chewitt
-
-
Starting over should not be needed, but when faced with a weird/old TV that's not playing ball and someone with a much upgraded config (and thus likely hoarding unknown bits of old config) .. a clean install eliminates some guesswork and reduces the number of variables involved.
RPi boots using code (that cannot be changed) in the chip. This boots firmware on the SD card which reads EDID data from HDMI, which boots Linux, which reads EDID data from HDMI, which boots Kodi, which reads EDID data from HDMI.
RPi boots from an SD card. So just use a different card to test with LE12 and then the existing setup isn't touched. You don't need a Linux machine to create a bootable SD card (even lowly Windows can manage it, and we have an app to make it simple).
-
Unless it has an nVidia GPU (which is unlikely, Chromeboxes are normally Intel) .. use normal (non-legacy) Generic.
-
Do you think I'm right in believing that an external dongle using an RTL8188 chip should be supported?
It's not the fastest chip, but for connectivity and fiddling it should work fine.
I can't explain the need to connect HDMI after boot. It's not something I've seen with any of my own test devices.
For kicks, update to https://chewitt.libreelec.tv/testing/LibreE…ch64-12.0.0.tar. It's unlikely to change anything but you never know what magic newer kernels and such might bring.
The remote can be gotten working with: https://wiki.libreelec.tv/configuration/…ration-advanced
-
Will be posible to do the same command in Liberelec linux? or automatic clean up in the next reboot?
In short, no, because the tool to do that, i.e. fsck.ntfs doesn't exist.
-
Spaces are legal but will need to be correctly quoted everywhere else things break. If you want an easier life, avoid naming devices and shares with spaces.
-
Not planned. LE is a deliberately simple media client/player OS for Kodi, not a general purpose distro.
If you want to run other apps, we support Docker or Podman containers.
If you want to run other OS, use a general purpose distro like Ubuntu not LE.
-
i noticed that 12.0.0 is out on git as a new branch.
LE 12.0.0 is tagged but there is no "libreelec-12.0" release branch yet (so we can still change/retag things if needed).
The two main rules to avoid git conflict problems are:
a) Fork our repo to your own GitHub account then clone from your repo (not ours).
b) Always work in a topic branch, never work in the master branch.
If you cloned our sources directly from our repo you can always fork it online then reset/change the 'origin' location in your local clone of the repo to be your fork (edit .git/config and change the URL). If you are working in the master branch you can simply checkout a new 'mychanges' branch from master, then you can add an 'upstream' remote, pull changes from upstream/master and then hard reset your local master branch to match upstream/master. Your local changes are still be in the 'mychanges' branch and now you can rebase against the (updated) local master branch before rebuilding an updated image. The process might initially sound complicated and there's some terminology to become familiar with, but it's just a new finger-habit to learn.
Have a read here: https://wiki.libreelec.tv/development/git-tutorial
-
If you ask or solicit opinions you will find a huge number of people who want it, a moderate number who offer to be "testers" for it, and nobody who's prepared to roll up their sleeves and do the actual work. Features like a browser are not wished into existence.
-
Ozone isn't new, it's been around for some years already and nobody took the bait, so I wouldn't hold breath.
-
It often takes a few weeks for all the Skins to be updated for the final release. Looks like this is one of them. You'll probably find an update ormore status info in the Eminence add-on support thread in the Kodi forum.
-
It's possible to disable UART output in (u-boot) software even if the hardware is correctly wired. It's a little unusual to see that done, but some vendors do more customisation than others. Those chips don't run hot so I wouldn't be too afraid of pulling the heatsink off for a look.
-
There are issues in the codec drivers that cause memory (buffer) starvation. Repeated plays using the same codec eventually hit the problem. Swapping between codecs seems to cause them faster. It's nothing specific to S912 and impacts all chips.
I'm told LibreComputer plan further work on the codecs (resuming where last years effort/funding stopped) but that all depends on sales revenues to provide funding, info from Amlogic, and availability of commercial developer resources. It's a large piece of work to line up, so no breath holding.
-
EDID capture fakes the presence of the TV so LE/Kodi boots and sees an HDMI connection when the TV is turned off. It does nothing more. It is not a magic cure for old TVs with weird resolutions. Ignore those guides/articles.
Start over with a clean LE12b2 install (newer kernel/drivers and RPi firmware than LE11).
If needed you can force the initial boot splash to 16:9 using "video=HDMI-A-1:1280x720M@60" in cmdline.txt but once Kodi runs it auto-switches based on available resolutions (determined from EDID data) so this does not force Kodi to a specific resolution.
XML
Display More<?xml version="1.0" encoding="utf-8" ?> <settings version="1"> <section id="system"> <category id="display"> <group id="1"> <setting id="videoscreen.screenmode"> <visible>true</visible> <default>0128000720060.00000pstd</default> </setting> <setting id="videoscreen.limitguisize"> <visible>true</visible> <default>3</default> </setting> </group> </category> </section> </settings>Creating /storage/.kodi/userdata/advancedsettings.xml with that ^ content may work to force the initial resolution. If the resolution is not available in the EDID data, it won't work. Start with standard 1280x720 resolution. If the 1360x768 resolution is 1080i it will not work as Kodi only outputs progressive and thus filters/ignores all interlaced modes.
-
The IP address makes sense, since that’s the address for the device, but I wasn’t sure how the 445 came into play. How does that need to be formatted if you’re trying to mount it using the sudo mount -t cifs command?
You only need to specify port details when a non-standard port for the protocol is used. LE shares SMB/CIFS on default ports so nothing is needed.
-
The answer lies under the silver heatsink, but if the 512MB RAM sticker is correct we won't support the board even if it can boot something. All recent LE images need 1GB to run Kodi properly.
-
-
I shipped mine to HiassofT some time ago so I'm out of the Slice game.
