Use the backup function in the LE settings add-on and then move the .tar (not .zip) file off the box. Go install another machine and then use the restore function to .. restore the backup. It is technically possible to custom build and pre-bake things into LE images, but if you have to ask how it's not worth your/my time attempting to explain the process and backup/restore is considerably easier.
Posts by chewitt
-
-
please try the RPi1/0 (not RPi2/3) image here and report back, thanks. -
-
There are a number of sync/timing issues for Amlogic/Krypton that are "work in progress" at the moment. Thanks for the detailed report.
-
A8 box has a CPU with ~20x the compute power, plus Ethernet. Pi is a small miracle for what it is, but ultimately it has a low-spec ARM chip and and a wireless connection. Your results are entirely as expected.
-
Put it in the patches subdirectory and re-run the build command. It will clean/patch/rebuild only that package.
-
aVLB <= this is the patch carried by most distro's
-
Running "dmesg | paste" will share the whole log (as asked) instead of the tiny bit you think is relevant.
-
NB: For the handful of people who are advance testing CM3 boards, the FiveNinjas folk requested the Slice2 image to be renamed to Slice3 to avoid user confusion. This means you will need to run "touch /storage/.update/.nocompat" before manually downloading the 7.95.1 beta else the compatibility check run during the update process will fail. It's technically possible for us to add an extra script to negate this, but with literally 5-6 people affected I've decided to finish something else and learn that trick another day
-
Our 7.0 branch is now closed to all development apart from add-on updates so anything testing/poking you do should be on Krypton builds.
-
They are different devices for different budgets and user styles (fully spec'd retail boxed product or bare board with accessory options). Both devices are in widespread use among the team, and ultimately our technical direction cares more about the chipset/internals than the manufacturer logo on the box so I'd say both have the same lifespan.
-
There is no official "team" and thus there is no official "leader" of the team although if you look at GitHub records some of us seem to press the merge button more than others. We operate more like a 60's hippy commune than a hierarchical army of developers
Why do you ask?
-
Nexbox has the board UPSIDE Down within the casing.
That to me is a bad design due to the fact that Heat Rises.
The casing is also smaller than other boxes.Users often misinterpret the function of cooling to be making their box/device run cool, or as cool as possible, which is never the [sic] case. In reality the main objective is ensuring a safe operating temperature range. As long as cooling holes do this, the objective is reached. Holes on the bottom generally result in lower levels of dust ingression to the device and avoid the opportunity for liquid spill damage so in most consumer products would be preferred to holes/vents on the sides or top.
-
-
There are some but the build server uploads to a private location as normally we don't want to distract attention from milhouse builds. He's moved on towards v18 so there's a gap at the moment. Be a little patient and the 7.95.1 beta will be along soon.
-
openssh: UsePrivilegeSeparation/StrictModes not needed by MilhouseVH · Pull Request #844 · LibreELEC/LibreELEC.tv · GitHub <= this has been resolved properly in LE 8.0 builds (no hacking of user/group with scripts)
-
Anything that uses autostart.sh is a dirty hack. Their instructions should be updated for 7.0 builds too, and for the same reasons.
-
17:44:26 19.334791 T:1963106304 NOTICE: ADDONS: Using repository
no support to users of piracy add-ons and repo's, particularly as the crapware in them frequently causes instability issues. Thanks.