v0.0.12

HushTelegram v0.0.12 has 56 patches for telegram.org's Telegram 12.10.6 (org.telegram.messenger.web) and the official Telegram beta 12.10.7 (org.telegram.messenger.beta). Fifty-four are selected by default, and the one new switch starts off. Most of this release is about reading easier. Every patch description, settings row and message inside HushTelegram is rewritten in plain English, and Expert mode groups the patches the way you'd look for them. Keep deleted messages now marks a message the moment it's deleted while the chat is open, and it can clear what it kept. On the beta, Disable analytics also stops Firebase's crash and session reports.

What's new

• Telegram: On Telegram Beta, Disable analytics now also turns off Firebase's crash and session reports. Telegram's own crash reporter setup, which handed Crashlytics your user ID and username and switched collection back on at every launch, no longer runs, and Crashlytics' own setting is saved off, so it stops collecting and sending from the next start. Session reports stop right away. Push notifications don't change, and the regular build has neither reporter. Turning the switch off brings both back at the next launch.
• Telegram: A new Turn off beta debug logs switch, off by default, stops Telegram Beta from writing debug logs all the time. The beta turned them on at every start, its connection log included, and its own debug menu couldn't stop that. Logs already saved stay until you clear them, and the regular build doesn't change. Restart Telegram after you turn it on.
• Telegram: Keep deleted messages has a new Clear kept messages row in HushTelegram settings, right under its switch. One tap gives every message it kept, in every signed-in account, to Telegram's own deletion, so they go the way they would have without the patch. A notice tells you how many went. It's translated into all five languages.
• Telegram: Keep deleted messages now marks a message as deleted the moment someone deletes it while you have that chat open. Before, the label only showed up after you left the chat and came back.
• Telegram: Contributors have a new audit of the stock beta, signed in on a real phone. It covers a live search ad, the app's own settings screens, what the app sends on the local network, and how busy it stays in the foreground and background. It also separates contact sync from contact suggestions and notes what you can't learn from encrypted traffic.
• Telegram: Added an app audit for sponsored-message delivery, ad reporting, telemetry, contact sync and current patch opportunities on the pinned 12.10.6 APK.
• Telegram: Build and Pause reports now use Morphe Manager's patch names for haptic feedback and link tracking. The pause card's test now matches its current wording about Debug logging.
• Telegram: Contributors now have a factory-app reference for the pinned APK, with the first-run flow, manifest entry points, stable anchors and fixture-update steps.
• Telegram: The three patch options (your Telegram API ID and hash, and your Google Maps key) have clearer names and say where to find each value.
• Telegram: Messages inside HushTelegram are plainer too: the notification status lines, the pause and safe mode notes, update check results, settings file errors, and the "this build doesn't change" notes now say what happened and what to do next, with no technical words. All five languages are updated.
• Telegram: The rows in HushTelegram settings now say in plain English what you'll notice when a switch is on, and a few titles are clearer (Stop vibrations on taps, Remove link tracking tags, Show where a profile photo is stored). The translations are updated to match.
• Telegram: Every patch description in Morphe Manager is rewritten in plain English. Each one now says what changes on screen, why you might want it, and ends with where to find its switch in HushTelegram settings and whether it starts on or off.
• Telegram: Each patch's description in Morphe Manager now says which page of HushTelegram settings holds its switch, under the switch's own name when that differs, and whether it starts on or off. Nothing is hidden behind Expert mode: every patch but the two credential patches was already in the default selection, and the README's install steps now say so.
• Telegram: Expert mode's Chats group held 41 of the 55 patches. It's now split into groups you'd look in: Chats for the chat list, Conversations for inside a chat, Playback, Notifications, Theme, Interface, Stories and Search. Hide promotional banners and Hide Premium, gifts and Stars moved to Ads, and Disable update checks moved to Updates.
• Telegram: Strip link tracking's description now reads plainly. It still removes only the listed tracking keys and still starts off.

Tooling

• Tooling: The scripts that patch Telegram with the desktop CLI (the all-patches check, the release receipt and the selection matrix) now wait their turn in the build queue that BUILD_QUEUE_SCRIPT names, so they don't fight a Gradle build for the same cores. Release runs go to the front. Without a queue they run straight away and print a warning.
• Tooling: The pre-push hook now reads HUSHTELEGRAM_BUILD_WRAPPER and its other settings from your user environment when the shell has them empty, not only when they're missing, since pwsh keeps an empty variable around. With no wrapper at all, its own gradlew run waits in the build queue too.
• Tooling: The selection matrix reads the whole fixture APK for its hash twice a run, before the first case and after the last, instead of up to three times in each of its 74 cases. Each case still checks the APK's size and write time, and a changed APK still fails the run.
• Tooling: The patch tests that open the vendor Telegram APKs now run in their own Gradle task, :patches:fixtureTest. :patches:test still runs every patch test and passes --tests on to it, while :patches:test -x :patches:fixtureTest runs the rest without opening an APK. The release check counts the results from both folders.
• Tooling: The pre-push gate runs its cheap checks before the long fixture suite. After the script suites it checks the release facts right away when no code changed, then runs every Gradle task except the fixture tests, the advisory scan and the facts that read the runtime results, and only then the fixture tests. A broken script, lint error or stale fact now stops a push before any vendor APK is patched.
• Tooling: verify-all-patches.ps1 -KeepIn <dir> keeps a clean run's patched APK and CLI report, stamped with the commit and the hashes of the fixture, bundle, patch list and CLI. build-release-receipt.ps1 -AppliedDir <dir> reads a kept run whose stamp matches instead of patching that fixture a second time, and still runs every check on it. Anything that doesn't match gets patched as before.
• Tooling: Releases now run from scripts/release/release.ps1, one command per stage: prepare, preflight, build, publish and index. Each stage records the commit it finished on and won't start until the one before it has finished. A stage can be run again after a fix, and one that already finished checks its work and says so. Preflight is a five-minute check of the scripts, release text, facts and the patch tests without the fixture suite. Build runs the full tests, the bundle and every declared Telegram build once, and the receipt reads those runs. The release notes builder now lives in the repo too, and it carries every bullet of the version's CHANGELOG section and checks the published notes still do.

Install

1. Install Morphe Manager 1.34.0 or newer.
2. Add HushTelegram as a patch source: https://morphe.software/add-source?github=SysAdminDoc%2FHushTelegram
3. Get Telegram 12.10.6, version code 71129, from APKMirror's Telegram (Web version) page and pick the universal APK. It's telegram.org's own build. The Download button on telegram.org now gives you 13.0.0, so use the APKMirror link for this release. If you already have the official beta 12.10.7, build 71239, you can patch that instead. The patched app needs Android 9 or newer.
4. Coming from v0.0.11? Patch again and install over it with the same Morphe Manager signing key. New to HushTelegram? Uninstall the stock Telegram first, since Android won't put one over the other. Your chats come back when you sign in, but secret chats don't. Back up Morphe Manager's signing key after your first patch. You'll need it for every update.
5. If Telegram won't send you a login code, register your own app at my.telegram.org/apps. Use only letters and numbers in the short name. Then select Use registered Telegram API credentials, fill in apiId and apiHash, and patch again. The result installs over your current HushTelegram build. Keep both values private.
6. For notifications, open Telegram's Settings, then Notifications and Sounds, and turn on Keep-Alive Service and Background Connection.
7. To change HushTelegram's switches, open Telegram's Settings and tap HushTelegram settings.

The .mpp download is a patch bundle, not a Telegram APK. Installation instructions.

Validation

786 runtime tests and 364 patch tests passed locally, along with both Android lints. All 56 patches applied without forcing to Telegram 12.10.6 and to the 12.10.7 beta, build 71239. The release receipt checked each patched app's manifest, native libraries, resources and alignment.