alpine-qbittorrent-openvpn VS termux-adb-fastboot

Wow, was about to suggest what I've been using for years only to notice it's been deprecated since November of last year hah: https://github.com/guillaumedsde/alpine-qbittorrent-openvpn

This was the docker container I used; there's a guide on there but it assumes you're familiar with docker.

There are Docker images for this exact purpose: https://github.com/guillaumedsde/alpine-qbittorrent-openvpn/

I'm running qBittorrent + OpenVPN Docker image. Is there a way to make Windscribe OpenVPN config work with ephemeral port forwarding we create from website?

I use guillaumedsde/alpine-qbittorrent-openvpn

qBittorrent : torrent downloader. The Docker image includes an OpenVPN client which is connected to my ProtonVPN account.

qBittorrent: torrent downloader. I used this container to enable the VPN

My current setup is similar to yours, but everything runs in its own container on Docker. For the torrent client, I use this image which makes sure torrents are only downloading when there’s a good connection with the VPN. If you got any questions, I’d be glad to help you.

Using only the device itself (you will need to be connected to wifi for this to work, these instructions are hot garbage): Install Termux from F-Droid. In termux install platform-tools adb/fastboot. Then Enable Wireless ADB, Settings-> System -> Developer Options -> Wireless Debugging, turn the slider to on, then get the port number from the Wireless Debugging sub menu get the port number. (Remember to turn off Wireless Debugging when done!). In Termux run adb connect localhost:PORT then check adb devices you should see an authorization prompt for a debug connection, you'll need the connection challenge code from settings (this authorization only needs to happen once). Then adb shell and run one of the commands below.

Termux for the help install in termux this: https://github.com/rendiix/termux-adb-fastboot pair your localhost:port with termux's adb connect to it and run adb shell wm size [Xres]x[Yres] -d [display number]

Just a heads up for anyone reading that tries this and finds it doesn't work: in the comments /u/-korni- linked to an alternative version of adb and I found that fixed the problem for me and the task works again.

There is a known bug with Samsung devices and the version of android-tools included in the repo. You have to use a different version of ADB to getaround the issue with the server not running right, I personally use https://github.com/rendiix/termux-adb-fastboot on my A32 5G. Not sure if others like termux-ADB work.

This one works; https://github.com/rendiix/termux-adb-fastboot

newest binary