GameNative boosts Android FPS to 100

Android PC gaming is getting weird in a very specific way — not because phones suddenly became as fast as gaming laptops, but because software is getting better at faking smoothness. GameNative, the open-source app that lets you run PC games you own on Android, just added Lossless Scaling frame generation in its 0.9.1 release. The flashy example is The Last of Us Part I jumping from around 30 fps to roughly 100 fps on Android hardware. That sounds like a raw horsepower breakthrough, but basically it’s a frame-synthesis trick layered on top of the frames the game really renders. (github.com) ### What actually shipped? GameNative 0.9.1 added LSFG-VK integration — a Vulkan-based version of Lossless Scaling frame generation — and exposed it as a per-game feature inside the app’s quick menu. Users can toggle it on, pick 2x, 3x, or 4x frame generation, and adjust options like flow scale and performance mode while the game is running. The release also bundled other upgrades, but LSFG-VK is the part get(github.com)into an Android launcher people can actually use. (github.com) ### What is GameNative, exactly? GameNative is an Android app built to run PC games locally, not streamed from the cloud. It hooks into libraries like Steam, Epic, and GOG, then uses compatibility layers and translated drivers so x86 PC games can run on ARM Android devices. That means the app is already doing a lot of heavy lifting before frame generation even enters the picture. The new feature sits on top o(github.com)gamenative.app) ### So how does the 100 fps trick work? The short version is that the game still renders a smaller number of real frames, then LSFG-VK generates extra in-between frames using optical flow. Think of it like the software watching where pixels seem to be moving, then drawing plausible intermediate moments to fill the gaps. If a game is rendering near 30 fps and you use 4x generation, the display can show something close to 100 or 120 f(gamenative.app)e frames were synthesized after the fact. That is why the demo number is exciting, but also why it needs a footnote. (videocardz.com) ### Why is Android the hard version? On Linux handhelds, lsfg-vk can hook directly into Vulkan apps as a layer. Android is messier. The Android implementation exists because newer Android security rules block the usual kind of injection into non-debuggable apps, so the project works by capturing the screen through MediaProjection, generating frame(videocardz.com) tells you this is still enthusiast tech, not a clean built-in platform feature. (github.com) ### What’s the catch? Generated frames can improve perceived smoothness, but they do not reduce the game’s real input latency. In some cases they can make latency feel worse, and optical-flow generation can create visual artifacts around fast motion, HUD elements, or messy scene changes. Hardware support is limited too — the Android LSFG project says end-to-end frame generation works on Adreno 7xx-class GPUs and ne(github.com)ork on Adreno 6xx and up. That gap suggests compatibility is still moving and probably uneven across devices. (github.com) ### Why does this matter beyond one demo? Because it shows where Android handheld gaming is heading. First came translation layers that made more PC games boot. Then came better drivers, scaling, and controller support. Now the stack is borrowing the same “render less, look smoother” ideas that helped modern PC handhelds. If this keeps improving, Android gaming devices will feel less like novelty emulation toys and(github.com)or lighter games. (github.com) ### Bottom line The big news is not that Android can magically brute-force The Last of Us Part I at 100 fps. It’s that GameNative turned frame generation into a usable feature inside a real Android PC-gaming stack. That moves the whole category forward — even if, for now, the smoothness is part rendering and part illusion. (github.com)