Possible this is already asked, but a search didn't find a result.
Is it possible to set libreelec as a nbd-client to access a nbd server, so it is possible to acces a dvd-rom over the network. And if yes, can it be binded to the pop-up "play DVD" on the homescreen (I'm still on Confluence) as when you insert a dvd in a native dvd-rom? In general can you configure the "play DVD" pop-up?
See this blogpost of bootlin: Delivery of Allwinner VPU driver main goals - Bootlin's blog
Link to the image: Releases · bootlin/LibreELEC.tv · GitHub
Link to the sunxi howto: Sunxi-Cedrus - linux-sunxi.org
For me, travel nirvana is providing each of my kids with their own tablet loaded with movies and music..and headphones.
That was my first idea to, but I just wondered if it was possible. Apparently nobody is interested in this. I would think hotels & other sectors use such technology for infotainment.
I didn't try it but according to this tutorial: How to Stream Videos and Music Over the Network Using VLC
it could be done, probably it can also be captured by kodi.
Are there some vlc wizards here that can make a easy script for vlc so you can launch a stream with a simple clic by changing the default program to launch the movie.
thanks,
I installed emby and tried to stream but it doesn't stream. I will ask on their forums, maybe if you have a premium account it can do it.
If somebody has other suggestions...
I already looked in to emby, but as I understood, it only serves content to the network. So the client choses what to play. Can it also broadcast a stream?
Hello,
I was wondering if there exist a application on linux or android to broadcast a video stream. I want to stream a .mkv file over the home network to different clients. So it acts like live tv.
The reason is when we go on holiday with the van the kids can watch the same video, the video can then be started on the front seat and picked up by android tablets through wifi.
Is something possible, I googled around but didn't find a decent result. Seems VLC can do it, but it's not so easy.
Display MoreWorth a try. Very frustrating with these builds. I flashed the 06/17 Kodi 17.3 build and the Beelink splash flash a few times and then the critical error on the top. Fantastic weather and I'm inside messing with this old box.
If I remember correctly to flash the downloaded files is via SD card, add the following files from the download and toothpick boot:
factory_update_param.aml
The Eny OTA.zip
recovery.img
However, the eny download also includes the following:
aml_autoscript and U-boot.bin.
and I'm not sure what to do with these.
Hopefully you can help with this.
I was already to sleep yesterday, so I didn't see your post. You have to put them all on the root of the sd-card and then do the toothpick method. If everything is alright you should see the picture of the droid with a spinning wheel in his body. If you are still on TWRP it will not work. Then you have to install the recovery.img first from TWRP (if I remember correctly) and then do the toothpick method again.
If you are not sure you can do following command in a linux terminal: cat factory_update_param.aml
It will show you the text inside of the file. With a little imagination, you can read what files the update needs and what it will do.
You can do the same for the aml_autscript: cat aml_autoscript (make sure you cd to the folder where the files are located).
No, I mean android.
I don't have knowledge of a MXIIIplus, but does it have to be firmware from beelink. Why not try firmware from tronsmart?
I have a Eny M8S and I flashed it with this 5.1 firmware from acemax: ACEMAX Products SW Downloading Center
Worked like a charm, to be honest I never use android, but the box booted without complaint. After the flash, the toothpick method worked (no on and off bootsplash anymore) and I can boot from sd and usb.
You should find a more recent firmware. It's because the installed uboot doesn't accept the aml-autoscript. Try to find a more recent firmware.
just a thought, but I remember when I installed the first time coreelec on my khadas vim, I had to update my dtb file. With the old dtb, my remote didn't work. Maybe there should be done something there.
can it be possible you should change
# Amlogic IR remote support (yes / no)
AMREMOTE_SUPPORT="yes"to
# Amlogic IR remote support (yes / no)
AMREMOTE_SUPPORT="no"in -> /projects/Amlogic/devices/S812/options
I don't find a CONFIG_MESON_IR line in your linux.arm.conf either. But maybe it shouldn't be set there.
Another possibility is this commit from kszaq:
projects/Amlogic: switch to meson-ir, disable amremote · LibreELEC/LibreELEC.tv@7f343ad · GitHub
-> on your github page it's still there: https://github.com/150balbes/libreelec.tv/blob/amlogic-leia/projects/amlogic/devices/s812/filesystem/usr/lib/libreelec/remote-config
A new problem showed up. I wanted to update with the tar file, but I got this error: Missing (target) files kernel and /system
I burned the MXIII-plus image on my SD-card and otted the M8S from the sd-card. No problems with resizing the storage partition.
After the first-run items I did following:
- Added my remote.conf to the rc_keymaps folder and adjusted rc_maps.conf to use my remote.
- Did the following command: ir-keytable -a /storage/.config/rc_maps.cfg -s rc0
- No error messages, but remote didn't seem to work.
- ir-keytable -t didn't respond to the keypresses on the remote.
- ir-keytable without flag gave me this result:
LibreELEC-M8S:~ # ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event0) with:
Driver: rc-loopback, table: rc-empty
lirc device: /dev/lirc0
Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6
Enabled protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6
Name: rc-core loopback device
bus: 6, vendor/product: 0000:0000, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
So it seems meson-ir is not used by the system.
output from lsmod:
LibreELEC-M8S:~ # lsmod
Module Size Used by
hci_uart 41143 1
bluetooth 191493 2 hci_uart
8021q 15927 0
dhd 657022 0
cfg80211 204691 1 dhd
wifi_dummy 737 0
mali 160908 5
Added support for the remote control, but I can not figure out what is the reason that "ir-keytable" does not accept codes from the remote control.
I will look into this, maybe I can figure it out. But I have little time, so it could take some time.
Didn't test the remote yet, but I don't expect problems with it.
Seems there are some problems. I kill kodi and eventlircd and when I want to activate my own remote.conf, I get this message:
LibreELEC-M8S:~/.config # ir-keytable -a /storage/.config/rc_maps.cfg -s rc0
/sys/class/rc/: No such file or directory
No devices found
Maybe it is indeed missing module meson-ir as stated in the error message of systemd.
This is the output from cat /proc/bus/input/devices:
I: Bus=0010 Vendor=0001 Product=0001 Version=0100
N: Name="aml_keypad"
P: Phys=keypad/input0
S: Sysfs=/devices/platform/meson-remote/input/input3
U: Uniq=
H: Handlers=kbd mouse1 event3
B: PROP=0
B: EV=f
B: KEY=7fffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff fffffffe
B: REL=103
B: ABS=0
I: Bus=0010 Vendor=0001 Product=0001 Version=0100
N: Name="gpio_keypad"
P: Phys=gpio_keypad/input0
S: Sysfs=/devices/platform/gpio_keypad.6/input/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=100003
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="rn5t618_pmu"
P: Phys=m1kbd/input2
S: Sysfs=/devices/i2c-0/0-0032/rn5t618_pmu.0/input/input5
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=7
B: KEY=100000 0 0 0
B: REL=0
It seems also the inputstream-adaptive addon is not installed. I wanted to install it from the libreelec add-ons repository but I get following message: Could not connetct to repository.
I tested all you images for 100Mb network. For your knowledge, I have a Eny M8S with a AP6330 wifi chip. Recently I had some problems with it, but I flashed the android firmware again and now everything is fine again. Seems doiing the toothpick method to much for different AML_AUTOSCRIPTS corrupts uboot after a while...
So I tested all images to boot from sdcard and from usbstick.
The 100M image boots, I had to do a manual resizing of the storage partition because it stuck in the boot on the resizing. It can be it had something to do with my old uboot because after reflashing the android firmware the other firmwares didn't have that problem anymore. Same for the freezing as mentioned in post 737.
Conclusion: this image works OK, including network, wifi and bluetooth.
The image in folder 1: boots but no wifi and bluetooth
The image in folder 2: didn't boot at all, the M8S stuck at the S812 boot logo
The image for the mxIII-plus: Works without glitches on the M8S. Network OK, Wifi OK, Bluetooth OK
The only thing I noticed is that the option in the shutdown menu to install the image to nand doesn't work, and also some systemd message during boot about systemd-modules-load.service:
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static;
vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-05-29 18:44:02 UTC; 23min a
go
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 2291 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, st
atus=1/FAILURE)
Main PID: 2291 (code=exited, status=1/FAILURE)
May 29 18:44:02 LibreELEC systemd[1]: Starting Load Kernel Modules...
May 29 18:44:02 LibreELEC systemd-modules-load[2291]: Failed to find module 'aml
videodri'
May 29 18:44:02 LibreELEC systemd-modules-load[2291]: Failed to find module 'mes
on-ir'
May 29 18:44:02 LibreELEC systemd[1]: systemd-modules-load.service: Main process
exited, code=exited, status=1/FAILURE
May 29 18:44:02 LibreELEC systemd[1]: systemd-modules-load.service: Failed with
result 'exit-code'.
May 29 18:44:02 LibreELEC systemd[1]: Failed to start Load Kernel Modules.
I will continue with the MXIII-plus image. Didn't test the remote yet, but I don't expect problems with it.
It's as I already told balbes in post 737: the .please_resize_me file could not be deleted. It's easy to fix if you have a linux pc. Just put the usb stick or sdcard in your linux pc. Go to the storage partition of your usb stick or sdcard and remove the file .please_resize_me as root (or with sudo in the terminal). After you done this, You can use gparted to expand the storage partition.
I don't think it is possible on a windows pc as windows doesnt support the ext4 filesystem. But actualy, I don't know as I'm not a windows user.
If you don't understand the above howto, wait for a next image of Balbes150 where he fixed the permissions of the storage partition. -> just noticed it could be a uboot problem also, as a reflashed my android firmware and started again with the toothpick method to activate multiboot. After I did this the resize problem was gone.
I tried your Leia version for the 100Mb network. Following things I noticed:
1) It keeps on rebooting because it can't delete the file .please_resize_me, after manualy deleting this file as root and expanding the filesystem myself I was able to boot.
2) When in Kodi after a few seconds it freezes, sometimes kodi restarts itself another time I had to pull the plug.
3) The script "install to internal" doesn't seem to work, or there is something wrong with uboot of my M8S.
I see on the download page there is a folder for the 100Mb network with two folders, both with an image. What is the difference between all the 100Mb images. I used the one from the front page.
