blueribb, perhaps you could write guide? even if you do a basic it guide, it would help. Place under a new thread, so it doesn't get lost in this one.
Although I have a windows 10 pc. I use nfs to the storage on my nas.
blueribb, perhaps you could write guide? even if you do a basic it guide, it would help. Place under a new thread, so it doesn't get lost in this one.
Although I have a windows 10 pc. I use nfs to the storage on my nas.
Hello, I successfully install libreElec on my S912 KM8 Pro. So far so good. I'm using a small 2GB USB drive. I have noticed that the movie and tv database scanning takes forever (compared to all my other devices that I have run Kodi on in the past) . Curious if this is normal on a S912 or if there something I can do to speed up the scan. (Scanning my movie and tv files on my ubuntu server smb sharing. Few hundred movies taking hours to build the Kodi database).
My S912 scans ok. I'm suprised 2GB is big enough. I would, have a direct network connection to the server, wifi might be too slow.
I have an MECOOL M8S Pro+ with bad eMMC memory, and made an stupid mistake to try to upgrade the Android firmware
I already got an refund so it's not a big problem.
I am trying to revive the box, so I can run this LibreELEC build from microSD, but I can't flash an full factory image. Mainly the system partition is problematic, because it has an large size it corrupts easily on my box. So I am trying to flash only the basic partitions to my box to boot LibreELEC.
An amlogic image has several partitions, but I am not sure which ones are needed to succesfully boot LibreELEC from microSD? I think the bootloader + recovery partitions are needed? But maybe also the boot (kernel) partition? Or does the bootloader also check if the system partition is OK?
And also if it boots where does it save the setting that it keeps on auto booting from microSD?
I don't know about bootloaders, but you have nothing to lose, by burning an image to sd, with the correct device tree, & then try it.
After the first boot, (use reset button) it should always boot the sd card first.
Yes, i have the same ‘issue’ here using another backend (dvblogic).
In my case, it takes a couple of retries installing (like you described), after which it is correctly installed.
To avoid this error on reboot i had to set a dhcp reserved address to be assigned (vs static ip) AND set kodi to wait for network ( for 5 seconds). This works around it nicely.
Good luck.
Not sure if this is relevant, I had problems with my tvheadend on my NUC. I uninstalled the backend, & client, rebooted, then ran the addon kcleaner. I was then able to install tvh again.
Failing that, try deleting the pvr files via ssh. (I use ftpcore lite)
disable LIRC in the libreelec configuration to cure the remote problem
What kind of info are you looking for and/or which kind of problem are you trying to solve?
In general: if you use a typical x86 HTPC box with an integrated IR receiver (like eg a NUC) and an original (or 100% compatible) Microsoft MCE remote it will work out of the box.
so long,
Hias
Mine didn't (too many button presses) running a Harmony 350 on a nuc, it worked before the update 17.5. under thread on the kodi forum, that suggested changing the settings in the harmony software, but that didn't work.
Then after disabling LIRC, it works fine.
with the sd card plugged in, ssh in, installtointernal some devices you need to do it twice.
8.2.0.1 scheduled for upload. I will update the changelog later today. Please update your device trees with this release as it would allow the new feature - automatic device tree update - to work for the future builds.
But, ksaq, says there are new device trees, I think I'll wait
you seem to be burning an older version. I don't know where you got the device tree from, but the device trees have changed, for some versions.
I assume you know for sure the LAN & RAM?
My S905 beelink minimx III uses a realtek device tree
So, just try a different device tree, you don't need to burn the original image again, just overwrite the device tree
I use rufus, to write the image
Perhaps in some cases there is also no reason to be spiteful or judgmental.
Just because you might not see a benefit in installing to internal, does not mean everyone thinks the same way.
I see a few reasons - convenience, speed (yes, it is faster - think access times), spare SD card to use for test builds and/or other things, potentially free SD slot in the box to use for other things (game ROMs, pictures, video files, music)... and probably more reasons for others that I am not thinking of.
Since I used installtointernal before, followed the protocol exactly and had no issues whatsoever in the past, I did not see a risk in doing so.
Furthermore, as far as I remember and the feedback here goes, the particular issue I described has never been encountered by someone else before.
sorry, but I agree with Poida. If you get problems with internal, then you should bite the bullet, start a fresh install to sd, then, bearing in mind the possible consequences, install to internal again.
Have you read the post, creating a remote conf from scratch?
Display MoreHi all
wonder if someone has the remote.conf for my Beelink Mini MX v. 1.0, 2Gb/16Gb/Gibabit lan...
Been spending quite some time trawling the forum and the web but to no avail.
I'm using [8.1.10] LibreELEC 8.2 for S905/S905X but the remote doesn't work. Can't turn the box on or off. Using bluetooth keyboard for the moment . Everthing else works a treat.
TIA
I have a Beelink Minimx III the only remote, conf files I could find, were in \etc\amremote they were named libreelec.conf & wetek.conf the only code in there is for the power button
Perhaps you could edit & add one of these to your existing remote.conf
# WeTek Play NEC remote
factory_code = 0xbc430001
work_mode = 1
repeat_enable = 1
release_delay = 150
debug_enable = 1
reg_control = 0xfbe40
key_begin
0xca 116 ;POWER
key_end
# OpenELEC NEC remote
factory_code = 0x00680001
work_mode = 1
repeat_enable = 1
release_delay = 150
debug_enable = 1
reg_control = 0xfbe40
key_begin
0xdb 116 ;POWER
key_end
Also read Create remote.conf from scratch
Well my Samsung evo+ was working fine up until the 8.1.6 update using the micro SD slot on s912 box.
After 8.1.7 system stuck on read only.
But latest update is working fine if I put the sd card into a usb adapter and run from there.
You could always try cloning it to a usb using clonezilla
Download Generic AMD/Intel/Nvidia GPU HTPC from downloads – LibreELEC
Using the Libreelec SD creator, burn this image to a usb stick.
Put the stick in the NUC, I am assuming bios it set to EUFI?
Connect another tv, NOT 4K
With a keyboard & stick plugged in, turn on NUC, press the F? key to check the stick can be seen in the Bios.
then insert another usb stick, select install to the second usb
Then follow instructions on screen
You are probably thinking I want to install to the hard disk, well if the install works on the second usb, then you can try to install to the internal hard disk, although Libreelec will run quite well from usb.
I run my celeron nuc from a 32GB usb with no problems.
Is there a official release for 905 amlogic 905 boxes with install guide? I’ve looked but I can’t see one
Not official, community
[HOWTO + FAQ] Install community builds on S905/S905X/S912 device
If you read & followed the installation guide, then you would have tried to install Libreelec to usb/sd first.
So Android would not have been touched.
I do not know how to find out the box specs, so unless someone else can help, my suggestion is
Download the latest image for s905/s905x (same image) 8.1.10 [8.1.10] LibreELEC 8.2 for S905/S905X
burn, the image to microsd using rufus. then trying the device trees one at a time.
Try the S905X from Index of /s905/8.2/device_trees/S905X choose one, depending on the RAM size
If they don't work, try the device trees from S905 Index of /s905/8.2/device_trees/S905 device tree depends on RAM & LAN 100MBit or 1Gbit
Sorry, I can't help more.
Note, you do not have to burn the image every time, you can just copy the dtb.img to the root each time.
Remote repository remote.conf repository
if nothing there search on the forum, creating a remote from scratch