PPSSPP development builds add mini video player and Android UX fixes

PPSSPP posted development builds around Feb. 26–27, 2026 that integrate a mini video player and return Android exit behavior, restoring a landscape-only exit button and controller-based exit while applying assorted UI layout improvements. The change is aimed at users testing dev builds from the project's Development builds page who want quicker UI tweaks and in-app video playback during testing.

The project's Atom feed author said they set up a new personal buildbot because Orphis' buildbot experienced a multiweek outage, writing, "Due to a 3+ week downtime of Orphis' buildbot, I went ahead and set up my own." That new buildbot currently produces Android, Windows and Windows for ARM64 processors and the feed notes, "Currently, it builds for Android, Windows and Windows for ARM64 processors. More platforms will be added in the future."

Android builds from the PPSSPP tree have supported a single package for phones and standalone headsets since build v1.17.1-60, which the feed spells out: "From build v1.17.1-60, our Android builds are cross-compatible between phones and VR setups like the Quest 2. So there's no longer any need for a separate downloadable VR app." The compatibility means testers no longer need a distinct Quest 2 APK to try VR behavior when using current Android dev builds.

The feed also warned about signing and upgrade paths. "Due to using different signing keys, you can't directly upgrade from an Orphis-build to these, but you can upgrade from an official release APK downloaded from this website to a buildbot build." The Atom feed added a direct pointer for downloads: "The builds that it produces can be found here: Development builds." The author suggested GitHub and the /devbuilds page for fresh dev downloads.

Beyond the Feb. 26–27 user-visible items, the feed included a "What's new in 1.19.3" platform excerpt listing concrete fixes and PR numbers: improved iOS/Mac support and Game Mode support (#19287, #19281, #19269, #19270, #19257, #19254, #19244, #19227, #19224, #19213, #19200, #19187, #19184, #19161, #19118); IR Interpreter correctness and optimizations (#19299, #19280, #19268, #19265, #19262, #19260, #19255, #19252, #19240, #19233, #19231, #19193, #19189, #19173, #19128); Interpreted Vertex Decoder optimizations (#19243, #19241); SDL fixes (#19131); a Legacy Edition for old Android TV (#19401); Android and Windows shortcuts icon and bugfix work (#19139, #19142, #19138); and improved performance of CHD loading (#18931).

The Atom feed explains why per-commit builds matter for regressions: "A classic emulator buildbot makes new builds (emulator executables) for every single change to the emulator source code. This can be very useful when tracking down regressions, that is, finding out when specifically something that was working before now broke." For bisection the feed gives stepwise guidance: "By using the halving or bisection method, you can often track down errors over huge ranges of commits in a small number of tries. Simply try two builds that you know work and don't, then try the one in the middle between them. Then if it's still broken, try the range from the first commit to the one you just tried, and if not try the second half. Repeat!"

The feed also listed build scripts and packaging files included in the repo, showing filenames such as b-ios.sh, b.sh, build.gradle.kts, build_fontatlas.sh, build_ppgeatlas.sh, copyrelease.sh, copysym.sh, font_atlasscript.txt, git-version.cmake, gradle.properties, gradlew, gradlew.bat, history.md, link_readme.py, notinstalled.txt, ppge_atlasscript.txt, ppsspp.desktop.in, ppsspp.iss. With the Feb. 26–27 dev builds live and the new buildbot running, expect incremental UI and platform work to appear faster, though the feed cautions Mac builds will be limited and the buildbot "will be less reliable" for the time being.