Skip to content

v0.0.19

Choose a tag to compare

View all tags
@SysAdminDoc SysAdminDoc released this 17 Oct 22:47
· 56 commits to main since this release
v0.0.19
3446c0c

HushTelegram v0.0.19 has 67 patches for Telegram 13.0.3, and it patches two builds now. One is telegram.org's (org.telegram.messenger.web, version code 71839). The other is the build from Google Play (org.telegram.messenger, version code 71831), the one most people already have on their phone. Sixty-three are selected by default, and every new switch starts off. The last release only knew telegram.org's build, so Morphe Manager turned the Play APK away with "Wrong package selected." Now either one patches, and telegram.org's build works exactly as it did. The official beta isn't a target anymore. If you're on it, move to telegram.org's build or the Play one before you patch. The first time you sign in, Telegram may turn down the API ID that ships with any patched build and show API_ID_PUBLISHED_FLOOD, so no login code arrives. It's the same on every patched Telegram, HushTelegram included. The one-time fix is to register your own Telegram API credentials, and the steps are under Install.

What's new

  • Telegram: The Google Play version of Telegram 13.0.3 (org.telegram.messenger, version code 71831) can be patched now. That's the APK APKMirror and Uptodown carry, and Morphe Manager used to turn it away with "Wrong package selected" because it only knew telegram.org's build. telegram.org's build still works the same way.
  • Telegram: Repair Firebase push registration also covers the Play build, so its notifications sign up with Google like they do on telegram.org's build.
  • Telegram: The official Telegram beta isn't a target anymore. Turn off beta debug logs is gone with it, and so is the part of Disable analytics that only stopped the beta's crash and session reports. If you're on the beta, switch to telegram.org's build or the Play build before you patch.

Tooling

  • Tooling: The release's clean-APK check accepts the Google Play build as a vendor baseline. It now asks that the signing certificate the catalog declares for the package be present on the APK, and it allows the extra certificate Google Play App Signing adds. Before, it required every certificate on the APK to be one the catalog declared, so the Play build's Google certificate stopped the release even though the patcher applied every patch to it.

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 13.0.3. Two builds work: telegram.org's Download button (org.telegram.messenger.web, version code 71839) and the Google Play build (org.telegram.messenger, version code 71831), the one most people already have, which APKMirror and Uptodown also carry. The patched app needs Android 9 or newer.
  4. Coming from an earlier HushTelegram on telegram.org's build? Patch the new 13.0.3 APK and install it over your current HushTelegram with the same Morphe Manager signing key. On the beta? It isn't a target now, so switch to telegram.org's build or the Play build, patch that, and install it fresh, since it's a different app than the beta and Android won't put one over the other. New to HushTelegram? Uninstall the stock Telegram first, for the same reason. 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 turns down your login code with API_ID_PUBLISHED_FLOOD, that's Telegram refusing the public API ID that ships with any patched build, the Play one included. Register your own app at my.telegram.org/apps, using 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. Want HushTelegram's own icon, or Telegram's logo in white on the black launch screen? Turn on Expert mode in Morphe Manager and pick HushTelegram icon and name or Black and white launch logo before you patch.
  7. For notifications, open Telegram's Settings, tap Notifications, and turn on Keep-Alive Service and Background Connection under Other, near the bottom of the page. Phones where Firebase notifications don't come through can also try the UnifiedPush notifications switch on HushTelegram's Notifications page with a UnifiedPush app like ntfy.
  8. To change HushTelegram's switches, open Telegram's Settings and tap HushTelegram settings, or press and hold the Telegram title at the top of your chat list. The side menu is the Side menu switch on the Chat list page.

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

Validation

All 1348 runtime tests passed locally, and all 481 patch tests passed too, along with both Android lints (the shared library and the Telegram extension). Every one of the 67 patches applied to Telegram 13.0.3 without forcing, on both telegram.org's build (version code 71839) and the Google Play build (version code 71831). For each patched build the release receipt checked the package name, version, manifest, native libraries and zip alignment. The Google Play build was also installed on a clean Android 13 system and launched straight to Telegram's sign-in screen with no crash.

Assets 6
Loading