This is the complete source code and the build instructions for the official alternative Android client for the Telegram messenger, based on the Telegram API and the MTProto secure protocol via TDLib.

• Telegram X on Google Play (subscribe to beta)
• APKs and Build Info
• Bot to verify APK hash

Build instructions

Prerequisites

• Repository must be fetched via git
• JDK or Android Studio (with compatible bundled JDK)
• At least 8GB of RAM
• At least 7,32GB of free disk space when cloning with --shallow-submodules --depth=1
• At least 2-5x times more disk space for files generated during build process.

macOS

• Homebrew
• git with LFS: $ brew install git git-lfs && git lfs install
• JDK: $ brew install openjdk@25
• rustup, then Rust of version.rust of version.properties with targets of Android: $ scripts/setup-rust.sh, which prints rust.dir for local.properties

Ubuntu

• git with LFS: # apt install git git-lfs
• Run $ git lfs install if you just installed git-lfs
• JDK: # apt install openjdk-25-jdk
• rustup: # apt install rustup, then Rust of version.rust of version.properties with targets of Android: $ scripts/setup-rust.sh, which prints rust.dir for local.properties. Run it again after a change of version.rust
• If multiple JDK versions are installed:
  # update-java-alternatives --list
# update-java-alternatives --set java-1.25.0-openjdk-amd64 (or other compatible version)

Windows

• MSYS2 (UCRT64 environment)
• Update packages: pacman -Syu
• Run pacman -S --needed git mingw-w64-ucrt-x86_64-git-lfs perl make diffutils
• Run git lfs install
• Run git config --global core.longpaths true
• rustup, then Rust of version.rust of version.properties with targets of Android: scripts/setup-rust.sh, which prints rust.dir for local.properties
• Clone the repository
• Set msys2.dir in local.properties after cloning
• Note: you have to use \\ or / as path separator in properties files

Building

1. $ git clone --recursive https://github.com/TGX-Android/Telegram-X tgx
2. In case you forgot the --recursive flag, cd into tgx directory and run: $ git submodule update --init --recursive
3. Open project via Android Studio or build manually from the command line: ./gradlew assembleLatestDebug
4. If build fails, follow the instructions provided in the error message.

Publishing

1. Obtain Telegram API credentials
2. Create local.properties file in the root project folder using any text editor:
   

   # Location where you have Android SDK installed
   sdk.dir=YOUR_ANDROID_SDK_FOLDER
   # Home of rustup with Rust of version.rust, printed by scripts/setup-rust.sh
   rust.dir=YOUR_RUSTUP_HOME_FOLDER
   # Telegram API credentials obtained at previous step
   telegram.api_id=YOUR_TELEGRAM_API_ID
   telegram.api_hash=YOUR_TELEGRAM_API_HASH

3. Setup Firebase and replace google-services.json with the one that's suitable for your app.id

Commands

scripts/setup.sh

./gradlew :app:validateGitSetup

./gradlew :app:installLatestDebug -Pabi=arm64

./gradlew :app:assembleLegacyDebug -PuseLegacyNdk=true -Pabi=arm32

./gradlew :app:buildLibvpx
./gradlew :app:buildFfmpeg
./gradlew :app:buildTlottie

ANDROID_SERIAL=<device> ./gradlew ":app:generateTlottieProfile[arm64-v8a]" -Ptlottie.samples=<samples>

Reproducing public builds

In order to verify that there is no additional source code injected inside official APKs, you must use one of the following versions of Ubuntu:

• 21.04: for builds published before 26th May 2023
• 22.04.2 LTS: for builds published before 27th September 2025
• 24.04 LTS: for builds published before 1st October 2026
• 26.04 LTS: for any newer releases

And update its configuration:

1. Create user called vk with the home directory located at /home/vk
2. Clone tgx repository to /home/vk/tgx
3. Check out the specific commit you want to verify
4. In rare cases of builds that include unmerged pull requests, you must follow actions performed by Publisher's fetchPr and squashPr tasks
5. cd into tgx folder and install dependencies: # apt install $(cat reproducible-builds/dependencies.txt), then Rust with its targets of Android by scripts/setup-rust.sh as in the requirements above
6. Follow up the build instruction from the previous section
7. Run $ apkanalyzer apk compare --different-only <remote-apk> <reproduced-apk>
8. If only signature files and metadata differ, build reproduction is successful.

Verifying side-loaded APKs

If you downloaded Telegram X APK from somewhere and would like to simply verify whether it's an original APK without any injected malicious source code, you need to get checksum (SHA-256, SHA-1 or MD5) of the downloaded APK file and find whether it corresponds to any known Telegram X version.

In order to obtain SHA-256 of the APK:

• $ sha256sum <path-to-apk> on Ubuntu
• $ shasum -a 256 <path-to-apk> on macOS
• $ certutil -hashfile <path-to-apk> SHA256 on Windows

Once obtained, there are three ways to find out the commit for the specific checksum:

• Sending checksum to @tgx_bot
• Searching for a checksum in @tgx_log. You can do so without need in installing any Telegram client by using this URL format: https://t.me/s/tgx_log?q={checksum} (click to see in action). Note: unpublished builds cannot be verified this way.

License

Telegram X is licensed under the terms of the GNU General Public License v3.0.

For more information, see LICENSE file.

License of components and third-party dependencies it relies on might differ, check LICENSE file in the corresponding folder.

Third-party dependencies

List of third-party components used in Telegram X can be found here. Additionally you can check the specific commit of the third-party component used, for example, here and here.

Contributions

Telegram X welcomes contributions. Check out pull request template, code style and guide for contributors to learn more about Telegram X internals before creating the first pull request.

If you are a regular user and experience a problem with Telegram X, the best place to look for solution is Telegram X chat — a community with over 4 thousand members. Please do not use this repository to ask questions: if you have general issue with Telegram, refer to FAQ or contact Telegram Support.