GitHub Kotlin Daily Trending Repositories

HuangZhuoRui/LocationSpoofer

虚拟定位软件，主要是定位，集成了 WiFi、蓝牙、基站等方案，主要有定点模拟和路线模拟。非全局方案，需要单独 hook 对应的软件(因为不想单独去适配各大手机厂商的系统)，

LocationSpoofer

基于 KernelSU + LSPosed 的 Android 系统级虚拟定位与无线环境伪装框架

Android system-level location spoofing and wireless environment simulation framework based on KernelSU + LSPosed

📢 加入我们的 Telegram 交流群进行~~技术探讨、催更、~~吹牛逼、搞抽象。

📖 查看 LocationSpoofer 详细使用教程

项目简介

在现代 Android 系统的风控与反作弊环境中，传统的“模拟位置（Mock Location）”开发者选项已被商业 SDK（如高德风控、腾讯安全、百度定位、网易易盾、各类考勤及打卡风控系统）列为高风险特征。这类检测机制不仅验证 isFromMockProvider / isMock 标志位，还会主动采集并交叉比对设备所处的周围物理环境：

Wi-Fi 接入点与 BSSID 列表（比对 Wi-Fi 信号指纹库）
移动蜂窝基站数据（GSM / WCDMA / LTE / 5G NR 小区指纹与运营商信息）
周围 BLE 蓝牙信标
底层 GNSS 卫星分布与可见卫星星历
加速度计与计步器传感器联动状态
对连续定位坐标序列进行傅里叶变换（FFT）或离散度分析，识别非自然的静态固定点或机械式等速直线轨迹。

LocationSpoofer 是专为应对深度风控检测而设计的系统级虚拟定位与无线环境模拟方案。项目基于 KernelSU / APatch / Magisk 获取底层 Root 权限，并利用 LSPosed (libxposed API 101+) 框架在 Zygote 阶段注入目标应用进程，以高物理契合度拦截并伪造所有与位置、卫星、基站、Wi-Fi、蓝牙、传感器相关的底层 API 响应，确保应用获取自洽且真实的虚假环境指纹。

功能特性

┌─────────────────────────────────────────────────────────────────────────┐
│                             LocationSpoofer                             │
│                    系统级虚拟定位与无线环境模拟                         │
└─────────────────────────────────────────────────────────────────────────┘
        │                            │                            │
        ▼                            ▼                            ▼
  【空间定位与物理仿真】       【无线电与传感器模拟】         【反检测套件】
  • 三地图引擎自由切换         • Wi-Fi 扫描与连接态伪装       • Xposed 堆栈调用帧清洗
  • WGS-84/GCJ-02/BD-09 自适应 • 2G-5G NR 蜂窝基站小区模拟   • ClassLoader 探测隔离
  • Ornstein-Uhlenbeck 抖动    • BLE 蓝牙信标扫描过滤         • isFromMockProvider 抹除
  • 步态横向摇摆与高斯噪声     • WiGLE / OpenCellID 云端导入  • AppOps OP_MOCK_LOCATION 隐藏
  • 真实路网拟合与红绿灯停候   • 空间反距离加权 (IDW) 插值    • Settings.Secure 开关覆写
  • 悬浮窗遥控阻尼摇杆         • 步频与计步传感器联动         • MultiDex 动态 Class 拦截

1. 多地图引擎与坐标系适配

三引擎自由切换：集成高德 3D 地图 (AMap)、百度地图 (BaiduMap) 与 Google Maps，满足境内外不同场景下的路网检索与 POI 选点需求。
开箱即用与全语言支持：默认“自动匹配”在所有语言（包括中文、英文、阿拉伯语等）环境下均稳定选用高德地图，无需 Google 服务或特殊网络即可顺畅使用。
Google 地图自定义 Key：App 不内置任何 Google Maps 默认密钥；如需使用 Google 地图渲染与 Places 全球搜索，只需在“设置”中填入您自行申请的 Google API Key 即可。
智能坐标系自适应（Smart Auto）：
- 系统原生接口统一输出标准 WGS-84 物理坐标与卫星数据；
- 各大地图定位 SDK（高德/腾讯/百度）及视图渲染层（如百度地图蓝点 MyLocationData）自动映射对应坐标系（GCJ-02 / BD-09），规避坐标偏移与 (0.0, 0.0) 兜底问题；
- 支持在“配置应用坐标系”中为目标应用强制指定 WGS-84、GCJ-02 或 BD-09。
零延迟计算：Hook 阶段直接从预计算的内存数据读取坐标，避免高频回调中的重复三角函数开销。

2. GPS 物理抖动与步态模拟

真实 GPS 芯片输出的坐标因电离层延迟、多径效应及接收机热噪声，天然具有高斯分布的白噪声特征。

Ornstein-Uhlenbeck 随机过程：引入物理学均值回归随机过程模型来生成自然位置抖动，其状态随机微分方程定义为：

$$\mathrm{d}X_t = -\alpha X_t \mathrm{d}t + \sigma \mathrm{d}W_t$$

其中 $\sigma$ 为漂移强度，$\alpha$ 为均值回归系数（设定为 0.05，即每秒将当前漂移拉回 5%）。它产生符合物理规律的低频缓慢漂移，并在 3-Sigma 原则下严格有界（硬性限制在 4 米内），防止漂移发散引发异常。
步频横向抖动（Gait Jitter）：步行或跑步模式下，引擎沿当前移动方向的正交横向上施加高斯横向位移：

$$\Delta L_{\text{lateral}} = 0.15 \cdot \mathcal{N}(0, 1) \quad (\text{米})$$

模拟人类真实行走时身体左右晃动的步态特征。
高度（Altitude）与精度（Accuracy）慢漂移：精度值与海拔高度动态波动，模拟大气对流层延迟与卫星几何分布的自然变化。

3. 反检测与 MultiDex 支持

调用栈深度清洗（Stack Traces Scrubbing）：拦截 Throwable.getStackTrace 和 Thread.getStackTrace，自动过滤移除包含 de.robv.android.xposed、io.github.libxposed、org.lsposed 等特征调用帧，阻止反作弊 SDK 在异常堆栈回溯中嗅探 Hook 框架。
类加载器探测隔离：拦截 Class.forName 和 ClassLoader.loadClass，对 Xposed 特征类名的探测统一返回 ClassNotFoundException。
MultiDex 动态感知：拦截 ClassLoader.loadClass 动态捕获并安装次级 Dex（如 classes16.dex）中的定位组件，配合 /proc/self/cmdline 锁定宿主进程主包名，避免内嵌 WebView 或插件改变全局上下文。
Mock 属性彻底抹除：
- Location.isFromMockProvider() 和 Location.isMock() 永久覆写为 false；
- 反射将 Location 内部字段 mMock 和 mIsFromMockProvider 重写为 false，并移除 Extra Bundle 中的 mockLocation 标记；
- 拦截 AppOpsManager 的 OP_MOCK_LOCATION (58) 权限查询，返回 MODE_IGNORED (1)；
- 拦截 Settings.Secure 中 mock_location 及 allow_mock_location 的读取，返回 0；
- 隐藏 LocationManager 中的虚拟 Test Provider，将其统一伪装为系统原生 gps 提供者。

4. Wi-Fi、基站与蓝牙环境模拟

实地扫街扫描器（EnvironmentScanner）：后台自动扫描物理世界中的 Wi-Fi 接入点（SSID/BSSID/RSSI/频率/信道/Wi-Fi标准）、基站小区信息（GSM, WCDMA, CDMA, LTE, 5G NR 及 dbm 信号强度）以及附近 BLE 蓝牙信标。
空间反距离加权（IDW）插值：在 Room 数据库中检索周边 50 米范围内的历史采集点，使用反距离平方比作为权重：

$$w_i = \frac{1}{d_i^2}$$

对 Wi-Fi RSSI 信号强度与蜂窝小区 dbm 信号进行平滑插值，保证移动过程中信号连续渐变。
无线电数据精细化管理与手动指定：
- 支持在“管理采集数据”页面中手动指定具体使用的 Wi-Fi、基站或蓝牙条目；
- 支持自定义修改 Wi-Fi SSID、BSSID、RSSI 信号强度、信道频段、加密类型以及基站小区数据；
- 支持在主页地图点选锁定特定环境数据，超出设定范围自动恢复环境插值计算。
Wi-Fi 与基站全接口模拟：
- 拦截 WifiManager.getScanResults()、getConnectionInfo()、getConfiguredNetworks()、getDhcpInfo()；
- 拦截 TelephonyManager.getAllCellInfo()、getCellLocation()、getNetworkOperator()、getServiceState()、getSignalStrength()、PhoneStateListener、TelephonyCallback；
- 采用真实品牌合法 OUI（TP-Link、Huawei、Xiaomi、Cisco 等）生成非采集区的虚拟 MAC 地址。
云端数据导入 (WiGLE & OpenCellID)：支持配置 WiGLE API 与 OpenCellID API，在线拉取全球指定坐标周边的真实物理 Wi-Fi 与移动基站，自动入库缓存并离线复用。
海量数据空间索引：采用空间索引与分页机制，支持高效检索与存储数千条本地与云端无线电记录，保障界面与后台运行流畅。

5. 卫星矩阵与 NMEA 模拟

GnssStatus 矩阵注入：Hook 系统的 GnssStatus 类，模拟 20+ 颗包括 GPS、北斗、GLONASS 的卫星分布矩阵，注入 PRN 标识、信噪比（CNR）、俯仰角、方位角等，并正确汇报 usedInFix 状态。
NMEA 语句流动态拼装：劫持 OnNmeaMessageListener / GpsStatus.NmeaListener，根据当前模拟坐标、航向角、速度和卫星信息，动态拼装符合规范的原始 $GPGGA, $GPRMC, $GPGSA, $GPGSV 语句并计算校验和（Checksum）输出。
卫星元数据保活注入：在向各大地图 SDK 派发 Location 对象时，强制在 getExtras() 中注入 satellites=20, satellites_in_view=20, satellites_used_in_fix=18，防止定位 SDK 判定无卫星搜星而丢弃 GPS 信号。

6. 传感器与步频模拟

计步传感器联动：Hook SensorManager，接管 Sensor.TYPE_STEP_COUNTER（总步数）和 Sensor.TYPE_STEP_DETECTOR（单步脉冲）。
步态频率计算：当开启路线模拟且处于步行或跑步状态时，根据移动距离与步长（默认按 0.7m/步 换算）自动生成平滑递增的步数事件，适配运动健康与校园跑打卡软件。

7. 路线规划与红绿灯模拟

真实路网拟合：支持多点路径规划，调用路网搜索算法拟合实际道路轮廓，防止直线穿墙。
红绿灯智能识别与驻留：路线规划自动解析红绿灯路口，行进到红绿灯点时自动停驻 15 秒再重新平滑加速起步。
悬浮窗遥控摇杆：提供悬浮窗虚拟摇杆，支持 0 ~ 10 m/s 速度无级调节与航向角阻尼转向。

8. 用户界面

基于 Jetpack Compose 构建，采用现代毛玻璃质感、内阴影与阻尼手势拖拽设计，实现完全模块化与解耦的组件架构。

系统架构

本项目采用 MVVM + Clean Architecture，并按职责拆分为 6 个 Gradle 模块：

模块	类型	职责
`app`	Android App	宿主壳工程：`Application` / `MainActivity`、签名与打包配置、聚合各模块的 Koin DI；仅把 `xposed` 模块的产物（`LocationHooker` 类与 `META-INF/xposed/` 元数据）打进最终 APK 供 LSPosed 扫描加载，自身不直接调用*其代码
`app-ui`	Android Library	全部 Jetpack Compose UI：页面、弹窗、自研“液态玻璃”组件（`ui/liquid`）与 ViewModel 层
`service`	Android Library	前台保活服务 `SpoofingService`、悬浮摇杆 `FloatingJoystickService`、开机自启广播等后台/服务层
`xposed`	Android Library	LSPosed / Xposed 注入模块本体：`LocationHooker` 入口 + `hooks/`、`hooks/network/` 下的各类 Hook 实现
`core-data`	Android Library	`app` / `app-ui` / `service` 三端共用的数据与业务层：Room 数据库、各类 Repository，以及 `ConfigManager`、`RootManager`、`EnvironmentScanner` 等核心工具类
`core-geo`	纯 Kotlin/JVM	全项目唯一不依赖 Android 的模块：坐标系换算、路线几何与运动真实度引擎，以及 Hook 端与 App 共用的系统识别规则（`vendor/`）

两个变体统一通过 libxposed 的远程配置通道传递 JSON，Hook 从内存缓存读取：

┌─────────────────────────────────────────────────────────────────────────┐
│     LocationSpoofer 宿主进程（app / app-ui / service / core-data）      │
│  ┌─────────────────────────┐  ┌──────────────────────────────────────┐  │
│  │     Triple Map Engine   │  │          RouteStateMachine           │  │
│  │ (AMap / Baidu / Google) │  │     (IDLE / READY / RUN / PAUSE)     │  │
│  └────────────┬────────────┘  └──────────────────┬───────────────────┘  │
│               │                                  │                      │
│  ┌────────────▼──────────────────────────────────▼───────────────────┐  │
│  │                    ConfigManager（core-data）                     │  │
│  │     序列化配置与坐标系映射，通过框架发布完整配置快照     │  │
│  └──────────────────────────────────┬────────────────────────────────┘  │
│  ┌──────────────────────────────────▼────────────────────────────────┐  │
│  │                    SpoofingService（service）                     │  │
│  │           前台保活服务、悬浮摇杆控制器与路网 / 步态计算           │  │
│  └───────────────────────────────────────────────────────────────────┘  │
└─────────────────────────────────────┬───────────────────────────────────┘
                                      │ (ConfigManager 发布远程偏好 / 远程文件)
                                      ▼
               ┌─────────────────────────────────────────────┐
               │ 框架管理的远程偏好 / 配置文件 │
               └──────────────────────┬──────────────────────┘
                                      │ (框架通知 → 后台解码 → 原子更新内存缓存)
                                      ▼ LSPosed / libxposed (API 101+) 注入
┌─────────────────────────────────────────────────────────────────────────┐
│                              目标 App 进程                              │
│  ┌───────────────────────────────────────────────────────────────────┐  │
│  │                         LocationHooker                            │  │
│  │  • Location/GNSS：BaseLocationHooker、GnssStatusHooker 等         │  │
│  │  • 地图 SDK：AMapHooker / BaiduMapHooker / TencentMapHooker       │  │
│  │  • hooks/network/：Wifi* / Cellular* / Bluetooth*Hooker 等        │  │
│  │  • SensorStepHooker（计步）/ AntiDetectionHooker（反检测）        │  │
│  └───────────────────────────────────────────────────────────────────┘  │
└─────────────────────────────────────────────────────────────────────────┘

Note

跨进程通信 (IPC) 设计： ConfigManager 使用 XposedService.getRemotePreferences() 发布完整 JSON 快照；UTF-8 配置超过 128 KiB 时先写入框架管理的独立远程文件，再原子发布文件指针，避免大配置占满 Binder 事务。全局与非全局版共用这一通道，无需修改 SELinux 策略或向公共临时目录写配置。 Hook 在模块加载时获取初始快照并注册配置变化监听，由后台线程解码、归一化后替换内存缓存；Hook 调用只读缓存。后台每秒检查框架偏好的内存快照以重试启动时的失败，路线派发和服务发现仍由独立定时器执行。 App 私有偏好保存最新期望状态，发布失败自动重试，框架重连后重新发布；停止或暂停请求不会被较早的活动配置覆盖。新通道发布成功后会清理旧配置、探针及脚本。框架仍负责配置持久化，此方案并非完全不落盘。需要框架实现远程配置能力。升级后安装对应变体、启用模块并重启设备，再开始模拟；全局版可在“系统适配 → Hook 运行状态”检查配置来源为 libxposed:remote-preferences 或 libxposed:remote-file，并核对各进程的发布时间。此次通道迁移尚需真机复验。

系统适配（全局方案）

全局方案直接 Hook 系统服务，不同厂商 / 系统版本的内部实现不一样，需要逐个适配：

ADAPTATION_PROGRESS.md：各系统、机型在两个方案下的实机验证进度（App 内"系统适配 → 完整适配进度"显示的就是这份文件）；
vendor/README.md：适配框架说明与新增一个系统的完整检查清单；
xposed/ADAPTATION_GUIDE.md：如何在真机上定位系统内部类与方法、如何根据 App 内"Hook 运行状态"页排查适配问题。

环境要求

系统版本：Android 8.0 (API 26) 及以上
Root 方案：已获取 Root 权限（推荐 KernelSU / APatch / Magisk）。
Xposed 框架：已安装并激活 LSPosed (API 101+) 或兼容 libxposed API 101+ 的框架环境。

使用指南

1. 编译与安装

# 1. 克隆代码仓库
git clone https://github.com/your-username/LocationSpoofer.git

# 2. 编译 Debug APK 并直接安装到设备
./gradlew installDebug

2. 权限与激活

打开 KernelSU / APatch / Magisk 管理器，授予 LocationSpoofer Root 权限。
打开 LSPosed 管理器，在模块列表中找到 LocationSpoofer 并启用。
在模块的作用域（Scope）中，勾选需要进行定位伪装的目标应用（如微信、企业微信、钉钉、超星学习通、百度地图、高德地图等）。
强行停止勾选的目标 App（或重启手机）以使其加载 Hook 逻辑。

3. 常见场景

定点模拟与环境锁定

启动 LocationSpoofer，在主页地图上拖动准星或搜索栏搜索目标位置。
在底部抽屉开启所需伪装开关：伪造 Wi-Fi、模拟基站、模拟蓝牙、模拟传感器计步、开启随机抖动。
点击“启动模拟”接管系统 GPS。
如需锁定使用具体的本地采集点，可在“管理数据”中点击对应采集点进行锁定绑定。

路线模拟

切换至“路线规划”标签页，在地图上依次标记多个路点。
设定移动模式（循环 / 往返 / 单程）以及速度档位（步行、跑步、骑行、自驾或自定义速度）。
开启 “使用真实路线规划”（系统将自动拉取真实道路轮廓并标记红绿灯等待节点）。
点击“开始模拟”。可随时开启“悬浮窗摇杆”在前台微调坐标与速度。

实地采集与数据自定义

开启“设置” -> “环境图谱与扫街” 模式，手机将在后台记录沿途的真实 Wi-Fi、基站与蓝牙信标。
进入“管理采集数据”页面，可查看列表、编辑备注，或手动指定/修改某条 Wi-Fi（如 SSID、BSSID、RSSI 等）或基站小区数据。
支持将采集到的无线电指纹一键导出为 JSON 文件，用于备份或共享导入。

独立应用坐标系配置

若遇到特定 App 存在固定坐标偏移：
- 进入 LocationSpoofer “设置” -> “配置应用坐标系”；
- 添加目标应用包名；
- 将坐标系指定为 WGS-84、GCJ-02 或 BD-09，Hook 层将自动根据目标 App 进行转换。

技术栈

编程语言：100% Kotlin
模块划分：app / app-ui / service / xposed / core-data / core-geo 六个 Gradle 模块（详见系统架构）
UI 框架：Jetpack Compose & Material Design 3，叠加第三方 Miuix（top.yukonga.miuix.kmp）提供的毛玻璃模糊底层能力，并在此之上自研 ui/liquid 组件包（改编自开源项目 AndroidLiquidGlass / ILoveWork，Apache-2.0）实现悬浮底栏、透镜折射与阻尼拖拽等 Liquid Glass 交互效果
依赖注入：Koin，按模块拆分为 coreDataModule / serviceModule / viewModelModule 三个子模块，由 app 模块的 appModules 统一聚合注册
持久化存储：Room Database (SQLite) + 空间索引（core-data 模块）
网络与序列化：OkHttp 3 + Kotlinx Serialization
地图组件：AMap 3DMap SDK / BaiduMap SDK / Google Maps & Places SDK
Xposed 框架：LSPosed API 101+ / libxposed (Service 模式)，Hook 实现位于 xposed 模块的 hooks/ 与 hooks/network/ 子包

免责声明

本程序仅供学习研究、技术交流以及个人合法合规测试（如开发者定位测试、设备兼容性调试）使用。使用者请勿将本工具用于任何违法违规或违反相关平台服务协议的活动（包括但不限于虚假打卡、网络考试作弊、商业欺诈等）。使用本模块造成的任何账号封禁、数据丢失、法律纠纷或其他直接/间接损失，均由使用者自行承担，作者不对此承担任何责任。

开源协议

本项目基于 GNU General Public License v3.0 协议开源。

Copyright (C) 2026 SuseOAA

KernelSU-Next/KernelSU-Next

An advanced Kernel based root solution for Android

https://kernelsu-next.github.io/webpage/

KernelSU Next

A kernel-based root solution for Android devices.

🚀 Features

Kernel-based su and root access management.
Module system based on Magic Mount and OverlayFS.
App Profile: Limit root privileges per app.

✅ Compatibility

KernelSU Next supports Android kernels from 4.4 up to 6.12.

Kernel version	Support notes
5.10+ (GKI 2.0)	Supports pre-built images and LKM/KMI
4.19 – 5.4 (GKI 1.0)	Requires KernelSU driver built-in
< 4.14 (EOL)	Requires KernelSU driver (3.18+ is experimental and may need backports)

Supported architectures: arm64-v8a, armeabi-v7a and x86_64

Caution

Recent kernel versions have implemented a breaking change causing KernelSU Next to fail and potentially trigger a kernel panic on x86_64! Check the website for more info!

📦 Installation

Please refer to the Installation guide for setup instructions.

🏅 Contribution

Go to our Crowdin to submit a translation for the manager!
To report security issues, please see SECURITY.md.

📜 License

/kernel directory: GPL-2.0-only.
All other files: GPL-3.0-or-later.

💸 Donations

If you'd like to support the project:

USDT (BEP20, ERC20): 0x0b269716dc00692676e4217e23c7f67abd5f0f3e
USDT (TRC20): TXu6VX8dvJLQPx4WBobjbYT5tefHTDikWo
LTC: LMYRqRXPKAFpYncBhNS44W1iwFit14LH1u

🙏 Credits

Kernel-Assisted Superuser – Concept inspiration
Magisk – Core root implementation
Genuine – APK v2 signature validation
Diamorphine – Rootkit techniques
KernelSU – The original base that made KernelSU Next possible
Magic Mount Port – For Magic Mount support

tiann/KernelSU

A Kernel based root solution for Android

https://kernelsu.org

KernelSU

A kernel-based root solution for Android devices.

Features

Kernel-based su and root access management.
Module system based on metamodules: Pluggable infrastructure for systemless modifications.
App Profile: Lock up the root power in a cage.

Compatibility state

KernelSU officially supports Android GKI 2.0 devices (kernel 5.10+). Older kernels (4.14+) are also supported, but the kernel will need to be built manually.

With this, WSA, ChromeOS, and container-based Android are all supported.

Currently, the arm64-v8a and x86_64 architectures are supported.

Caution

Recent kernel versions have implemented a breaking change causing KernelSU to fail and potentially trigger a kernel panic on x86_64! Check the website for more info!

Usage

Translation

To help translate KernelSU, we no longer accept translation contributions via Weblate. All translations are now handled using LLMs.

If you would like to add support for a new language, feel free to open a PR. Please note that modifications to existing English and Chinese translations are not accepted.

Discussion

Telegram: @KernelSU

Security

For information on reporting security vulnerabilities in KernelSU, see SECURITY.md.

License

Files under the kernel directory are GPL-2.0-only.
All other parts except the kernel directory are GPL-3.0-or-later.

Credits

Kernel-Assisted Superuser: The KernelSU idea.
Magisk: The powerful root tool.
genuine: APK v2 signature validation.
Diamorphine: Some rootkit skills.

sk2andy/candy-browser

Gesture-first Android browser with Material 3 Expressive design and local privacy tools

Candy Browser

Firefox extensions on Android, powered by GeckoView.
A gesture-first browser with selectable GeckoView and Android System WebView engines, an iOS WKWebView/Liquid Glass target, and local privacy tools.

GitHub Pages website · Privacy · Releases

Note

Next release: stability fixes. I'm focusing on finding and fixing as many bugs as possible and testing the changes over an extended period to make Candy Browser more reliable.

🎉 Firefox extensions on Android

Candy uses GeckoView by default and supports Mozilla-signed Firefox extensions directly inside the Android app. A fresh Gecko profile comes with uBlock Origin and I still don't care about cookies, while additional compatible extensions can be installed and managed from Candy's browser settings.

Extension actions, popups, options, permissions, updates, and enable/disable controls stay inside Candy's browser chrome. See Platform engines for the supported GeckoView integration and current compatibility boundaries.

Cross-device sync

Candy Sync turns every connected Android, Chromium, or Firefox device into a writable profile. Open a desktop profile on your phone to inspect its live tab list, open new tabs, navigate, pin, reorder, or close them. The same small tab changes flow back to every connected client instead of re-uploading the complete browser state.

Changes are encrypted locally and written to a durable outbox. REST commits provide ordered, retry-safe storage; authenticated WebSocket notifications deliver committed changes immediately. After suspension or network loss, clients recover missing changes through REST.

E2EE in short

The first client creates a random 256-bit workspace key. The immutable passphrase derives a local recovery key with Argon2id; HKDF-SHA-256 derives purpose- and device-specific keys, and AES-256-GCM encrypts and authenticates tab data. Every device also creates its own P-256 private key locally. The passphrase, workspace key, private keys, URLs, titles, device names, and icons never reach the server in plaintext—the server stores ciphertext plus the routing metadata required for sync.

Start Candy Sync

cd sync/server
cp .env.example .env
# Set a unique username, password, public URL, and TLS host in .env.
# Never put the E2EE passphrase in server configuration.
docker compose pull candy-sync
docker compose up -d

The public sk2andy/candy-sync:latest image supports Linux AMD64 and ARM64. Contributors can still build the server locally with docker compose up --build -d.

Build and load the WebExtension from sync/extension/, open its browser-managed Options Page, and enter the endpoint plus an E2EE passphrase. In Candy Browser, open Settings → Synchronization and join with the same endpoint, credentials, and passphrase.

See the Candy Sync guide for server deployment, local TLS, Chromium/Firefox loading, Android setup, backups, protocol details, and the full security model.

Candy Sync roadmap

Add multi-user support
Publish the extension to the Chrome Web Store and Mozilla Add-ons
Publish a prebuilt server image to Docker Hub
Offer a hosted solution for people who do not want to self-host

See Candy in motion

Watch or download the 16:9 feature showcase (MP4, 60 fps)

After its gesture-first opener, the showcase moves straight to the Android engine choice and Firefox extensions. It then combines self-hosted Android/Chromium/Firefox tab sync with E2EE, live API 36 emulator footage, current Topping scripts, and repository screenshots to show Link Peek, Spoilerfree Sports, Hacker News Comfort, Privacy X-Ray, Reader Studio, Candy Trails, and profiles. Its original soundtrack, kinetic typography, and camera motion are generated entirely from repository-owned sources.

Why Candy?

Made for gestures. Switch tabs from the address bar on phones, use a scrollable tab strip on wider screens, swipe into the visual overview, and dismiss cards with spring motion and haptic feedback.
Private by design. Filtering, history, favorites, profiles, and privacy telemetry stay local.
Cross-device without surrendering your data. Self-hosted E2EE sync exposes desktop and Android tab lists as writable device profiles while the server never sees their contents in plaintext.
Pick the engine that fits. Use GeckoView for Mozilla-signed Firefox extensions such as uBlock Origin, or Android System WebView for Android's system-managed runtime while keeping Toppings and Candy protection.
Feels at home on Android. Dynamic color, edge-to-edge content, Predictive Back, Autofill, passkeys, downloads, sharing, printing, and default-browser integration.

Architecture

Candy keeps browser behavior and production UI in shared Kotlin. The address bar, gestures, menus, tab switcher, Hero/Grid/List previews, settings structure, and their motion rules are not rebuilt for each platform. Small platform adapters connect that shared product layer to the native browser engine, image types, resources, haptics, and visual effects.

flowchart TD
    K[Shared Kotlin behavior and state] --> C[Shared Compose UI and motion]
    C --> A[Android platform adapter]
    C --> I[iOS platform adapter]
    A --> E{Selected Android engine}
    E --> G[GeckoView sessions]
    E --> S[System WebView sessions]
    G --> F[Signed Firefox WebExtensions]
    K --> T[Shared Topping model and grants]
    T --> GT[Gecko userScripts host]
    T --> ST[System WebView userScripts host]
    T --> WT[WKUserScript host]
    I --> W[WKWebView sessions]
    W --> WT

Android defaults to GeckoView and can switch the whole app to Android System WebView from Browser settings. Candy checkpoints tab URLs and restarts into a fresh process, keeping tabs, bookmarks, history, profiles, and settings shared while cookies, logins, native back-forward lists, and other engine-owned session state stay separate. Firefox extensions remain available only in GeckoView; System WebView keeps Toppings and Candy protection. iOS uses WKWebView behind the same shared Kotlin contracts and Compose browser chrome, with native Liquid Glass supplied through an iOS effect adapter.

Implementation boundaries, invariants, and the current parity status are documented in Platform engines and Platform feature parity.

Tablet and Foldable support

At 600 dp and wider, the floating address bar shows a horizontally scrollable tab strip. Tap another tab to open it, or tap the current tab to edit its address. Configurable actions and the More menu stay in place. Horizontal swipes scroll the strip; the upward overview gesture remains. The visual tab overview also adapts its previews and grid to larger screens.

Tablet browsing with floating, scrollable tabs and website favicons.

Unfolded foldable layout with the same tab strip and fixed browser actions.

Features

Browsing and gestures

Floating chrome over edge-to-edge browser-engine content, with configurable actions around the address field or wide-screen tab strip and a docked edge mode
Pull to refresh, direct URL navigation, QR scanning, local domain completion, and optional provider-backed search suggestions (disabled in private tabs)
Google, DuckDuckGo, Bing, Brave, Ecosia, Startpage, Qwant, Kagi, Perplexity, ChatGPT, and configurable SearXNG search
Optional Google AI Mode routing through a toggleable address-bar logo, enabled from search settings
Address commands with > for tab, profile, cache, cookie, and navigation actions
Candy Recall: optional, profile-scoped local full-text search across visited pages from the normal address input, History, or >recall, with no private-tab or cloud indexing
Background tabs, sharing, printing, external apps, assistant summaries, and built-in or external download managers
Link Peek: long-press a link to inspect it in a live, disposable preview without creating a tab or history entry, then send it to a background tab through the pulsing plus target
External Link Preview: optionally open links from other apps in a temporary Candy preview instead of creating a tab immediately. A compact bottom pill keeps the current host visible, combines the outlined Open in Candy action with its profile picker, and offers share, copy, find-in-page, and desktop-site actions before the page is promoted to a real tab. Temporary app switches keep the preview; explicitly opening Candy from its app icon, widget, or launcher shortcut discards it.

Appearance and browser chrome

System, light, dark, and AMOLED appearances with Material You, Candy, or neutral color palettes
Clear or frosted browser surfaces plus angular, rounded, or extra-rounded shapes
Independent transparency controls for general browser chrome and the address bar, with adjustable live background blur where the selected Android engine and version support it

Tabs, profiles, and journeys

Persistent tabs with saved page previews, favicons, pinning, reordering, and automatic cleanup
Coverflow, compact grid, and preview-free list layouts
Candy Stacks: group compatible tabs by name and color, choose the stack preview, collapse from the card marker in Coverflow or Grid, and choose Coverflow, Grid, or List for the folder-style member view
Tab snoozing with scheduled returns, notifications, and a dedicated snoozed-tab manager
Per-profile browser-engine storage isolation with private sessions kept in memory
Optional profile controls for a simpler single-profile setup
Private tabs that keep their session and journey data in memory only
Candy Trails: persistent branching navigation graphs with pan, zoom, direct navigation, and forkable paths
Site Capsules: profile-bound home-screen shortcuts with configurable navigation boundaries and minimal browser chrome

Reading and page tools

Reader Studio: local article extraction with typography, alignment, paper and night themes, offline saves, and text-to-speech
Find in page with live match counts and previous/next navigation that stays visible above the keyboard
Toppings: Candy's lightweight, transparent alternative to traditional browser extensions. Discover, install, update, toggle, import, and edit bounded userscripts that customize matching regular tabs without privileged browser or GM_* APIs. The reviewed catalog lives in candy-browser-toppings, so new Toppings do not require a Candy Browser release
Per-domain mute controls for silencing noisy sites
Optional full immersive mode and a setting that prevents video autoplay

Firefox extension support

A clean Android Gecko profile gets uBlock Origin and I still don't care about cookies by default from pinned, unmodified Mozilla-signed XPIs bundled for offline installation. Their corresponding GPL-3.0-only sources are pinned to immutable upstream Git commits.
Existing installs are matched by Firefox extension ID and left unchanged. Disabling a default is respected; uninstalling it records a durable removal marker, so Candy does not restore it later. Default extensions are never enabled for private tabs without the user's explicit opt-in.
Android can install Mozilla-signed Firefox extensions directly from an HTTPS XPI URL. Candy uses GeckoView for signature validation, permission approval, installation, updates, enable/disable, uninstall, and explicit private-browsing access.
Failed installs retain GeckoView's reason: Candy distinguishes download, package integrity, storage, signature, identity, compatibility, platform support, Mozilla blocklist, enterprise-only, cancellation, and restart-required failures instead of showing one generic error.
Supported extension UI stays inside Candy's shared browser chrome: browser/page actions, popups, and options pages do not introduce a second address bar, menu system, or tab switcher.
Candy supports the public WebExtension APIs exposed by the pinned GeckoView 155 runtime. This is not a guarantee that every Firefox Desktop extension is compatible. Desktop-only APIs and fields GeckoView rejects before Candy can handle them cannot be emulated reliably. For example, tabs.update({ muted: ... }) and tabs.update({ pinned: ... }) are rejected by GeckoView 155's extension schema.
See the tested Firefox WebExtension capability matrix for supported APIs and exact platform boundaries.

Pinned source URLs, versions, hashes, licenses, and delivery modes live in app/src/gecko/assets/gecko_default_extensions/catalog.json. Maintainers verify local assets with python3 scripts/generate_gecko_default_extensions.py verify, audit both upstream files with python3 scripts/generate_gecko_default_extensions.py audit-remote, and refresh the bundled XPI only with python3 scripts/generate_gecko_default_extensions.py refresh.

Media, fullscreen, and picture-in-picture

Native fullscreen support for HTML5 and YouTube video, including rotation-aware Android system UI
Automatic Android picture-in-picture when leaving Candy with an active regular-tab video
Website picture-in-picture buttons for eligible top-level and fullscreen-capable embedded HTML5 video
Google Cast playback for compatible direct HTML5 MP4, WebM, HLS and DASH video in regular tabs
Seamless PiP entry and return without pausing or recreating the decoder surface, even when a site replaces or restyles its video element
Draggable in-app mini-player when switching tabs, plus background audio playback where supported
Android media notification and system controls for play, pause, stop, and seek
Private-tab media remains transient and never enters PiP, the mini-player, or system media controls

Local protection

EasyList/EasyPrivacy hosts and cosmetics, a pinned safely representable uAssets subset, and a pinned HaGeZi Pro host delta
Third-party-cookie blocking and cosmetic cookie-banner hiding
Privacy X-Ray: live per-tab block counts, categories, domains, and exceptions
Permission Radar: per-site camera, microphone, location, and other WebView permission activity
Filter Studio: global or profile rules, import/export, and confirmed HTTPS subscriptions
Safe Browsing, TLS failure handling, blocked unsafe schemes, and external-scheme allowlisting

Download

Candy Browser requires Android 13 (API 33) or newer.

Download Candy Browser

Standard and User CA production builds check GitHub for updates at startup and offer a signed APK for download. Standard installs on ARM64 devices prefer the smaller ARM64 APK and fall back to the universal APK when needed. Both use the same application ID, version, and signing key, so either can update an existing standard install. The FOSS build disables this updater. Android still requires you to open a downloaded file and approve installation.

Obtainium

Use the filtered setup link so Obtainium always selects the standard certificate-trust channel:

The standard and User CA channels use separate application IDs, so both can stay installed and keep independent profiles, settings, and caches. Keep the asset filter: it prevents Obtainium from selecting a different channel than the configured app.

F-Droid

Candy includes a separately installable foss distribution flavor for the official F-Droid repository. It uses the application ID dev.sk2andy.materialbrowser.foss, removes Google Play services, Google Cast, Google Code Scanner, and Candy's GitHub update checker, and keeps its profiles, settings, and caches isolated from the other channels. Remote search suggestions default to off. F-Droid builds this variant from tagged public source and verifies it against Candy's upstream-signed FOSS APK.

The isolated F-Droid listing starts with 0.37; older FOSS APKs used the universal application ID and cannot become versions of the new package. Submission files and maintainer steps live in distribution/fdroid. Candy publishes a signed FOSS reference APK so F-Droid can verify its source build and preserve update compatibility with the upstream signing key.

Releases contain four APK channels plus an architecture-optimized standard APK:

APK suffix	Certificate trust	Intended use
`-release.apk`	Android system CAs only	Universal compatibility fallback
`-arm64-v8a-release.apk`	Android system CAs only	Recommended smaller APK for ARM64 devices
`-systemwebview-release.apk`	Android system CAs only	Small, separately installed build using only Android System WebView
`-foss-release.apk`	Android system CAs only	F-Droid reproducible-build reference without proprietary Google integrations
`-ca-release.apk`	System CAs plus every CA in Android's user store	Explicit opt-in for HTTPS filtering/proxy tools such as AdGuard

Both standard APKs use dev.sk2andy.materialbrowser and the same release signature. The System WebView-only build uses dev.sk2andy.materialbrowser.systemwebview, the FOSS build uses dev.sk2andy.materialbrowser.foss, and the User CA build uses dev.sk2andy.materialbrowser.ca. Android therefore installs all four channels side by side with isolated app data. Their launcher labels distinguish the channels; the warning under Settings → Protection & data additionally identifies the User CA build's broader trust policy. Updates stay on the installed channel. The System WebView build never downloads a GeckoView APK.

Releases through v0.36 used the standard application ID for all three APKs. Android cannot migrate an installed package to a different application ID, so the isolated FOSS and CA channels start with fresh app data. The new CA asset name is -ca-release.apk; legacy CA installs therefore do not get offered an incompatible package as an in-place update.

Security warning: a trusted user CA can inspect and modify all HTTPS traffic made by Candy, including normal and private tabs, suggestions, filter subscriptions, and update metadata. Only install the User CA APK when you trust every CA in Android's user credential store and the software that controls its private key. APK signature verification still protects Candy updates from APKs signed by another key.

Advanced users who intentionally need this channel can use the filtered User CA Obtainium setup.

Build from source

Requirements: Android SDK 37.1 and JDK 17. Point JAVA_HOME to your JDK 17 installation.

./gradlew testFullDebugUnitTest lintFullDebug assembleFullDebug

To verify the F-Droid-compatible build:

./gradlew testFossDebugUnitTest lintFossDebug assembleFossDebug

To verify the small System WebView-only build:

./gradlew testSystemwebviewDebugUnitTest lintSystemwebviewDebug assembleSystemwebviewDebug
./gradlew assembleSystemwebviewRelease
python3 scripts/test_systemwebview_apk.py

To build the explicit User CA development variant:

./gradlew testFullUserCaDebugUnitTest lintFullUserCaDebug assembleFullUserCaDebug
python3 scripts/test_network_security_apks.py

Debug APK: app/build/outputs/apk/full/debug/app-full-debug.apk. It installs as dev.sk2andy.materialbrowser.linkpeek, uses the label Candy Link Peek, and has a badged launcher icon, so it can stay installed beside the release app.

Signed release builds

Release builds are minified with R8 and require a signing key. Never commit a keystore or its credentials. Configure signing locally with either an ignored project file or environment variables.

For the first release only, create a long-lived key if no release key exists yet. Reuse that same key for every later release:

mkdir -p .signing
keytool -genkeypair \
  -keystore .signing/candy-release.keystore \
  -storetype PKCS12 \
  -alias candy \
  -keyalg RSA \
  -keysize 4096 \
  -validity 10000

For an ignored project file:

cp keystore.properties.example keystore.properties
# Replace every placeholder in keystore.properties, then:
./gradlew assembleFullLocalRelease

Alternatively, export the same values from ~/.zshrc.shared:

export CANDY_RELEASE_KEYSTORE_PATH=/absolute/path/to/project/.signing/candy-release.keystore
export CANDY_RELEASE_STORE_PASSWORD='replace-me'
export CANDY_RELEASE_KEY_ALIAS='candy'
export CANDY_RELEASE_KEY_PASSWORD='replace-me'

Signed local APK: app/build/outputs/apk/full/localRelease/app-full-localRelease.apk

localRelease installs beside the GitHub build as dev.sk2andy.materialbrowser.local and uses a separate launcher icon and the label Candy Browser Local. GitHub update prompts are disabled for this side-by-side build because production APKs cannot update its package. The GitHub release workflow uses assembleFullRelease, assembleFossRelease, assembleSystemwebviewRelease, and assembleFullUserCaRelease; those outputs use the standard, .foss, .systemwebview, and .ca application IDs and matching launcher identities. A separate workflow signs and publishes the FOSS output from explicitly allowlisted release tags.

For current edge-to-edge experiments, use the separate Candy Edge package consistently:

./gradlew lintFullLocalRelease assembleFullLocalRelease \
  -Pcandy.localReleaseApplicationIdSuffix=.edge \
  '-Pcandy.localReleaseAppLabel=Candy Edge' \
  -Pcandy.performanceDiagnostics=true

This signed, minified APK installs as dev.sk2andy.materialbrowser.edge, without replacing standard Candy or sharing its app data. Its diagnostic authority is content://dev.sk2andy.materialbrowser.edge.performance; launch the component dev.sk2andy.materialbrowser.edge/dev.sk2andy.materialbrowser.MainActivity. Keep production release identities unchanged. Device commands must use the explicitly selected serial.

GitHub releases

The manual Release Android APK workflow tests the selected source revision, builds the FOSS flavor, builds and verifies the signed universal standard, ARM64 standard, System WebView-only, and User CA APKs, creates a v<version> source tag, and publishes the four signed GitHub APKs plus their SHA-256 checksums. Add four repository secrets once:

base64 < "$CANDY_RELEASE_KEYSTORE_PATH" | gh secret set CANDY_RELEASE_KEYSTORE_BASE64
printf '%s' "$CANDY_RELEASE_STORE_PASSWORD" | gh secret set CANDY_RELEASE_STORE_PASSWORD
printf '%s' "$CANDY_RELEASE_KEY_ALIAS" | gh secret set CANDY_RELEASE_KEY_ALIAS
printf '%s' "$CANDY_RELEASE_KEY_PASSWORD" | gh secret set CANDY_RELEASE_KEY_PASSWORD

Pin the public certificate fingerprint separately. This prevents an accidentally replaced keystore from publishing an APK that installed copies cannot update to:

keytool -exportcert \
  -keystore "$CANDY_RELEASE_KEYSTORE_PATH" \
  -storepass:env CANDY_RELEASE_STORE_PASSWORD \
  -alias "$CANDY_RELEASE_KEY_ALIAS" \
  | shasum -a 256 \
  | awk '{print $1}' \
  | gh variable set CANDY_RELEASE_CERTIFICATE_SHA256

The separate Publish F-Droid reference APK workflow builds without access to signing secrets, then passes the unsigned APK to an isolated signing job that executes no repository code. It accepts only explicitly allowlisted release tags and commits and uses Android Build Tools 34 for compatibility with F-Droid's signature-copying process. Reference APKs disable the legacy v1/JAR signature and enable modern APK signature schemes so F-Droid can copy the signature onto its independent build. F-Droid accepts the resulting signed APK only when that build matches byte for byte apart from signing.

The workflow uses the release GitHub environment. Configure required reviewers for that environment if releases should require a manual approval after dispatch.

Before each release, update candy.versionName and the monotonically increasing candy.versionCode in gradle.properties. The workflow rejects an input version that differs from the committed version. Add the matching English changelog at release-notes/<version>.md; it is bundled into Android’s one-time What’s New page and published unchanged as the GitHub Release body. The project skill at .agents/skills/release-changelog/SKILL.md documents the supported Markdown and screenshot format. Then dispatch a release from GitHub Actions or with GitHub CLI:

gh workflow run release.yml \
  -f version=0.33 \
  -f changelog=release-notes/0.33.md \
  -f prerelease=false \
  -f play_track=alpha

The workflow publishes to Google Play after the GitHub Release by default. For a GitHub-only release, pass -f publish_play=false; the signed APK and release checks still run.

Google Play releases

The Play build uses the standard application ID dev.sk2andy.materialbrowser, targets API 36, and disables Candy's GitHub update prompt. bundleFullPlayRelease produces one Android App Bundle containing ARM64, ARMv7, x86, and x86_64 libraries; Google Play generates and serves only the configuration APKs needed by each device.

Candy's Google Play developer account ID is 6525963931496038407. This ID identifies the account but is not a publishing credential. The Android Publisher API authenticates a narrowly permissioned service account through GitHub's short-lived Workload Identity Federation credentials.

For seamless updates between existing GitHub installations and Google Play, configure Play App Signing with the existing Candy release key as the app signing key. Do not let Play generate an unrelated app signing key. Create a separate upload key for the GitHub workflow:

mkdir -p .signing
keytool -genkeypair \
  -keystore .signing/candy-play-upload.keystore \
  -storetype PKCS12 \
  -alias candy-play-upload \
  -keyalg RSA \
  -keysize 4096 \
  -validity 10000

The google-play GitHub environment supplies four secrets and three variables:

Kind	Name	Purpose
Secret	`CANDY_PLAY_UPLOAD_KEYSTORE_BASE64`	Base64-encoded Play upload keystore
Secret	`CANDY_PLAY_UPLOAD_STORE_PASSWORD`	Upload keystore password
Secret	`CANDY_PLAY_UPLOAD_KEY_ALIAS`	Upload key alias
Secret	`CANDY_PLAY_UPLOAD_KEY_PASSWORD`	Upload key password
Variable	`CANDY_PLAY_UPLOAD_CERTIFICATE_SHA256`	Pinned upload certificate digest
Variable	`GCP_WORKLOAD_IDENTITY_PROVIDER`	Full Google Cloud WIF provider name
Variable	`GCP_PLAY_SERVICE_ACCOUNT`	Play publisher service-account email

Restrict the WIF attribute condition to repository sk2andy/candy-browser and environment google-play. Allow either the reusable job_workflow_ref identity at refs/heads/main or the direct workflow_ref identity for publish-google-play.yml on main and release tags matching v*. Grant the service account access only to Candy in Play Console. Configure the google-play GitHub environment to accept main and v* release tags. Automatic release publication must not require a reviewer. The workflow builds without Google or signing credentials; only the separate publish job can sign the AAB and request a short-lived Google credential. No service-account JSON key is stored in GitHub.

The account must be verified and the app, declarations, Play App Signing, upload key, service account access, and first internal release must be created once in Play Console. After that, publish an existing GitHub release tag with:

gh workflow run publish-google-play.yml \
  -f version=0.42 \
  -f track=internal \
  -f status=completed

By default, the Android release workflow directly invokes the reusable Play workflow after creating each GitHub Release; publish_play=false skips that job. The direct invocation avoids GitHub's protection against recursively triggering workflows with GITHUB_TOKEN. Its play_track input defaults to the closed alpha track and can target internal, beta, or production explicitly. A manually created stable GitHub Release also publishes to closed alpha, while a manually created prerelease publishes to Play beta. After production access is approved, select production when dispatching the release workflow. Manual dispatch from main remains available for drafts and existing releases. All paths check out the fully qualified v<version> tag and require a corresponding published GitHub Release. The workflow also requires matching English and German files at fastlane/metadata/android/<locale>/changelogs/<versionCode>.txt, verifies their Play length limit, the upload-key certificate, all four ABIs, the signed AAB, and the R8 mapping file. It defaults to a draft internal release when dispatched manually. Manual production publication additionally requires -f production_confirmation=PROMOTE-TESTED-TO-PRODUCTION. Each automatic release needs a new versionCode; rerunning an already uploaded version can be rejected by Play. The release workflow intentionally does not overwrite the Store listing. Store descriptions and artwork in fastlane/metadata/android remain the canonical source for the one-time Play Console setup and explicit later listing updates.

Publish a FOSS reference APK from an allowlisted release tag with:

gh workflow run publish-fdroid-reference.yml -f tag=v0.33

Before each later F-Droid release, add its exact tag and immutable commit to the workflow allowlist through normal code review, then dispatch the workflow.

Android versionCode is stored in source so GitHub and F-Droid can build identical version metadata from a tag. Tags and releases are created only after full and FOSS tests, release build checks, APK signing, certificate pinning, and signature verification succeed. Back up the original keystore and credentials securely: Android updates must always use the same signing key.

Privacy and limitations

Candy offers GeckoView and Android System WebView as selectable Android engines and uses WKWebView for the iOS target. It does not bundle a Chromium fork or route traffic through a proxy or VPN. Shared Candy filtering policy stays local and crosses a platform-specific engine adapter.

Engine APIs still define the visibility boundary. WebSockets, CNAME cloaking, some redirects, and content inside closed cross-origin or Shadow DOM contexts may get through. Firefox extensions can use only GeckoView's public embedder surface; Firefox Desktop support does not imply GeckoView support. Android System WebView and WKWebView cannot run Firefox extensions, so both use bounded Toppings instead.

Privacy X-Ray includes only blocked requests that the active browser engine can reliably attribute to one tab. Service-worker requests are filtered but excluded from per-tab telemetry when no reliable tab ID is available.

Google Cast is used only after explicit device selection for compatible regular-tab video. Media URLs and metadata are sent to the selected Cast device and remain memory-only in Candy. Google's Cast Sender SDK can send Cast-device interaction activity to Google's logging service; release Data Safety disclosures must account for the current SDK behavior.

Candy Rules and filter-source details

Candy Rules v1 supports exact host block/allow rules, positive site-to-host pairs, HOSTS entries, and origin-scoped standard CSS selectors. It deliberately rejects JavaScript, regular expressions, redirects, response-header filters, scriptlets, and advanced cosmetic operators rather than approximating them.

Bundled EasyList/EasyPrivacy and uAssets cosmetics are compiled separately from user rules and merged in memory so exceptions work across sources. Only domain-specific standard ##selector rules, their domain exclusions, and matching #@# exceptions are retained. Generic selectors, conditional capability blocks, and procedural operators are skipped. Runtime lookup resolves selectors for the current host before registering a bounded, exact-origin document-start script; invalid browser-specific selectors fail independently through insertRule. Mail, Maps, and Accounts Google hosts intentionally receive no bundled cosmetic CSS.

Bundled defaults may additionally use audited, declarative WebView rules: a site-scoped literal request-path prefix or a known Reject/Remind-later consent control. These rules cannot run imported JavaScript, never click Accept, and never intercept a main-frame navigation. An exact bundled path rule may override the general same-party escape only for its audited page-host, request-host, and literal non-root path prefix.

Imports are bounded and validated atomically. HTTPS subscriptions update only after a user-requested fetch, show a diff, and require confirmation. Private-profile imports remain in memory.

EasyList, EasyPrivacy, and EasyList Cookie data are distributed under CC BY-SA 3.0 or later. The uAssets-derived network and cosmetic subsets are generated from one pinned revision of the official uBlock Origin Ads source and distributed under GPL-3.0. The HaGeZi Pro host delta is generated from a pinned official revision and distributed under GPL-3.0. Exact sources, revisions, transformations, and notices ship in app/src/main/assets/; maintenance entry points live in scripts/update_*.sh.

Languages

29 app languages, including Russian (ru, also used for ru-RU). See the complete language list.

Licensing

Candy Browser source code is available under the Mozilla Public License 2.0. Third-party components and filter data retain their own licenses; bundled notices are available in app/src/main/assets/third_party_notices.txt and inside the app.

PimpinPumpkin/Vela

Maps and turn-by-turn navigation for Android without Google Play Services: the best of open map data, with Google lookups by choice. Runs on degoogled phones and can avoid Flock cameras

https://pimpinpumpkin.github.io/Vela/

Vela Maps

The best of OpenStreetMap and Google Maps, in one app.

Live traffic, real place data and turn-by-turn navigation, with no Google account, no Play Services and no Google code on your phone.

Install · What you get · Docs · FAQ · The book · Privacy · How it works · Build · Discussions · Translate

Warning

Vela is in beta, so you may run into bugs. If you do, open an issue and fill out the template. Nightlies and canary builds are newer still and less tested than the weekly stable.

An open-source Google Maps alternative for Android: what NewPipe is to YouTube, for Google Maps. The map is open data. The basemap is open vector tiles (OpenStreetMap), and the places on it are Vela data: Overture Maps and AllThePlaces, positioned with OpenStreetMap, baked into tiles in this repo and streamed from its releases. Browsing around never asks Google anything. Search, tap a place or ask for a route, and the phone itself asks Google's public web endpoints, with no account, no key and no server in between, for what only Google does well: search, hours, reviews, photos, and routes that know about traffic and closed roads. Built for degoogled phones such as GrapheneOS, and it runs on stock Android too.

What reaches Google, by default

It is not a Google Maps wrapper. Vela is a native Android app drawing open vector tiles (Jetpack Compose and MapLibre). There is no Google SDK in it, no Play Services, no API key and nothing to sign in to. It looks like Google Maps on purpose.

What you do	What reaches Google
Pan, zoom, browse the map	Nothing. Tiles from OpenFreeMap, streets and labels from OpenStreetMap
The places drawn on the map	Nothing, where Vela has place data. Open data baked in this repo: Overture Maps and AllThePlaces, positioned with OpenStreetMap. Where Vela has none for the area on screen, Google's places are drawn and Google is sent that area
Drop a pin, tap a house number	Nothing. OpenStreetMap's Nominatim names the spot
Read a departure board	Nothing, for the stops Vela draws from open transit data: the board comes from Transitous. Where Transitous has no coverage, Vela falls back to the stop's Google page
Ask for directions	Where the trip starts and ends, anonymously. A driving route is Google's own, so it knows about traffic and closed roads. The turn-by-turn instructions are put on it from OpenStreetMap, by the open OSRM and Valhalla routers, which are sent the same trip. While you drive, Google is asked again when you leave the route and every couple of minutes for traffic; Settings → Navigation turns the second off. Walking and cycling routes come from the open routers (for a walk Google is asked once, and its route used only when it is much shorter). Offline, the route is computed on the phone
Type a search	Your text, anonymously, like a logged-out browser. Typing sends Google's own autocomplete each time you pause; submitting sends a Google search. Text that starts with a house number also goes to the open Photon geocoder
Tap a place	An anonymous lookup of that place, with no account and no app key, for its hours, reviews and photos. Settings → Places can stop the lookup for places tapped on the map
Everything you save	Nothing, ever. No account, no Vela backend, no Vela telemetry; saved places, history and settings stay on the phone

Download a region and the map, search, routing and turn-by-turn navigation work with no network. Offline, or with Settings → Privacy → Use Vela without Google on, nothing reaches Google at all. The first run asks which you want, before the map loads. A few things Google only serves to a real browser, a place's reviews among them, are read from a Google page in an offscreen WebView, anonymously; the list is in PRIVACY.md.

The full comparison against the Google Maps app and Google Maps web is below, and the per-request detail is in PRIVACY.md.

Screenshots

Navigation	Map & search	Place details	Directions	Search results

Public transit	Departure board	Stops on the line	Light theme - map	Light theme - place

Turn-by-turn with lane guidance, route shields and the speedometer. The OpenFreeMap basemap in Google's colors with Google Sans Flex labels. Place pages with live data. The route picker with alternates, traffic and the avoid switches. Live departure boards with the stop list for every route. Light and dark themes, set in the app.

Install

Obtainium tracks the weekly stable release. Turn on "include prereleases" for the nightly channel.

The F-Droid badge is Vela's own repository, not the f-droid.org catalog. Add https://pimpinpumpkin.github.io/Vela/repo to any F-Droid client and it serves the same signed APKs, weekly stable by default (fingerprint and nightly setup in FDROID.md). Or take an APK straight from Releases.

Check you got the real thing

Every Vela APK, from any channel, is signed with the same key. Its certificate fingerprint is:

SHA-256  29:93:8B:48:58:06:3E:42:E6:77:FF:95:C9:01:CD:48:24:8A:7F:03:2A:3A:E8:5F:9B:9E:56:17:56:8B:0D:36

Check a downloaded file against it before installing:

apksigner verify --print-certs vela-maps-*.apk

On the phone, App Verifier checks the same thing. It wants the package name on the first line and the fingerprint on the second, so paste this block, not the line above:

app.vela
29:93:8B:48:58:06:3E:42:E6:77:FF:95:C9:01:CD:48:24:8A:7F:03:2A:3A:E8:5F:9B:9E:56:17:56:8B:0D:36

Android enforces this for you after the first install: an update signed with a different key is refused, so a build that installs over your existing Vela came from the same place this one did.

This is the certificate the app is signed with, and it stays the same across releases. It is not a checksum of a particular APK, and it is not the same as the F-Droid repo fingerprint in FDROID.md, which signs the repo index rather than the app.

There is a one-page tour at pimpinpumpkin.github.io/Vela, and the docs in this repository are published as a searchable site at pimpinpumpkin.github.io/Vela/docs.

What you get

Routes and traffic from Google. A driving route is the one Google would give you, with live traffic and closed roads accounted for. Each option shows its time in green, amber or red and says light, moderate or heavy traffic in words. Turn-by-turn navigation runs on top: lane diagrams, exit shields, a speedometer with the posted limit, and a faster-route offer when a jam builds ahead.
The places on the map are open data, and Google fills in the details. Every pin, dot and label you pan past is Vela data: Overture Maps and AllThePlaces, positioned with OpenStreetMap, baked into map tiles in this repo, streamed from its releases and carried offline with a downloaded region. Browsing sends Google nothing. Tapping a place asks Google for what open data lacks: hours with holidays, reviews you can search, photos, busy times, phone and website, and a warning if the place will be closed when you arrive. Settings → Places → "Place icons on the map" switches the map between Vela data (the default), Both, or Google, and a separate switch stops a tapped place from being looked up. The FAQ says what each feature uses.
No Google software on your phone. No Play Services, no account, no app key, no ads. Google never sees your map browsing or your saved places, and your GPS trail stays on the phone. A position reaches Google only in specific requests: a route from where you are, a search that ranks nearby places first, and the reroute and traffic checks while you navigate. Privacy has the breakdown.
Flock cameras on the map. Mapped license plate cameras (the community DeFlock project's OpenStreetMap data) are drawn out of the box. Avoid surveillance cameras, in Settings → Navigation or the route picker, counts the cameras pointed along each route and picks a lower-camera one when the detour is small. Two more switches give a card or a spoken "License plate camera ahead" as you approach one. The dataset lives on the phone and updates weekly.
Vela Voice. Spoken directions from a neural voice that runs on the phone, and a mic that transcribes your search on the phone too. Nothing you say goes to a speech service.

🔊 Hear it, the in-app voice at its default pace:

https://github.com/user-attachments/assets/17f246e4-51c8-4d01-998b-dcd7f29dc15f
Offline maps and routing. Download a state or a country, or just the area on screen, and its map, its places, typed street addresses and turn-by-turn routing work with no signal.
Public transit. Departure boards and the stop list of every run come from the open timetables transit agencies publish (served by the community Transitous project). Transit directions come from Google, with the open planner as the fallback. Rail lines draw in their own colors, and a trip draws along its real track.
Gas prices. Search for gas and each station's price is on its marker, in the list and on its page.
Street View in the app: look around, walk the street, go back to older captures, half screen over the map or full screen.
Satellite imagery from Esri.
Lists and saved routes. Keep places in lists with a note each, save a route you like, pin a trip to the home screen, and back all of it up to a file. Paste a shared Google Maps list or a My Maps link into the search bar to import it.
Parking. Tap P when you park, tap the pin later for the walk back.
Say it or type it. "Take me home", "navigate to the station", "Davis to San Francisco", "nearest pharmacy", "what's my ETA": the search box treats those as actions, spoken or typed, in every language the app speaks.
It repairs itself when Google moves things. The request recipes live in a signed file the app checks at launch. When Google shifts a field, a fix reaches every install in minutes with no app update. SPEC.md sections 3 and 11 describe it.
The rest. 18 languages, light and dark themes, optional wallpaper colors, full operation by D-pad on keypad phones, a built-in updater with stable, nightly and canary channels, and Android Auto screens (a car accepts a sideloaded app only in some setups; see docs/ANDROID-AUTO.md).

The whole list is in FEATURES.md.

Why Vela talks to Google at all

A phone without Google Play Services cannot run Google Maps, and the open map datasets fall well short on search, reviews, hours and live traffic. So for those, Vela is a client of Google's public web endpoints. It asks them the way a logged-out browser does, from each user's own phone, with no account, no shared API key and no server in the middle. NewPipe does the same for YouTube. There are no ads, and your search history, saved places and settings stay on the phone.

The map, the streets, the labels and the house numbers come from OpenStreetMap (in much of the US the house numbers come from OpenAddresses). The businesses on the map come from Overture and AllThePlaces. Google is used for search, place details, driving routes and traffic, plus things you open yourself such as Street View and transit directions. So street names and house numbers can differ from what Google Maps shows, and how much you see offline depends on how well OpenStreetMap covers your area. I'm thinking of ways to improve OSM and fill the gaps in the data. Stay tuned.

Privacy

There is no Vela backend, no account and no Vela telemetry. Vela fetches from Google directly from your phone like a logged-out browser. Google sees your IP, your query and the map area, but not a Google account or any app key, much like google.com/maps in an incognito window. Google does keep its own logged-out session cookie; Vela starts a new one every week by default (Settings → Privacy → Google session: weekly, daily, or every launch, plus a button to start one now). Your saved places, history and settings never leave the device. What each service receives is in PRIVACY.md.

In short, Google goes from knowing who you are and everywhere you go to answering anonymous questions now and then. With the default place source your map browsing never reaches Google, and your GPS trace is never uploaded anywhere. While you navigate, Vela asks Google for fresh traffic from your current position every couple of minutes, which is what powers the faster-route offers and the live arrival time. Settings → Navigation → "Live traffic re-checks while navigating" turns that off. Reroutes when you leave the route stay, because turn-by-turn cannot work without them.

What Google gets	Google Maps app	Google Maps web	Vela
Tied to your Google account	Yes, always signed in	Yes unless incognito	Never. There is no login
A persistent device identifier	Yes (device and ad IDs via Play Services)	Browser cookies	No account, no app key. A logged-out Google session cookie that Vela replaces weekly by default, and an IP like any website visitor
Your precise GPS position	Continuously while open, plus Location History if enabled	While the tab is open	Never while browsing. Searches send the map area you are looking at and, to rank nearby places first, can ask about a small area around you. A route from your location sends that point as the start. While navigating, reroutes and the optional traffic re-check send your current position
Every pan and zoom of the map	Yes, their servers render the map	Yes	No, by default. Map tiles come from OpenFreeMap and the places on them from Vela's own data
Your searches	Yes, saved to your account history	Yes	The text reaches Google anonymously, as you type (autocomplete) and when you search
Place pages you open	Yes	Yes	The place lookup reaches Google anonymously, under that logged-out session cookie
Turn-by-turn routes	Yes, full trip telemetry	Yes	Google is asked anonymously for the route between two points, and again during the drive for reroutes and the optional traffic re-check. The open OSRM and Valhalla routers get the same trip, to supply the turn instructions. Your GPS trail as a whole never leaves the phone
Saved places, home, work	Stored on their servers	Stored on their servers	Stored only on your phone
Ad profile building	Feeds your ads profile	Feeds your ads profile	Nothing to attach it to
Works with no Google contact at all	No	No	Yes. One switch (Settings → Privacy → Use Vela without Google), and downloaded regions show the map, search, route and navigate offline

How it works

SPEC.md is the technical reference: the basemap, the places bake, the requests to Google, routing, navigation, the offline data and the signed remote-repair channel. The book explains each subsystem in plainer words.

File	What's in it
`SPEC.md`	Every technical rule, contract and constant
`docs/book/`	Each subsystem explained: how places rank, when data is rebuilt, how a route is put together
`FEATURES.md`	What the app does, one line each
`PRIVACY.md`	What each service receives
`docs/FAQ.md`	The questions people ask first
`ROADMAP.md`	What is open. What shipped or was dropped is in `docs/ROADMAP-HISTORY.md`
`docs/BUILDING.md`	Building from source
`docs/TRANSLATING.md`	The languages, and how to translate (in the browser on Weblate)
`docs/dpad.md`	Operation without a touchscreen
`CLAUDE.md`	Rules and traps for anyone changing the code, human or AI

GrapheneOS notes

Location: Vela uses Android's own LocationManager, never Google's fused provider. On GrapheneOS, enabling PSDS (Settings → Location) drops the cold GPS fix from about 30 seconds to a few. Indoors GPS may not lock at all: turn on Network location (Settings → Location → Location services). Vela shows a tip when no position has come after a few seconds.

Roadmap

Still open (details in ROADMAP.md):

Android Auto without a Google Play listing.
F-Droid's own catalog, which needs a build with no prebuilt parts.
A Google Play listing, so Android Auto works on factory head units: a separate build with the Google half compiled out, while the full app stays on GitHub, Obtainium and F-Droid. A big job. On the radar, not started.
An iOS build. The engine module is plain Kotlin and would move to Kotlin Multiplatform; the interface would be rewritten. On the radar, not started.

Not going to happen: anything that needs you to sign in to Google or hand data to a backend. That covers contributing reviews, photos or edits, live location sharing, a location timeline, and the data Google strips from anonymous requests (live busyness). No account and no server ever sees you.

A note on the name

Vela Maps (app.vela): the navigator's constellation "the Sails", and "sail" in several languages.

Contributing

Read CONTRIBUTING.md first. It covers the hard rules (no backend, no static Google keys, no Google libraries, the :core / :app module boundary, docs in the same commit) and how to send a change. There is no separate code of conduct: keep it about the code. Security issues go through SECURITY.md (GitHub private vulnerability reporting), not a public issue.

Map data

The map is OpenStreetMap data, © OpenStreetMap contributors, under the Open Database License, served as vector tiles by OpenFreeMap. Offline routing regions, place packs, house-number and building overlays are built from OpenStreetMap, OpenAddresses and Microsoft Building Footprints extracts and carry their licenses in the release notes of the hosting release. The places on the map are Overture Maps (CDLA-Permissive 2.0) and AllThePlaces data, positioned with OpenStreetMap. Closed places are weeded out with Foursquare OS Places (Apache 2.0), OpenStreetMap and Wikidata. Transit boards come from Transitous and the agencies' own GTFS feeds. UK fuel prices come from the UK government's Fuel Finder, through matthewgall/fuelfinder-archive, and contain public sector information licensed under the Open Government Licence v3.0. Satellite imagery is Esri World Imagery, with Google imagery where Esri has none at close zoom.

License

Vela is Free Software: you can use, study, share and improve it at your will. You may use, modify and redistribute this project only if your modifications remain open source under the same license.

The app bundles the Google Sans Flex font, copyright The Google Sans Flex Authors, under the SIL Open Font License 1.1. Google Sans Flex is a trademark of Google LLC; Vela is not affiliated with or endorsed by Google.

Lelonio/Square

Unofficial YouTube Music / Spotify Premium client for Android, built in Liquid Glass. Audio effects, Spotify Connect, listening history, 8 languages. Rust core on librespot.

https://github.com/Lelonio/Square/releases/latest

Square

An unofficial Android music client for Spotify Premium and YouTube Music, built in Liquid Glass.

Download · Features · First launch · FAQ · Telegram community · Building

Player	Lyrics	Effects

Artist	Album	Glass settings

Features

Two sources, one app

Spotify or YouTube Music, chosen at first launch and switchable in the settings. Home, search, the library and the player work the same on both.
Spotify: your own account, with its playlists, library and Connect devices. Needs Premium.
YouTube Music: the whole catalogue and the music videos, with no account needed. Sign in with Google to bring in your playlists, albums and followed artists.

Player

The cover or the song's looping canvas video behind the controls.
Music videos: switch from the song to its video in place, without losing the queue or the position, and keep watching in picture-in-picture.
Radio from any song, and autoplay of similar songs when the queue ends.
Crossfade between songs, with an option to skip trailing silence.
Sleep timer: after 5 to 60 minutes or at the end of the song, fading out before it stops.

Audio effects

Speed and pitch, each on its own, plus reverb.
Presets, so "slowed + reverb" is one tap on any song.
Karaoke: turn the voice down.
Streaming quality that follows the connection, or a fixed one.

Lyrics

Synced lyrics, word by word where they exist and line by line otherwise.
Translation into your language, under the original lines.

Library and discovery

Playlists, albums, artists and liked songs. Create, rename and delete playlists, add and remove songs, pin favourites, follow artists.
A home page of shelves made for you, a New tab with releases and charts, and a Radio tab of stations, moods and genres.
Search, with your recent searches kept (swipe one away to remove it).
The music already on your phone, in a Local files shelf.

Offline

Download playlists, albums and songs, from either source. A song kept by two playlists is downloaded once.
Downloads over Wi-Fi only, and automatic downloads of your liked songs.
Offline mode: play only what is on the phone.

Spotify extras

A Connect device: send playback to Square from any other device, and control your other devices from it.
What your friends are listening to.
Similar playlists at the end of each playlist.
Song credits: performers, writers and producers.
What you play is saved to your listening history, as it would be anywhere else you listen.
Spotify links can open straight in Square.

Android Auto

Browse playlists and recently played, search by voice, like a song or start a radio from the car.

Look and language

Every control, the tab bar, the player, the sheets and the menus are made of one refracting glass. Blur, refraction and tint are adjustable, with a lighter mode for slower phones.
Eight languages: English, Italian, Spanish, French, German, Portuguese, Hindi and Turkish, chosen independently of the phone's own.

Download

Download the APK from the latest release and install it. Square needs Android 8.0 or later.

Square updates itself: it checks for new releases and installs them from the settings. It is not on the Play Store and cannot be; see the disclaimer.

The first minutes after installing are slower

Android takes a while to optimise a freshly installed app, and until it does the interface is noticeably slower. To do it straight away, open the app once and give it a few seconds, then run this with the phone connected:

adb shell cmd package compile -m speed-profile -f dev.lelonio.square

Run before the app has been opened, the command finds nothing to compile.

First launch

Square first asks where the music should come from. You can change it later in the settings.

YouTube Music plays straight away. Signing in with Google, from the settings, is optional.
Spotify needs a Premium account and a few minutes of guided setup: you sign in, then register a free app of your own in Spotify's developer dashboard and paste its client ID. Search and a few other features go through Spotify's Web API, which limits requests per app, so with your own app the limit is yours alone. The setup walks you through every step.

FAQ

Square does not appear in Android Auto. Android Auto only lists apps installed from the Play Store. Turn on "Unknown sources" in Android Auto's developer settings and Square shows up.

Can I use a free Spotify account? No. A free account can sign in, but Spotify only streams to a client like this one with Premium. YouTube Music works with no account at all.

YouTube Music search works, but songs do not play. YouTube changes how its streams are served every so often. Update to the latest release, which is usually where the fix is.

Disclaimer

Square is not affiliated with, endorsed by or connected to Spotify or Google. Both sources are used on terms they do not offer: Square re-implements Spotify's protocol, which Spotify's Terms of Service forbid, and reads YouTube Music through the private endpoints its own web client uses. It cannot be published on the Play Store, and you use it at your own risk. There is no warranty of any kind; see the licence.

Help and feedback

Telegram community: join Square | Community for questions, feedback, bug reports and feature requests.
Release announcements: Square | Official automatically shares new APKs and release notes from GitHub.
Questions (how something works, how to set it up): Discussions, Q&A
Ideas and requests: Discussions, Ideas
Something broken: open an issue. If the app closed or froze, attach a report from Settings → About → Save a report.

The same two links are in the app, under Settings → About.

Support

Square is free and has no ads. If it is useful to you, you can support its development on Ko-fi.

Credits

Project	Licence	How it is used
librespot	MIT	The Spotify engine. `librespot-core`, `librespot-playback` and `librespot-connect` are vendored with local patches.
Spotify Web Playback SDK	Spotify Developer Terms	Playback for accounts Spotify refuses audio keys, through the listener's own developer app.
Metrolist	GPL-3.0	Its InnerTube client, vendored as `innertube/`, because it is published nowhere else. Powers the signed-in YouTube Music library.
NewPipeExtractor	GPL-3.0	Anonymous YouTube Music search and stream URLs.
lossless.wtf	n/a	Synced lyrics timed to the word, asked first on both sources.
LrcLib	n/a	Synced lyrics for the YouTube Music source, over its open API.
Spicy Lyrics	AGPL-3.0	The lyrics animation, ported to Compose by @donutnotnut in #50.
Bungee	MPL-2.0	Time stretching, fetched at build time.
AndroidLiquidGlass	Apache-2.0	The glass material; the catalog components are copied with their notice.
Phosphor Icons	MIT	Every icon in the app.
ebur128	MIT	Loudness of local files, so they play at the level of the streamed tracks.
librespot-java	Apache-2.0	The listening-event format, re-implemented from its `EventService` rather than copied.
go-librespot and go-librespot-termux	GPL-3.0	The remote sleep timer's command and state fields, and the check on truncated audio keys, re-implemented from their findings rather than copied.

Building from source

Requirements, build steps, signing, the architecture and notes on the code are in docs/DEVELOPMENT.md.

Licence

GPL-3.0-or-later. See LICENSE.

The lyrics view, LyricsView.kt, is ported from Spicy Lyrics and stays under AGPL-3.0, combined with the rest as section 13 of both licences allows.

android/compose-samples

Official Jetpack Compose samples.

https://developer.android.com/jetpack/compose

Jetpack Compose Samples

This repository contains a set of individual Android Studio projects to help you learn about Compose in Android. Each sample demonstrates different use cases, complexity levels and APIs.

For more information, please read the documentation.

💻 Requirements

To try out these sample apps, you need to use Android Studio. You can clone this repository or import the project from Android Studio following the steps here.

🧬 Samples

Project
A sample blog post viewer that demonstrates the use of Compose with a typical Material app and real-world architecture. • Medium complexity • Varied UI • Light & dark themes • Resource loading • UI Testing > Browse

A sample chat app that focuses on UI state patterns and text input. • Low complexity • Material Design 3 theme and Material You dynamic color • Resource loading • Back button handling • Integration with Architecture Components: Navigation, Fragments, LiveData, ViewModel • Animation • UI Testing > Browse

Jetsnack is a sample snack ordering app built with Compose. • Medium complexity • Custom design system • Custom layouts • Animation > Browse

A sample podcast app that features a full-featured, Redux-style architecture and showcases dynamic themes. • Advanced sample • Dynamic theming using podcast artwork • Image fetching • `WindowInsets` support • Coroutines • Local storage with Room > Browse

A compose implementation of the Reply material study, an email client app that focuses on adaptive design for mobile, tablets and foldables. It also showcases brand new Material design 3 theming, dynamic colors and navigation components. • Medium complexity • Adaptive UI for phones, tablet and desktops • Foldable support • Material 3 theming & Components • Dynamic colors and Light/Dark theme support > Browse

A sample sleep tracker app, showcasing how to create custom layouts and graphics in Compose • Custom Layouts • Graphs with Paths > Browse

🧬 Additional samples

Project
An app for keeping up to date with the latest news and developments in Android. • Jetpack Compose first app. • Implements the recommended Android Architecture Guidelines • Integrates Jetpack Libraries holistically in the context of a real world app > Browse

A catalog of Material Design components and features available in Jetpack Compose. See how to implement them and how they look and behave on real devices. • Lives in AOSP—always up to date • Uses the same samples as API reference docs • Theme picker to change Material Theming values at runtime • Links to guidelines, docs, source code, and issue tracker > Browse on AOSP

High level features

Looking for a sample that has the following features?

Custom Layouts

Theming

Animations

Text

Jetchat: Downloadable Fonts

Large Screens

TV

Jetcaster - TV

Wear

Jetcaster - Wear

Formatting

To automatically format all samples: Run ./scripts/format.sh To check one sample for errors: Navigate to the sample folder and run ./gradlew spotlessCheck To format one sample: Navigate to the sample folder and run ./gradlew spotlessApply

Updates

To update dependencies to their new stable versions, run:

./scripts/updateDeps.sh

Any other version updates need to be made individually.

Obsolete Sample Projects

Over time some of our samples become a little stale and are removed to keep the repository easy to navigate. If you are curious you can still find them in the history, however if you are new you might be better served sticking to the most up to date resources.

Project	Removed	Commit
Crane	2024-08-02	ee8e272
Owl	2024-08-02	ee8e272
Jetsurvey	2024-08-02	ee8e272
Rally	2024-08-02	ee8e272

License

Copyright 2024 The Android Open Source Project

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

software-mansion/enriched-markdown

Multiplatform Markdown-Based Rich Text Solution

https://enriched.swmansion.com/markdown

A multi-platform SDK for rendering Markdown as native text and editing rich text with Markdown output. Ships as a React Native library with iOS, Android, macOS, and Web support, plus standalone native SDKs for iOS (Swift) and Android (Kotlin).

Features

Native text rendering — High-performance Markdown rendering built on platform text APIs (no WebView)
Rich text input — Text input with Markdown output, inline formatting, headings, lists, links, and mentions
Cross-platform — Consistent API across React Native (TypeScript), iOS (Swift), and Android (Kotlin)
CommonMark & GFM — Full CommonMark compliance with GitHub Flavored Markdown extensions (tables, task lists, strikethrough)
LaTeX math — Block and inline math rendering powered by RaTeX
Markdown streaming — Real-time streaming support for AI/LLM chat interfaces
Code syntax highlighting — Native syntax highlighting powered by tree-sitter
Accessibility — VoiceOver on iOS, TalkBack on Android, semantic HTML on web

See the feature comparison table for a detailed breakdown of supported features per platform.

Packages

Platform	Package	README
React Native		React Native
Android		Android
iOS		iOS

Quick start

React Native

yarn add react-native-enriched-markdown

import { EnrichedMarkdownText } from 'react-native-enriched-markdown';
import { Linking } from 'react-native';

<EnrichedMarkdownText
  markdown={"# Hello\n\nThis is **enriched** [markdown](https://commonmark.org)."}
  onLinkPress={({ url }) => Linking.openURL(url)}
/>

Android

dependencies {
  implementation("com.swmansion.enriched.markdown:compose:0.2.0")
}

import com.swmansion.enriched.markdown.compose.EnrichedMarkdownText

EnrichedMarkdownText(
  markdown = "# Hello\n\nThis is **enriched** [markdown](https://commonmark.org).",
  onLinkClick = { url -> /* open url */ },
)

iOS

dependencies: [
  .package(
    url: "https://github.com/software-mansion-labs/enriched-markdown-ios.git",
    from: "0.1.0"
  ),
]

import EnrichedMarkdown
import SwiftUI

EnrichedMarkdownText("# Hello\n\nThis is **enriched** [markdown](https://commonmark.org).")
  .onLinkPress { url in
    UIApplication.shared.open(url)
  }

Contributing

See the contributing guide to learn how to contribute to the repository and the development workflow.

License

Enriched Markdown is licensed under The MIT License.

Built by Software Mansion.

alex193a/Root-My-Pixel

Jailbreak supported Google Pixel phones with CVE-2026-43499

Root My Pixel

Root My Pixel is an Android application designed to automate root access on Google Pixel devices leveraging the NebuSec IonStack exploit (CVE-2026-43499) and integrating ReSukiSU / KernelSU.

How the Application Works

Root My Pixel lets you temporarily gain root access with ReSukiSU in just one tap.

Installation Workflow

Device Detection & Profiling
- At startup, the app uses native JNI (NativeProbe), /proc/version queries, and system properties to detect the device codename, kernel version, CPU ABI, memory page size, and build display ID.
- Via ResolveTargetUseCase, it matches the device details against supported target profiles defined in assets/profiles.json.
Shizuku Integration
- The app uses Shizuku (UID 2000) to acquire ADB shell privileges without needing initial root access, which is required to stage and execute payload binaries in /data/local/tmp.
- A managed ExploitService is bound via Binder IPC to stream exploit execution logs to the UI in real time.
Exploit Payload Extraction & Execution
- Precompiled binary payloads (.so) corresponding to each supported build and the native helper tool (libcve43499root.so) are extracted from APK assets to /data/local/tmp.
- The IonStack exploit (CVE-2026-43499) is executed to establish a local root daemon socket (temp_su.sock), acquiring full root privileges.
KernelSU / ReSukiSU Integration
- Staging of the ksud binary matching the device's Kernel Module Interface (KMI, e.g., android15-6.6).
- The app triggers the KernelSU late-load mechanism (ksud late-load --kmi <kmi>).
- Verifies KernelSU through its UAPI, with ksud debug info and /proc/modules as compatibility fallbacks.
- Registers the installed ReSukiSU Manager only after validating its production APK signature.
User Interface & Management Tools
- Real-time live log progress monitoring.
- Handy actions for Soft Reboot (restarting system_server) and Log Exporting for debugging purposes.

Supported Devices & Build Profiles

Device	Codename	Supported Builds	Kernel KMI	Tested
Pixel 11	`cubs`	`CD1A.260618.001.C2`	`android16-6.12`	✅
Pixel 11 Pro	`grizzly`	`CD1A.260618.001.C2`	`android16-6.12`	✅
Pixel 11 Pro XL	`kodiak`	`CD1A.260618.001.C2`	`android16-6.12`	✅
Pixel 11 Pro Fold	`yogi`	`CD1A.260618.001.C3`	`android16-6.12`	✅
Pixel 10	`frankel`	`CP2A.260705.006`	`android15-6.6`	✅
Pixel 10 Pro	`blazer`	`CP2A.260705.006`	`android15-6.6`	✅
Pixel 10 Pro XL	`mustang`	`CP2A.260705.006` `CP2A.260805.005`	`android15-6.6`	✅
Pixel 10 Pro Fold	`rango`	`CP2A.260705.006`	`android15-6.6`	✅
Pixel 10a	`stallion`	`CP2A.260705.006` `CP2A.260805.005`	`android14-6.1`	✅
Pixel 9 Pro Fold	`comet`	`CP2A.260705.006`	`android15-6.1`	✅
Pixel 9 Pro	`caiman`	`CP2A.260705.006`	`android15-6.1`	✅
Pixel 9 Pro XL	`komodo`	`CP2A.260705.006`	`android15-6.1`	✅
Pixel 9	`tokay`	`CP2A.260705.006` `AD1A.240905.004`	`android14-6.1`	✅
Pixel 9a	`tegu`	`CP2A.260705.006`	`android14-6.1`	✅
Pixel 8 Pro	`husky`	`CP2A.260705.006`	`android14-6.1`	✅
Pixel 8	`shiba`	`CP2A.260705.006`	`android14-6.1`	✅
Pixel 8a	`akita`	`CP2A.260805.005`	`android14-6.1`	✅
Pixel 7a	`lynx`	`CP2A.260705.006`	`android14-6.1`	✅
Pixel 7 Pro	`cheetah`	`CP2A.260705.006`	`android14-6.1`	✅
Pixel 7	`panther`	`CP2A.260705.006` `BP2A.250705.008`	`android14-6.1`	✅
Pixel 6a	`bluejay`	`CP2A.260705.006` `CP1A.260405.005`	`android14-6.1`	✅
Pixel 6	`oriole`	`CP2A.260705.006`	`android14-6.1`	✅
Pixel 6 Pro	`raven`	`CP2A.260705.006`	`android14-6.1`	✅
Pixel Fold	`felix`	`CP2A.260605.012` `CP2A.260705.006`	`android14-6.1`	✅
Pixel Tablet	`tangorpro`	`BP1A.250405.007` `CP2A.260705.006`	`android14-6.1`	✅

Prerequisites

A supported Google Pixel device listed in the table above.
Shizuku installed and running via ADB (adb shell sh /sdcard/Android/data/rikka.shizuku/starter.sh or Wireless Debugging).
ReSukiSU Manager installed on the device to manage root permissions granted to apps.

Building from Source

To compile the entire project (native helper, exploit payloads for all targets, and the final debug APK):

Build Requirements

Android NDK r25+ (ANDROID_NDK_HOME set or present in Android SDK)
macOS (arm64/x86_64) or Linux (x86_64) host
Java 17+ and Gradle Wrapper

Build Command

./build-all.sh

The compiled APK will be generated at: app/build/outputs/apk/debug/app-debug.apk

To install it on a connected device via ADB:

adb install -r app/build/outputs/apk/debug/app-debug.apk

⚠️ Keep in mind that the exploit does not have a 100% success rate. Many users have had to try more than 20 times. Many report higher success by opening the app immediately after a reboot, while others find better results 10–40 minutes after rebooting.

🚨 If you root your phone, you might run into trouble making payments with Google Wallet and using RCS messages. Once you unroot, you'll have to wait a couple of days before everything works properly again.

Credits

Exploit: NebuSec IonStack
App architecture: Inspired and adapted from Root My Galaxy
ReSukiSU (https://github.com/ReSukiSU/ReSukiSU)

JunkFood02/Seal

🦭 Video/Audio Downloader for Android, based on yt-dlp

Seal

Video/Audio Downloader for Android

📱 Screenshots

📖 Features

Download videos and audio files from video platforms supported by yt-dlp (formerly youtube-dl).
Embed metadata and video thumbnail into extracted audio files supported by mutagen.
Download all videos in the playlist with one click.
Use embedded aria2c as external downloader for all your downloads.
Embed subtitles into the downloaded videos.
Execute custom yt-dlp commands with templates.
Manage in-app downloads and custom command templates.
Easy to use and user-friendly.
Material Design 3 style UI, with dynamic color theme.
MAD: UI and logic written with pure Kotlin. Single activity, no fragments, only composable destinations.

⬇️ Download

For most devices, it is recommended to install the arm64-v8a version of the apks

Download the latest stable version from GitHub releases
- Install the pre-release versions to help us test out new features & changes
Stable releases are also available on F-Droid

💬 Contact

Join our Telegram Channel or Matrix Space for discussion, announcements, and releases!

💖 Sponsors

Seal will be always free and open source for everyone. If you like it, please consider sponsoring me!

🤝 Contributing

Contributions are welcome!

You can help translate Seal on Hosted Weblate.

Note

For submitting bug reports, feature requests, questions, or any other ideas to improve, please read CONTRIBUTING.md for instructions and guidelines first.

⭐️ Star History

🧱 Credits

Seal is a simple GUI of yt-dlp, based on youtubedl-android

Some of the UI designs and codes are borrowed from Read You and Music You

dvd

Material color utilities

Monet

📃 License

Warning

Except for the source code licensed under the GPLv3 license, all other parties are prohibited from using Seal's name as a downloader app, and the same is true for Seal's derivatives. Derivatives include but are not limited to forks and unofficial builds.

👆 Scroll to top

utkarshdalal/GameNative

Native PC gaming with Steam, Epic, GOG and Amazon integrations on Android

https://gamenative.app

GameNative

Play the PC games you already own — from Steam, Epic and GOG — on your Android device, with cloud saves.

Download · Discord · Support on Ko-fi

GameNative lets you run the PC games in your Steam, Epic and GOG libraries directly on Android — no streaming required. Your saves sync to the cloud, so you can stop on your PC and keep going on your phone.

It's still early. Not every game runs yet, and some need tweaking to play well, but the community is constantly finding and sharing configs that work — and these get applied automatically. You can see if anyone has tried running your game successfully at https://gamenative.app/compatibility.

What you get

Play games you actually own on Steam, Epic, GOG and Amazon
Cloud saves that carry over between your PC and your phone
Automatically applied known configs, so many games just work out of the box with no tweaking required
Controller and touch support, with a custom control editor and on-screen HUD
Steam DLC, workshop and branch support
Active support over Discord if you need help getting a game running

Demo

TechDweeb walks through setting up GameNative on an Android handheld in a couple of minutes:

How to use

Download the latest release here
Install the APK on your Android device
Log in to your Steam account
Install your game
Hit play and enjoy

Support

The fastest way to get help is the Discord server — we're 35k+ strong and someone's usually around.

Please don't open issues on GitHub; they're closed automatically. Bring it to Discord instead.

If you'd like to chip in, you can support the project on Ko-fi.

Contributing

Want to help out? Message us to get into the #development channel on Discord, or open a thread there. Things we're currently looking for help with live on our Trello board.

Building

Most of the time you don't need this — if you just want to play, grab the release above. This is for contributors.

Build it like any normal Android Studio project. Ask on Discord if you get stuck.
SteamGridDB API key (optional): to pull game artwork for custom games, add your key to local.properties:
```
STEAMGRIDDB_API_KEY=your_api_key_here
```
You can get one from your SteamGridDB preferences. Without it everything still works — it just won't fetch images.

Analytics & privacy

GameNative uses PostHog for anonymous analytics. No personal information is ever collected — no names, emails, IPs or device identifiers.

Always collected, to improve game compatibility:

Game launch, close and exit events (game name, store, session length, average FPS, container config)
Game install, cancel and uninstall events

This is how we figure out which games work, how well they run, and which configs to apply automatically for the next person. It can't identify you.

Optional, and switchable under Settings → Info → Usage Analytics:

Feature usage (on-screen keyboard, controller, HUD, control editor)
Login success/failure events
Recommendation interactions
App lifecycle events (foreground/background)
Cloud sync events

The full Privacy Policy has the details.

Supporters

Thanks to our Ko-fi sponsors and GitHub sponsors, including CodeRabbit.

License

GPL 3.0.

See THIRD_PARTY_NOTICES for attributions, copyleft source offers, and notices about third-party and proprietary components bundled with the app.

Disclaimer: This software is meant for playing games that you legally own. Don't use it for piracy or anything else illegal. The maintainer takes no responsibility for misuse.

The412Banner/Bannerlator

Bannerlator — run Windows PC games and apps on Android (Wine + Box64/86). A personal, community-driven continuation of the discontinued Winlator Star Bionic project. GitHub Actions builds + releases.

Bannerlator

Windows applications and games on Android.

Contents • Ask AI • Download • Config Library • Mali Reports • Discord • Telegram • Builds • Credits

📌 Project Notice

Bannerlator is a personal build — made by me (The412Banner), for my own device, my own needs, and my own use.

It's a personal continuation of the Winlator Star Bionic project (star-emu/star) after it was discontinued and archived. None of the original developers are involved except me; it stands on their work plus cherry-picked commits from across the community — all credited below.

This is NOT an official or general-purpose Winlator release. It is built and tuned for my hardware and my workflow, and published as-is purely in case it happens to be useful to someone else.

No guarantee it works on any other device, GPU, or Android version.

No support, and no commitment to fix anything that works for me but not for you. If a feature works on my device, it isn't broken — for me, which is what this build is for.

Bug reports / feature requests for setups I don't run may simply be closed. That's not personal; this just isn't a community-support project.

You're free to use, modify, fork, or share it (GPL-3.0). If it doesn't work on your setup, that's expected — it wasn't built for it.

🤖 AI Disclaimer

All coding, features, and changes in this project are developed with the assistance of Claude AI by Anthropic. Claude is used to help with the heavy lifting — writing, reviewing, and modifying the emulator's code and the features added here: the Kotlin/Compose app shell and the native emulation glue (Wine/Proton, box64/FEX, DXVK/VKD3D → Vulkan), the storefront and cloud-save integrations, and the per-game/container features — as well as porting and re-deriving community changes into this build.

Before any stable release is published, all changes are manually debugged and tested by me across multiple devices — both rooted and unrooted. Debugging is done using logcat/getlog output and in-app debug log files to diagnose and verify behaviour, and no stable release is cut until the change is verified end-to-end on real hardware. Test devices:

Samsung Galaxy Fold 8 Ultra — Snapdragon 8 Elite Gen 5 — not rooted
AYANEO Konkr Pocket Fit — Snapdragon G3 Gen 3 — rooted
Odin 2 Portal (base) — Snapdragon 8 Gen 2 — rooted
Retroid Pocket 5 — Snapdragon 865 — rooted

A note on root: using any root-only features is entirely your own choice and at your own risk. I don't encourage rooting your device in general — especially without the proper knowledge and tools to do it correctly. Bannerlator runs fine unrooted; root only unlocks a few optional performance extras.

ℹ️ Information


App label	`Bannerlator Bionic` (standard) · `Bannerlator Bionic PuBG` (pubg) · `Bannerlator Bionic Ludashi` (ludashi) · `Bannerlator Bionic AnTuTu` (antutu)
Packages	`com.winlator.banner` (standard) · `com.tencent.ig` (pubg) · `com.ludashi.benchmark` (ludashi) · `com.antutu.ABenchMark` (antutu)
Version	Bannerlator V 3.1.6-pre3 — built from Star marcescence (`versionName 3.1.6-pre3`, `versionCode 97`)
Android SDK	`compileSdk 34` · `targetSdk 28` · `minSdk 26` (Android 8.0+)
Lineage	Winlator → cmod → Bionic Nightly → Star Bionic → marcescence → Bannerlator

🐛 Report a Mali GPU Game Issue

Games misbehaving on a Mali GPU (Exynos / Dimensity / Kirin / Helio devices)? We run a dedicated public bug-report board for Mali devices — file a structured report with your logs, and get answers back from the developers in a public discussion thread on each report.

📝 File a Mali game report — a quick form; attach the log file(s) so we can actually help.
📋 Browse all reports & dev answers — see what's been reported, answered, and fixed.

Every report gets its own public discussion thread. You can reply as the original poster — no account or password needed — and the developers answer right there in the thread.

📖 Contents

⬇️ Small updates, Win Components offline & smarter game adding (3.1.6)

3.1.6 is the stable release of everything below (Headless Steam, Steam Input, Force SSBS and the v14 layers, Mali on Wayland, Box64EC), plus:

Small updates, from the next release on — the in-app updater downloads a small patch (usually 5–25 MB instead of 525 MB), rebuilds the new app from the installed one, checks it's an exact copy of the release and installs it as a normal update. No patch for your version, or anything goes wrong → the full download, as before. 3.1.6 itself still downloads in full; first installs and this page always give the full APK.
A new update notice — a slide-in pill (Dismiss / View), a What's new pop-up with highlights and the real download size, and a download card with progress and Cancel. Automatic checks happen at most every six hours.
Win Components install offline — 113 of the 123 catalog components (VC++, .NET, DirectX, XNA, codecs, fonts…) are laid out straight into the container in seconds, without starting it.
Adding games — names from the game's own files, Steam's name, art and details found by title, an art picker in Edit Game, components suggested per game in folder import, scrolling game and container menus.
VKD3D_SHADER_MODEL=6_6 by default on every container, so Unreal Engine 5 games such as Gothic 1 Remake no longer refuse DirectX 12.

⚡ Force SSBS, v14 layers & Mali on Wayland (3.1.6)

First in 3.1.6-pre3: a CPU speed fix for Wine on ARM, the v14 layers that carry it, and Wayland settings for Mali phones.

Force SSBS — Wine on ARM kept switching off the CPU's SSBS feature on game threads (the slower, extra-safe way of handling memory). The v14 layers carry Wine's own fix (MR 12262) and the toggle (Advanced tab, container and per game) is on by default; older layers get the bit back through a small add-on. Biggest gains expected on Snapdragon 8 Elite (Oryon) in CPU-heavy games.
v14 layers — all ten Proton layers, both Proton 10 layers included again, in the catalog (release notes).
Mali on Wayland — a Mali (PanVK) section in the Wayland driver settings, and System offered as the Wayland driver on Mali (experimental).
Menu button — Input Controls › Device: pick a controller button that opens the in-game side menu (off by default; B can't be picked). Also a Toy Story 2 window fix.

🆕 SteamLite Steam Input & Wayland xdg-shell v3 (3.1.6)

First in 3.1.6-pre2: Steam Input for SteamLite and xdg-shell version 3 to the Wayland compositor.

SteamLite Steam Input — a per-game toggle and layout pick in the SteamLite launch options hands the controller to the game through Valve's own Steam Input layer (needs the SteamLite v8 package, offered by the app). Keep it off for games that already read a controller themselves; the default layout keeps the pad a pad.
Wayland xdg-shell v3 — the compositor now implements real positioners, pop-up windows and reposition and advertises version 3, which the Wayland driver of the new Proton-CachyOS 11.0-20261005 layer requires to open any window. Layers asking for version 1 or 2 are unchanged.
Proton-CachyOS 11.0-20261005 (arm64ec + x86_64, v13) is in the catalog — on app builds before 3.1.6-pre2 use it with X11.

🎮 Headless Steam & Server Browser (3.1.6)

Since 3.1.6-pre1, Steam games have a second online launch option next to SteamLite. Headless Steam runs a game on the app's own signed-in Steam session: a small native host (Valve's Android Steam library, driven by the app) signs in on your account in about a second and the game talks to it through the Steam bridge in the Proton 11 layers — no Steam client window, nothing installed in the prefix, every Steam call native. Cloud saves, stats, achievements and multiplayer work; Counter-Strike: Source was the proving case, including a live community match.

How to use it: sign in to Steam in the app, then pick Headless Steam in a Steam shortcut's launch popup (Headless Steam / SteamLite / Goldberg / Raw). Needs the v13 Proton 11 arm64ec layers from the catalog (the x86_64 layers and the Proton 10 layers have no Steam bridge).
Find Servers works. Valve's Android library has no working server browser, so the v13 layers carry their own: the app fetches the master list through Steam's Web API, the layer pings every server and feeds the game, and a small x86-64 front keeps the game's sort lookups inside the emulator — the list refreshes at 316 to 376 fps.
VAC: Headless Steam is not VAC-protected — Valve's Android library has no VAC scanner (only the Windows and x86 Linux clients do). Secure servers may admit you, but for a VAC session use SteamLite.
Log Manager: a Headless Steam toggle writes a per-game headless_steam.txt with a PASS/FAIL checklist of the session and the server browser.
Box64EC (experimental, unofficial): arm64ec containers also gain an Emulator (64-bit) picker (FEXCore, the supported default, or Box64EC). Box64EC components are built by The412Banner from the box64 project's work-in-progress ARM64EC target and airidosas252's PR #4480; they are not releases of the box64 project and the picker only appears once a Box64EC component is installed from the catalog.

🎬 Cutscenes & Codecs (3.1.5)

3.1.5 makes in-game cutscenes play on every DXVK version, and on x86_64 layers for the first time. The fixes ship in the v12 Proton layers (the catalog default; take the in-place update) plus two app pieces: a Codecs block in Win Components — builtin decoder GStreamer (default) or FFmpeg (winedmo, arm64ec only) and software decoding — and new defaults for new containers: Box64 0.4.5-gst (box64 with the GStreamer-wrapper fix, so x86_64 containers can decode video; upstream ptitSeb/box64#4528) and FEXCore 2609-unix. Existing x86_64 containers: pick Box64 0.4.5-gst once in Advanced. 3.1.5 also brings X11 raw mouse (XInput 2), full-colour game cursors, pointer auto-hide and a non-blocking X server, and Steam Cloud save-sync fixes — details in the release notes.

⚡ Fast OpenGL (3.1.4)

3.1.4 makes OpenGL games on X11 about 4 to 5 times faster, on every Wine version. A new Fast OpenGL setting (on by default) sends OpenGL frames straight to the screen through Vulkan instead of copying each one back first. It picks the right method by itself: Wine's EGL route on Wine 11 / Proton 11 arm64ec, and a new GLX route on everything else (Proton 10, Wine 9.5, every x86_64 layer). Old DirectDraw games through WineD3D get about 2 times faster too, and no freedreno is needed, just your Turnip driver. 3.1.4 also brings one compact OpenGL card (Fast, Show FPS, Vsync off), a Sync selector, Android games in the Games tab, and on Wayland one driver choice through the new adapter, no tap to start and uncapped DirectX 12. Full details are in the release notes.

📘 Plain-language explainer, with before-and-after screenshots and fps for every Wine version: Fast OpenGL — OpenGL games now run 4 to 5 times faster

🐧 Linux Steam Client (3.1.3)

Since 3.1.3, Bannerlator runs Valve's own native ARM64 Linux Steam client. Sign in, install a game from your library and play it through Valve's ARM64 Proton, with no Wine container involved. Proton is ready at first sign-in. Big Picture works with your fingers as well as a controller, a Components tab swaps FEX, DXVK and VKD3D per Proton, and the games in the app's Games tab show up in Steam with shared saves. It's an optional, experimental extra in the stable release: nothing changes unless you download it.

⚠️ Adreno GPUs only, and it needs Android's Disable child process restrictions developer setting. Mali, Xclipse and PowerVR phones get sound over a black screen. Leave the experimental Steam Deck mode off: it breaks game controllers. Full caveats are in the release notes.

📖 Step-by-step in plain English — a brand-new install, or upgrading (tap to expand)

🆕 New here? Installing for the first time

Before you start — check two things:

Your phone needs an Adreno GPU (Snapdragon). Mali, Xclipse and PowerVR phones will get sound over a black screen. Contents → Linux Runtime warns you about this before the download.
Turn on one Android setting first: go to Settings → Developer options → Disable child process restrictions and switch it on. Do not see Developer options? Go to Settings → About phone and tap Build number seven times, then it appears. Without this switch, Android randomly kills the Steam client and your session just dies for no visible reason. Some phones do not have the switch at all — on those, the client won't stay up yet.

Then:

Download and install the APK. There are four — just take standard unless you specifically use the pubg, ludashi or antutu build already.
Open the app and go to Contents → Linux Runtime → Download. This is about 755 MB, once. It is not in the APK, so this step is required.
When it finishes, a Steam (Linux) entry appears in your games list. Tap it.
First launch takes a few minutes. A loading screen first downloads Proton Experimental (ARM64) (about 400 MB), then lets Steam download and update itself. There's a clock on screen so you know it's still working.
Sign in with your Steam account. Password, or the QR code with the Steam mobile app — both work.
Install a game and play. There's nothing to pick and no restart to wait for, because Proton is already there.

If the Proton download on the loading screen fails, the app skips it and Steam fetches Proton itself instead. In that case, watch for the Proton Experimental (ARM64) install box, let the client restart itself once, and only then install a game. A game installed before that restart fails to launch.

That's it. Your existing Wine containers and games are completely untouched by any of this.

Optional tweaks — the ⚙️ next to the Steam (Linux) entry holds resolution (720p by default, because Steam's own interface is expensive to draw), drivers, cores, audio, frame generation, the HUD, Touch, Components, Your games in Steam and the Steam client update channel. GE-Proton and proton-cachyos (ARM64 builds) can be downloaded in Contents → Linux Runtime and picked per game on Steam's own Compatibility page.

⬆️ Upgrading

From 3.1.2: install over. Nothing else changes until you download the Linux Runtime.
From a 3.1.3 pre-release: install over. You stay signed in, and your games, Proton and settings are kept.
From the September 21 test build: install over, then open Contents → Linux Runtime once. That moves the Steam (Linux) entry out of its old Wine container and carries your settings over (HUD, LSFG, audio, drivers). Don't remove or re-download the runtime. If you made a container only for Steam, you can delete it afterwards (the Linux Desktop entry stays in the container — leave that one alone if you use it).

🐞 If something goes wrong

Post the whole session folder from Download/Bannerlator-LinuxSteam/session-<date>-<time>/. It is already scrubbed — tokens, Steam IDs and login files are masked or never copied, so it is safe to post.

Known and already on the list, no need to report: Steam Deck mode breaks game controllers, FlatOut shrinks to the corner after Guide → Resume, TF2 says "insecure", GTA V Enhanced does not run, Serious Sam Shatterverse is killed for memory, NFS Hot Pursuit Remastered faults. Almost everything was proven on one AYANEO Pocket FIT — reports from any other device are the single most useful thing right now.

🆕 What's New in 3.1.2

The Wayland update. Bannerlator can now draw a game through its own embedded Wayland compositor instead of the Java X server — a second display backend, chosen per container. It does things X11 cannot: HDR10, launching a game on your TV, zero-copy presentation, eight bundled game drivers to pick from per game, real mouse-look, and frame generation in HDR.

🧪 Wayland is EXPERIMENTAL and is not a replacement for X11. It is very new and it has bugs — some games run worse than on X11, some will not run at all. X11 remains the default and stays fully supported, and is still the right choice for anything you actually want to play. Wayland is off unless you turn it on, per container, and your existing containers are untouched.

It only works on the new versionCode 8 arm64ec Proton 11 layers (the (v8) rows in the catalog) — not on the x86_64 (box64) layers and not on the Proton 10 layers, which stay on v7. It also needs an Adreno GPU, because the bundled drivers are Turnip; Mali, Xclipse and PowerVR phones stay on X11.

🌊 Wayland display backend (experimental). Turn it on per container. A game draws straight into Bannerlator's compositor, and you pick one of eight bundled Wayland Turnip drivers per game.
🌈 HDR10 on HDR screens. Your screen's real peak, frame-average and black level are described to Windows, so a game's own HDR option stops being greyed out.
📺 Play on your TV. A TV tab appears while an external screen is connected: launch the session straight onto the TV (in HDR when it supports it), with a companion screen on the handheld. Unplug and the game moves back and carries on.
🎭 GPU name spoof on Wayland, plus a DXVK memory cap and present-mode picker in the driver gear.
⚡ Wayland performance, phase 1 — measured on an Adreno 750: +9% Vulkan, +12% D3D12, +20% DirectDraw, with higher 1% lows.
📦 New versionCode 8 compatibility layers — every Proton / GE-Proton 11.x layer rebuilt with the Wayland driver and HDR10, plus Proton-CachyOS joining the catalog and x86_64 builds for GE 11.0-7, 11.0-7.1 and CachyOS. Proton 10.0-4 and GE 10.0-34 stay at v7.
🎮 A physical controller stick can move the mouse with the on-screen controls switched off.

🆕 Earlier — 3.1.1 (the XMB update)

The XMB update. The Games tab gets an XMB view — scroll through your games side to side, the way the PlayStation 3's menu works, and open every setting and tool for the game in focus right there, without pop-ups; built for a controller, in portrait and landscape. LSFG Native gets two experimental options from community contributor clintOnSky — a lower capture resolution that makes frame generation much lighter on weaker phones, and support for stock drivers that only report Vulkan 1.1 — and it starts faster when you turn it on. Entirely app-side — no ImageFS reinstall; install over 3.1.0 and everything carries over. Full notes: docs/releases/3.1.1.md.

🎮 XMB view. Tap the Games tab's view button until you reach XMB. Games run across, the focused game's options run down, with an info panel (store badges, settings chips, playtime, genres, Metacritic, description) and an animated background in your accent colour. Settings, Game Details, Properties, Clone, Remove, logs, community configs, cover scraping, Copy to Drive C, save backup / restore and Change executable all open as further XMB columns instead of pop-ups, and changes save as you go. Controller: left / right games, up / down options, A picks, B goes back, LB / RB jump five games or switch sections. Tested on an AYANEO Pocket FIT in both orientations.
🎞️ LSFG Native: capture resolution and Vulkan 1.1 drivers (experimental, off by default). Run frame generation at a lower height (Panel / Game / a height, never below a quarter of the screen) and scale the result up — far cheaper on the GPU, post effects and upscalers still work. A Vulkan 1.1 compat switch lets it run on a stock driver that has the right extensions. From clintOnSky (#512), tested on his Adreno 710.
⚡ LSFG Native starts faster. In some setups it built its shaders twice when turned on; it now builds them once.
🕹️ Per-game settings pop-up: L1 / R1 switch between its sections from anywhere.
🎮 Steam Controller over a USB cable is now tested (thanks to TAR).

🆕 Earlier — 3.1.0 (the Steam Controller update)

The Steam Controller update. Bannerlator now talks to the Steam Controller directly — the 2026 model, and the original over Bluetooth — so it works as a real controller in games, with your bindings, remappable back buttons and a trackpad mouse. Frame generation now fits your screen by itself and warns when your numbers can't work. Plus SGSR HQ upscaling, per-game texture filtering, and new containers that start at a screen size matching your panel. Entirely app-side — no ImageFS reinstall; install over 3.0.9 and everything carries over. Full notes: docs/releases/3.1.0.md.

🎮 Steam Controller support (opt-in). Input Controls → Device → Steam Controller. Out of the box a Steam Controller acts as a keyboard and mouse; Bannerlator now opens it through SDL3's Steam Controller driver and reads it as a full controller — its own player slot, rumble, your profile's Default / Any Controller bindings, extra buttons (L4 / L5 / R4 / R5 and the … button) mappable to any button, click or key, a trackpad mouse (right, left or both), and the Input Controls Test dialog. Tested over Bluetooth and a USB cable; the wireless puck is supported but not tested yet. Thanks to TAR for testing it through six builds.
🎞️ Frame generation that fits your screen. A side-menu warning when Max FPS × multiplier is more than your screen can show, with a one-tap Set Max FPS to N; Auto (match FPS) fits the display to exactly Max FPS × multiplier (or the closest rate above it) and turns on while frame generation runs — turn it off and that game remembers; and a plain "can't run here" reason (Renderer Driver below Vulkan 1.3, missing Lossless.dll, non-Vulkan renderer) with the multiplier buttons greyed out.
🖼️ SGSR HQ. A new Scaling mode next to SGSR that follows the direction of edges for cleaner diagonals, at about the same cost (Vulkan and OpenGL).
🧵 Per-game texture filtering. Anisotropic filtering (2×–16×) and Texture sharpness (Auto matches your upscaling) in the DXVK / VEGAS settings, for DirectX 9–11 games.
📐 New containers fit your panel. 1280×800 on 16:10 and 3:2 screens, 1280×960 on 4:3 ones; 16:9 stays at 1280×720. Existing containers are never changed.
📘 LSFG Native guide updated for 3.1.0 — LSFG Native Made Simple.

🆕 Earlier — 3.0.9 (the frame-generation update)

Win-FG Native, Bannerlator's own frame generation, moved into Bannerlator's compositor — where it finally works: nothing to buy, nothing to import, an exact 2× on real hardware, and its source is public (MIT). Full notes: docs/releases/3.0.9.md.

🎞️ Win-FG Native in the compositor. Measured 45 → 90 fps at 2× on an Adreno 750 — as an in-game layer it had been losing its generated frames — and it switches on in about 124 ms. Source: The412Banner/win-fg.
🩹 LSFG Native — three fixes. No smear on switch-on, the switch-on stall roughly halved (4.8 s → 2.25 s), and two freeze paths closed.
💾 Save backups carry the emulator's account id, so a restored save no longer shows only New Game after a container rebuild.
💽 Move an installed Steam game between internal storage and the SD card, from the game's ⋮ menu.
🎛️ Preset editing on the Container screen and in a game's own settings, scoped to where you make the edit.
📦 New -arm64ec-6 compatibility layers — controllers no longer stop working part-way through a game.

🆕 Earlier — 3.0.8 (the downloads-and-containers update)

The downloads-and-containers update. Epic, GOG and Amazon downloads move onto the same Rust engine Steam uses — two to nearly three times faster on the same titles. Containers are no longer stuck on the compatibility layer they were created with: when a newer layer appears, the container card offers Update layer, downloads it if needed, keeps your games, saves, shortcuts and settings, and can put the old one back. New -arm64ec-5 layers fix the Denuvo unwinder crash (Need for Speed Heat now reaches gameplay). Also: one-tap Screen Effect Looks, a Media tab on every store page, and the file-manager and EA fixes reported since 3.0.7. Entirely app-side — no ImageFS reinstall; install over 3.0.7 and everything carries over. Full notes: docs/releases/3.0.8.md.

⬇️ Epic, GOG and Amazon downloads on the Rust engine. The last three Java download managers are replaced by the adaptive-concurrency engine Steam already uses. Same title, same Wi-Fi: GOG 4.5 s → 2.2 s, Epic 11.4 s → 4.3 s, Amazon 68 s → 48 s. A Store download speed row in Log Manager (Slow/Medium/Fast/Blazing, default Fast) sets how many pieces are pulled at once; the Java engines stay as a fallback.
🔄 Update a container's compatibility layer in place. When a newer build of your container's layer exists, the container card offers Update layer → vN with a ? explainer. It backs up the registry, switches the layer and refreshes only Wine's own files — games, saves, shortcuts and container settings are kept, DXVK / FEX / game files untouched. If the layer is only in the catalog it is downloaded first. The old layer stays installed and Revert layer is in the ⋮ menu.
📦 New -arm64ec-5 compatibility layers. All seven Proton / GE-Proton layers rebuilt (build-bionic-layers-20260907-eccode, now the catalog default): a Wine RtlIsEcCode bounds check that stops Denuvo-protected games dying in the exception unwinder (Need for Speed Heat now reaches gameplay, and Titanfall 2 boots), DirectAudio v1.3.2, and one .wcp per layer for both 4 KB and 16 KB page sizes. Components matter: Heat was proven on this layer with a FEXCore nightly, and black-screens on a different one — see the release notes.
🎨 Screen Effect "Looks". One-tap presets heading the drawer's Screen Effects section on both renderer paths — Game Clarity, Vivid, Cinematic, Competitive, Filmic, Arcade, Retro CRT and more — plus a new Saturation control on both paths so the colour Looks grade identically.
🛒 Store Media tab. Screenshots and trailers on the Steam, GOG, Epic and Amazon detail pages; the official catalog can also be used as a Contents repository, and a download can be kept as a save archive only.
🛠️ Fixes. File manager: the up arrow and Back work after opening a Favorite or a side-bar shortcut, and every folder lists a .. row (#476); EA setup finds games added before EA support existed (the Need for Speed Heat "couldn't locate the install folder" report); layers with a version code of 10 or higher resolve instead of falling back to Proton 9; Relative Mouse saved per game (#431); uniform file-manager card height (#475); the launch failure card's Close works from the Games screen.

🆕 Earlier — 3.0.7 (the EA update)

EA-published games from your Steam library launch the way they do on a PC — Steam starts EA Desktop, EA Desktop starts the game. A one-time Set up EA Desktop session per container, an EA badge on detected titles, a card naming EA's reason when it refuses a licence, -arm64ec-4 layers with the EA networking and installer fixes, and a rebuilt Input Controls import flow with live previews. Full notes: docs/releases/3.0.7.md.

🎮 EA games from your Steam library. Origin-era and EA-app-era titles are detected and get an EA badge. The first launch offers a one-time Set up EA Desktop session (you click through EA's installer; the app handles Mono, Gecko, the registry and the Steam install script). After that it is press-play: the game starts through Steam and EA Desktop in the right order, and the session stays alive through EA's hand-offs. Device-proven with Need for Speed Payback / Most Wanted (2012) / Rivals and STAR WARS Jedi: Survivor. Needs the SteamLite launch mode (selected and remembered for EA titles), the new -4 compatibility layers from the catalog and the hosted SteamLite v7 client. Titles using EA's Javelin anti-cheat are refused up front. Researched and implemented by The412Banner by reverse-engineering GameHub's EA launch methods and techniques.
📦 New compatibility layers. All seven Proton / GE-Proton layers rebuilt into a new -arm64ec-4 slot (build-bionic-layers-20260906-eanet2): EA Desktop can go online (dual-stack DNS + a real default route) and, on the Wine 11 layers, EA's installer no longer aborts on a GDI+ assertion. Create a fresh container on a -4 layer for EA titles; existing containers keep their layer.
⚠️ EA limits to know. Older EA games (e.g. Payback) ask for the EA sign-in on every launch, and EA counts each one — too many in a short period and EA refuses the game for a while ("too many computers"; clears in hours, or via Deauthorize computers in your EA account). Every container looks like a separate PC to EA. Need for Speed (2015) goes black after activation — open.
🛑 When EA says no, you see why. If EA Desktop refuses to license a game, a card names EA's reason with Retry / Open log folder / Close instead of a black screen.
🕹️ Input Controls import rebuilt. Arrows point the right way, a proper import chooser (in-app file manager / system picker / community list), and a per-row preview in Download Profiles so you can see a layout before importing it.
🎞️ LSFG Native follow-ups. Each generated frame is presented as soon as it is ready; the drawer shows the chain's GPU cost in ms per generated frame; the shader cache is built at import; the pacer's ceiling comes from the panel's top refresh mode.
🛠️ Fixes. HUD API line reads the game's real API on EA titles (D3D11 · DXVK, not D3D12); stray "EA" cards no longer appear in the Games grid; SteamLite / Goldberg updates can't leave the client missing; one broken shortcut file no longer crashes the app at start; EA titles render on app-built containers (ASCII install path); install-script registry parity with the real Steam client.

🆕 Earlier — 3.0.2 (the Steam-focused update)

A Steam-focused update on top of the 3.0.1 point release — Friends & Chat, real-Steam (VAC) online play, achievements & cloud saves, one-touch save syncing and SD-card installs, plus graphics / frame-gen and runtime polish. Entirely app-side — no ImageFS reinstall; install over 3.0.x and your containers, Wine installs, themes, accent colour and per-game settings all carry over. (Real-Steam is a separate one-time in-app download.)

🖥️ Steam Friends & Chat (off by default). A full friends list with live presence (online / in-game / away), unread badges and collapsible sections; per-friend chat with text and images, persisted history that opens at the newest / first-unread message, add-by-code / name-search / quick-invite, an in-app friend profile, a landscape two-pane view, chat notifications with a sound toggle, typing indicators, and instant reconnect after a background drop. The whole feature is a master opt-in that stays dormant until you turn it on. 🙏 Thanks to iamtooshaar (Discord) for helping test and shake out the bugs.
🔐 SteamLite — real Steam (VAC) online. A new launch mode that runs a game through the genuine Steam client for a VAC-eligible, online session — chosen per game in the launch popup (RealSteam / Goldberg / Raw). It watches the game's launcher exe (not the arch-specific …_win64) so the game launches secure regardless of which exe the shortcut names, pops the in-game gold achievement pill for real-Steam unlocks, and can capture an opt-in scrubbed log for diagnosing a launch. The Steam client + clean-room headless agent ship as a downloadable steamlite-v1 content package, installed from inside the app. Device-proven online on Counter-Strike 1.6, Counter-Strike: Source, Team Fortress 2 and Left 4 Dead 2 (VAC-secured), plus Brawlhalla and Stumble Guys (live-service); Borderlands 2 is in testing.
🏆 Achievements & cloud saves — in both launch modes. Real Steam achievements are seeded from your account into a tabbed detail-page grid, with in-game gold pills as you unlock them — and they unlock and sync whether you play through Goldberg (emulated) or SteamLite (real Steam / VAC), the same pill and the same sync-back either way. Cloud saves keep parity around each play session, and a new one-touch "Sync Now" button on the Save Manager banner syncs every flagged game at once — each in the correct direction (upload what's newer locally, pull what's newer in the cloud) — with a live "Syncing 3/7…" count instead of tapping each game.
💾 Install Steam games to an SD card. A per-game toggle installs a Steam download onto a removable SD card to free internal space; the shortcut resolves through a container drive letter, so secure launch, saves and achievements are unaffected.
🏪 Rebuilt Steam store. The per-game detail screen was redesigned into a cleaner, landscape-aware tabbed layout (overview · achievements grid · DLC) with the store badge, connection state and launch actions in one place — plus a live connection pill, auto-connect on launch, download hardening and full owned-DLC listing.
🎞️ Graphics & frame-gen fixes. A fuller frame-gen pause / teardown / resume reset on level / model / preset change, a swapchain-recreate config reload, an Adreno-840 present-id freeze fix, and in-app frame-gen diagnostics.
🎛️ Containers, launch & file manager. DXVK HUD is now off by default on new containers (still toggleable in the env-var editor), a redesigned source- and orientation-adaptive launch popup, a CUSTOM origin badge for games you add yourself, and file attributes (Read-only / Hidden) shown in the File Manager.

Also rolled up from the 3.0.1 point release on 3.0.0: swipeable on-screen controls (slide-to-press, a per-element toggle and a dedicated Swipe drawer tab), an LSFG frame-gen fix, a Steam depot OOM fix (#408), a controls-alignment fix (#413), and assorted File-Manager / ETA / crash fixes.

🆕 Earlier — 3.0.0 (the big 3.0 stable)

The big 3.0 stable — rolls up everything since 2.9.9, including the 3.0.0-pre1 / pre2 opt-in betas. Entirely app-side — no ImageFS reinstall; install over 2.9.9 and your containers, Wine installs, themes, accent colour and per-game settings all carry over. Full notes on the 3.0.0 release page.

🔊 New three-engine audio stack (the headline). The ground-up audio rebuild that was "coming soon" in 2.9.9 has landed: a new adaptive PulseAudio engine (grows its buffer on crackle/underruns, re-opens cleanly when your output changes), a second adaptive ALSA engine, and an experimental third DirectAudio driver — each with an Audio cog in the container editor, per-game shortcut settings and the in-game side-menu, presets + fine-tune rows, a per-row "?" explanation, and a latency slider that really drives the buffer. Strict per-engine / per-scope settings mean changing one never rewrites another.
🛒 Storefronts + automatic cloud saves across GOG, Epic & Steam. GOG gets a major overhaul — automatic cloud saves (auto-path, upload-on-exit / download-on-launch, content-hash skip), MD5 verify + repair, redistributable auto-install, per-DLC installs, faster parallel downloads, and a Save Manager tab with cover art. Epic / EOS adds cloud saves, real launch-time sign-in + EOS game IDs, EPIC/EOS badges, Denuvo & offline support, and a robust cancelable downloader. Steam adds one-tap Lossless Scaling "Detect from store", beta-branch selection, and non-game apps in your library.
🎮 Games & shortcuts. The internal-storage intro-movie hang fix — add a game from Drive C and Copy game to Drive C (moves a game onto the container's fast C: drive and re-points the shortcut), plus Change executable, a file picker that opens at your storage root with a working Back button, responsive shortcut settings, per-DLL toggles, per-game graphics persistence, and an opt-in Big Picture games wall.
🖥️ Graphics & performance. Hardened Native Rendering with a per-container / per-game backend picker, clean-room win-fg frame generation (replaces bionic-fg, adapts AMD FidelityFX FSR3), Samsung Galaxy no-root power control, a live Performance dashboard, an upgraded Fusion HUD (battery temp, accurate DXVK/VKD3D label), and a new Contents hub for browsing/installing/removing GPU drivers & components. Plus a wrapper + Adreno Vulkan fix (#403) — DXVK/games start again on wrapper drivers and low-tier Adreno (e.g. 610).
🐛 Stability. Rootless native crash-capture with real backtraces, a background-pause fix for games with very long executable names, malformed-environment-variable resilience, and assorted X-server leak/crash fixes.

🎞️ Frame Generation & Present Modes

Frame generation inserts in-between frames to make motion look smoother — it helps most when a game runs below your screen's refresh rate. It runs on the Vulkan renderer, and there are two engines:

Engine	Where it runs	Needs
Win-FG Native	inside Bannerlator's compositor (Android side)	nothing — Bannerlator's own, weightless
LSFG Native	inside Bannerlator's compositor (Android side)	your own `Lossless.dll`

(The older lsfg-vk engine, which ran the same shaders as a layer inside the game, is retired: its generated frames were routinely lost on the way to the screen. LSFG Native uses the same DLL and replaces it; containers still set to lsfg-vk run LSFG Native.)

Both engines are what to reach for on a game you've capped: lock the game at 30, pick 4×, and the panel gets 120 — with the game itself untouched, the device cooler than running it uncapped, and the in-game HUD showing 30→120. They work best at or under panel ÷ 4 (36 fps on a 144 Hz screen fills every refresh). Win-FG Native needs no files at all; LSFG Native runs the Lossless Scaling shaders out of your own DLL.

Present mode decides how finished frames are handed to your screen:

Mode	What it does
FIFO (default)	"Vsync on" — smooth, tear-free, most battery-friendly, but it makes the game wait for the display.
Mailbox	"Fast vsync" — never makes the game wait, still tear-free.
Immediate	"Vsync off" — lowest input lag, but can tear.

Bannerlator handles the present mode for you. Both native engines force FIFO while they're generating — they queue the real and generated frames together and need FIFO to show them one per refresh; under Mailbox the display would keep only the newest and discard the rest. Your chosen mode is restored the moment frame generation turns off. While a native engine is generating it also switches the FPS limiter on and turns Auto (match FPS) on, which fits the screen to Max FPS × multiplier — the exact rate, or the closest one above it (turn Auto off and that game remembers). If Max FPS × multiplier is more than your screen can show, the side menu warns you and offers a one-tap fix. Both controls come back as you had them when frame generation stops. New to it? Read LSFG Native Made Simple. You can also switch modes live from the Present Mode selector in the in-game Graphics tab, and every mode is explained by a "?" button and in the in-app "What is all this?" glossary.

Should I switch my games to Wayland?

No — not the ones you care about. Wayland is experimental and new. X11 is still the default, still fully supported, and still the right choice for playing. Wayland exists so you can try the things X11 cannot do — HDR10, playing on a TV, zero-copy presentation, picking a game driver per game — ideally on a spare container rather than the one with your save files.

It also has hard requirements: a versionCode 8 arm64ec Proton 11 layer (the (v8) rows in the catalog) and an Adreno GPU. On anything else the option is greyed out and a launch falls back to X11 with a notice. If a game misbehaves on Wayland, switch that container back to X11 — one setting — and report it with the log from Download/Wayland-logs/.

Why is my FPS reading different from another emulator?

With frame generation on, two apps' FPS numbers can look very different — because they count frames at different points in the pipeline:

An app that reads the game's raw output shows a clean 2× / 3× / 4× — impressive, but it counts frames your screen never actually displays.
Bannerlator's HUD counts the frames the game delivers. With either native engine the generated frames are added after that point, so every HUD style shows both numbers — 30→120 — the game's rate and what actually reaches the panel. On a guest-side layer (the frame-gen training-capture path) the same arrow appears only if frames are being lost between the game and the panel (e.g. 70→35), which is a problem rather than a feature.

Neither number is "frames on glass." Your panel's refresh rate (e.g. 120 or 144 Hz) is the true ceiling — above it, frames are generated but not shown. A result like 65 → 107 fps at 2× on a demanding game, with the frametime roughly halving, is frame generation working correctly.

✨ Full Features

Everything Bannerlator offers, at a glance. No PC and no root required — it runs Windows apps and games directly on your Android device.

🍷 Windows compatibility

Wine Windows compatibility layer — run native Win32/Win64 applications and games.
Box64 / Box86 x86 & x86-64 → ARM translation, with selectable performance presets.
WOWBox64 for arm64ec containers (correctly labelled per container).
FEXCore as an alternative x86/x64 emulation backend — with automatic unixlib (.so) matching: whichever FEXCore version you pick per game or container, the native .so companion is kept in sync on every launch (matched for unixlib builds, cleared for DLL-only), so there's never a stale or mismatched .so.
arm64ec and x64 container support.

🎨 Graphics & translation layers

📖 Not sure which graphics driver or wrapper to use? Read the wrapper & driver guide → — what a wrapper actually does, a pick-by-GPU table (Adreno / Mali / Xclipse / PowerVR), every built-in driver explained, all 18 catalog wrappers with their authors and upstream links, which of them are byte-identical across projects (so you don't test the same file twice), and troubleshooting.

DXVK — DirectX 8 / 9 / 10 / 11 → Vulkan (with GPLAsync and Sarek variants).
VKD3D-Proton — DirectX 12 → Vulkan.
WineD3D / DirectDraw OpenGL fallback paths for older titles.
D7VK — DirectX 7 / DirectDraw (Direct3D 3–7) → Vulkan for old 2D/3D titles that otherwise take the slow OpenGL path (WinterSnowfall's DXVK-lineage Vulkan implementation). Selectable in the DDraw Wrapper picker per container and per game; ships bundled as the default and is catalog-backed — a "D7VK Version" dropdown lets you download and switch between nightly d7vk builds.
Proton bionic translation layers (via GameNative) — including Proton 11.0-1 in arm64ec and x86-64 builds, packaged per Android SDK (SDK 28 for Android 9-era, SDK 35 for Android 15) and downloadable from the Compatibility Layers menu.
VEGAS — Adreno-optimized DXVK for reduced stutter and real-time upscaling on mobile GPUs.
- 📖 New to VEGAS? Read the VEGAS DXVK FAQ — install, config, FSR, tiers, frame generation & shader-stutter troubleshooting.
- 🚀 Support VEGAS Development — low-level graphics dev & vibecoder: debugging, refactoring & improving original DXVK code for Adreno. ❤️ Sponsor isygold →
Per-game texture filtering (new in 3.1.0) — Anisotropic filtering (2× / 4× / 8× / 16×) and Texture sharpness (Game default / Auto / −0.25 to −1.0; Auto matches your upscaling, following AMD's FSR guidance) in the DXVK / VEGAS settings, per container or per game. DirectX 9–11 (DXVK) only; nothing changes at Game default.
Turnip / Mesa open-source Adreno Vulkan drivers, with Timeline Semaphore patches for newer DXVK; bundled and downloadable driver options.
Driver-source management — add, toggle and remove your own adrenotools GPU-driver feeds (a custom JSON URL or a GitHub owner/repo) on top of the built-in sources, so you can pull Turnip / driver builds straight from the repos you trust. (Requested in #160.)
BCn transcoding for Mali / Xclipse — a "Wrapper + bcn_layer" graphics driver (leegao's bcn_layer, shader-v3) that decodes BC textures on the GPU, so BCn games run on GPUs without hardware BC support — with a BCn Layer Settings panel (force-decode, ETC2 / ASTC transcode, image-view mode, debug logging). An experimental "Wrapper-gamenative" driver (BCn baked into the wrapper, Adreno-only) is also selectable. (Device-proven on Mali-G57.)
Wrapper Version Manager — bring your own graphics wrapper: import / update / delete any .tzst wrapper (from another project or your own build), browse a curated downloadable catalog of wrappers from across the Winlator family (each credited to its source, flagged "Mali only" where relevant), and get auto-detected settings — real toggles / sliders / dropdowns read straight from what each wrapper actually supports, with driver internals and log noise filtered out. Per-entry Update / Reset / Edit / Delete / Details plus a pre-import inspection view. (Modeled on WinlatorMali's graphics-driver manager; requested in #132.) 📖 Which wrapper for my device? →
Mali DX12 (experimental) — a new opt-in 6th graphics driver, "Wrapper + compat + bcn", pairing leegao's BCn transcode layer with a DX12 compat layer and a "Use GameNative engine (DX12)" toggle, for Valhall-class Mali GPUs. Inert unless selected and unaffected on Qualcomm / Adreno; DX12 on Mali is still being proven on hardware — treat it as a test path and report back with logs.

🖥️ Renderers

Multiple host renderers — Vulkan, OpenGL, SurfaceFlinger, and VirGL.
Wayland display backend (experimental, new in 3.1.2) — an alternative to the Java X server: the game draws into Bannerlator's own embedded Wayland compositor. Brings HDR10, launching a game on an external screen / TV, zero-copy presentation, real mouse-look and eight bundled Wayland Turnip drivers selectable per game. Chosen per container, off by default. (3.1.4 pre-release 1: a built-in adapter runs your normal Turnip driver on Wayland too, so it's one driver choice, like X11.)
- ⚠️ Experimental, and not a replacement for X11. Expect bugs; X11 stays the default and stays supported. Requires a versionCode 8 arm64ec Proton 11 layer (the (v8) catalog rows) and an Adreno GPU — Mali / Xclipse / PowerVR stay on X11.
SurfaceFlinger renderer colour fix — the SurfaceFlinger (ASurfaceRenderer) host renderer got a crash + colour-accuracy fix (red/blue channel swap corrected, GPU-side format converter, proper fencing), with a "Correct SurfaceFlinger colours" toggle available per container and per game (shown inline under the Renderer picker when SurfaceFlinger is selected, on by default). (Ported from GameNative #1620 / #1644.)
ℹ️ The Vulkan host renderer uses the rendering path from StevenMXZ (Winlator-Ludashi); its AHardwareBuffer present path — what makes Vulkan / DXVK / VKD3D content actually display correctly — was ported from / cross-examined against GameNative. See Credits.
Native Rendering (Low-Latency Mode) — low-latency direct-scanout presentation on both the Vulkan and OpenGL renderers, skipping the compositor blit to cut input lag (mutually exclusive with that renderer's post-processing effects / scaling, since it bypasses the compositor).
Spatial upscalers on both the Vulkan and OpenGL renderers — SGSR (Snapdragon GSR 1.0), SGSR HQ (new in 3.1.0 — its edge-direction variant, for cleaner diagonals) and FSR / FSR-Fit (AMD FidelityFX Super Resolution 1.0), plus NIS (NVIDIA Image Scaling, Vulkan), a Sharpen (RCAS) mode and Linear / Nearest, all switchable live in the in-game drawer. On Vulkan it engages when a game renders below display resolution; on OpenGL it renders the scene at a reduced internal resolution and reconstructs it back up. Every sharpness slider runs 0 (off) → 100 (max). Your chosen scaling mode is now remembered per game across relaunch.
Fullscreen aspect-ratio modes — control how a game fills the screen, per container and per game: Off (windowed, letterboxed), Fit (fullscreen, aspect preserved), Stretch (fills, ignores aspect), Fill (fills with aspect kept, cropping the overflow — no bars, no distortion) and Integer (largest whole-number scale, pixel-perfect and centered). A five-button selector in the in-game drawer switches modes live without closing the drawer, on all three host renderers. Your choice is saved per game.
Supersampling (Render scale) — render above display resolution (1.25× / 1.5× / 2×) and downsample with a Lanczos-2 filter for DSR / OGSSAA-style anti-aliasing; set per container / per shortcut.
Screen effects on both the OpenGL and Vulkan renderers — FXAA, Toon, CRT, NTSC, Color grading, CAS sharpening, and fake-HDR (the Vulkan path runs them through a new post-processing pipeline; previously they were OpenGL-only).
Debanding (Vulkan) — an optional terminal dither pass that removes the visible banding from smooth gradients, skies, and dark scenes on 8-bit output, with an adjustable strength.
ReShade post-processing — run real ReShade .fx effects (colour grading, sharpen, film grain, CRT, tonemap…) on DXVK / VKD3D games. Effects compile on-device via a bundled vkBasalt layer; pick from an on-demand catalog of ~100 curated MIT/CC0 effects or drop your own into the ReShade/ folder. A dedicated in-game ReShade tab auto-generates properly typed controls (sliders / toggles / dropdowns / colour pickers) from each shader, so you can toggle and tune effects live with a Reset-to-defaults button. Effects are configured per game (container or shortcut), persist across relaunch, and can be run solo or stacked. (Color effects today; depth effects such as SSAO/DOF are not included yet.)
- ⚠️ Stacking multiple effects? Add them a few at a time. Each effect compiles on-device and costs GPU — selecting too many at once can stop a game from starting, showing a flat / blank screen instead of the game. If that happens, uncheck effects one at a time (or the specific heavy one) in the per-game ReShade effect settings until it boots, then add more gradually.
Match refresh rate to FPS (VRR) — the display's refresh rate can follow your frame rate: an Auto (match FPS) toggle or a manual 60 / 90 / 120 / 144 Hz slider, on all three host renderers, auto-disabled on displays that don't support variable refresh.
Adjustable resolution and frame-rate limit.

🎞️ Frame generation & pacing

Two selectable frame-generation engines — pick Off / Win-FG Native / LSFG Native per container; the running engine is shown as a badge in the in-game drawer. Both now run inside Bannerlator's own compositor, which is what lets their generated frames actually reach the panel.
- Win-FG Native — Bannerlator's own clean-room frame generation (source, MIT): FSR3-family optical flow plus from-scratch synthesis, no proprietary weights, nothing to buy and nothing to import. Built in and ready out of the box. Device-proven 45 → 90 fps at 2× on an Adreno 750, and it arms in ~124 ms because its shaders are compiled in rather than parsed from a file. It previously ran as a layer inside the game, where the compositor discarded most of its generated frames — the in-game counter read 2× while the panel showed 1×; running it natively removes that hop.
- LSFG Native (new in 3.0.6) — Lossless Scaling's frame generation running inside Bannerlator's own compositor, ported from the Eden emulator's native present path with WinNative's implementation as the reference. The shaders come from your own Lossless.dll, extracted on device. Device-proven 30 → 120 fps at the panel. Device support: generally Adreno A7xx and newer GPUs, plus some MediaTek Dimensity devices in community testing; elsewhere it reports itself unsupported in-game or may not keep up. Experimental (3.1.1, off by default): a capture resolution that runs the frame generation at a lower height and scales it up — far cheaper on weaker GPUs — and a Vulkan 1.1 compat switch for stock drivers that report only Vulkan 1.1 but have the needed extensions (#512 by clintOnSky). (The former lsfg-vk in-game layer engine is retired; anything still set to it runs LSFG Native.)
ℹ️ Why win-fg exists, and what it is. Bannerlator previously bundled a different frame-generation layer that was later found to embed compute shaders whose model weights were essentially identical to the proprietary Lossless Scaling frame-generation model — which cannot be redistributed. That layer was removed, and win-fg is its clean-room replacement: a frame-gen engine we built from the ground up. Its motion estimation is our MIT adaptation of AMD FidelityFX FSR3 optical flow (an algorithm — no learned weights), and its frame synthesis is written from first principles using published, permissively-licensed math. It bundles no proprietary code or weights. That's also why the two engines sit side by side: LSFG Native relies on your own legally-owned Lossless.dll, while Win-FG Native is entirely Bannerlator's own and needs nothing to run. Its full source, shader-by-shader provenance and engineering log are public at The412Banner/win-fg.
⚠️ LSFG Native requires you to supply your own Lossless.dll. Bannerlator bundles no proprietary Lossless Scaling files. You must own Lossless Scaling (THS, on Steam) and import its Lossless.dll via Settings → Frame Generation — LSFG Native (Detect from the in-app Steam store, or import a copy). The DLL is copied into app storage, its shaders are extracted and cached on device, and it serves all containers. Until you import a valid Lossless.dll, the LSFG Native option stays greyed out; Win-FG Native needs no DLL and works without it.
Live in-game controls for whichever engine the container runs: switch between Off / 2× / 3× / 4× and adjust the flow-scale slider right from the in-game Graphics drawer, hot-reloaded with no restart.
Screen fit & warnings (new in 3.1.0) — while frame generation runs, Auto (match FPS) fits the display to Max FPS × multiplier (the exact rate or the closest one above; a per-game opt-out), the side menu warns when your numbers are more than the screen can show and offers a one-tap Set Max FPS to N, and a plain reason appears when frame generation can't run on your driver or renderer.
FPS Limiter — a standalone, engine-independent live frame cap. It paces the X11 Present extension by delaying the IdleNotify that frees the guest's buffer, so the game itself throttles (the in-game HUD reflects the cap and GPU/power draw drops). Works the same with frame gen Off, win-fg, or LSFG Native, on both host renderers, all guest APIs. While LSFG Native is generating the limiter is locked on — a steady, capped game is what frame generation is built on — and restored when it stops. This guest-side present-pacing mechanism was ported from GameNative (see Credits).
Performance model — LSFG Native always runs Lossless Scaling's lighter "performance" model (about 2 ms of GPU per generated frame on an Adreno 750). (The lsfg-vk Performance-mode toggle requested by @Tony57319 in #152 is retired with lsfg-vk; that model is now the one LSFG Native uses.)
Confirmed on both the OpenGL and Vulkan host renderers.

⚡ Performance & thermal controls

Power-user device-tuning, reachable from App Settings → Performance and mirrored live in the in-game Debug tab (kept in two-way sync), with global defaults and optional per-game overrides — an override is honored only when it differs from the global default, and each has a one-tap reset-to-global.

No root required — Sustained Performance Mode (steadies clock speeds over long sessions), Thread Priority Boost (raises the guest CPU-worker threads for more CPU time, never downgrading an already-hot thread), and Prefer Big Cores (pins the running game to the fastest CPU cluster instead of the efficiency cores).
Opt-in root tier (Magisk / KernelSU / APatch) — behind a Grant Root gate and a scroll-to-accept "USE AT YOUR OWN RISK" disclaimer: CPU governor → performance, lock CPU frequency to max, keep all cores online, lock GPU to max clock, disable thermal throttling, fan to maximum, and a one-shot "Free memory now" action. Entirely optional — nothing writes to your system files unless you grant root and accept the warning.
Always-on snapshot-revert — the first time a setting is touched its exact prior value is captured, and everything is restored to precisely that value on game-exit, app-background or crash. The snapshot is persisted to disk, so even a hard kill is repaired on next launch. It never guesses defaults and can't be disabled.
Temperature Watchdog — anchored to your device's own thermal trip points, it polls the hottest CPU/GPU zone and force-reverts all performance state before the device overheats. Presets Conservative / Balanced / Aggressive / Manual, on by default (turning it off needs the same scroll-to-accept disclaimer).
In-app help — a "?" explainer on every toggle, an "Explain toggles" overview, a watchdog "What's this?", and live CPU / GPU temps plus your device's own thermal limits shown inline. (Device-verified on an AYANEO Pocket FIT / Adreno.)

📦 Containers

Create and manage multiple isolated Wine containers.
Redesigned container cards — a clean spec-chip layout (renderer · DXVK on top, driver · VKD3D · backend beneath) that matches the game cards.
Auto-close on game exit — the session closes itself once the launched game quits (per-container "Close when game exits" toggle, on by default), so you're not left at a black Wine desktop.
Import / export containers to move or back up setups.
Per-container control of Wine version, graphics driver, DXVK / VKD3D version, Box64 preset, drive mappings, Z-drive selector, and environment variables — the Add Environment Variable picker includes a large set of presets (DXVK / VKD3D / Wine / Mesa) with typed value editors, so common tuning vars are one tap away.
Desktop wallpaper picker — set an image as a container's Wine desktop wallpaper from the container editor, and choose whether it applies to just this container or globally to all of them.
Compatibility Layers download menu — a cloud button on each component (Wine/Proton, DXVK, VKD3D, Box64/WOWBox64, FEXCore) opens a downloader to browse, install or remove versions, with Wine/Proton tabs, an "in use" marker, install-from-file, and byte-accurate download + install progress bars.
In-game refresh-rate unlock — a per-container / per-game toggle that lets a game pick a refresh rate above 60 Hz from its own display menu (requires a "Refreshed" Proton 10.0-4 / 11.0-1 layer; stays off on older layers by design). Distinct from the display's Match refresh rate to FPS (VRR).
Custom startup-services mode — alongside Normal / Essential / Aggressive, a Custom startup option starts with every Wine service off so you enable only the ones you need. (Requested in #168.)
DXVK HUD off by default (new in 3.0.2) — new containers no longer show the DXVK overlay on top of the game. The DXVK_HUD variable stays listed but empty in the env-var editor, so it's one tap to opt back in whenever you want it.
Screen size that fits your panel (new in 3.1.0) — new containers start at 1280×720 on 16:9 screens, 1280×800 on 16:10 and 3:2, and 1280×960 on 4:3 (Retroid Pocket, foldable inner screens). Existing containers and games are never changed.

🕹️ Games, shortcuts & input

Game library with grid or list layout, sorting, and installed/updated filters.
Redesigned game cards — primary chips (renderer · DXVK · frame-gen) over a muted driver · VKD3D · backend line, with the resolution in the subtitle; long component names no longer blank the game title.
Add shortcuts from external storage — a single .exe, or a whole games folder (point at a library folder and every game subfolder is scanned for its real executable, named and cover-arted for one-tap batch add).
Smart import — importing an .exe auto-resolves the authoritative game name and cover art from the Steam store, fixing generic launcher-exe misnames, with a Search Steam confirm step.
Recommended components — a game's bundled redistributables are detected and surfaced as one-tap install chips.
Back up & restore game saves as GameHub-compatible zips, with per-game save discovery and a confirm checklist before anything is overwritten.
SteamGridDB cover-art scraping.
Per-game settings including display language / locale.
Virtual Controller Pro on-screen controls — a Compose-rebuilt controls editor with an in-game live editor, control types Button / D-Pad / Range / Stick / Trackpad plus Dynamic Stick, Mouse Area, Button Grid (with optional multitouch and QWERTY / F-row / NumPad quick-fill) and Expandable Buttons (radial or list fly-outs). Includes control groups (show/hide a whole set), key combos, per-element dead zones, a Hold key, custom control icons (import, tint or use as the whole button), a category-filtered binding picker, an editor reference image, and a control scale up to 300%. Profiles export as ICpx (or best-effort legacy ICP). Overlays follow your app theme or take a per-game custom colour set in the Controls editor. (PR #156 by arro000.) Swipeable controls (new in 3.0.1) — a per-element slide-to-press toggle plus live per-category swipe gates (Buttons / D-Pad / Sticks), mirrored to a dedicated Swipe tab in the in-game drawer so you can slide across buttons instead of tapping each one.
Physical controller support (SDL2), plus touchpad / mouse emulation with adjustable cursor speed. The external controller-binding screen lists each input as a card with readable labels, and buttons you press while binding appear instantly.
Steam Controller support (new in 3.1.0, opt-in) — the 2026 Steam Controller, and the original over Bluetooth, read directly through SDL3's Steam Controller driver (Input Controls → Device → Steam Controller): a real controller in games with rumble and your Default / Any Controller bindings, extra buttons (L4 / L5 / R4 / R5 and the … button) mappable to any button, click or key, a trackpad mouse (right / left / both / off), and full support in the Input Controls Test dialog. Other controllers are untouched.
Controller vibration — PC-accurate dual-motor rumble (strong/weak driven independently) with a per-container vibration mode and intensity, backed by a winebus duration patch so sustained rumble doesn't auto-expire mid-effect (Proton 10/11, arm64ec + x86-64). Plus per-slot rumble toggles and a master switch (in the in-game Vibration section) that silences all rumble regardless of slot, saved globally.
Gyroscope — motion aim — tilt to aim, driving the right stick, left stick or the mouse, in either Rate mode (how fast you turn) or Tilt to Aim orientation mode (the angle you hold), with a choice of activator button (L1 / L2 / R1 / R3 / always-on), Hold or Toggle activation, adjustable sensitivity / deadzone / smoothing / invert, device-level drift calibration, and settings saved per container and per game. 📖 Full guide →

🌐 Community Configs

Browse community-shared, per-game / per-device tuning configs in-app and apply a known-good setup in one tap.

Catalog browser (globe button in the Games header) with search, Steam / Title filters, sort by upvotes / name / device count, and a "Matches my device" filter that narrows to configs shared from hardware like yours.
Per-config cards showing ★ upvotes and ↓ downloads (best-rated first), the source device / SoC and the date, aggregated across every folder a game is known by.
One-tap Apply that surgically merges just the config's settings — DXVK / VKD3D / Turnip driver / FEX preset / renderer / resolution / launch args / environment variables — into your shortcut, preserving everything else you've set. Applies to any shortcut, warning you if it doesn't match the game.
Smart install of a config's missing DXVK / VKD3D / FEXCore build or Turnip GPU driver: an exact match installs with one confirm, otherwise pick from the closest versions (or browse all), and the config auto-applies afterward. FEX date builds match by their YYMM monthly tag; components you already have are recognised, not re-installed.
Config detail page — provenance (source device / SoC / app / date), a plain-language list of what the config sets in Bannerlator's own component terms, and a before-you-apply diff against your shortcut, plus the config's live description, upvotes, downloads and comments — you can upvote and comment yourself.
Read-only for your setup — nothing changes unless you tap Apply; your containers, imagefs and existing settings are never touched.
Share your own setups — export a game's working settings and upload them for the community in a couple of taps. The export captures the full recipe (graphics translator + all its options, driver, renderer, resolution, launch args, env vars and the rest) plus your device / graphics chip — but never your files, store logins, or device-specific driver tuning. Sharing is anonymous by default and Bannerlator keeps its configs in its own space, separate from other apps' libraries. My uploads lets you edit a description inline or delete an upload any time.
Optional account (no email needed) — you never need one, but a username + password account makes your uploads follow you to a new device, puts your name and picture on configs you share, and is recovered with a one-time recovery key instead of an email reset. Everything — browse, apply, share, manage, upvote, comment — works fully anonymously without it.
📖 Read the full plain-English guide → for a friendly, non-technical walkthrough of browsing, applying, sharing, and the optional account/recovery-key system.

🛒 Built-in stores & cross-store Download Manager

Sign in to your existing storefronts and play from libraries you already own — Bannerlator does not sell, bundle or circumvent any game or DRM.

Steam — sign in with username / password or QR code, browse your owned library, and download + install games through a built-in depot engine (built on JavaSteam). Includes a 4-tier download-speed picker (Slow / Medium / Fast / Blazing), session hardening that recovers from Steam's ~1-hour connection-manager logoff so long installs finish, a connection / login status pill, and a depot-download OOM fix.
- DLC picker — a "Choose DLC" sheet lets you opt out of owned DLC before downloading, with the download size updating live as you check and uncheck, plus an "Includes DLC" line and a size breakdown (footprint / download / catalog / free space) and download ETA + speed on the detail page. A true-size install fix fetches real depot-manifest sizes so fully-downloaded games are no longer wrongly flagged "incomplete."
- Optional Goldberg auto-patch on a game's detail page — a Goldberg / gbe_fork Steam-emulator patch for offline / emulated play, in Regular / Experimental / ColdClient tiers, installed automatically and cleanly reverted on switch-back. (Modifies a game's shipped files — use at your own risk, for games you own.)
- Real-Steam (VAC) online — "SteamLite" launch mode — a per-game launch option (RealSteam / Goldberg / Raw) that runs the game through the genuine Steam client driven by a clean-room headless agent, for a VAC-eligible online session with real friends, matchmaking and achievements. It stages the game so Steam sees it installed (secure LaunchApp, not an insecure CreateProcess) and watches the launcher exe so the game launches secure regardless of which exe the shortcut names. The Steam client + agent ship as a downloadable steamlite-v1 content package, installed from inside the app. Device-proven online: CS 1.6, CS: Source, Team Fortress 2, Left 4 Dead 2 (VAC-secured), Brawlhalla and Stumble Guys (live-service); Borderlands 2 in testing.
- EA games from your Steam library (new in 3.0.7) — EA-published Steam titles get an EA badge and a one-time Set up EA Desktop session; after that the game launches through Steam → EA Desktop automatically (SteamLite mode, GE-Proton 11.0-6 / Proton 11 layers). Proven with Need for Speed Payback / Most Wanted / Rivals and STAR WARS Jedi: Survivor. Origin-era titles ask for the EA sign-in every launch and EA rate-limits those activations — see the 3.0.7 notes.
- Steam Friends & Chat (off by default) — a master-opt-in friends list with live presence (online / in-game / away), unread badges and collapsible sections; per-friend chat with text and images, persisted history, add-by-code / name-search / quick-invite, an in-app friend profile, a landscape two-pane layout, notifications with a sound toggle, typing indicators, and instant reconnect after a background drop.
- Steam achievements — seeded from your account into a tabbed detail-page grid, with in-game gold unlock pills — working and syncing in both launch modes: unlocks fire and sync back whether you play through Goldberg (emulated) or SteamLite (real Steam / VAC).
- Steam cloud saves + Save Manager "Sync Now" — automatic cloud-save parity around each play session, plus a one-touch "Sync Now" button on the Save Manager banner that syncs every flagged game at once, each in the correct direction (upload what's newer locally, pull what's newer in the cloud), with a live "Syncing 3/7…" count.
- Install to an SD card — a per-game toggle installs a Steam download onto a removable SD card to free internal space; the shortcut resolves through a container drive letter, so secure launch, saves and achievements are unaffected.
- Rebuilt game detail pages — a redesigned, landscape-aware tabbed per-game screen (overview · achievements grid · DLC) with the store badge, connection state and launch actions together in one place.
Epic Games — sign in, browse your library, and download / install / launch your titles (including Epic free games).
Amazon Games — sign in, browse your library, and download / install / launch your titles.
GOG — sign in and browse your owned library; download and install your DRM-free games with cloud-save sync and one-tap launch into a container.
⬇ Cross-store Download Manager — one unified manager across all four stores: see every active download and your whole installed library in one place, with live two-bar download/install progress, background downloads + notification-shade support (a foreground service keeps them running when you leave the app), and launch / verified uninstall for any installed game. Install state, cover art and update-available status stay in sync across a game's detail page, its download card and the store list.
🔒 These sign-ins are a third-party login system, exactly like any other emulator/launcher that logs into these stores — use them at your own risk (see Security Hardening).

🔒 Security Hardening & your store accounts

The Steam / Epic / GOG / Amazon sign-ins are a third-party login system, exactly like any other emulator or launcher that logs into these stores. Bannerlator is not affiliated with, authorised by, or endorsed by Valve/Steam, Epic Games, GOG, or Amazon.

Use at your own risk. You are logging your real store account into a community app. That's a normal trade-off for this kind of tool — but it's your account and your call.
Steam save sync & achievements — use at your own risk. Steam cloud-save sync and achievements run through third-party systems (Valve's Steam and Goldberg), exactly like the store sign-ins. They depend on your connection — an unstable or dropped internet connection or network, while downloading (syncing saves, achievements or games) or uploading, can leave data un-synced, incomplete or out of date. It is your responsibility to ensure a proper, stable connection and to complete the sync/download/upload when required; verify it finished before relying on it across devices.
Your credentials are redacted from logs. This release strips sensitive values out of everything the stores write, to logcat and the shareable diagnostic files, via a new StoreLog.redactUrl helper: signed download / manifest URLs (Amazon / Epic / GOG CDN links carry access tokens in the query), OAuth authorization codes, GOG client_secret + refresh_token, and account identity IDs (Epic account ID, GOG user ID). Steam credentials were already redacted. None of this changes how login, downloads or cloud saves work — only what gets written to a log.
Still be careful sharing logs. Even with redaction, a log or debug file can contain other diagnostic detail — so only share one publicly if you're comfortable doing so.

🧰 Bundled Start-menu utilities

New containers ship with handy Windows tools in the Start menu — Banner File Manager (our own file manager — see below), AIO Graphics Test, and Game Controller Test.
.lnk working-directory ("Start in") support so shortcuts for apps that only run from their own folder launch correctly.

📁 Banner File Manager

The bundled Windows file manager (C:\windows\wfm.exe) is Banner File Manager — our own native Win32 file manager, forked from BrunoSX's Winlator File Manager (MIT). It ships in every new container's Start menu.

Dual-pane split view (View ▸ Split View) — two independent panes, active one highlighted, copy between them.
File actions — Open as administrator, Open with ▸ (registered apps + choose another program), Properties.
Native Win32 copy / move / delete instead of shell32 SHFileOperation — sidesteps the Wine shell32 copy-paste crash on Proton 10.0-4.
Quality of life — keyboard shortcuts (F2 / Del / F5 / F6 / Backspace / Enter / Ctrl+C·X·V·A), Show Hidden Files, byte-accurate copy progress bar with cancel, status-bar total size.
Theme-aware (light + dark, follows the container theme; owner-drawn header / status bar / search to match) and universal x86-64 (Box64 / wowbox64 / FEXCore).

Source, releases & issues: github.com/The412Banner/banner-file-manager.

🎛️ Interface & in-game overlay

Modern Jetpack Compose user interface with a redesigned, icon-led navigation drawer.
Theme-aware everywhere — your selected preset / accent recolours the whole app and the in-game side drawer, including dialogs, chips, sliders and overlays.
Customizable themes — 16 presets (AMOLED default, Classic Dark, Ocean, Forest, Sunset, Rose, Steel, plus Midnight Cobalt, Phosphor, Carbon & Ember, Amethyst, Crimson, Synthwave, Royal Gold, Frost and Monochrome) plus an HSV custom-accent picker.
XMB view (new in 3.1.1) — a fourth Games-tab layout after List, Grid and Compact: games run across and the focused game's options run down, with every per-game setting and tool (Settings, Game Details, Properties, Clone, Remove, logs, community configs, cover scraping, Copy to Drive C, save backup / restore, Change executable) opening as further XMB columns instead of pop-ups. Built for a controller (A / B, LB / RB, ◀ ▶ to change values), with touch and swipe too; portrait and landscape.
Big Picture mode — a Compose-built couch launcher for TV / handheld use: full D-pad navigation, direct rails to your games, settings and features, and per-game spec chips showing what each title is actually set to.
In-game overlay drawer for settings, input, and quick toggles, with a Task Manager that lists processes as cards and can launch new tasks on any renderer. The Controls tab is split into Touch / Mouse / Vibration / Gyro sub-tabs, with a uniform 3-across grid of toggle chips.
In-game Task Manager — a full control panel. Beyond the process cards it now offers Windows-style per-process Processor Affinity ("Set affinity" on a process's ⋮ menu — pin it to specific CPU cores live, mid-game, applied through the guest's real affinity path with no relaunch), a live telemetry header (CPU & GPU usage and temperatures, GPU clock, FPS + minimum, RAM, swap, battery level / watts / temperature / charging, and a per-core clock strip), and a collapsible container info panel (Wine/Proton, DX wrapper, renderer, driver, resolution, device).
Built-in File Manager with Favorites — bookmark folders and jump to them from a dedicated list, each labelled by storage source (Internal / SD card / a container's Drive C: or Z:) and full path. Image files show real thumbnails, and the File Manager doubles as the app's file picker for every import (WCP / ICP / wallpaper / drivers / assets) — reliable on OEM skins where Android's system picker fails, with the system picker still available as a secondary option. It also handles multi-select bulk operations, archive extraction (zip / 7z / tar / tar.gz / xz / bz2 / zst, Zip-Slip-guarded with progress and cancel), and search / sort / hidden-file toggle / free-space display.
Performance HUD — FPS, frame time, CPU/GPU temperature, and RAM, in vertical or horizontal layout, with its on-screen position saved per game. Four switchable overlay styles — Classic, GameHub, a GameNative-style HUD with live graphs, and the new Fusion HUD (MangoHud-style: size modes Full / Tiles / Pill / Minimal / Mega, VRAM, GPU model, 1% / 0.1% lows and a frametime graph) — with long-press to lock any HUD in place.
FEX runtime indicator — a live badge in the Graphics tab shows what's actually translating the running game: arm64ec vs x86-64, the translator (FEXCore / wowbox64 / Box64), and — for FEXCore — whether the native unixlib (.so) or the classic DLL path is active. Read straight from the running process, so it reflects reality, not just the setting.

📥 Builds & distribution

Three build flavors with distinct package IDs — standard, PuBG, and Ludashi.
Optimized release builds (not debug) for a smoother Compose UI, AOSP-testkey signed so updates install over previous installs.
In-app updater — Settings → Updates checks GitHub for a newer release and installs the correct flavor APK for you, with notify-on-update and an opt-in include-prereleases (beta channel) toggle.
Continuous GitHub Actions action builds and tagged stable releases.

🎨 Adding your own ReShade effects

Show / hide

Besides the built-in download catalog, you can add any ReShade effect yourself by dropping it into a folder. Follow these steps exactly:

1. Open the ReShade drop-in folder on your device (create the ReShade folder if it isn't there yet):

Android/data/com.winlator.banner/files/ReShade/

📁 That path is for the Standard build. For the other builds, swap the package name: PuBG → Android/data/com.tencent.ig/files/ReShade/ · Ludashi → Android/data/com.ludashi.benchmark/files/ReShade/ · AnTuTu → Android/data/com.antutu.ABenchMark/files/ReShade/.

2. Make one folder per effect. Name the folder whatever you want the effect to be called in the menu — for example MySepia.

3. Put the effect's files inside that folder — all in the same place, next to the .fx:

the effect's .fx file (required),
any .fxh files it #includes (very common — e.g. ReShade.fxh, ReShadeUI.fxh),
any image / texture files the effect uses.

ReShade/
  MySepia/
    MySepia.fx          ← the effect (folder name match = used first)
    ReShade.fxh         ← copy in any .fxh the .fx #includes
    ReShadeUI.fxh
    noise.png           ← copy in any textures it uses

4. Pick it in the app. Open the app → edit a container or a game shortcut → ReShade effect picker. Your folder now appears in the list — select it.

5. Use it in-game. Launch a DirectX (DXVK / VKD3D) game, open the in-game drawer → ReShade tab, and turn the effect on/off and tune its sliders live.

⚠️ Read this if something doesn't show up or work

Only colour effects work — sharpen, colour grading, film grain, CRT, tonemap, vignette, etc. Depth effects (SSAO, depth-of-field, MXAO) do not work yet.

ReShade only affects DirectX games running through DXVK / VKD3D — it does nothing on OpenGL / WineD3D / older 2D titles.

Effect not in the list? Make sure it's in its own subfolder and that the subfolder actually contains a .fx file (a loose .fx sitting directly in ReShade/ is ignored).

Effect selected but no change in-game? Most often a missing #include — open the .fx in a text editor, find any #include "Something.fxh" lines, and make sure each of those .fxh files is copied into the same folder as the .fx. Same for any texture files.

Game won't start / flat or blank screen after enabling effects? You likely stacked too many effects at once. Each one compiles on-device and costs GPU, and too many together can stop the game from launching. Go back into the per-game ReShade effect settings and uncheck the effects one at a time (or the specific heavy one) until the game boots correctly, then re-enable them gradually. Adding effects a few at a time avoids this.

Can't even find Android/data? Many stock file managers hide it on Android 11+. Use a file manager that can open Android/data, or copy the effect folder over from a PC via a USB cable, then drop it in.

🎮 Frontends Workaround

Show / hide

Bannerlator does not work by itself on frontends out of the box. See the frontends workaround guide to get it running.

🛠️ Building

This project is built via GitHub Actions only — local builds are not supported.

Action builds — every fix is compiled and published as a downloadable workflow artifact.
Releases — tagged stable builds are published as GitHub Releases.

🤖 Ask Me Anything

Show / hide

Got a question about Bannerlator? Ask the codebase directly. An AI reads the actual source code and answers with the exact file names and line numbers, so you can check it yourself. It never guesses — if the answer isn't in the code, it says so.

It's three steps:

Open an issue (you'll need a free GitHub account).
Type your question — be specific, and name a feature, setting, or file.
Submit. The AI replies in a comment on your issue, usually within 1–2 minutes.

That's it — no form, no approval step, nothing else to do.

ℹ️ The AI replies to every new issue automatically. A few per person per day are free; past that, it will ask you to try again later.

Good things to ask:

"How does the FPS limiter work?"
"Where is the GOG store integration implemented?"
"What values does the scaling mode picker accept?"
"How are release builds signed and distributed?"

Avoid device-specific troubleshooting like "why is my game slow?" — the AI explains what the code does, not how a game runs on your phone.

Prefer the command line?

With opencode installed (npm install -g opencode-ai), run the same agent locally against a clone of this repo:

opencode run "your question" --agent ama-agent --model opencode/big-pickle

Maintainers / forks — one-time setup

The bot runs on the opencode/big-pickle model via your opencode credentials (not a separate API key). To enable it on a fork:

Locally run cat ~/.local/share/opencode/auth.json and copy the whole JSON.
Add it as a repository secret named OPENCODE_AUTH under Settings → Secrets and variables → Actions.
Make sure the answered and question labels exist.

Every newly opened issue is answered automatically, bounded by a per-user daily limit and a monthly cap — tune both at the top of .github/workflows/ama-answer.yml (PER_USER_PER_DAY, MONTHLY_CAP; maintainers are exempt from the daily limit). You can also force a re-run on an older issue by adding the question label. Without the secret, the bot posts a notice explaining what's missing.

🙏 Credits

Show / hide

This build stands on a long chain of prior work — its direct lineage, plus the projects whose commits and work are cherry-picked and implemented here:

Contributor	Contribution
brunodev85	Original Winlator — Wine + Box64 + Turnip on Android. Foundation of every fork below. Also serves the `input_controls` profiles consumed by this fork: https://raw.githubusercontent.com/brunodev85/winlator/main/input_controls/
coffincolors	`cmod` Winlator fork — package `com.winlator.cmod` and the customization layer this codebase is built on.
Pipetto-crypto	Winlator Bionic fork (the "Bionic" half of Star Bionic) and the upstream Box64 fix branch. Co-credited on cmod. Also packaged vkBasalt into the Winlator shortcut pipeline — the integration Bannerlator's ReShade feature builds on.
jacojayy	Maintainer of the Star line. Timeline Semaphore patches in the bundled Turnip driver for newer DXVK compatibility. Official site developer and maintainer.
Star / Frost dev team	The star-emu team behind the original Star Bionic and Winlator Frost lines this build continues from.
isygold (AGBOOLA Israel Oluwagbogo)	Star Engine / VEGAS — the Adreno-optimized DXVK fork this build's `v1.3-vegas` is named for, eliminating stutter and adding real-time upscaling on mobile GPUs, plus tuned dxvk.conf profiles. See the VEGAS DXVK FAQ for help & configuration. 🚀 Support VEGAS Development — low-level graphics dev & vibecoder: debugging, refactoring & improving original DXVK code for Adreno. ❤️ Sponsor →
vivsi	Controller support contributions.
arro000	Virtual Controller Pro (#156) — a ground-up on-screen touch-controls overhaul: new control types (Dynamic Stick, Mouse Area, Button Grid, Expandable Buttons), a Jetpack Compose-rebuilt controls editor with an in-game live editor, control groups, key combos, per-element dead zones, custom control icons, and a control scale limit raised to 300%.
clintOnSky	LSFG Native capture resolution + Vulkan 1.1 driver compat (#512, 3.1.1) — runs LSFG Native's frame generation and the post-effect chain at a lower capture height and scales the result up, and lowers the LSFG shaders' SPIR-V so a Vulkan 1.1 stock driver with the right extensions can run them; tested on his Adreno 710. Also found the double shader build that slowed LSFG Native's start.
StevenMXZ	Winlator-Ludashi and extensive cherry-picked work implemented in this build. This includes the new user interface and the Vulkan rendering path — both of which were still unreleased and unfinished at the time these builds and this repo were created — along with various other cherry-picked commits. This work is set to be released properly in his upcoming 3.1.
GameNative	GameNative by utkarshdalal — Proton bionic translation layers and cherry-picked commits adapted into this build. Its rendering pipeline was also the reference used to fix and rewire Bannerlator's render options — the `AHardwareBuffer` present path that makes Vulkan / DXVK / VKD3D content render correctly on both the OpenGL and Vulkan host renderers (GPUImage socket-buffer locking + EGLImage sampling, DRI3 direct-scanout, the Present extension's FLIP / COPY branches, and the Native Rendering+ direct-scanout path) was ported from and cross-examined against GameNative's implementation. The standalone FPS limiter is GameNative's too — its guest-side present-pacing mechanism (delaying the X11 Present `IdleNotify` to throttle the game itself, plus the rule that lsfg-vk's own pacing governs when its multiplier is ≥ 2) was ported from GameNative. For the Steam store (2.3), the session-hardening patterns (derived-`loggedIn` state, off-pump PICS sync, single reconnect funnel, dead-token clearing, keep-alive / watchdog) and the `DownloadSpeedConfig` cores × ratio 4-tier download-speed model were also ported / adapted from GameNative. The PC-accurate controller vibration feature (dual-motor rumble with per-container mode + intensity) originates from GameNative #1214, reaching this build via TideGear's port (see below). In 2.9.8, the external-display ("game on TV") concept and the suspend-sink audio-recovery approach (re-establishing the guest's audio output after backgrounding or a mid-game output-route change) were referenced from GameNative and reimplemented clean-room — the TV Options suite and Bannerlator's native `pasink` libpulse audio client are original work, and the wireless casting feature is entirely Bannerlator's own with no upstream equivalent.
TideGear	GameHub-Vibration-Fix — the PC-accurate controller vibration work this build's rumble is built on. TideGear authored both halves: the original vibration feature PR (carrying GameNative #1214 forward) and the preload-free `winebus.so` rumble-duration patch (PR #91) that drops the `libevshim` `LD_PRELOAD` hook and instead byte-patches SDL's rumble duration to never auto-expire — which is what makes sustained rumble actually hold instead of dying after ~1s. Adopted with the author's permission. Bannerlator re-derived the patch patterns per Proton build (9.0 / 10 / 11 aarch64 + Wine 10.0 x86-64) and added a build-agnostic structural fallback.
WinNative	WinNative — the reference for Bannerlator's gyroscope (motion aim) support. Its rate-mode gyro implementation is what ours is derived from: the sensor→stick pipeline (deadzone → sensitivity → exponential low-pass → clamp), the axis and sign conventions, and the fractional-remainder accumulator that keeps slow tilts from rounding away to nothing. Bannerlator adapted it to our evdev gamepad-injection path and extended the gyro-mouse mode to also drive the X pointer directly, so motion control works on a Wine container desktop and not only in captured mouse-look games. In 3.0.6, WinNative's native-side LSFG frame-generation implementation was the design reference for LSFG Native — its choice to run the shaders in the emulator's own present path rather than as a guest layer, verified against its merged code stage by stage. GPL-3.0, same as this project.
Win-FG Native (Bannerlator)	Bannerlator's own clean-room frame generation — FSR3-family optical flow (MIT, AMD FidelityFX) plus a from-scratch synthesis, compiled into the compositor. No third-party frame-generation code or weights are bundled. Public repo, MIT, with per-shader provenance.
Eden Team / camillelavey	Eden — LSFG Native (new in 3.0.6) is ported from Eden's native Lossless Scaling frame-generation present path (PR #4263 by camillelavey, GPL-3.0): the PE-resource shader map, the ALPHA/BETA/GAMMA/DELTA stage decomposition and the pacer, re-hosted inside Bannerlator's compositor. Bannerlator bundles no Lossless Scaling shaders — they are extracted on device from the user's own `Lossless.dll` (Lossless Scaling by THS).
doitsujin (DXVK)	DXVK — its `dxbc` shader compiler (Zlib) is vendored to translate the Lossless Scaling DXBC shaders from the user's DLL into SPIR-V for LSFG Native, the same step lsfg-vk takes.
PancakeTAS	lsfg-vk — the open-source Vulkan frame-generation layer (a Vulkan-layer reimplementation of Lossless Scaling's frame generation) that Bannerlator's former lsfg-vk engine was built on, and whose DXBC→SPIR-V translation approach LSFG Native's on-device shader step follows. (The lsfg-vk engine itself is retired in 3.0.6.)
FrankBarretta	lsfg-vk-android — the Android/bionic port of lsfg-vk (AHardwareBuffer path + `vkCmdPipelineBarrier2` shim) that ran as Bannerlator's lsfg-vk engine on the Turnip stack through 3.0.5. The in-game live multiplier/flow-scale reload uses the `conf.toml` mtime-watch mechanism from GameNative's lsfg-vk-android fork. No proprietary shaders are bundled — users supply their own `Lossless.dll` (Lossless Scaling by THS) via the in-app picker.
DadSchoorse	vkBasalt (zlib) — the Vulkan post-processing layer that embeds the ReShade FX compiler. Bannerlator's ReShade feature is a continuation of this work: the bundled layer is built from DadSchoorse's source, patched for live on-device toggle and slider control. The bundled / catalog `.fx` effects are MIT / CC0 shaders by the ReShade (crosire), prod80 (prod80-reshade-repository), luluco250 (FXShaders) and fubax authors, each under their own MIT / CC0 license.
leegao (Lee Gao)	Vulkan texture-compression work used for mobile-GPU compatibility and performance — the BCn decompression layer (shader-v3, powering 2.5's "Wrapper + bcn_layer" Mali driver) and the DX12 `compat_layer` that, alongside it, powers 2.7's new opt-in "Wrapper + compat + bcn" Mali DX12 driver — including the just-landed layer-composition fix — plus real-time ASTC/ETC compute-shader encoders and the bionic-vulkan-wrapper (ETC2-Milestone-2) bundled as the base wrapper for the Mali BCn path.
WinterSnowfall	d7vk — the DXVK-lineage Vulkan implementation of DirectX 7 / DirectDraw (Direct3D 3–7) that powers Bannerlator's new D7VK DDraw-wrapper option (new in 2.9.6). Bundled as the default and offered as downloadable nightly catalog builds.
WinlatorMali (GunaCharanTeja / Charan)	WinlatorMali — the Wrapper Version Manager (new in 2.7) is modeled on WinlatorMali's graphics-driver manager, introduced in Winlator Mali Bionic 1.1; a number of the downloadable catalog wrappers come from WinlatorMali too (each credited in-app). The feature was requested in #132 by @6ui99uhkllj.
BrunoSX	The bundled Windows file manager is Banner File Manager (new in 2.7.1), Bannerlator's fork of BrunoSX's Winlator File Manager (MIT) — rebuilt with native Win32 file operations (sidestepping the Proton 10.0-4 shell32 copy-paste crash), a dual-pane split view, and Open-as-administrator / Open-with.
@Tony57319	Reported / requested the lsfg Performance mode frame-gen toggle new in 2.7.1 (#152).
@clintOnSky 🌱 (first-time contributor)	Downstream fixes surfaced in #96, applied to `main` individually: the Xiaomi/HyperOS `libjpeg.so` symlink-shadow removal that lets the frame-gen Vulkan layer load; the sign-agnostic battery-wattage fix for Xiaomi/MTK devices that report discharge current as positive; and the `WOWBOX64` content-type fix for arm64ec Box64 downloads with live refresh of the component version lists after a download sheet closes.
JavaSteam	JavaSteam (`in.dragonbra:javasteam`) by Longi94 — the Steam connection-manager client the built-in Steam store logs in and talks to Steam with, and — via the `javasteam-depotdownloader` fork by joshuatam — the entire depot-download engine Bannerlator's Steam store is built on.
Goldberg Steam Emu / gbe_fork	Goldberg Steam Emu by Mr_Goldberg, and gbe_fork by Detanup01 — the Steam emulator Bannerlator's Goldberg auto-patch installs (Regular / Experimental / ColdClient tiers) for offline / emulated play of games you own.
Pluvia	Pluvia — an Android Steam client whose patterns were referenced alongside GameNative while building the Steam store's login / session handling.
The412Banner	Full Jetpack Compose UI migration, in-game overlay rewrite, controller-support restore (SDL2 SoName fix + four event files), Box64 edit-dialog fix, theme system, and CI/release infrastructure. In 2.3, building on JavaSteam / GameNative / Goldberg, the original engineering is Bannerlator's own: the cross-store Download Manager, the four storefront integrations (Steam / Epic / GOG / Amazon), the multi-week Steam session-hardening work, the depot OOM fix, the Goldberg auto-patch integration, the store Material-3 restyle, and the store-log credential redaction (`StoreLog.redactUrl`). In 2.4, the fullscreen aspect-ratio pipeline (Off/Fit/Stretch/Fill/Integer across all three renderers), the in-app File-Manager import picker replacing SAF (with image thumbnails + percent/ETA import progress), the DLC picker, the true-size depot install fix, per-game persistence of scaling / fullscreen / HUD position, and the container wallpaper picker. In 2.5, the Mali / BCn hardening — wiring leegao's bcn_layer (shader-v3) + ETC2-Milestone-2 wrapper into the "Wrapper + bcn_layer" and experimental "Wrapper-gamenative" drivers, the BCn Layer Settings UI, and the in-game logging overhaul (copy-logs button, selectable log location, co-located DXVK/VKD3D logs, scrollable debug-channels dialog). In 2.5.1, the SurfaceFlinger colour + crash fix and per-container / per-game "Correct SurfaceFlinger colours" toggle (ASurfaceRenderer R/B-swap fix + GPU converter, ported from GameNative #1620 / #1644), the in-game FEX runtime indicator (arm64ec / x86-64 · FEXCore / wowbox64 / Box64 · unixlib / DLL, read live from `/proc/<pid>/maps`), the FEXCore unixlib (`.so`) auto-match at launch (per-game version sync + uninstall cleanup), and 18 new Environment Variable presets (DXVK / VKD3D / Wine / Mesa). In 2.5.2, the Community Configs system — the in-app catalog browser, per-uploaded-config cards with live upvotes / downloads / comments, the surgical config-apply engine, and the smart inline installer for DXVK / VKD3D / FEXCore + Turnip drivers — plus two new Proton 11.0-1 x86-64 compatibility layers (SDK 28 / SDK 35) built and published to the downloadable catalog. Also maintains the Nightlies WCP Hub and Banners-Turnip.

Upstream stack

The Wine/translation stack this app bundles or downloads:

Component	Author
Wine	WineHQ
Box64 / Box86	ptitSeb
FEXCore	FEX-Emu
DXVK	doitsujin / Philip Rebohle
DXVK-GPLAsync patch	Ph42oN
DXVK-Sarek	pythonlover02
VEGAS (Adreno-tuned DXVK / GPLAsync fork — `v1.3-vegas`)	isygold · FAQ · ❤️ Sponsor
D7VK (DirectX 7 / DirectDraw → Vulkan)	WinterSnowfall
VKD3D-Proton	Hans-Kristian Arntzen
Turnip / Mesa	Freedreno team @ Mesa
Proton layers (bionic)	GameNative
Steam depot engine	JavaSteam by Longi94 · depotdownloader fork joshuatam
Steam emulator (Goldberg auto-patch)	Goldberg Steam Emu (Mr_Goldberg) · gbe_fork (Detanup01)
Controller vibration (PC-accurate rumble)	Feature GameNative #1214 · port + preload-free `winebus` duration patch TideGear (#91)
Gyroscope (motion aim)	Rate-mode pipeline + axis conventions from WinNative
Steam Controller support	SDL3 (Sam Lantinga & the SDL contributors, zlib) — the official 3.4.16 Android release, bundled unmodified
EA games from Steam (EA Desktop chain)	Researched and implemented by The412Banner — the methods and techniques GameHub uses to launch EA titles were reverse-engineered and re-implemented for Bannerlator on its SteamLite agent
Frame Generation (win-fg)	Bannerlator (clean-room)
Frame Generation (lsfg-vk)	PancakeTAS · Android port FrankBarretta · live-reload fork GameNative · DLL Lossless Scaling (user-supplied)
Post-processing (ReShade / vkBasalt)	vkBasalt by DadSchoorse (zlib) · Winlator packaging Pipetto-crypto · effects by crosire · prod80 · luluco250 · fubax (MIT / CC0)

Community reports & requests

Much of Bannerlator's polish is driven by the people who file issues and test builds. Recent features came directly from:

Angel — requested the environment-variable presets that seeded 2.5.1's new preset set (DXVK_DISABLE_TIMELINE_SEMAPHORES, VKD3D_SHADER_MODEL).
@kylinzang — the driving force behind 2.5's Mali / BCn support (#70, originally #54 / #53): the original request, the env-var spec, the in-game logging overhaul, and iterative on-device testing on Mali-G57 through a full sign-off. Also fullscreen aspect-ratio modes (#71) and the in-app File-Manager import picker (#73).
@rizky2-crypto — Mali-G610 BCn testing (#30).
@SombraShadow — the container wallpaper picker (#66).
@abdogm — magnifier cursor-follow & no-dim fixes (#44).
@Devaspe — the Steam install-blocker report that drove the true-size depot install fix.
iamtooshaar (Discord) — testing and bug-hunting on Steam Friends & Chat (3.0.2), helping shake out the presence, history and image-send issues on real hardware.
TAR (Discord) — tested the Steam Controller support through six builds (3.1.0) and shaped it: the bindings fix, the remappable back buttons and … button, the 18-input controller test and the left / both trackpad options.

…and everyone in the Discord and on GitHub who tests builds and reports issues. 🙏

Additional credits surfaced in the Star Bionic REVAMPED project (star.bionic-revamp):

@The412Banner — Converting the UI to Jetpack Compose and rewriting the controller implementation.
@jacojayy — Timeline Semaphore patches in Turnip.

If you have contributed and are not listed, open a PR — this list is intended to be complete.

⚖️ Disclaimer

Winlator and its forks are unofficial community projects. They are not affiliated with or endorsed by Microsoft, Wine, the Mesa project, Qualcomm, Valve/Steam, Epic Games, GOG, Amazon, or any game publisher. The built-in store sign-ins are a third-party login system for libraries you already own — see Security Hardening & your store accounts, and use them at your own risk. Compatibility varies by device GPU, Android version, and individual game.

📄 License

Bannerlator is licensed under GPL-3.0 as a whole, because it incorporates GPL-3.0-licensed components (notably GameNative and lsfg-vk), whose copyleft governs the combined distribution.

The upstream Winlator → cmod → Bionic → Star → Ludashi lineage it builds on is MIT © 2023 BrunoSX (permissive, and GPL-3.0-compatible). That MIT notice — and the license and copyright of every incorporated component (GameNative, lsfg-vk, gbe_fork/Goldberg, vkBasalt, bcn_layer, JavaSteam, Wine/Box64/Mesa/DXVK, FSR/NIS/SGSR, ReShade shaders, …) — is preserved in THIRD-PARTY-LICENSES.md.

See LICENSE for the full GPL-3.0 text and THIRD-PARTY-LICENSES.md for all third-party attributions.