Transmission torrent server script install#
Transmission torrent server script for android#

I also delayed myself by not installing eclipse and the SDK tools properly at first.

What I finally did was find the current path in osx by typing 'echo $PATH' in terminal and then I copied and pasted adb into one of the current paths.

I also never succeeded in editing the environment variables path thing.

Settings.json was created, and I was able to edit through vi as desired. For me, I had to type su AFTER doing adb connect. Took me a while to figure that one out too. After finally resolving the wget thing (took me longer than I will admit), I got the daemon installed but couldn't get it to create settings.json.

after you first connect through adb, type 'su' and hit enter.

Otherwise, you'll run into errors when you get to the actual installation of ipkg and transmission-daemon (no wget)

if you're doing this through Terminal on osx, you need to have Xcode installed, and then command line tools installed within xcode.

Maybe my experience can help other dumb people: I ran into some problems, mostly because I'm dumb. Following your directions for OUYA accomplishes exactly what I want, and no need to buy a new router. But I love having transmission on an always-on device so I can start torrents, whenever, at home or remotely and they'll be ready when I get home. I had transmission-daemon running on dd-wrt but then I bricked my router. This should start up transmission-daemon only when you've got a network connection on each and every boot and runs as root (which I'm now starting to think this isn't the right way to go about this little endeavour. If busybox test $(busybox id -u) = 0 then HOME=/opt/home/root else HOME=/opt/home/user fi Ls /opt >/dev/null 2>&1 || su -c /data/opt/optware-init.shД®xport PATH=/opt/sbin:/opt/bin:/bin:/system/bin

Then check the SU, Boot and Net icons and click edit to amend start.sh to include the below transmission-daemon command #!/system/bin/sh Starting transmission-daemon to run on bootДў) In Script Manager click - Menu - Scripts - Browser and navigate to the file /data/opt/start.sh Which it should find, here /data/opt/home/root/.config/transmission-daemon/settings.jsonД®dit it to your hearts content vi /data/opt/home/root/.config/transmission-daemon/settings.json

Transmission torrent server script install#

Which if successful should show BusyBox v1.10.3 ( 09:43:47 UTC) built-in shell (ash)Д®nter 'help' for a list of built-in commands.Д¦) Install transmission-daemon ipkg install transmissionД§) Run transmission and then kill it so as it creates its config file for you to, erm, configure! transmission-daemon To start optware session, execute /data/opt/start.sh on the deviceДҐ) Like it says, run the above shell script.

Transmission torrent server script for android#

Optware for Android installation complete. If all goes well you should end up seeing something like this I crudely fixed this with (it may differ depending on your install environment) PATH=/YOUR/FOLDER/adt/sdk/platform-tools:/root:/usr/sbin:/usr/bin:/sbin:/bin This means that the folder in which adb and the script reside aren't in your environment variables PATH. optware-install-via-adb.sh: adb: not f^C optware-install-via-adb.sh: adb: not found (Also guys remember - if you're on a version of android >4.2.1 you'll need to accept the RSA fingerprint on your device before any of this!)ДЈ) Ensure the script for optware is in the same folder as adb and is executable./optware-install-via-adb.shД¤) You'll probably get an error running the script to bootstrap optware saying adb not found./optware-install-via-adb.sh: 100. adb connect :XXX:5555Д®dit: After trying this on my phone, which unlike the JustOP box doesn't have a writeable /system out of the box, and I had to remount the /system folder with. YOU CAN NOT INSTALL THIS WITHOUT ADB ACCESS.ДЎ) (sudo) su in a terminal on your unix box so you have root accessДў) Connect to your device with adb./adb devices I had to use wireless adb (which works fine too!!!) and is installable from the Play Store here. Just boot a LiveCD from Ubuntu maybe?ДЄndroid SDK (or just the tools does fine) with ADB access to the device. There's other solutions to this (see: BotBrew) but having used optware before it took my fancy.ДЄn unix command line OS (probably doable in Winblows but file permissions and cygwin makes me weep). Since there's no application on the Play Store or elsewhere we I got mad and went down the good old fashioned route of try ALL the things to make this work, and found that optware-for-android works fine. Two years later edit: Seems an app has been updated with this functionality at last!