jqssun/android-titanium-browser

Titanium Browser for Android

A secure and fully open-source, Chromium-based web browser with support for extensions, based on Vanadium by GrapheneOS. This project was formerly known as Helium Browser for Android but was later renamed to avoid branding confusion. To maintain a fast and native experience for everyone, advanced features are modularized into Titanium Extension for Android.

For the latest builds, see Releases. You can also update between GitHub and Google Play releases seamlessly.

Usage

Installing Extensions

For Chrome extensions, navigate to Chrome Web Store, enable Desktop site using the menu button ⋮ in the top right corner, and proceed as normal.

For Opera Add-ons, Microsoft Edge Add-ons, or other marketplaces, targeted User Agent modifications may be required. See Titanium Extension for Android for instructions.

You can also load an unpacked extension manually by navigating to the Manage extensions page or chrome://extensions. Enable Developer mode, select Load unpacked, and choose the folder containing the extension in the Storage Access Framework (SAF) picker. Manifest V2 (MV2) extensions are supported. It may take a moment for the extension to load.

Using Extensions

To run an extension in Incognito (OTR) mode, go to Manage extensions, find the extension you want to use in Incognito mode, select Details, and turn on Allow in Incognito.

For advanced features including external download manager support, enhanced dark mode, and additional privacy options, you can use Titanium Extension for Android.

Debug URLs

To view and access the debug URLs, use chrome://chrome-urls. For Experiments, use chrome://flags.

WebRTC IP Policy

The option is available by using the menu button ⋮ in the top right corner, then selecting Settings, Privacy and security. If you experience issues with WebRTC due to IPs being shielded by default (e.g. Discord Voice), try changing it to Default public interface only, or Default.

Implementation

[!WARNING]

Titanium Browser for Android only attempts to improve security and privacy where possible. For better protection on Android, you should instead use GrapheneOS with Vanadium, which additionally integrates patches into Android System WebView and provides significant kernel and memory management hardening on the OS level.

---
config:
  layout: dagre
---
flowchart TD
 subgraph s1["Additional Patches"]
        n5["Feature Overrides"]
        n6["UI Overrides"]
        n7["Manifest V2 + Secure Off Store Install Support"]
        n8["Miscellaneous Fixes + Improvements"]
  end
 subgraph s2["Vanadium"]
        n9["Generic Patches
patches/*.patch"]
        n10["Subprojects Patches
subprojects_patches/**/*.patch"]
  end
 subgraph s3["Titanium Browser for Android"]
        n11["GN Build Configuration
args.gn"]
        n12["Signed Release"]
  end
    n1["Chromium"] --> s1 & s2
    n5 --> n6
    n6 --> n7
    n7 --> n8
    s1 --> s3
    s2 --> s3
    n11 --> n12
    n5@{ shape: subproc}
    n6@{ shape: subproc}
    n7@{ shape: subproc}
    n8@{ shape: subproc}
    n9@{ shape: subproc}
    n10@{ shape: subproc}
    n11@{ shape: subproc}
    n12@{ shape: subproc}
    n1@{ shape: rounded}
    classDef Aqua stroke-width:1px, stroke-dasharray:none, stroke:#46EDC8, fill:#DEFFF8, color:#378E7A
    style n5 stroke:#FF6D00
    style n7 stroke:#FF6D00

Building

All releases are built using Actions. Current releases can also be attested using GitHub CLI.

gh attestation verify *.apk -R jqssun/android-titanium-browser

This repository provides the build script to compile on the latest Ubuntu, and may also work with other Linux distributions.

To build these releases yourself via CI (e.g. GitHub Actions), fork this repository. Supply your base64 encoded keystore.jks and local.properties (containing keyAlias, keyPassword and storePassword) to Repository secrets under Settings > Secrets and variables > Actions. To generate a release, go to Actions, select Build, and select Run workflow. Under Runner, you can either use a GitHub-hosted runner by entering ubuntu-latest, or self-hosted for your own hardware.

Credits

This project would not have been possible without the huge community contributions from Vanadium, and without the privacy-focused, open-source approach shared by various other Chromium projects. All credit goes to the original authors and contributors. This project started around the same time as Helium Browser for Linux but it is not affiliated with the desktop Helium project.