Swarm v1.4 Released
by Matt
I released Swarm 1.4 on Saturday evening. The release included retooled peer communication code, several optimizations to increase download speeds, and a updated UI. The update spans all devices and TVs that were previously supported. As always, if you have any issues or find any bugs, let me know.
-Matt
I’m very interested in evaluating Swarm for use under the Android runtime environment on the RIM Playbook. However, I don’t have access to the Android marketplace and using one of the myriad apk downloads seems unethical. Is there an alternative way to test drive Swarm 1.4 and, if it works well, compensate you for the license? Let me know…thanks!
Hi i have a problem when i use the aplication swarm.when i download something the speed icreases very fast but not very stable the speed drop down like 60kb,80kb and 100kb and don’t increases again. can you help me?
What device are you using and are you on cell or wifi. I have noticed that on some devices, the file write times seem to be longer and become a bottleneck (I’ve been working on making the file writing more efficient to combat it.) If you’re interested in trying a beta version with some updates to the file writing system, send me an email.
Hi, I am using swarm on my Logitech google TV. I absolutely love it and is downloads good. But the same does not upload the file. Is there any setting for this or swarm does not upload the files?
I have a probelm with the swarm does not send torrents download of torrents from a private tracker but well Siag send a bad seeding can be charged overnight and the tracker shows the seeding a few minutes my device is logitech revue and even how to siagal the cable and not just wifi it would was great but the most important to me right calculation seedin
swarm picks the first available port starting at 49160 to listen on. You may need to make sure that port on your router forwards to the Revue. I will run some tests on my revue to make sure there isn’t some other problem. I did have an issue in an earlier version where the listening port was throwing an error a few minutes after starting, that may have made its way back in the last update.
I found the problem, there was a miscount of bytes on incoming connections that was causing the infohash to not match up to the downloaded torrent, I’m working on the fix now.