HushThreads v0.0.3 has 6 patches for Threads 449.0.0.54.82 (com.instagram.barcelona), the same six as v0.0.2, and every one of them is selected by default. It's a smaller release. Two patches got stricter about where they patch, and the code that lets a same-key Instagram call into Threads got a fix.
New patches
None this time. All six from v0.0.2 are still here.
Fixes and changes
- Hide ads and Sanitize sharing links now need exactly one match for the spot they change inside Threads. If a future Threads build offers two candidates, patching stops and lists them instead of picking one, so you can check a changed build before you install it. Both still apply cleanly to Threads 449.0.0.54.82.
- Restore screens on re-signed builds no longer trips over Android failing a package or caller lookup while an Instagram signed with your key is calling into Threads. Threads gets its normal signer answer back instead of an error. Which apps it trusts hasn't changed.
- Username and password sign-in was checked again on Threads 449.0.0.54.82. One account reached its feed with the published 0.0.2 bundle and with six different 0.0.3 patch selections, with signed-in stock Instagram on the phone and without it. Threads can ask to save your login info twice. Tap Not now on each if you don't want it saved.
Update
- You need Morphe Manager 1.32.0 or newer. If HushThreads is already one of your patch sources, Manager shows 0.0.3 once it refreshes. If it isn't, add it: https://morphe.software/add-source?github=SysAdminDoc%2FHushThreads
- Patch the arm64-v8a bundle of Threads 449.0.0.54.82, version code 511908382. It's the same Threads build v0.0.2 targeted.
- Patch with the Morphe Manager signing key you used last time. That's what lets the update install over your patched Threads and keep your data. With a different key you'd have to uninstall and sign in again. Coming from the stock Threads, uninstall it first.
The .mpp download is a patch bundle, not a Threads APK. Installation instructions.
Known limitations
- Sign in with your Instagram username and password. Continue as the Instagram account already on your phone still isn't offered on a patched Threads.
- Someone reported Threads rejecting their password on a patched build (discussion #2). It hasn't happened in any check here and the cause isn't known yet. If it happens to you, please add your Threads build, the patches you picked and how you installed it there.
- This exact bundle hasn't been installed on a phone yet. The 0.0.3 sign-in checks ran on an Android 16 emulator, and they ran before the stricter Hide ads and Sanitize sharing links checks went in.
- Hide ads still hasn't been seen taking a real ad out, because the test account wasn't shown any. If an ad gets through, please open an issue with a diagnostic report.
- Automatic safe mode is covered by tests and hasn't been triggered on a phone.
Validation
371 runtime tests and 109 patch tests passed locally, along with both Android lints and the release script checks. All 6 patches applied without forcing to Threads 449.0.0.54.82, with no resource or injected-code structural errors. Patching changed the manifest in the two expected ways, adding the settings entry and taking out the advertising ID permission. The dependency advisory check passed.