@
enen92 I detected some strange behaviour with AceStream in the Raspberry Pi 2. I commented before but I now know exactly how reproduce (in my OS).
I have a famous sport's AceStream link (from a web that have some enumerated channels, some in acestream and other in sopcast). I added one Acestream channels into My Streams, so I can get these links in other Kodi installation and they are equal (no typos in URL, etc.):
I open one of these channels in the Raspberry Pi 2 with OSMC and Kernel 3.18. It shows:
Starting Ace Stream
Awating Response
Downlading Torrent
Pre-buffering. Seeds: 0 Download: 0 Kb/s
And it stops here.
In my router a new NAT entry is added (supose via UPnP): AceStream port 8621 -> 8621 for TCP (internal and external 8621 to IP Raspberry).
I can wait, it doesn't move. Seed: 0 Download: 0
Now, i go to my laptop, with Ubuntu x64, open Kodi, Plexus and open the same channel:
Pre-buffering. Seeds: 5 Download: > 0 Kb/s, Seeds: 10...
And in my router I have another rule: AceStream port 8621 -> 8622 for TCP (external 8622, internal 8621 to IP laptop)
And reproduction starts....
But, what happens at this moment? Raspberry see 1 seed (supose my laptop) and, then, sees all the other seeds (supose that the laptop informs other seeds) and it starts reproduction.
I have one small theory: With other AceStream it doesn't happens (your torrent file to test, or other stream that I have that doesn't pertain to this famous web), so ¿can be the tracker beside this web blocking this Acestream engine? (the Android AceStream engine) is very strange that it works just at the same moment that I open the same channel in my x64 laptop (I supose that it have some lan discovery method).
I don't think that is a problem with ports, because router indicates that are open (as you can see) and other AceStream works. The sopcast links from the same web works fine without laptop interaction.