New GameLoop Beta Runs COD Mobile Again, and It Is TAC Underneath

A GameLoop beta build released in early September 2026 installs and runs Call of Duty: Mobile on PC. It is the first time we have been able to write that since the classic build stopped working after client 1.0.53.

It is also not what most people are assuming it is.

What the build actually is

The runtime is Tenstore Android Connect. The launcher interface sitting on top of it comes from classic GameLoop. So this is not a repaired classic build, and it is not the ground up engine rework that has been speculated about. It is TAC, shipped by Tencent, wearing the GameLoop face.

That reframes a lot of what we have published this year. TAC has been the workaround route we documented because it ran the current client when nothing else did, with the standing caveat that it was not an officially supported COD Mobile platform. Tencent is now distributing that runtime itself, from GameLoop's own download servers, under GameLoop branding. The workaround and the official path are converging.

The practical upside for anyone already on TAC is that your existing knowledge transfers. Behaviour, quirks and most troubleshooting carry over. What changes is the shell and the install source.

The short version

• Beta channel GameLoop build, public on September 4 and 5, 2026.

• TAC runtime with the classic GameLoop launcher interface.

• Installs and runs Call of Duty: Mobile, multiplayer and battle royale.

• Ships with client 1.0.56 bundled, while the live client is 1.0.57.

• Distributed as a direct installer, not from the gameloop.com download page.

• Tencent has published nothing about it: no blog post, no release note, no changelog.

Where it came from

Three Call of Duty: Mobile community accounts posted the same installer link within about a day of each other, each with a version of the same message: beta build, bugs expected, report them through GameLoop's Discord server.

The link points at GameLoop's own download infrastructure, which is the strongest available signal that this is a genuine Tencent build rather than a repackage. It is still not a supported release. No documentation, no version notes, and no guarantee that the file behind that link is the same file next week.

What we found in testing

Our testing has been steady. One crash across the whole test period, and nothing else that needed working around.

Keymap is behaving. Smart Keymap loads and works without manual reassignment, as long as the client is on 1.0.57 and the game is launched from the emulator rather than from the Play Store. For anyone who has been rebuilding control schemes by hand since the 1.0.54 break, that is the change that actually matters.

Other testers also report stable 120 FPS in multiplayer and battle royale, both Vulkan and OpenGL available in the engine settings, and first launch failures when the emulator is installed outside the C drive or with virtualization turned off in BIOS. We have not verified those independently, but they match how these builds behave.

The caveat is real. One test environment is not a sample, and this is a beta rather than a stable release. Performance is the most likely place for other people's experience to diverge from ours, so expect frame pacing and stutter reports from some users until a stable build ships.

The 1.0.56 versus 1.0.57 gap

The most important practical detail: the installer bundles Call of Duty: Mobile 1.0.56, and the live client is 1.0.57. Install it, press play, and you are launching a client the servers have moved past.

The working sequence is to open the COD Mobile Smart Tool, use its one click Play Store launcher, sign in with a Google account, update Call of Duty: Mobile to 1.0.57 there, and only then start the game from the emulator. Our setup guide covers the full sequence including the Windows preparation around it.

Install clean, not on top

Remove your existing installs before you install this one. Classic GameLoop and TAC both have to be uninstalled, and the folders their uninstallers leave behind have to go too, including the old Android system files under C:\Program Files\TxGameAssistant and the settings trees under %APPDATA%\Tencent.

Kill every GameLoop process first, using the Kill GameLoop action in the COD Mobile Smart Tool, because uninstalling while the runtime is alive is what leaves the half removed state behind in the first place. Being on TAC already does not exempt you. Same runtime, same requirement to remove the old install properly. Our setup guide has the full order.

On ban talk

Tutorials promising no ban in the title are circulating alongside videos warning that specific actions will get you banned, and neither side is offering evidence. What is accurate is that this is an official installer from Tencent infrastructure running an official client updated through the Play Store, which is a materially different position from third party tooling. What is not accurate is any claim that someone outside Tencent knows the policy.

What we are watching

Whether the build graduates to the normal download page, whether the installer link stays live, and whether the next client update lands on it without a repeat of the 1.0.54 situation. That last one is the real test. Running today's client is good news. Surviving the next season update is what would make this something to rely on.

The build is in our emulator directory, and we will keep that entry and our guides updated as this develops.