SysAdminDoc/HushFacebook

Hushfacebook is a set of Morphe patches for the Facebook app on Android. You bring the Facebook APK, Morphe Manager patches it on your phone, and you get a Facebook with a settings screen of its own. Sponsored and suggested posts go away, and so do the ads in Stories, Reels, search and Marketplace. You can save reels, videos, stories and photos, open links in your own browser, hide the Reels tab and send Facebook less about what you do.

Each row in the patch table says how its switch starts. The ad filters and a handful of others start on, and most of the rest start off until you turn them on. On a computer, HushFacebook Web is a separate userscript for Facebook in the browser.

This project has no connection to Meta or to the Morphe project. Neither endorses it, and neither wrote it.

The latest release is v0.11.0, with 88 patches. It includes all changes since v0.10.0, among them the new Frame step patch, switches that hide comments with shop links or your words, a Home that shows just Friends, Favorites, Groups or Pages, and fixes for the kept reel progress bar and Material You's Menu, as the changelog describes.

Add to Morphe | Download a release | Browse the patches

1. Install Morphe Manager 1.34.0 or newer.
2. Add Hushfacebook as a patch source: https://morphe.software/add-source?github=SysAdminDoc%2FHushfacebook
3. Download Facebook 582.0.0.50.54 from APKMirror. Take the bundle labelled (arm64-v8a) (320-640dpi) (Android 11+), build 475417104, which is a .apkm file. A phone with a 32-bit processor takes the (armeabi-v7a) (320dpi) (Android 11+) bundle, build 475417036, instead.
4. In Morphe Manager, tap Select other apps, then Open APK file, and pick that file. Android may ask for file access the first time.
5. Patch with the default selection and install. If Meta's own Facebook is on the phone, Android makes you uninstall it first, as Package conflict explains.

The default selection is every patch but three, so you don't need Expert mode. To add AMOLED black theme, Material You theme or Disable Play Store updates, turn on Settings → Advanced → Expert mode in Manager before you open the file, then pick them on the Hushfacebook tab. If you saved an Expert mode selection before, Manager keeps using it, so tap Enable recommended patches once to pick up the patches that joined the default selection since. If you also use another Facebook patch source, check that the two don't patch the same thing (Patching stops on one patch).

Morphe Manager signs the patched Facebook with a key it makes on your phone, and every update has to carry that same key. Back it up right after your first patch, under Settings → System → Import & export → Signing key in Manager, then tap Export. The button only shows up once you've patched something. Keep the Morphe.keystore file somewhere private, because anyone who has it can sign an APK your phone will take as an update.

On a new phone, import the key in the same place before you patch anything. Reinstalling Manager or clearing its storage makes a new key, and Morphe's settings backup doesn't include it. With a different key, the only way forward is to uninstall the patched Facebook, which deletes its data. A Root Mount install sits over Meta's own Facebook and doesn't have this problem. Morphe's own guide is Backup and keystore.

There are three ways in. Long-press the Facebook logo at the top of your feed. Long-press Facebook's icon on your home screen and tap Hushfacebook (if it isn't there, open Facebook once and try again). Or open Facebook's Menu, expand Settings and privacy and tap Hushfacebook settings at the end.

The overview groups the main pages in one list, with search and Pause above it. More settings holds the rest. Search reaches every setting, and you can flip a switch right in the results.

Switches act straight away, with no restart and no new patching, but what's already on screen stays as it was until Facebook draws it again. A reel keeps the buttons it was built with, and rows already in the feed stay until it loads fresh posts. The Stories tray switch shows the next time you pull the feed down to refresh. A row that tells you to restart Facebook, such as the font and tab switches, waits for that restart.

Changing one of those brings up a Restart Facebook row at the top of the page, and a tap reopens Facebook on the same page. Quick setups turns on a ready-made set of switches at once, and Report a problem opens a GitHub bug report with your versions and switches filled in.

Pause Hushfacebook turns every switch off from the next start without forgetting your choices. A few things stay in, Lock Facebook among them, and the screen lists them. If Facebook crashes or freezes within a minute of starting three times in a row, Hushfacebook pauses itself and the screen says so.

Morphe Manager can back up your patch choices but not these switches. Export settings saves them to a JSON file, word lists included, and Import settings reads one back on this phone or a new one. It shows what the file would change before anything does. Check for new Hushfacebook releases under Updates is off until you turn it on. Then it asks GitHub once a day and tells you when there's a newer release, and you update through Morphe Manager as usual.

The settings follow the language Facebook shows. German, Spanish, Indonesian, Brazilian Portuguese and Turkish are translated, and any other language gets English.

Reels turn up in several places, and no one switch covers them all. Searching the settings for "block reels" brings up a map of them.

Each row says what the patch does, how its switch starts and which settings page it's on. A row that says "with no switch" works as soon as you patch it in.

Morphe Manager's default selection has every patch except AMOLED black theme, Material You theme and Disable Play Store updates. The themes put their colors in when you patch, and the Play Store patch changes the version number Android sees, so undoing any of them means patching again. Turn on Expert mode in Manager to pick them.

Both themes show in Facebook's dark mode, so turn that on first. A tablet whose Facebook settings have no Dark mode row can use Force dark mode under Appearance. Material You theme takes its colors from your wallpaper on Android 12 and newer, and Android 11 gets a fixed palette built from Facebook's blue. AMOLED black theme has one option, Background color. Leave it blank for black, or give a dark six-digit color such as #0D1117. A color too light to keep text readable is refused, and the message says what to pick instead. The two themes work together, with the background staying black (or your color) and the palette coloring what sits on top.

Videos save to your gallery at the quality you pick under Downloads, best by default. A running save shows its progress in a notification and at the top of the Downloads page, each with a Cancel button.

Questions about setting up, or about whether a Facebook build works, go in Discussions. For something that's broken, use the bug form and attach a diagnostic report from Hushfacebook settings. It leaves out links, IDs and the credentials it recognizes, but read it before you share it. If Facebook crashes before you can reach the settings, attach the newest crash- file from Download/Hushfacebook instead. Ideas go on the feature form. When Morphe Manager misbehaves with every app, not only Facebook, Morphe's own tracker is the place.

Manager shows this before it patches, usually with "This is a different build of the same version". Facebook 582.0.0.50.54 comes in several builds, each compiled separately, and Hushfacebook declares only the two its patches are checked against, 475417104 for 64-bit phones and 475417036 for 32-bit ones. Download one of those as Install describes and the warning goes away. Proceed anyway patches the build you have, but other builds haven't been tried, and if a patch can't find what it changes, patching stops and names it. The same check is why Manager won't offer the Facebook you installed from Google Play unless it's that exact build.

A patch couldn't find the code it changes. The log's Source: lines name each patch bundle and its version, and the error below them names the patch that stopped. When that patch belongs to another Facebook source, such as De-ReVanced, the two sources are usually patching the same thing. Turn on Settings → Advanced → Expert mode, open the supported bundle again, tap Disable all on every other Facebook source tab and pick what you want on the Hushfacebook tab. If your Facebook was patched with Disable Play Store updates before, keep it picked on one tab. Don't uninstall Facebook or replace your signing key to get past an error like this.

If Hushfacebook still stops on the supported bundle with the other sources off, please report it with the full error, every Source: line and the patches you picked.

Four patches work down a list of separate targets, Block background ad prefetch, Block ad telemetry, Disable Audience Network and Hide suggested and promoted posts. They stop only when a build has none of their list, so a WARNING: line naming a missing target means the patch still applied to the rest. On Facebook 582, Hide suggested and promoted posts names six feed units Facebook took out earlier, and that's expected. Any other one is worth reporting with the log.

The .apkm file is damaged, usually by a download that didn't finish. Delete it, download it again and check it against the SHA-256 under Supported Facebook builds.

The phone ran out of storage partway through. Keep at least 2 GB free while you patch.

Your Morphe Manager is older than this bundle can work with. Update it to the version Install names and patch again.

Android only installs an update signed with the same key as the app it replaces, and Meta's Facebook carries Meta's key, so Manager asks you to uninstall it first. That deletes what Facebook keeps on the phone and you'll sign in again, but your account itself isn't touched. A Facebook you patched earlier with another key hits the same wall (Keep your signing key). A Root Mount install on a rooted phone goes over Meta's app and doesn't ask.

Messenger, Facebook Lite, Meta Business Suite and Workplace declare two permissions under the same names as Facebook, and Android lets only one signing key own each name. Install beside Meta's apps renames Facebook's two, and it's on by default. If you patched without it, patch again with it, install over the top and then install the other app.

Android ties facebook.com links to Meta's signature, so it may stop sending them to a re-signed Facebook. Supported links under Links shows what Android reports and opens the page where you can select Facebook's addresses by hand. If they won't stay selected, another Meta app such as Messenger, Instagram or Meta App Manager holds them. Turn off Open supported links for that app, then select them again.

A patched Facebook can't install Meta's updates, so it stays on the version you patched until you patch a newer one. Stop update prompts stops Facebook's own prompts. Meta App Manager, which comes on Samsung and some other phones, posts notices of its own, and you can turn those off in its notification settings. To stop Google Play offering an update, pick Disable Play Store updates in Expert mode when you patch. Keep picking it every time after that, because a build without it counts as an older version and won't install over yours.

After three crashes or freezes within a minute of starting, Hushfacebook pauses itself. If you can't reach the settings at all, an empty file named hushfacebook-safe-mode in Android/data/com.facebook.katana/files pauses it too. A pause only changes what the switches answer and every patch's code stays in place, so if Facebook keeps closing, patch again without the patch you suspect. The next diagnostic report you export shows the error that closed Facebook.

Can Meta tell? Assume it can. A patched Facebook carries your signing key instead of Meta's, and some of what Facebook normally sends home goes quiet, like the ad reports Block ad telemetry turns off.

What stays the same? Your feed, stories and reels still come from Meta's servers, ads included, and Hushfacebook hides things on your phone after they arrive. It never posts, likes, follows or messages for you, and it doesn't change how you sign in.

Could my account be suspended? Nobody can promise it won't be. Meta's Terms of Service ask for its written permission before anyone modifies its apps (section 3.4), and they let Meta suspend or disable an account it decides has broken them (section 4.2). I haven't heard of an account suspended over Hushfacebook, but it's a young project. If you'd rather not risk the account you care about, try it with a test account first.

Hushfacebook doesn't collect anything and has no server. The patched app goes online on its behalf for two things only. One is a save you asked for, downloaded over HTTPS from Meta's media servers (fbcdn.net, fbsbx.com and cdninstagram.com), the same place the player streams it from. When you save from a copied share or fb.watch link, it first asks facebook.com or fb.watch where that link leads, and it stops at any address that isn't Facebook's. The other is the release check, which stays off until you turn it on. It asks api.github.com for the newest release once a day, or when you tap Check now, and it carries nothing about you or your phone. GitHub sees your IP address, as any site you visit does.

A few rows hand a link to another app instead of going online themselves. Send the link to an app under Downloads passes a www.facebook.com link built from the video's number. Facebook's Whitehat settings opens Facebook's own screen, or hands https://www.facebook.com/whitehat to your browser. Support Hushfacebook opens the Ko-fi page on ko-fi.com, and the About and Licenses pages link to the source and its licenses on github.com, gitlab.com, www.gnu.org and www.apache.org.

There are 88 patches for com.facebook.katana, and a release only goes out once every one of them has applied to both builds. Older Facebook versions like 581 and 580 aren't supported any more, so update Facebook before you patch. When a newer stable Facebook comes out, Hushfacebook moves to it and drops the one before. Meta's builds for Android 9 and 8 can't be patched at all, since their code sits in a compressed archive the patcher can't read.

SHA-256 of the two .apkm files the release checks ran against:

475417104  ce599f49afc9e189ae71bbd6a62eedbee82fcc2ad3b7ae963aa343e6a9f276e3  arm64-v8a
475417036  f2dec14920a1fe623c153625e99d443530c065626f346cba02e7831f97fe4ada  armeabi-v7a

On Windows, compare yours with Get-FileHash -Algorithm SHA256 .\facebook.apkm, or use sha256sum facebook.apkm on Linux and macOS.

Every release ships SHA256SUMS.txt beside the bundle, with a line for the .mpp and for each file published with it. Hash the .mpp you downloaded the same way as above and compare it with that line. The release receipt published beside it names the two Facebook bundles the patches were applied to, with the hashes listed above.

You need JDK 17 or newer, the Android SDK and a GitHub token with read:packages, because the Morphe patcher comes from GitHub Packages. On Windows, run the tests on JDK 25 or newer, such as the JBR that comes with Android Studio.

export GITHUB_ACTOR=<your GitHub user>
export GITHUB_TOKEN=<a token with read:packages>
./gradlew :patches:generatePatchesList
./gradlew :patches:buildAndroid

Run generatePatchesList first, or the bundle loses its Android payload. The bundle lands in patches/build/release/patches-<version>.mpp, beside its SHA-256 and a CycloneDX SBOM. Tests run with ./gradlew :patches:test :extensions:facebook:testDebugUnitTest. Set HUSHFACEBOOK_FIXTURE_DIR to a folder holding the Facebook bundles for the tests that read real builds, and put FFmpeg and ffprobe on PATH for the codec tests. Without them those tests skip and say so. scripts/verify-all-patches.ps1 -Apk <facebook .apkm> -DesktopJar <morphe-desktop jar> -WorkDir <scratch folder> applies every patch to a real build and checks the result.

Where things live:

• patches/src/main/kotlin/app/morphe/patches/facebook/ holds the patches, one folder per area (ads, feed, reels, stories, downloads and so on). patches/src/main/kotlin/app/morphe/patches/shared/compat/AppCompatibilities.kt names the supported builds.
• extensions/facebook/ is the Java that runs inside Facebook, with the settings screen, the feed filter, downloads and the rest. settings/PatchFamily.java there lists each patch's switches and what Pause reaches.
• extensions/shared/library/ is the extension library that came from Hushfeed. Its translations are the .tsv tables in src/main/l10n/, which scripts/gen-l10n.py turns into Java.
• patches-list.json is the generated catalog, and a test holds the patch table above to it. patches-bundle.json is the Morphe source index and only changes at release time.
• scripts/release/release.ps1 runs a release stage by stage, and scripts/validate-release-facts.ps1 holds this README, the index and the CHANGELOG to the catalog.

CONTRIBUTING.md has the patch workflow and the rest of the checks.

• The first Facebook patches here were ported from Andrew Liang's patches at 5db2e57 and rewritten with fixes rather than copied commit by commit. Hide post prompts and Hide reel interest prompts came later from its commit 16464b2, and Hide affiliate product links from a934b40, each with a switch put in front. Many of the others were written here.
• SapitoSucio/FroggoMorphePatches gave the idea of dropping promoted posts beside sponsored ones, and of hiding posts Facebook detected as AI. Andrew Liang credits it for some ideas and implementations too.
• Following feed on Home is rewritten from the Following feed swap in ArunTS96/FroggoMorphePatches at 319cde2.
• Hushfeed at 1f1f81a gave the Gradle build, the shared extension library with its settings screen and diagnostics, the pause, the bytecode helpers and the release checks. The settings export and import came later, from bcc57ee.
• HushMessenger at e1e90d8 gave the photo hooks and the video idea behind Send chat photos and videos at original quality, since Messenger and Facebook's in-app chats share one media transcoder.
• HushPinterest at c5be4d9 gave four pieces of the settings screen. They're the quick setups, the search, the Report a problem page and the return to the page you were on after a restart.
• Morphe and ReVanced gave the patcher and the patch template. Disable Play Store updates is Morphe's own patch from MorpheApp/morphe-patches at 1bcd0bc, which grew from ReVanced's Change version code. Its two files keep Morphe's notice, and their headers say what Hushfacebook changed.

Every source file says where it came from in its header, and provenance.json maps each file to the project and commit it came from, with its license. docs/sources.md covers the other Facebook and Messenger patch projects and what this bundle took from each, and sources/facebook-sources.json pins their branches and licenses.

GPL-3.0, with the Morphe section 7 notices carried in NOTICE. Facebook, Messenger and Meta are trademarks of Meta Platforms, Inc.