BitComet and more

Check out the new release, version 1.1.7, which includes many bug fixes and small(er) improvements, plus all new BitComet support and improved labels. Thanks for contributions by Sergey (SeNS) and Alexey Rogovoy. The power of open-source, baby!

You should get a notification when starting Transdroid – or get it directly from the Google Code site.

17 thoughts on “BitComet and more”

  1. I’ve been getting the notification every day for the last week. Seems that despite saying version 1.1.7 is available, tapping the notification automatically downloads version 1.1.6, which is the version I already have.

    1. Actually, just figured it out. The mobile version of this site still points to 1.1.6 as the latest download. Viewing the desktop site from my phone allowed me to get 1.1.7. I would have thought they were linked. Weird.

  2. Awesome app and link to 1.1.7 works perfect on a mobile browser. One request and most likely heard before: any possibility of creating a search that searches across multiple sites?

  3. Is it ever going to be possible to use transdroid with rtorrent, without the need for /RPC setting?
    I am asking because as a frontend for my server i use ruTorrent which has a plugin, httprpc, a substitute for the scgi mount which uses 1/10 of the necessary bandwidth..
    Thanks for any reply!

  4. Never mind my last question…
    Thanks to the guys in rutorrent forum I found out that if you use httprpc, then instead of /RPC2, if I enter /rutorrent_install_folder/plugins/httprpc/action.php the problem is solved!
    Just posting here in case someone else needs this, too!
    Thanks a lot for this great app!

  5. You are welcome, Erik… The least I can do in return of your great app!
    Another thing I learned today regarding rutorrent: If I use httprpc but for some reason don’t want to change settings in transdroid, thus leaving /RPC2 in settings, then rutorrent will benefit from that plugin while transdroid will simply still use the SCGI mount to connect. A bit useless to use both since setting plugins/httprpc/action.php in transdroid settings works, but JFYI…

  6. It seems there was an update to Vuze that has broken Transdroid – I no longer am able to connect to it (or rather, I can connect but it errors out).

    The transaction logged in Vuze is:

    REQUEST START: 172.16.0.32, time: 10:46:50 PM
    [22:46:50] About to deserialise the RPRequest
    [22:46:50] Beginning deserialisation of RPRequest instance.
    [22:46:50] Deserialising field (“method”, type: String)
    [22:46:50] Attempting to deserialise simple value of type “String”
    [22:46:50] Deserialisation of simple value successful.
    [22:46:50] Field “method” deserialised and set.
    [22:46:50] Deserialising field (“request_id”, type: long)
    [22:46:50] Attempting to deserialise simple value of type “long”
    [22:46:50] Deserialisation of simple value successful.
    [22:46:50] Field “request_id” deserialised and set.
    [22:46:50] REQUEST: method=getSingleton, object=null
    [22:46:50] About to serialise the RPReply
    [22:46:50] RESPONSE: com.aelitis.azureus.plugins.xmlhttp.GenericRPPluginInterface@2eff813e
    [22:46:50] Serialising object of type “GenericRPPluginInterface”
    [22:46:50] Need to use XMLSerialisationUtils to serialise GenericRPPluginInterface@2eff813e
    [22:46:50] Going to process 6 attributes on GenericRPPluginInterface@2eff813e
    [22:46:50] About to serialise attribute “azureus_version”
    [22:46:50] Serialising object of type “String”
    [22:46:50] Value was easily serialised into a string format.
    [22:46:50] About to serialise attribute “azureus_name”
    [22:46:50] Serialising object of type “RuntimeException”
    [22:46:50] Need to use XMLSerialisationUtils to serialise RuntimeException@45db3348
    [22:46:50] Going to process 0 attributes on RuntimeException@45db3348
    [22:46:50] Finished serialising RuntimeException@45db3348
    REQUEST END

    Hope this can be resolved soon.

      1. Hmm, strange thing is that I’d been using Java 7 for a while (AFAIK) and it didn’t seem to have a problem.

        But I’ll poke the Vuze folks and see if they’ve got a fix forthcoming.

        Thanks

        1. So I had a closer look, and it seems I had installed Java 7 on another of my systems sooner than this one, and mistakenly thought that it was an update to the XML plugin that caused the problem.

          Modified the startup for Vuze to point to the installed Java 6 binary, and that took care of the problem.

          Thanks for pointing me in the right direction – everything’s working again.

Leave a Reply

Your email address will not be published. Required fields are marked *