Open-source project
weixiansen574/HybridFileXfer avatar
weixiansen574/HybridFileXfer

HybridFileXfer splits one file transfer across a USB cable and several WiFi links

Multi-channel fast file transfer: simultaneously uses USB, 5G and 2.4G WiFi to send files from phone to PC, squeezing out every bit of your phone's I/O.

2,720 stars128 forksJavaGPL-3.0

At a glance

What is it?
HybridFileXfer is an Android app with a Java desktop client that runs one transfer over every network interface the phone has, including a USB cable turned into an interface by adb forward. The throughput figures come with no test setup, the help text misspells the program's own name, and there is no progress bar on purpose.
Who is it for?
HybridFileXfer is worth a try if you move large files between one Android phone and one computer every day, your phone can hold a second WiFi link, and you are willing to run a jar under ADB or root on the phone side. It is not a general purpose file manager: the channel list is fixed to whatever the system reports as an interface, the progress bar was cut for a measured reason, and the transfer view copies another app's layout.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 91 days ago.
What is it written in?
Mainly Java, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • weixiansen574/HybridFileXfer2,720 ★ · +25
Star history
Repository2026-09-292026-11-15
weixiansen574/HybridFileXfer2.7k2.7k

25 Stars in the last 47 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The help text spells the program's own name HybirdFileXfer

The desktop client is a jar, and its usage block misspells it. The first line reads:

code
Usage: HybirdFileXfer [OPTION]...
	使用多 I/O 通道(如 USB 和 WiFi)加速从手机到电脑的文件传输。

Every example inside that block starts with HybirdFileXfer as well, and the report line points at github.com/weixiansen574/HybirdFileXfer/issues, with the i and the y in the wrong places. The jar that actually has to be launched is HybridFileXfer.jar, the repository is HybridFileXfer, and the command the Arch package installs is HybridFileXfer. So the swap is inside the program, not only in the prose.

The options are short. `-c, --connect=ADDRESS` takes either adb or an IP address, and the documentation says any network interface address on the phone will do. `-s, --device=ID` selects a USB device, `-d, --dir=DIRECTORY` sets the receiving directory and defaults to `/`, and `-h` and `-v` print help and version. The documentation is in Simplified Chinese throughout, and no English version sits alongside it.

The two speed figures arrive without a test setup

The project opens with two throughput numbers. USB 2.0 plus WiFi 6 on a gigabit network port reaches 150MB/s, written out as 40 plus 110MB/s. USB 2.0 plus WiFi 6 on 5GHz at 160MHz together with 2.4GHz at 40MHz reaches 200 plus MB/s. Both totals are channel arithmetic: the number is the sum of what each link is said to carry on its own.

No test setup comes with them. There is no phone model, no computer, no file size, no file count and no measurement tool named, and the section heading that would hold a benchmark has nothing under it. The figures are also written in MB/s rather than Mbit/s, which reads as file throughput rather than link speed. Anyone deciding whether this is worth installing for a large video has to take the ceiling on trust, and the faster combination depends on a phone holding two WiFi links at once and a computer able to receive that much.

The USB channel is an adb forward, not a USB driver

There is no USB driver in this design. The documentation describes the USB channel as `adb forward tcp:<port> tcp:<port>`, which takes a port on the phone and forwards it to 127.0.0.1 on the computer, so the cable shows up in the channel list as an ordinary interface and the transfer runs over it like any other. The sample session output shows what that looks like:

code
正在连接 网卡名:USB_ADB 远程地址:127.0.0.1 绑定地址:null
正在连接 网卡名:wlan1 远程地址:192.168.8.242 绑定地址:null
正在连接 网卡名:wlan0 远程地址:192.168.8.146 绑定地址:null
传输通道已全部连接完成

Port 5740 is the one in the sample, two WiFi interfaces appear on 192.168.8.x, and every line ends with a bind address of null. Under the ADB connection the phone also has to authorise USB debugging, and the client only becomes usable after the forwarding succeeds. One constraint is easy to miss: even on the USB path the phone still has to be joined to a WiFi network on the same LAN as the computer, because the point of the tool is to aggregate channels, not to replace them.

Three start modes, and one directory decides between them

The phone side offers normal, ROOT and ADB as start modes, and all three are launched through Shizuku rather than by the app on its own. Permissions differ in one documented way. ROOT reaches the data directory, and ADB sits slightly above normal, enough to open an external SD card directory.

The Android data directory is the dividing line. The documentation says the `~/Android/data/` tree needs ROOT mode and that ADB cannot do it, and the bookmark demo repeats the point with a version floor, marking that path as needing root on Android 11 and later.

That constraint is also why the bookmark feature is split in two. Bookmarks arrived in v1.2.0 and live in a phone list and a computer list, with the side decided by which pane has focus. A shortcut pointing into the Android data directory is only reachable in ROOT mode, so a bookmark list that stored only paths would be pointing at something the session cannot open.

Dual-WLAN only pays off once each port is pinned to a channel

The channel list is whatever the system reports as a network interface, and the documentation walks the cases: a connected WiFi link, a second WiFi used for dual-WLAN acceleration, the phone's own hotspot, USB tethering, Bluetooth tethering, a physical Ethernet port, and the TUN interface a VPN creates. Three carry warnings. Bluetooth tethering is marked as not recommended, the VPN interface is marked do not select, and the cellular interface is filtered out of the list, with a note that bringing it back means editing the source and rebuilding.

The dual-WLAN tip is where the real configuration sits. On a Xiaomi phone the path runs through WLAN settings, the WLAN assistant, smart multi-network acceleration and dual-WLAN, and the second network has to sit on a different band, because the documentation warns that matching bands will connect and still slow the transfer down. With two gigabit ports on the computer, bridging them is said to perform best but to be hard to operate. The fallback is two cables into one router, and then the app needs a setting that pins each channel to its own computer port, since otherwise both WiFi links can share one of them.

Phone to phone over USB detours through the computer twice

Two phones are where the design has to borrow the computer. An OTG cable or a dual-head Type-C cable would do it directly, except that running the ADB side on a phone needs root, and Android phones cannot use USB tethering on each other.

The workaround makes the computer a relay. Both phones plug into it, the server phone's port is forwarded to the computer with adb forward, and the computer forwards it on to the client phone with adb reverse. A script drives the sequence, USB-forward.bat, with USB-forward_中文.bat for the Chinese build. Once forwarding is in place the USB_ADB interface can be selected like any other, and the control channel may be pointed at the local 127.0.0.1 address, though the documentation calls that optional. The same warning appears on both paths: with no ADB forwarding in place, do not select the USB_ADB interface.

The progress bar was cut because counting cost a third of the time

There is no progress bar, and the documentation explains why instead of apologising for it. Walking a directory to compute progress was measured at a third of the total transfer time on a folder of screenshots, because such a folder is mostly small files, and the feature was dropped in reference to how fastcopy handles the same situation.

The transfer view is a two-pane file manager, the left pane holding the phone and the right pane the computer, described in the documentation as copied from MT Manager. Selection works by long press, the direction of transfer follows which pane you start from, and a sample mapping given in the documentation moves a test folder from /sdcard/test/ on the phone to E:/transfer/test/ on the computer. Finishing means leaving the file list and then stopping the server, which the documentation asks you to do rather than just closing the window.

Three ways to get the client, and only one of them is packaged

Linux support arrived in v1.1. You download the client for the platform, unpack it, and run `java -jar HybridFileXfer.jar -c adb`. That client is x86 only, because adb is the piece with the architecture requirement: on ARM, RISC-V or Loongson the documented workaround is to supply an adb binary for that architecture in the same directory as the jar, or to fall back to USB tethering. Arch Linux has a package, hybridfilexfer-git, installed with `yay -S hybridfilexfer-git` or `paru -S hybridfilexfer-git`, and the issue tracker carries a notice that packaging questions belong in the AUR page comments rather than there. macOS is untested by the author. On the phone side the jar can run under Termux, though the application already ships its own phone to phone mode.

Licensing is split in a documented way: the bundled JDK is Dragonwell JDK under GPL-2.0 with the Classpath Exception, and the project as a whole is GPL-3.0, with the licence file at LICENSE.txt. The newest release tag is v3.0.0 from 2025-03-12, following v2.2.0 and v2.1.1, while the last push on record is 2026-08-16.

Editorial conclusion

HybridFileXfer is worth a try if you move large files between one Android phone and one computer every day, your phone can hold a second WiFi link, and you are willing to run a jar under ADB or root on the phone side. It is not a general purpose file manager: the channel list is fixed to whatever the system reports as an interface, the progress bar was cut for a measured reason, and the transfer view copies another app's layout. Check three things before you move anything private with it. Which start mode you grant, since ADB cannot read the Android data directory and ROOT can. Whether your two computer ports are each pinned to a channel, because without that mapping both WiFi links can share one port. And whether the client matches your CPU, because the ADB path is x86 only and other architectures need your own adb binary next to the jar. Also mind the name: the file to launch is HybridFileXfer.jar even though the program's own help text prints HybirdFileXfer.

Frequently asked questions

How many transfer channels can HybridFileXfer use at once?

One channel per network interface. The list holds whatever the system recognises, including a connected WiFi link, a second WiFi used for dual-WLAN acceleration, the phone hotspot, USB tethering, Bluetooth tethering, a physical Ethernet port and a VPN TUN interface. The cellular interface is filtered out of the list.

Does HybridFileXfer need ADB for its USB channel?

The USB_ADB channel is created by adb forward tcp:<port> tcp:<port>, which forwards a phone port to 127.0.0.1 on the computer. USB debugging must be enabled in developer options and the phone must authorise the computer. The documentation names USB tethering as the substitute when ADB is unavailable.

Can HybridFileXfer run on a Mac?

The author states he has not tried it on a Mac, noting that Java is cross-platform and that adb has a Mac build. Linux support arrived in v1.1, and the Arch package hybridfilexfer-git installs a HybridFileXfer command once installed.

Why does HybridFileXfer have no progress bar?

Computing progress was measured at a third of the total transfer time on a folder of screenshots, since such a folder holds many small files. The feature was left out in reference to how fastcopy deals with the same case.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. README
  4. Releases
  5. weixiansen574/HybridFileXfer on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/weixiansen574-hybridfilexfer.svg)](https://hysenlabs.com/projects/weixiansen574-hybridfilexfer)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/weixiansen574-hybridfilexfer.svg)](https://hysenlabs.com/projects/weixiansen574-hybridfilexfer)

Was this useful?