Hello guys, i have acestream configured with kodi. Whenever i stream something the stream will crash after 2-5 minutes. I cant figure out what the problem is
Linux distro/version, Ace stream engine version and log files?
By “i stream something” - do you mean using Ace Stream as client (for watching third-party broadcasts), or as server (creating your own broadcasts)?
there is a fix for RPi2/3. It basically works like this:
Get into the command line of your raspberry pi (for OSMC you can do this by repeatedly pressing Ctrl when the osmc logo shows during the boot sequence).
Enter username and pass if required (for OSMC: username: osmc, pass: osmc).
Type in the following lines in order:
cd ~/.kodi/userdata/addon_data/program.plexus
sudo rm -r acestream
tar xfv acestream_rpi_3.1.5.tar.gz
reboot
Hope this helps!
hello, guys. I have a Raspberry Pi 4 with the new 64bit Os. I am using the latest Kodi available in the repos: Version: 2:19.3-1~bullseye I was wondering on how I can install Acestream-engine for Kodi on it. I been looking on google but i can’t really find a tutorial.
There no official Linux version of Ace Stream engine for ARM yet, but you can try third-party mods - Telegram: Contact @AceStreamMOD
Hi! I’m creating this topic to ask about Acestream for arm64 devices not running Android. In my case, I’d like to use a Raspberry Pi 5 to host Acestream but, as there aren’t arm64 versions of the software available (apart from the apks, which I don’t know how to run in the RPi), I don’t know how I can do it.
So, I’ll be glad to know if someone runs Acestream in a Raspberry Pi 5 or a similar device with an arm64 arch (or knows how to run it) so I can get some info about this topic.
Thanks in advance!
One of simplest ways to run Ace Stream on RasPI - GitHub - ef1f/RaspberryAceProxy: Docker image to run acestream-engine and HTTPAceProxy on RaspberryPI, ARMv7.
I know there are some ways to run acestream in raspberry pi, but they are all for armv7 CPUs. However, the new Raspberry pi 5 ships with an armv8 (or arm64), so my question is about some way to run acestream in this kind of architectures.
armv7 (aarch32) binaries should work on armv8 (aarch64) - you can check this yourself, by installing armv7 APK from Products - Ace Stream DAO on armv8 device.
Okay, I’ll try that then.
Hi, has anyone been able to install acestream on a Raspberry Pi with Raspi OS with arm64? I’ve tried everything but I haven’t been able to do it. If anyone has any information, I would greatly appreciate it.
Wow, that’s impressive. But this also can be read as “I’ve did nothing, because I din’t find a working solution which i can copy/paste”.
Please, be more specific, and write a few words about what you actually “tried” and on which stage(s) of these “tries” you’ve encountered a problem(s).
Hi again, I’m trying to run sshmanko/acestream-armv7 version of acestream for armv7 architecture (as Benny said, it should work in armv8 arch as well).
When I run the acestream.start script, everythig seems to be running fine until the last line, which is
chroot $ACEADDON/$ACECHROOT /system/bin/busybox sh -c "/system/bin/acestream.sh"
I removed the “redirection to a log file” to see the output in the terminal but, even though I get no errors, I get no output either, and it seems to be doing nothing as the port 6878 does not open. Any ideas about what might be happening?
Edit: I’m trying to run acestream in a Raspberry Pi 5 with the latest 64-bit OS (Debian GNU/Linux 12 (bookworm) in arm64 arch).
If you’re not familiar with chrooted environment and don’t know how to debug app startup problems within - try Docker container first.
There a plenty prebuilt images at Docker hub - just give it a try: Docker
Okay, as it is true that I’m not used to chroot, I tried some prebuilt docker images. This is the list of images I tried and the reason they failed:
| Docker image | Reason of failure |
|---|---|
| inutil/acelu4t | Segmentation fault |
| danielchc/acestream-arm | Segmentation fault |
| mikhaildedeiko/acestream-arm-updated | Segmentation fault |
| trananhtuan/acestream-armv7 | Segmentation fault |
| sath89/acestream-armhf | Segmentation fault |
| plaza24/acestream-arm64v8 | Exited (139) |
| huangw5/cheapstream | Segmentation fault |
| aaaler/acestream-pi | Exited (139) |
I’m suspicious about so many Segmentation fault errors. Any ideas about this or how to debug it?
PD: I’m sorry but as a new user I can’t write more than two links 
You should focus on containers with “Exited” status first - there a slim chance, that something wrong with command line option(s).
Also you should bear in mind, that “aarch” compatibility for “aarch64” system is OS/kernel depended - if such “compat” modes don’t enabled at kernel/OS level, then you out of luck.
You can try Ubuntu 24.04 - their approach to software config and default packaging is less conservative than Debian distro.
I tried to fix the containers with Exited status, but I couldn’t do it. I also tried to install 32bit dependencies of the software in the pi and I almost break the system. The process is too complicated (and kind of dangerous) just to get acestream running (in my opinion). I guess I’ll wait until an arm64 linux version is published.
Thanks for your help and patience anyways, @Benny.
Hello
I have been able to install acestream in rpi5. The trick is to install a virtualization layer (qemu) of the different architectures → amd64 and thus be able to run it
The steps are:
docker run --privileged --rm tonistiigi/binfmt --install all
This way you can run dockers of different architectures, for example:
docker run --platform linux/amd64 -d -p 6878:6878 wafy80/acestream
It could still be installed in a better way, but it works.
I hope it helps someone
Hi @zael, thanks for sharing your solution. I have to admit I also tried this solution, but I didn’t post anything about it as it didn’t work for me, even with different images to wafy80/acestream one. Now, however, it is working for you, so I suppose it is something wrong with my particular setup.
Having followed your exact steps (although I think it is only necessary to install amd64 emulator with the tonistiigi/binfmt image), and even though the container is running, I get an error when trying to fetch the .m3u8 file for any stream. The error is the following:
Traceback (most recent call last):
File "core/src/CoreApp.pyx", line 1526, in
File "core/src/AirCast/AirCastManager.pyx", line 158, in
File "core/src/AirCast/DiscoveryManager.pyx", line 308, in
File "ACEStream/third_party/zeroconf/zeroconf.py", line 1405, in __init__
File "ACEStream/third_party/zeroconf/zeroconf.py", line 1441, in _init_sockets
OSError: [Errno 92] Protocol not available
2024-06-02 12:31:19,407|MainThread|acestream.SocketHandler.InterruptSocket|bound on 127.0.0.1:39023
2024-06-02 12:31:19,412|MainThread|acestream.SocketHandler.SocketHandler|bind: socket bound: host=0.0.0.0 port=62062
2024-06-02 12:31:19,415|Instance2InstanceThread-30|acestream.APIServer|run: ready to receive remote commands on 62062
2024-06-02 12:31:19,425|PlaylistTaskManagerThread-31 (_run)|acestream.TaskManager|started
2024-06-02 12:31:26,534|Thread-19 (__forward)|acestream.upnp|Unable to create Port Forward. Error: Success: <class 'Exception'>:Success
2024-06-02 12:31:54,650|SegmenterThread-50 (segmenter_thread_func)|acestream.ProxyTransporter|segmenter_thread_func: error
Traceback (most recent call last):
File "core/src/live/LiveClientTransporterProxy.pyx", line 942, in
ImportError: /opt/acestream/lib/acestreamengine/pysegmenter.so: failed to map segment from shared object
Does anyone know why is this happening? (I think I should note that the image starts acestream with the start-engine script)
Hi,
Its true, I installed all emulators and in theory only amd4 is needed.
You are right, I cant get a m3u8 from other host (i have check it). However I can get a stream from Kodi + addon Horus in same machine (i don´t know what is the diference). These metod is a bit buggy _> it need two o three times in order to get a stream, but works.
I hope it helps you