Warning
Only install official stable releases (like this one). Do NOT install pre-releases or raw CI artifacts — pre-release builds use a different package name (com.tencent.ig) and cannot be upgraded to stable without uninstalling first.
Important
Notification permission required. BannerHub will prompt for the Post Notifications permission when you start your first Epic, GOG, or Amazon download. You must allow it to receive download progress and completion notifications. Without it, you will not be notified when downloads finish or fail.
Important
Files access required for SD card storage. To save games to your SD card, BannerHub must be granted the Files and Media permission. Go to Android Settings → Apps → BannerHub → Permissions → Files and media and set it to Allow management of all files (or equivalent on your device). Without this permission the SD card toggle will have no effect.
Hotfix for v3.7.1
This is a hotfix release. No new features. All v3.7.1 functionality (and everything earlier) is preserved.
What changed
The launch-time auto-update dialog no longer probes upstream GameHub either.
v3.7.1 stubbed the manual upgrade probe — the Settings → About → "Check Update" row. But there is a second call site for the same upgrade endpoint: an auto-fired dialog that pops on every cold start, routed through ApkUpdateUtils.checkUpdate rather than the Settings row. In v3.7.1 that auto-dialog was still asking GameHub's servers for an upgrade on every launch, getting back 6.0.1 / versionCode 110, and offering it to the user — i.e. offering to replace BannerHub with stock GameHub.
v3.7.2 closes the second mouth. The same singleton (AppUpgradeRepo.b()) is now neutralised at both call sites with the same anchor-patch shape — its suspend invocation is replaced with const/4 p1, 0x0, so the result resumes as null and the existing "no update" branch (if-eqz) is always taken.
In v3.7.2:
- No upgrade dialog on app launch. Cold-starting the app no longer pops the GameHub upgrade prompt.
- Settings → About → "Check Update" — unchanged from v3.7.1, still reads "Already the latest version" in gray.
- Logcat shows zero
getAppUpgradeApktraffic from either surface.
The patch is one extra 5-instruction smali edit in ApkUpdateUtils$checkUpdate$1$1.smali, mirrored across both build.yml (stable) and build-quick.yml (pre-release). Same singleton as v3.7.1, different inner class. No behavior change for any other surface — login, store, prices, achievements, Steam card, ratings, downloads, AI Frame Generation, Vibration / Rumble, EOS authentication are all untouched.
Tracking BannerHub updates
Since both in-app upgrade surfaces are now silent, use either:
- This GitHub repo's Releases page — watch the repo to get notified
- Obtainium — add
https://github.com/The412Banner/BannerHubas an app source with "Reconcile version string with version detected from OS" enabled
Upgrading
- v3.7.1 → v3.7.2: install the matching variant directly over your existing install. No certificate change, no data loss.
- v3.7.0 or earlier → v3.7.2: install normally. If the signing certificate differs, uninstall first.
- Variants with different package names cannot replace each other in-place.
Credits
Hotfix patch developed and tested by @The412Banner. AI Frame Generation engine (still active from v3.7.0) is the work of the GameHub team; PC-accurate Vibration / Rumble (still active from v3.7.0) is from TideGear's PR #80 via GameNative PR #1214. Please go support GameNative: https://github.com/utkarshdalal/GameNative
For the full v3.7.0 feature set (AI Frame Generation menu, PC Vibration / Rumble, and everything earlier), see the v3.7.0 release notes. For details on the original (v3.7.1) Check Update row stub, see the v3.7.1 release notes.