Fuse

Fuse setup: use Wi-Fi and cellular for downloads

Follow this Fuse setup guide to combine Wi-Fi and cellular for eligible downloads, check each link's usage, and understand the free beta's limits.

Fuse setup starts with Settings → Fuse → Bond downloads, then downloading an eligible file while connected to Wi-Fi with cellular data allowed. Fuse can split that download between both connections, but Safari, App Store installs, and background downloads stay on one link. Here is how to try the free beta, check what it actually used, and recognize downloads that do not qualify.

Fuse setup: turn on bonding and try one file

Fuse is a Dopamine rootless tweak for using Wi-Fi and cellular together on large file downloads. Add our source, https://tweaks.carterware.net/, in Sileo or Zebra and install Fuse. Its package identifier is com.carterware.bond, so that older name is expected if you see it in package details.

The switch starts off because bonding uses cellular data. Before enabling it, make sure you are comfortable spending data on the download; we designed Fuse for unlimited data plans.

  1. Open Settings → Fuse.
  2. Turn on Bond downloads.
  3. Stay connected to Wi-Fi and allow cellular data.
  4. Download a file in an app that uses Apple's standard networking.
  5. Keep that app open during the download.
  6. Return to Settings → Fuse → Last Bonded Download to check the contribution from each connection.

A large ZIP, video, IPA, or DEB is a useful starting point, provided the app and server meet the requirements below. Sileo is part of our testing, but that does not mean every Sileo request will use both connections. A repository refresh and a large package download can take different paths.

What happens to the two parts

Wi-Fi starts fetching the file from the beginning while cellular fetches the end. Fuse assigns each connection a share based on its speed, then joins the parts into the same file the app requested.

That division is not a fixed half-and-half split. A slower cellular connection takes less work, and Fuse can stop using cellular when it turns out to be far slower than Wi-Fi. If Wi-Fi alone would finish in a few seconds, cellular stays out.

This matters when interpreting a successful download. Seeing little or no cellular traffic does not automatically mean something is broken. Sometimes the useful choice is to leave the download on Wi-Fi.

Fuse also keeps the app's cookies and sign-ins, and it respects an app's request not to use cellular data. It leaves one-time download links alone. If a file changes on the server during the transfer, Fuse stops instead of joining pieces from different versions.

Think of the goal as helping an eligible file transfer when the second connection is useful. There is no promised speed multiplier, and switching bonding on does not make every network request use both links.

Check eligibility before troubleshooting

The largest limitation is the download path. Fuse works with apps using Apple's standard networking while those apps are open. Safari, background downloads, App Store installs, and apps with their own download engine, such as VLC, remain on a single connection.

That means a large App Store game install is not a good test of Fuse. A file downloaded inside an open app may qualify, but size alone cannot tell you whether that app uses a supported networking path.

The server and response matter too:

  • Files under 1 MB stay on one link.
  • Compressed responses stay on one link.
  • Servers that refuse range requests stay on one link.
  • Downloads whose apps disallow cellular stay on one link.

Range support lets Fuse request separate portions of a file. Without it, the server cannot provide the split transfer Fuse needs.

For a first check, change one condition at a time. Keep the app open, confirm both connections are available, and choose a substantial file download rather than a quick refresh. If the app or transfer falls into an excluded category, repeating it with the switch enabled will not make it eligible.

Read the counters and check your version

After a test, open Settings → Fuse → Last Bonded Download. The rows show how much came over each connection using the interface byte counts reported by iOS. Use those figures to check whether cellular contributed, rather than judging only by how quickly the progress bar moved.

Version 0.2.0 fixed crashes when downloads started on iOS 16. It also fixed some Sileo repository refresh failures that displayed “cannot decode raw data” when servers returned compressed files. Compressed responses still use one link; fixing the refresh error did not make them bonded downloads.

That release also handles redirects, including HTTP-to-HTTPS redirects, while keeping large eligible redirected downloads bonded. It added file types including M4A, FLAC, WAV, AVI, EPUB, CBZ, CBR, XZ, BZ2, ZST, IPSW, and TIPA.

If you are troubleshooting one of those older failures, check your installed version before repeating the test. Record the app, the kind of file, whether it stayed open, and what the last-download rows showed. Those details separate a compatibility limit from an unexpected failure.

Know the beta boundary and report useful failures

Fuse is BETA, verified on iOS 17.1 with an iPhone 15 Pro and real cellular, and on iOS 16.3.1 with an iPhone 14 Pro Max. We tested with interface byte counters, a test tool, and Sileo. iOS 15 has not been tested on a device yet.

The beta is free to keep. Fuse will become paid when it leaves beta, with the paid release delivered as a separate package; keeping this beta installed will not lock it.

For an unexpected failure, use Settings → Fuse → Report a Bug. That fills in your tweak version, iOS version, and iPhone model. Describe what happened and include your download observations, or use Report a bug.

If the symptom is an app crash or respring, Mountaineer can help you inspect the crash diary. Open its Timeline, refresh it, and tap the relevant entry to copy a summary. It reports what it observed and cannot guarantee a culprit.

FAQ

Does Fuse speed up App Store installs?

No. App Store installs stay on one connection, as do Safari and background downloads.

Why did my download use only Wi-Fi?

The app or server may not support bonding, or the file may be too small. Fuse also keeps cellular out when Wi-Fi would finish quickly or cellular is far slower.

Will the free beta stop working when Fuse becomes paid?

The beta stays free to keep. The paid release will be a separate package.

Start with one eligible download, then check Last Bonded Download before trying a larger batch. Open Fuse for the current beta details, enable bonding only when you want to spend cellular data, and send a report if a supported transfer fails unexpectedly.

← All posts · Report a bug