BannerHub

📥 Latest stable: v3.8.0

GameHub 5.3.5 ReVanced — extended with GOG Games, Amazon Games, and Epic Games Store library tabs, a full Component Manager, in-app component downloader, background download service with in-app cross-store download manager, SD card / external storage routing for store game downloads, Winlator HUD overlay (Normal + Extra Detailed + Konkr style with CPU/GPU/RAM/SWAP/temp/per-core metrics), in-game performance toggles, RTS touch controls, VRAM unlock, per-game CPU core affinity, root access management, offline Steam launch, community game configs browser, per-game config export/import with Frontend Export, Japanese locale, in-game voice chat (room-based, no Steam required, cross-compatible with BannerHub v6), per-game PC audio settings (recording-compatible mode), and more. Built entirely with apktool smali patching — no source code, no external library injection.

AI Disclaimer

All smali edits, patches, and code changes in this project are developed with the assistance of Claude AI Sonnet 4.6 by Anthropic. Claude is used to write, review, and modify smali bytecode and Java extension code since this project has no source code to work from — all changes are applied directly to the decompiled APK via apktool.

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 output and in-app debug log files to diagnose and verify behavior before changes are finalized.

---

Video — Installation & Feature Showcase

Installing the app, installing games, and showcasing all features.

---

Table of Contents

• Installation
• Keeping BannerHub Updated
• Features
  • GOG Games
  • Amazon Games
  • Epic Games Store
  • Component Manager
  • In-App Component Downloader
  • Download Manager Button
  • External Storage — SD Card
  • Winlator HUD Overlay (Normal + Extra Detailed + Konkr Style)
  • Performance Sidebar Toggles
  • AI Frame Generation Menu
  • RTS Touch Controls
  • PC Vibration / Rumble
  • PC Audio Settings
  • In-Game Voice Chat
  • VRAM Limit Unlock
  • Community Game Configs
  • Per-Game Config Export / Import
  • Per-Game CPU Core Affinity
  • PC Game Settings: Offline Mode
  • Offline Steam Launch
  • Settings: Advanced Tab
  • Controller Navigation
  • Wine Task Manager
  • Component Descriptions in Game Settings
  • Japanese Locale
  • Virtual Container Cleanup on Uninstall
  • UI Tweaks
• How It Works
• FAQ
• BannerHub Lite
• Implementation Reports
• Credits
• Signing

---

Installation

Download the APK that matches your existing GameHub package name from the latest release:

Which APK do I need?

If you do not already have any GameHub variant installed, use the Normal APK (banner.hub). It installs as a completely separate app alongside the official GameHub Lite — both can coexist. If you want BannerHub to take over the gamehub.lite package slot (e.g. so apps that launch GameHub Lite by package name launch BannerHub instead), use Normal.GHL — but you must uninstall the official GameHub Lite first since they share the same package name and have different signing certificates. If you want to use a specific GameHub variant for performance spoofing (e.g. PuBG or Genshin), pick the matching APK. Be aware: performance spoofing variants push your device harder and generate significantly more heat. Do not use these variants without proper cooling and a clear understanding of what you are doing. Use at your own risk.

All 9 variants can be installed simultaneously. All APKs are signed with AOSP testkey (v1/v2/v3).

Note: You must uninstall your existing BannerHub build before installing a new release if the signing certificate changed. Data is not preserved across uninstall.

---

Keeping BannerHub Updated

Use Obtainium to automatically track and install new BannerHub stable releases directly from GitHub — no manual checking required.

Add this repo (https://github.com/The412Banner/BannerHub) as an app source in Obtainium. Starting with v3.4.0, BannerHub reports its own version number to Android (e.g. 3.4.0) instead of the base GameHub version, so Obtainium can correctly detect when a new release is available and prompt you to update.

Required setting: When adding BannerHub in Obtainium, enable "Reconcile version string with version detected from OS". This tells Obtainium to compare the GitHub release tag against the version installed on your device. Without this, Obtainium may not detect version changes correctly.

[!WARNING] Only track stable releases in Obtainium. Pre-release builds use a different package name (com.tencent.ig) and cannot be upgraded to stable without uninstalling first — installing a pre-release over a stable build will break your install.

---

Features

GOG Games

Accessible via the left side menu → GOG.

For the complete technical implementation breakdown, see GOG_IMPLEMENTATION.md (API endpoints, auth flow, manifest format, download pipeline, BannerHub integration guide).

Authentication

• OAuth2 login — a WebView opens GOG's standard OAuth2 authorization page. After you log in, BannerHub captures the authorization code from the redirect URL and exchanges it for an access token + refresh token. Both tokens are stored in the bh_gog_prefs SharedPreferences file.
• Auto token refresh — before every API call, BannerHub checks the token expiry timestamp. If the token has expired (or will expire within the margin), it silently issues a refresh request using the stored refresh token. You never need to log in again unless you explicitly log out.
• Login persistence — your session survives app restarts and device reboots.

Library

• Library sync — on login or manual refresh, BannerHub fetches your full GOG library. Both Generation 1 (pre-Galaxy era) and Generation 2 (Galaxy) games are included.
• Metadata per game — title, developer, description, cover image, download size, Gen 1 / Gen 2 badge.
• Game cards — scrollable list and grid view with cover art, title, developer, install state, Install / progress / Add / Launch button.

Download Pipeline

BannerHub supports both GOG's current and legacy download systems:

Generation 2 (Galaxy-era games):

1. Fetches the build manifest from content-system.gog.com/products/{id}/os/windows/builds
2. Reads the depot manifest URL from the build record
3. Downloads and parses the depot manifest to get the full file list with CDN paths
4. Downloads each file individually, writing to filesDir/gog_games/{title}/
5. Per-file progress shown in real time — filename + percentage + download speed (MB/s)

Generation 1 (pre-Galaxy legacy games):

1. Fetches builds with generation=1 parameter
2. Reads the depot manifest, parses depot.files[], skips support-only files
3. Downloads each file using Range HTTP requests (byte-range resumable download)
4. Assembles files into the install directory

Installer fallback (very old pre-Galaxy games with no content-system builds):

1. Calls api.gog.com/products/{id}?expand=downloads
2. Reads the downlink or manualUrl from the downloads object
3. Downloads the Windows installer .exe directly

Multi-CDN failover (v3.7.3+): Each file probes every CDN advertised in the depot manifest (typically 4–6 endpoints) and falls back automatically when one rejects with HTTP 403 / 404 / 5xx. A CDN picker in the install-confirm dialog (with a ↻ Refresh button to re-fetch the live CDN list) lets you pin a specific CDN if your network plays better with one. When a download is interrupted mid-stream, the install state is recorded as PARTIAL so the next tap resumes from the same per-file progress instead of restarting from scratch. Originally ported from utkarshdalal/GameNative upstream PRs (see release notes for credits).

Install Flow

• Tapping Install opens a confirmation dialog showing download size and available storage — nothing downloads until you confirm.
• Downloads run via the BhDownloadService foreground service — a persistent notification with a Cancel action appears in the notification tray. The download continues if you leave the screen or switch apps.
• A ProgressBar + status text replaces the Install button during download. Live progress is also visible in the Download Manager.
• After install, BannerHub scans for qualifying executables (excluding redist/setup/unins/crash/helper paths). One found → auto-selected. Two or more → exe picker dialog.
• On completion an Add Game button appears. Tapping it opens GameHub's EditImportedGameInfoDialog pre-populated with the executable path.
• A green ✓ Installed checkmark appears on the card immediately — no app restart needed.

Post-Install

• Persistent install state — bh_gog_prefs is read on every app open; already-installed cards show checkmark and Add button automatically.
• Launch — Add Game button passes the stored executable path to EditImportedGameInfoDialog.
• Set .exe — detail dialog shows current executable and a Set .exe… button to re-scan and re-pick at any time.
• Copy to Downloads — recursively copies filesDir/gog_games/{dirName}/ to Downloads/{dirName}/.
• Uninstall — recursively deletes install directory, removes all prefs keys, resets card. Both header ✓ and expanded ✓ disappear immediately.

---

Amazon Games

Accessible via the left side menu → Amazon Games.

For the complete technical implementation breakdown, see AMAZON_IMPLEMENTATION.md (PKCE auth, GetEntitlements API, manifest.proto format, XZ/LZMA decode, FuelPump env vars, SDK DLL deployment, BannerHub integration guide).

Pipeline based on research by The GameNative Team.

Authentication

• PKCE OAuth2 login — a WebView opens Amazon's standard sign-in page. BannerHub intercepts the authorization code directly from the redirect URL — the detection checks for openid.oa2.authorization_code= in any redirect URL, so it works correctly through OTP / 2FA intermediate pages without hanging. Tokens are stored in bh_amazon_prefs.
• Auto token refresh — silently refreshed before expiry. You never need to log in again unless you uninstall.

Library

• Library sync — fetches your full Amazon Games entitlements list via GetEntitlements. Each entry includes title, product SKU, entitlement ID, and cover art.
• Game cards — scrollable list and grid view with cover art, title, install state, Install / progress / Launch button.

Download Pipeline

1. Calls GetGameDownload to retrieve the CDN download URL and version ID
2. Downloads manifest.proto — a protobuf manifest listing every file with its CDN hash path, size, and SHA-256 checksum
3. Downloads files in 6 parallel threads — each file fetched via its hash path, SHA-256 verified, renamed to final path
4. Progress shows current filename and download speed (MB/s)
5. Resumable — already-complete files (matching size) are skipped on retry

Downloads run via the BhDownloadService foreground service — a persistent notification with a Cancel action appears in the notification tray and the download continues if you leave the screen. Live progress is also visible in the Download Manager.

Post-Install

• Launch — reads fuel.json from the install directory to determine the executable and required FuelPump environment variables, then launches via GameHub's EditImportedGameInfoDialog
• SDK DLLs — FuelSDK_x64.dll and AmazonGamesSDK_* DLLs are deployed to the install directory at launch time
• Set .exe — detail dialog lets you override the detected executable at any time
• Update checker — compares installed version against current CDN version; marks cards with an update badge when newer version is available
• Uninstall — removes install directory and all prefs; both header ✓ and expanded ✓ disappear immediately

---

Epic Games Store

Accessible via the left side menu → Epic Games.

For the complete technical implementation breakdown, see EPIC_IMPLEMENTATION.md (OAuth2 auth, library API, manifest format, CDN selection, chunk download pipeline, BannerHub integration guide).

Pipeline based on research by The GameNative Team.

Authentication

• OAuth2 login — a WebView opens Epic's login page. After sign-in, BannerHub reads the authorizationCode from Epic's JSON redirect response body via evaluateJavascript, exchanges it for tokens using the Legendary client credentials, and stores them in bh_epic_prefs.
• Auto token refresh — silently refreshed before expiry.

Library

• Library sync — fetches owned games from Epic's library API, enriches each entry with catalog metadata: title, developer, description, cover art, DLC detection, CanRunOffline flag.
• Game cards — scrollable list and grid view with cover art, title, developer, and install state.

Download Pipeline

1. Fetches the manifest API JSON to locate manifest files on Epic's CDN
2. Downloads the binary or JSON manifest — parses full file list, chunk map, per-chunk SHA-1 hashes
3. Downloads chunks in 6 parallel threads from Fastly or Akamai CDN (public — no auth token required on chunks)
4. Assembles each game file from its ordered chunks, SHA-1 verified per chunk
5. Progress shows current filename and download speed (MB/s)

Downloads run via the BhDownloadService foreground service — a persistent notification with a Cancel action appears in the notification tray and the download continues if you leave the screen. Live progress is also visible in the Download Manager.

Post-Install

• Launch — sets pending_epic_exe in SharedPreferences → picked up by the main launcher activity → opens EditImportedGameInfoDialog
• Set .exe — override the detected executable at any time
• Uninstall — removes install directory and prefs; both header ✓ and expanded ✓ disappear immediately

---

Component Manager

Accessible via the left side menu → Components.

The Component Manager gives you full control over the WCP/ZIP components that GameHub uses to run Windows games — the DXVK, VKD3D, Box64, FEXCore, and GPU Driver entries that appear in per-game settings.

Card UI

Each installed component is displayed as a compact card with:

• Color-coded type badge — DXVK (blue), VKD3D (purple), Box64 (green), FEXCore (orange), GPU Driver (yellow), WCP (grey) — with a matching left accent strip
• Source badge — components downloaded via BannerHub show the repo they came from (e.g. "Arihany WCPHub", "Nightlies by The412Banner")
• Install count in the header showing total managed components
• Live search bar — type any part of a component name to filter cards in real time

Actions

Format Support

BannerHub uses GameHub's own bundled libraries (commons-compress, zstd-jni, tukaani xz) for extraction — no external dependencies are injected, so there are no class loader conflicts.

---

In-App Component Downloader

Inside the Component Manager, tap Download at the bottom of the screen to open the Download Components browser and install components directly from GitHub without leaving the app.

Navigation

Three-level navigation: Repo → Category → Asset list

• Repo list — all built-in sources shown as selectable entries
• Category list — choose from DXVK, VKD3D, Box64, FEXCore, or GPU Driver
• Asset list — shows all available assets with file size where available. Assets already installed via BannerHub show a checkmark; the mark clears when the component is removed

Tapping any asset downloads it to the cache directory and injects it as a new component automatically, with a progress screen showing "Downloading: <filename>" during the fetch.

Built-in Sources

---

Download Manager Button

A ⬇ button in the launcher dashboard opens the Download Manager (BhDownloadsActivity) — a live cross-store download dashboard accessible from anywhere in the app. The button updates in real time: at rest it shows ⬇; when one or more downloads are active it shows a red count badge (e.g. ⬇ 2) that increments and decrements as jobs start and finish.

Download Manager (BhDownloadsActivity)

A persistent screen showing all active and completed downloads across GOG, Amazon, and Epic simultaneously:

• Active rows — each active download shows the game name, current status message, and a live percentage ProgressBar. A Cancel button stops the download immediately and cleans up partial files.
• Completed library — finished downloads persist in bh_library SharedPreferences and are shown as completed rows with a color-coded store badge. Each row has:
  • Launch — opens EditImportedGameInfoDialog pre-populated with the stored executable path
  • Uninstall — confirms and deletes the install directory and all associated prefs
  • × — removes the entry from the completed list without uninstalling
• Clear ✓ — header button that removes all completed entries at once
• Active rows convert to completed rows in-place when a download finishes — no need to return to the store screen to see the result

The ⬇ button in each store's header (GOG, Amazon, Epic) also opens the Download Manager directly from within the store view.

All downloads are handled by BhDownloadService, an Android foreground service. A persistent notification with a Cancel action appears in the notification tray for each active download. Downloads survive leaving the detail screen, switching apps, or navigating elsewhere in BannerHub.

---

External Storage — SD Card

A "Save Store Games to External Storage (SD Card)" toggle in the BannerHub side menu settings controls where GOG, Epic, and Amazon game downloads are saved. Steam games are unaffected — this toggle only governs the BannerHub-added stores.

• Toggle OFF (default): games install to internal app storage at Android/data/<package>/files/{store}/{game}/
• Toggle ON: games install to your SD card at {SD card}/bannerhub/{store}/{game}/ — visible as a bannerhub/ folder at the root of the SD card with subfolders per store (gog_games/, epic_games/, Amazon/)

Turning the toggle on or off shows a confirmation dialog explaining what will change before anything is applied. Pressing Cancel reverts the switch without making any change.

Install location is locked at install time. The full absolute path is saved to SharedPreferences the moment a game finishes installing. All uninstall paths (game list, detail page, download manager) read and delete from that stored path directly — the toggle state at uninstall time is irrelevant. Installing with the toggle on, flipping it off, then uninstalling will still correctly remove the game from the SD card.

Upgrading from v3.5.0? That release accidentally moved Steam games to SD card alongside GOG/Epic/Amazon when the toggle was on. The first time you open a GOG/Epic/Amazon library after upgrading, BannerHub will offer a one-time prompt to switch Steam back to internal storage. From v3.6.0 onward this toggle is BannerHub-only and never touches Steam.

Install path display: each game's detail page shows the full install path in the ACTIONS card when the game is installed, alongside a colored badge indicating the storage location:

• 💾 SD Card — green pill, game is on the SD card
• 📁 Internal — grey pill, game is in internal app storage

---

Winlator HUD Overlay

An in-game heads-up display that shows real-time performance metrics while a game is running. Accessible from the in-game Performance sidebar.

Three HUD modes are available (only one active at a time):

Normal HUD

• FPS — current frames per second with a live frame-time graph
• Frame time — milliseconds per frame
• Resolution — current render resolution

Extra Detailed HUD

A second, expanded overlay that replaces the Normal HUD when the Extra Detailed checkbox is enabled. Displays a richer set of metrics:

• FPS — current frames per second with frame-time graph (spans both rows in horizontal layout)
• CPU usage — overall CPU load percentage
• GPU usage — GPU load percentage
• RAM — used / total memory
• SWAP — swap used / total in GB
• CPU temperature — thermal zone reading for the main CPU cluster
• GPU temperature — Adreno GPU thermal reading
• Battery temperature — battery thermal reading

Available in both horizontal (metrics displayed side-by-side in two aligned rows) and vertical (one metric per row) layouts — toggled with the same Orientation switch as the Normal HUD.

The Extra Detailed checkbox is automatically grayed out and disabled when the Winlator HUD toggle is off.

The Extra Detail HUD is a continuation and extension of the Winlator HUD by Stevenmxz. The additional metrics and layout were inspired by the performance HUD built into my personal device — no credit is claimed from any external project.

Konkr Style HUD

A third HUD style, mutually exclusive with Extra Detailed. Enable via the Konkr Style checkbox in the Performance sidebar. Reproduces the layout of the Konkr strategy game's built-in HUD.

Vertical (default): a 2-column table with:

• FPS (large, top row)
• CPU% + CPU temperature
• Per-core MHz for cores C0–C7
• GPU% + GPU temperature + GPU name + current clock + Wine container resolution
• MODE / SKN / PWR readings
• RAM — used / total GB (brown label background)
• SWAP — used / total GB (gray label background)
• BAT — battery % with a blue proportional fill bar
• TIME — current time

Horizontal: a compact multi-column strip — FPS block (current/min FPS + CPU temp), CPU 2×4 core grid, GPU block, thermal/power 2-column block, memory block with colored label backgrounds.

Tap anywhere on the HUD to toggle between vertical and horizontal. Drag to reposition. The opacity slider applies to the Konkr HUD.

Note: Not all data collected and displayed will always be correct. Each device detects and reads data differently. Values are read directly from sysfs/proc and may vary in accuracy depending on your device, kernel, and thermal zone mapping.

Configuration (all modes)

• Opacity slider — adjusts transparency of the active HUD overlay from fully opaque to nearly invisible
• Text shadow/halo — a centered shadow is automatically applied to all HUD text when opacity drops below 30% (stronger at <10%), ensuring readability against any background
• Position — drag to reposition on screen
• Orientation — horizontal or vertical layout

All position, orientation, and opacity settings are persisted in SharedPreferences and restored automatically the next time the Performance sidebar is opened.

---

Performance Sidebar Toggles

Located in the in-game Performance sidebar tab, above the Dual Battery Mode toggle. Both toggles persist their state in bh_prefs SharedPreferences and are re-applied automatically every time the Performance sidebar is opened.

WARNING — USE AT YOUR OWN RISK

These toggles override your device's thermal management. Forcing the CPU and GPU to run at maximum frequency continuously generates significantly more heat than normal operation. Sustained high temperatures can cause permanent damage to your device's processor, battery, and other components. Device manufacturers do not support or warrant against damage caused by overriding performance governors. By using these toggles you accept full responsibility for any damage, data loss, throttling, unexpected shutdowns, or reduced component lifespan that results. Do not leave these enabled unattended. Monitor your device temperature. Disable them immediately if your device becomes uncomfortably hot.

Both toggles require root. Without root, both are greyed out at 50% opacity and non-interactive. Root access is checked once when you grant it in Settings → Advanced — there is no root popup every time the sidebar opens.

Sustained Performance Mode

Sets all CPU cores to the performance frequency governor via su, eliminating all downclocking while the toggle is on. On disable, schedutil is restored.

# Enable
for f in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do echo performance > "$f"; done
# Disable
for f in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do echo schedutil > "$f"; done

Max Adreno Clocks

Locks the Qualcomm Adreno GPU clock floor equal to the ceiling via the KGSL devfreq sysfs interface, so the GPU cannot downclock under any load condition short of a kernel thermal emergency.

# Enable — set min_freq = max_freq
cat /sys/class/kgsl/kgsl-3d0/devfreq/max_freq > /sys/class/kgsl/kgsl-3d0/devfreq/min_freq
# Disable — remove floor
echo 0 > /sys/class/kgsl/kgsl-3d0/devfreq/min_freq

Use both toggles together for maximum sustained CPU + GPU performance (root required).

---

AI Frame Generation Menu

🙏 Credit: The AI frame interpolation engine itself — libGameScopeVK, the VK_NV_optical_flow Adreno path, the optical-flow synthesis pipeline, and the 6 quality presets — is the work of the GameHub team, who built it into GameHub 6.0.1. BannerHub adds only the user-facing wiring: the in-game sidebar entry, the settings dialog, persistence across launches, and the runtime ICD JSON path fix. All the heavy lifting that actually generates interpolated frames is theirs.

A new sidebar entry that drives GameHub 6.0.1's built-in libGameScopeVK AI frame-interpolation engine — generates synthetic in-between frames using Vulkan-side optical-flow vectors so your effective frame rate roughly doubles on supported hardware. No more hex-editing gamescope.control to use it.

📖 For the full technical breakdown — data classes, the 10-byte gamescope.control mmap protocol, libGameScopeVK Vulkan ICD, the VK_NV_optical_flow Adreno path, per-GPU capability gating, and the action/state classes — see gamehub_reports/GAMEHUB_600_MASTER_MAP.md § 26.8 (AI Frame Generation — Technical Deep Dive).

🧩 BannerHub-side deep dive — for a combined report covering the BannerHub feature/framegen-menu implementation, the runtime ICD-path fix, the launcher-regenerator gotcha, the 18:23 A/B failure post-mortem, verified 20:30 FPS results, and a layman's-terms breakdown of how all this works, see AI_FRAME_GENERATION_REPORT.md.

How it works (in plain English)

When the renderer produces a real frame, libGameScopeVK uses Adreno's hardware optical-flow extension (VK_NV_optical_flow) to compute motion vectors between the previous real frame and the current one, then synthesises one (or more) interpolated frame(s) in between. Those synthetic frames are pushed into the swapchain so the displayed framerate is a multiple of the rendered framerate. The GPU never has to draw the in-between frames from scratch — the real bottleneck (your game's CPU/GPU rendering work) is unchanged, but the screen sees twice (or more) the frames.

Where to find it

Open any PC game's in-game sidebar and tap the Performance tab. You'll see a new AI Frame Generation row above Dual Battery Mode, with:

• A switch for master on/off (writes byte 2 of gamescope.control and persists)
• A gear icon that opens the full settings dialog

Settings dialog

The gear icon appears next to the sidebar switch only when AI Frame Generation is enabled (v3.7.3+). Tapping it opens a translucent dialog over the dimmed game view:

A blue Close button dismisses; tapping outside the panel also dismisses. The sidebar switch is the single source of truth for on/off — there is no in-dialog Enable toggle. The multiplier is fixed at 2× (the only validated path on tested hardware).

Every change is applied immediately to the running game (writes through gamescope.control mmap) and saved to SharedPreferences so the value persists.

The FPS-limit byte (bytes 0–1 of gamescope.control) is owned by GameHub's separate sidebar control — our writer deliberately leaves it alone so toggling frame-gen never clobbers your existing FPS cap.

Practical guidance

• Start with Bal preset, 2× multiplier. This is the default for a reason — clean output without spending much GPU on the optical-flow pass.
• Drop to Eco or Flow if you're already GPU-bound and frame-gen costs more than it gains.
• Try Clear or Max if you have GPU headroom and want the cleanest possible interpolated frames (uses model 1, the higher-quality compositor path).
• Native FPS matters. Frame generation works best when the game's real framerate is already at least ~30 FPS. Below that, the interpolated frames have too much motion between samples and artifacts become noticeable.
• Pair it with the existing FPS-limit sidebar control if you want to cap output framerate — that control is GameHub's, lives separately, and the frame-gen menu deliberately doesn't touch its bytes.

Real-world result

On a working device, roughly 1.8–1.9× FPS scaling at 2× multiplier — e.g. 42 FPS off → 75–80 FPS on (validated via the in-game overlay during testing).

Persistence — why settings stick

Settings are global (per-game scoping is a v2 candidate). They persist across game launches via two layers:

1. SharedPreferences in bh_framegen.xml (keys: enabled, preset, flowScale, model).
2. Smali hooks at both WineActivity.onCreate and WineActivity.onResume re-apply all saved values to gamescope.control, so the AI overlay survives both fresh launches and Home/lock/resume cycles (v3.7.3 added the onResume hook — previously, resuming the game left the sidebar switch saying "ON" while the overlay was silently dead). The regenerator zeros byte 0 every launch, which is why the onCreate hook runs after it. The Vulkan ICD JSON is also re-written at launch using your APK's actual package name, so the menu works on any installed package — including manually-renamed APKs.

Note — requires Adreno GPU. GameHub 6.0.1's frame interpolation engine uses VK_NV_optical_flow, which on Android is currently only exposed by Qualcomm Adreno drivers. The menu controls work on any device but the actual frame interpolation is silently skipped on Mali, Xclipse, and other non-Adreno GPUs — you'll see the toggle move but not the FPS gain.

Caveats. Frame interpolation can introduce mild visual artifacts on fast camera motion or particle-heavy scenes, and adds a small amount of input-to-display latency by definition (the displayed frame is half a real frame "behind" the engine). Both are inherent to interpolated frame generation, not BannerHub-specific.

---

RTS Touch Controls

Thanks to @Nightwalker743 for making this possible.

Enable via the Controls tab in the in-game sidebar. Adds a full gesture overlay for PC strategy and RTS games that maps touch gestures to mouse inputs inside the Wine environment.

Gesture Map

Tap the gear icon in the Controls tab to configure pan direction and pinch-to-zoom scroll direction.

---

PC Vibration / Rumble

Thanks to @TideGear for the original feature (PR #80, from GameNative PR #1214) and for the v3.7.4 x86_64 / Box64 compatibility rework (PR #91).

Routes Wine's XInputSetState(slot, low, high) rumble calls into Android's VibratorManager so PC games actually shake your controller.

What works

• Independent low/high motors on dual-motor pads (DualSense, DualShock 4) via CombinedVibration.startParallel
• Single-motor blend fallback (low × 0.80 + high × 0.33) on 1-motor pads and the phone vibrator
• Sustained holds — (reworked in v3.7.4) every winebus.so in the container is patched on disk so SDL2's ~1 s rumble auto-expiry never fires, giving continuous rumble for as long as the game asks for it. This replaces the v3.7.0–v3.7.3 libevshim.so LD_PRELOAD shim, which mapped an extra library into the Wine process and broke x86_64 / Box64 game launches (see scope notes). No extra library is loaded anymore — same sustained-rumble behavior, no launch regression.
• Instant release on let-go (no phantom-suppression timer)
• Multi-controller auto-wake up to XInput's 4-slot cap, with 200 ms per-slot stagger for clean 3+ controller setups (no button presses required after connect)
• Samsung HAL workaround — 1 ms supersede pulse before VibratorManager.cancel(), since Samsung's BT-HID effect path doesn't reliably halt on bare cancel

Per-game settings dialog

A new PC Vibration Settings entry appears in each game's popup options menu, right after PC Game Settings:

Settings live in the stock pc_g_setting<gameId> SharedPreferences under bh_vibration_* keys, so the existing Export / Import Config flow picks them up automatically.

Scope notes

• XInput API path only. Modern PC games using XInput (the standard) get full rumble. The handful of older or niche titles using DirectInput Force-Feedback bypass our hook entirely.
• Native-XInput controllers need Bluetooth, not USB. DualSense and DS4 rumble fine over both. Xbox-style pads and 8BitDo controllers in XInput mode rumble over Bluetooth but NOT over USB — Android's USB-HID driver for XInput devices doesn't expose the rumble feature report path.
• Tested setups: Samsung devices with DualSense (Sony HID), DualShock 4 (Sony HID), and 8BitDo Pro 2 (XInput mode) across single, dual, and triple-controller configurations.
• x86_64 / Box64 safe (v3.7.4). Earlier builds (v3.7.0–v3.7.3) loaded libevshim.so into Wine via LD_PRELOAD; on Box64 this corrupted the dynarec and made x86_64 game launches die at startup (c000007b / wine has died). v3.7.4 removes the preloaded library entirely — x86_64 / Box64 titles now launch normally with rumble intact. arm64 / FEX containers were never affected.

---

PC Audio Settings

New in v3.8.0. A per-game PC Audio Settings entry in each game's popup options menu, right after PC Vibration Settings.

Stock GameHub loads module-aaudio-sink with no performance-mode argument, so PulseAudio opens a LOW_LATENCY AAudio stream the framework can grant as exclusive MMAP — which bypasses the AudioFlinger mixer that screen recorders tap (MediaProjection's AudioPlaybackCapture). The result: Android screen recordings capture video but no game audio whenever the in-game audio driver is PulseAudio. (ALSA uses a legacy mixed AudioTrack and records fine.)

Recording-compatible routes the default.pa sink line through the extension, appending pm=0 — the module computes setPerformanceMode(pm + 10), so 0 → PERFORMANCE_MODE_NONE → the stream stays on the mixer and screen recordings capture in-game sound. The active game's gameId is resolved from the live WineActivity's WineActivityData field (the 5.3.5 launch intent carries no gameId extra). Settings live in the stock pc_g_setting<gameId> SharedPreferences, so the existing Export / Import Config flow carries them automatically.

---

In-Game Voice Chat

New in v3.8.0. A built-in voice chat overlay you can use while in a game — no Steam, no root, no extra app. Identity is a user-chosen nickname plus a stable per-install client id; there are no friends lists and no ringing — it's a room model: Create or Join a room by a short code, or share a join link.

Two-gate activation

A new Voice Chat item appears in the dashboard side menu under Game Configs → opens a settings screen with a nickname field + Check availability. An Activate toggle stays disabled until the name is confirmed free; ticking it claims the name and turns the in-game pill on. The pill only attaches in-game once a nickname is claimed and activated.

In-game

A draggable edge pill opens a room box that shows the live roster (everyone's nickname), a call timer, and Mute / Leave; the pill stays pinned to the edge while the box drags freely, with a collapsible opacity slider. The mic is requested at runtime on activation.

Cross-play with BannerHub v6

Voice rides the same WebRTC mesh served from the BannerHub Cloudflare Worker (with Cloudflare Realtime TURN for strict NATs) that BannerHub v6 uses — so a BannerHub user and a BannerHub v6 user can share the same room and talk, in either direction. Rooms are identity-agnostic (any two clients on the same room code connect), and room codes use the same format on both builds. Device-confirmed both ways across different networks.

---

VRAM Limit Unlock

PC game settings → VRAM Limit now includes 6 GB, 8 GB, 12 GB, and 16 GB options in addition to the original GameHub range of 512 MB through 4 GB.

---

Community Game Configs

Accessible via the left side menu → Game Configs. A four-screen community browser for sharing and downloading per-game Wine/DXVK/component configurations.

Games list (Screen 1)

• Searchable list of all games that have community configs — each game shows a config count badge
• Populated from a pre-built games.json file refreshed every 30 minutes and on every new upload
• Total game count is shown in the header subtitle next to your device/SOC info (e.g. Samsung SM-G998B • Adreno 750 • 89 games); updates to X of Y games while the search box is active

Configs list (Screen 2)

• Lists all shared configs for the selected game — each card shows device model, SOC, upload date, vote count, and download count
• SOC filter chips — a scrollable chip bar at the top lets you filter by GPU type (e.g. filter to only configs from Adreno 750 devices). Chips are built from the SOC values present in the loaded configs. "All" chip shows everything. Resets when switching games.
• ✓ My SOC badge — configs uploaded from a device with the same SOC as yours are tagged in green
• Age indicator — configs older than 6 months are labeled "may be outdated"
• Upvote — tap to vote for configs you find useful

Config detail (Screen 3)

• Expanded metadata card — loaded on demand and displays up to 11 rows of actual config values:
  • Device, SOC, Date, Renderer, CPU, FPS Cap, BH Version
  • Wine / Proton, DXVK, VKD3D, GPU Driver, FEXCore, Box64 — component names used by the uploader
  • Resolution, Command Line, Env Vars (if set)
  • Settings key count, bundled component count
• Uploader description and verified SOC badge (green ✓ if SOC matches yours)
• Download to Device — saves the config JSON locally
• View Settings & Components — expands the raw settings and component list inline
• Share Config URL — copies a direct download link to clipboard
• Report Config — flag inappropriate or broken configs
• Comments — read and post comments on any config

My Uploads (Screen 4)

• Lists all configs you have uploaded in this session
• Edit Description — add or update a description visible to other users (token-authenticated, only the original uploader can edit)
• Delete — long-press any entry in the list, or tap the Delete My Upload button on the config detail screen, to permanently remove your config from the community database. A confirmation dialog is shown before anything is deleted. Token-authenticated — only the original uploader can delete their own config.

Backed by

All configs are stored in The412Banner/bannerhub-game-configs. The community is powered by a Cloudflare Worker — votes, downloads, descriptions, and comments are tracked without any account required.

You can also browse, search, filter, and download configs from the web at the412banner.github.io/bannerhub-game-configs — no app required.

The community database grows through contributions — if you find settings that work well for a game on your device, sharing them helps other users get a working config without trial and error.

---

Per-Game Config Export / Import

PC game settings include Export Config, Frontend Export, and Import Config options.

Export Config

Opens a preview dialog showing what will be exported before any file is created:

• Device model, SOC (GPU), settings count, components count

Then choose:

• Save Locally — saves to /sdcard/BannerHub/configs/ on your device
• Save Locally + Share Online — saves locally and uploads to the community database

The exported filename embeds the game name, device manufacturer, device model, and SOC (e.g. GodOfWar-Samsung-SM_S928B-Adreno_750-1234567890.json).

Frontend Export

A separate Frontend Export option in the PC game settings popup creates a launcher .iso file for use with a supported frontend instead of exporting a BannerHub config JSON.

• Opens a dialog to select the target frontend: Beacon or ES-DE
• For Beacon: creates Downloads/bannerhub/frontend/Beacon/{gameName}.iso
• For ES-DE: creates Downloads/bannerhub/frontend/ES-DE/{gameName}.steam

Both use the same game ID logic — localGameId for imported games, getSteamAppId() for catalog games.

ES-DE note: If the exported .steam file doesn't work for a particular game, RobZombie9043/steam-files-es-de is a community resource with pre-made .steam files for Steam catalog games.

Import Config

A dialog lets you choose:

• My Device — lists .json files saved in /sdcard/BannerHub/configs/. Selecting a file shows a preview card (device, SOC, settings count, components count) with a ⚠ SOC mismatch warning if the config was made on a different GPU. Tap Apply to proceed or Cancel.
• Browse Community — opens the Community Game Configs browser (see above) filtered to the current game

If a config references components not currently installed, a dialog lists the missing ones and offers to download and install them via the Component Manager before applying.

Cross-Compatibility with BannerHub Lite

Configs exported from BannerHub are fully compatible with BannerHub Lite, and vice versa.

Both apps store per-game Wine settings under the same SharedPreferences keys (pc_g_setting<gameId>) and export to the same folder (/sdcard/BannerHub/configs/). The export format is identical — the app that created the config has no effect on whether it can be imported. The app_source field in the JSON ("bannerhub" or "bannerhub_lite") is only used by the community config site for filtering and is ignored during import.

---

Per-Game CPU Core Affinity

PC game settings → Core Count is replaced with a multi-select dialog to choose exactly which CPU cores the game process is pinned to.

• Apply — saves the selected core bitmask and updates the settings row label immediately
• No Limit — clears affinity, the game process can use any core
• Selecting all 8 cores is equivalent to No Limit

---

PC Game Settings: Offline Mode

Opening PC game settings while offline no longer blocks with a spinner or error. Container and component lists fall back to empty data, and all settings rows remain fully accessible and editable without a network connection.

---

Offline Steam Launch

When Steam auto-login fails at cold start with no network, BannerHub detects the condition, skips the Steam login screen, and proceeds using the locally cached Steam configuration. You can continue playing your installed Steam library offline.

---

Settings: Advanced Tab

---

Compatibility API Source (GameHub / EmuReady / BannerHub)

BannerHub can pull its component catalog (DXVK, VKD3D, Box64, FEXCore, GPU drivers, containers, compatibility data) from one of three backends. The selector lives in Settings → Advanced → Compatibility API Source and opens a dialog with three options. Picking one saves it, clears the cached component + token data, and shows a toast — restart the app to refresh components against the new source.

How it behaves

• Default is GameHub (0). Fresh installs boot on the official source until you change it.
• Switching is sticky and cache-aware. The choice is stored in SharedPreferences (api_source); a separate last_api_source key lets the app detect a change across restarts and clear stale component/token caches automatically.
• The two external sources (EmuReady, BannerHub) bypass login and force-enable Steam Input — that's what lets you browse and install components without a XiaoJi account. The official GameHub source does not bypass login.
• A restart is recommended after switching so every in-app list re-queries the newly selected backend (the toast says as much).

Note: EmuReady is a separate third-party service — BannerHub neither hosts nor controls its catalog. Use the BannerHub option for the catalog curated by this project, or GameHub for the stock upstream feed.

---

Controller Navigation

All three game store activities (GOG, Epic, Amazon) support full D-pad / gamepad controller navigation.

• Game cards (list view) — navigate up/down with D-pad; focused card shows a gold 3dp border + slightly lighter background; press A to expand/collapse
• Game tiles (grid/poster view) — navigate in all four directions; focused tile shows a gold border via a foreground overlay (works correctly with rounded-corner art clipping); press A to expand/select
• Header buttons (back ←, view toggle, refresh ↺) — focusable with a gold 2dp border + lighter fill on focus; press A to activate

Focus highlight uses gold (#FFD700) consistently across all stores and view modes.

---

Wine Task Manager

Accessible from the in-game sidebar (three-bar icon) while a game is running. Provides live monitoring and control of the Wine session without leaving the game.

Tabs

All tabs auto-refresh every 3 seconds. The Kill button at the top terminates the selected process immediately.

Launch Tab

The Launch tab lets you run additional executables inside an already-running Wine session — useful for launchers, patchers, or tools that the game itself doesn't start. The browser starts at dosdevices/ in the WINEPREFIX and drills down from there.

A launch guard prevents Wine's "session complete" callback from tearing down the active game session when the secondary executable closes. The guard is released automatically 3 seconds after the secondary process exits.

---

Component Descriptions in Game Settings

When selecting a component in per-game settings (DXVK, VKD3D, Box64, FEXCore, or GPU Driver picker), components installed via BannerHub show their description text below the component name. The description is read from profile.json (WCP files) or meta.json (ZIP / adrenotools) at inject time and stored alongside the component.

---

Japanese Locale

BannerHub includes a complete 3,468-string Japanese translation covering every screen in the app. When your Android system language is set to Japanese, the app displays fully in Japanese. English users are unaffected — Android's locale fallback uses the default English strings automatically.

Translation contributed by reindex-ot via Crowdin (GameHub's official translation source).

---

---

Virtual Container Cleanup on Uninstall

When a game is installed and launched, GameHub creates a Wine virtual container at virtual_containers/{gameId}/ to hold the game's Windows environment. BannerHub ensures this container directory is fully cleaned up when the game is uninstalled, preventing orphaned containers from accumulating on disk over time.

UI Tweaks

• The "My" tab in the bottom navigation bar is renamed to "My Games" for clarity.
• Beacon launch no longer creates a second app entry in recents — GameDetailActivity is marked excludeFromRecents, so Beacon launches do not leave an orphaned BannerHub task in the recent apps list.
• System bars hidden across all store screens — the status bar and navigation bar are hidden on all GOG, Epic, and Amazon screens (store lists, detail pages, download manager, Component Manager, Component Download) so they no longer overlap UI buttons.
• Uninstall spinner — a "Uninstalling…" spinner dialog appears immediately after confirming an uninstall, covering the file-deletion delay before the completion toast. Applies to all three stores across game lists, detail pages, and the download manager.

---

How It Works

1. The original GameHub 5.3.5 ReVanced APK (compiled and patched by @playday3008) is stored as a permanent release asset under the base-apk tag in this repo (136 MB).
2. CI downloads the base APK, decompiles it with apktool, and overlays everything in the patches/ directory — new smali classes, modified smali files, new resource files, and layout edits.
3. apktool rebuilds the APK from the merged source tree.
4. The rebuilt APK is zipaligned and signed with AOSP testkey (v1 + v2 + v3 signatures).
5. The CI matrix builds all 9 package variants in parallel and uploads them to the GitHub Release.

All new BannerHub code lives in smali_classes16/. Existing GameHub smali files that needed modification are patched in place. No external dex files are injected — GameHub's own bundled commons-compress, zstd-jni, and tukaani xz libraries are used at runtime.

smali_classes12 is at the dex method index limit and is never reassembled — the original classes12.dex is extracted from the base APK and zip-injected directly after the rebuild step to bypass the limit.

---

FAQ

Q: Does BannerHub require root?

Most features work without root. The only features that require root are the two Performance sidebar toggles (Sustained Performance Mode and Max Adreno Clocks) — both are greyed out and non-interactive on non-rooted devices. All other features — the GOG, Amazon, and Epic Games tabs, Component Manager, component downloader, Winlator HUD, RTS controls, VRAM unlock, core affinity, offline modes, and settings — work on any non-rooted Android device.

Q: Will this replace my existing GameHub install?

Only if you choose a matching package APK. The Normal APK (banner.hub) installs as a completely separate app alongside the official GameHub Lite. The Normal.GHL APK (gamehub.lite) will replace the official GameHub Lite slot — uninstall it first. All other variant APKs replace their respective GameHub variant slots.

Q: Can I use BCI (BannersComponentInjector) with BannerHub?

Yes. BCI grants SAF access to any GameHub package, including banner.hub. Components injected via BCI are visible in BannerHub's Component Manager and vice versa. Launch BCI as a standalone app from your device's home screen or app drawer.

Q: Why does the Max Adreno Clocks toggle require root while some other apps can do it without root?

BannerHub uses a direct sysfs write to /sys/class/kgsl/kgsl-3d0/devfreq/min_freq which is a privileged operation. Some emulators use the KGSL ioctl interface instead, which is accessible to unprivileged apps — but that interface issues a performance hint the driver can still override under thermal pressure. The sysfs approach is a harder lock, at the cost of requiring root.

Q: My GOG game says "Generation 1" — will it still download?

Yes. BannerHub supports Gen 1 downloads via the legacy byte-range download pipeline. If your game is so old that it has no content-system builds at all, the installer fallback will download the Windows .exe installer directly.

Q: Where are GOG / Amazon / Epic games installed?

By default, inside the app's private storage: Android/data/<package>/files/gog_games/<name>/, amazon_games/<name>/, or epic_games/<name>/ respectively. If the Save Store Games to External Storage (SD Card) toggle is enabled in the side menu settings, games install to {SD card}/bannerhub/{store}/{game}/ instead. The toggle only affects these BannerHub stores — Steam games are managed independently. The install path is shown on each game's detail page with a badge indicating whether it is on SD card or internal storage. GOG games have a Copy to Downloads button in the detail dialog to copy files to Downloads/<name>/ for access from any file manager.

Q: Does Amazon login work with two-factor authentication (OTP)?

Yes. BannerHub detects the authorization code directly in the redirect URL regardless of which intermediate pages Amazon routes through during OTP/2FA, so login completes correctly with or without 2FA enabled on your account.

Q: Settings → About → Check Update always says "Already the latest version" — is that broken?

No, that is intentional. BannerHub is pinned to the GameHub 5.3.5 / versionCode 78 base so the Steam shopping card stays visible. The upstream GameHub upgrade endpoint now serves 6.0.x builds, and following that prompt would replace BannerHub with stock GameHub. The Check Update row was stubbed in v3.7.1 to read "Already the latest version" unconditionally and never call GameHub's upgrade endpoint. v3.7.2 extends the stub to the launch-time auto-update dialog (ApkUpdateUtils.checkUpdate) which previously popped on every cold start — that surface is now silent as well. Track BannerHub releases via this GitHub repo or Obtainium instead.

Q: My x86_64 / Box64 games stopped launching on v3.7.0–v3.7.3 — is that fixed?

Yes, in v3.7.4. The v3.7.0 PC Vibration / Rumble feature loaded a helper library (libevshim.so) into Wine via LD_PRELOAD. On Box64, mapping that extra library corrupted the dynarec and made x86_64 game launches die at startup (c000007b / wine has died); arm64 / FEX containers were never affected. v3.7.4 removes the preloaded library entirely and patches winebus.so on disk instead, so sustained rumble still works with no library injected. Update to v3.7.4 and affected x86_64 / Box64 titles launch normally again.

---

BannerHub Lite

BannerHub Lite is a companion project that ports the same BannerHub features into GameHub Lite 5.1.4 (vanilla, non-ReVanced base). If you are running GameHub Lite rather than GameHub 5.3.5 ReVanced, BannerHub Lite is the correct build to use.

Game configs exported from either app are cross-compatible — see Per-Game Config Export / Import.

---

Implementation Reports

Detailed technical breakdowns of each store integration and feature set — API endpoints, auth flows, data models, download pipelines, and known gotchas.

---

Credits

• GOG Games integration — The GameNative Team. The GOG API pipeline, authentication flow, download architecture, and library sync in BannerHub are based on their research and implementation.
• Amazon Games integration — The GameNative Team. The Amazon Games API pipeline, PKCE authentication flow, manifest.proto download architecture, exe scoring heuristic, FuelPump environment variables, and SDK DLL deployment in BannerHub are based on their research and implementation.
• Epic Games Store integration — The GameNative Team. The Epic Games Store API pipeline, OAuth2 authentication flow, chunked manifest download architecture, CDN selection logic, and chunk assembly in BannerHub are based on their research and implementation.
• Epic Online Services (EOS) Phase 1 — The GameNative Team. The EOS launch-arguments injection (-EpicPortal, -epicusername, -epicuserid, -epicsandboxid, -epiclocale, -epicdeploymentid and the -AUTH_LOGIN / -AUTH_PASSWORD / -AUTH_TYPE exchange-code triple) plus the deployment-ID sidecar fetch in BannerHub v3.6.1 are a Java port of their work. Specifically, PR #1286 / commit cbea7f7 ("Feat/eos overlay utkarsh"). Without GameNative's research and reverse-engineering of Epic's launcher protocols this feature wouldn't exist in BannerHub. Phase 2 — the in-game EOS overlay UI (Epic friends popup / notifications / achievement toasts) — is still pending and will land in a future BannerHub release. Please support GameNative: https://github.com/utkarshdalal/GameNative
• Japanese translations — reindex-ot via Crowdin
• RTS Touch Controls — @Nightwalker743
• GameHub ReVanced patches — @playday3008
• Winlator HUD — StevenMXZ. The Extra Detail HUD is a continuation and extension of the original Winlator HUD. Additional metrics were inspired by the built-in performance HUD of my personal device.
• Component sources — Arihany WCPHub, The412Banner Nightlies, Kimchi, StevenMXZ, MaxesTechReview, Whitebelyash

---

Signing

All APKs are signed with AOSP testkey (testkey.pk8 / testkey.x509.pem), v1 + v2 + v3 signatures via apksigner. The testkey is committed to this repository and is the same key used across all builds and all variants.

---

_{☕ Support on Ko-fi}

Community

Join our Discord: https://discord.gg/n8S4G2WZQ4