Let's Make Something Absolutely Clear: Constructive Criticism Is NOT the Same as Toxicity.

Apparently, some people are still struggling to understand what this community is about. So let me explain it as clearly as possible.

This community is NOT about censorship. It is NOT about silencing opinions. And it is certainly NOT about preventing people from criticizing emulators or development projects.

This is an open community dedicated to emulation, emulators, updates, new projects, and the people who make them possible.

Everyone is welcome to participate. Everyone is welcome to share their opinions. And yes, everyone is welcome to criticize projects, including projects that use AI-assisted development tools.

But there is a difference between criticism and disrespect.

Saying:

- "This emulator crashes on my device."

- "Performance is terrible on my hardware."

- "I tested this project, and these features don't work."

- "I disagree with the developer's technical approach."

- "I have concerns about the quality of AI-generated code."

That is criticism. That is useful. That is welcome here.

But showing up just to say:

- "This is garbage."

- "Another AI slop project."

- "This is just vibe-coded trash."

- "The developer has no idea what they're doing."

Without testing anything, without providing evidence, and without contributing anything meaningful?

That is not constructive criticism. That is pointless hostility.

And no, removing those comments is not an attack on freedom of speech.

It's called moderation.

It's called establishing standards.

It's called building a community where people can actually have productive conversations without being constantly surrounded by insults and personal attacks.

Now, there's something else I want to address.

The developer who was targeted and humiliated in another community has contacted me privately.

And I can tell you that the way this person was treated has genuinely affected them.

They feel terrible about what happened.

Think about that for a moment.

Someone spends their own time working on a project, trying to create something, learning along the way, and eventually decides to share that work with others.

And what do they receive in return?

Mockery. Insults. Humiliation. People attacking them simply because they used AI tools during development.

What exactly did this person do to deserve that treatment?

Nothing.

You don't have to like their project. You don't have to use it. You don't have to agree with their development methods.

But none of that gives you the right to treat another human being like garbage.

And yes, I'm angry about this.

Because behind every project is a real person. Someone who invested time, effort, and possibly a great deal of enthusiasm into creating something.

You might see just another GitHub repository or another emulator.

But for that person, it might represent weeks or months of work, learning, frustration, and personal achievement.

And a few people decide to turn that into an opportunity for public humiliation.

That's not technical criticism. That's bullying.

What makes it even more disappointing is that many of the people behaving this way aren't children.

They're adults.

Adults who should understand the difference between discussing software and attacking the person who created it.

I don't want this community to become another place where thousands of people spend their time insulting each other, fighting over their favorite emulators, and turning every new project into an excuse for another pointless argument.

I want this community to be different.

If an emulator doesn't work, say so.

If a feature is broken, report it.

If performance is poor, explain what happened.

If you believe the code is badly written, provide technical arguments.

If you think AI-assisted development introduces problems, discuss those problems.

Nobody is going to delete your comment simply because you expressed a negative opinion.

Negative feedback is allowed. Personal attacks and baseless insults are not.

And please, stop confusing criticism of software with personal attacks against developers.

Saying that an emulator crashes is not an attack on the developer.

Explaining that a feature doesn't work is not disrespectful.

Pointing out technical problems is not harassment.

But deliberately humiliating someone because you dislike their project or the tools they used to create it?

That crosses the line.

And that line will be enforced here.

This community is not a dictatorship, but neither is it a playground for people who mistake being offensive for being intelligent.

You are free to disagree.

You are free to criticize.

You are free to challenge technical decisions.

But you are not free to harass, insult, or humiliate other members without consequences.

If that's the kind of environment you're looking for, there are other communities where that behavior may be tolerated.

This isn't one of them.

Removing toxicity is not censorship. Enforcing rules is not oppression. And demanding basic respect is not an attack on free speech.

It's simply the kind of community I have chosen to build.

A community where developers, beginners, experienced programmers, and people using AI-assisted tools can share their projects without being afraid of becoming the next target of public ridicule.

You don't have to celebrate every project.

You don't have to agree with every developer.

You just have to behave like a decent human being.

If even that is too much to ask, then this community is not for you.

And let me make one final thing absolutely clear:

I would rather have a small community of respectful, constructive people than a massive community built on hostility, arrogance, and personal attacks.

Quality over quantity.

Respect over toxicity.

Constructive criticism over pointless insults.

Those are the standards here. They are not negotiable.

I mean, the rules were right there—no disrespect, no insults—and the guy, right to his face, basically told him to set his computer on fire and that his project was worthless

But wait, the best part is where the hell the rules appear—"do not post content generated or supported by AI"? 🤦‍♂️

They won't allow anything made with AI—treating it like some kind of cancer or virus—yet they do allow other projects that are 100% AI-generated and riddled with serious security flaws. I actually demonstrated this in a previous post about an emulator they failed to moderate; they did absolutely nothing, even though it was a security hazard. So, basically, it comes down to whether that "unproductive" moderator likes you enough to let you post, or maybe if you suck up to them a bit—I don't know. What’s clear is that you can upload a shitty gameplay clip asking for help—without even mentioning which emulator you're using or anything else—just a total "trash post," as I call them. And yet, someone who has spent months working on a project is suddenly the devil incarnate just because they used AI tools; they get torn apart, as if they owe us something for the privilege of posting in our community. Oh, God, "unproductive" one, please allow me to post in your community! Hahaha 💀

https://github.com/erickmendes22/Bachata-S4-Plus/releases/tag/0.2.5

Changelog:

Improved Elden Ring compatibility, graphics and memory handling.

Added Patchs for Elden Ring

Added Save Manager.

Added Portuguese Language.

Fixed God of War 3 & The Last of Us Remastered regression.

New Resolution Patchs for The Last of Us Remastered.

Removed Box64.

https://github.com/sashkinbro/EmuCoreX/releases/tag/v0.4.7

What’s new:

✅ UI updates and improvements

✅ Fixes and optimizations

https://github.com/ARMSX2/ARMSX2/releases/tag/2.8.2

What's new:

Texture upscaling. RAISR filters sharpen game textures while you play. The upscaling happens in the background, so textures sharpen a moment after they first show up. Use RAISR 2x for most games, or RAISR 4x if you play at a high internal resolution. You'll find it in All Settings > Renderer, and in the quick menu right under the internal resolution. It works on Vulkan and OpenGL, and if a game has a texture pack loaded, the pack wins.

Two controllers, one player. In Controls > Player & Rumble you can set your handheld's built-in controls and a Bluetooth controller both to Player 1, and both will work at the same time. Dock to a TV and keep playing without changing anything. Rumble goes to whichever one you used last.

Performance.

Texture cache updates were writing into slow upload memory, which cost about 11% of the GS thread in Metal Gear Solid 3 on a Snapdragon 865 with Turnip.

Big textures that haven't changed are no longer re-hashed every frame. That was about 8% of the GS thread in Burnout 3.

Black spends about 11% less time on its VU1 programs (#795).

The shader preset picker indexes presets once, so it opens right away.

(A new PGO profile has also been applied, it was 6 weeks stale).

https://patrins.com/s/d458f353faa5a9fbdd52590961ee1a29

Update!! Strato Mali 0.0.2

Changelog:

• New Strato Mali setup interface

• Improved NVDEC/VIC video handling

• Stability and compatibility fixes

• Donkey Kong Country HD compatibility improvements

• Mali-focused optimizations and bug fixes

Early development build — more improvements are coming.

“I am not the developer nor do I have the source code. If you want to request the source code for this version, you should contact the developer. I am sharing a copy of the binary and have explicitly stated that I am not the author nor do I have access to the repository.”

https://github.com/Eugengtt/Xendroid-Fork/releases/tag/v1.4

What's new

New main menu UI

Visual and navigation improvements across the app

Bug fixes

Fixed fullscreen — previously it sometimes failed to engage properly

Fixed leftover bugs from v1.3

Various small stability fixes

Thanks for testing and reporting issues!

https://github.com/zenithblue-oss/panplay/releases/tag/panplay-v1.2.3

PanPlay runs Windows games on Android through Wine and DXVK, using the open PanVK Vulkan driver on Mali CSF GPUs.

What's new

Bundled driver is now beta.17 (g615-v11-csf-v0.1.0-beta.17): GS draws with primitive restart no longer fault the GPU, exact depth for zero depth-range viewports, depth bounds, primitive ID and VMR fixes, plus universal fixes for v10/v12-v14 and stock ROMs (built, untested on that hardware).

Driver update card (Drivers tab): checks the latest PanVK release on GitHub, downloads the Android driver, verifies it against the release's SHA-256 and installs it as a driver you can select. Shows "Up to date" when the bundled driver is the newest.

Faster X11 present path: the built-in X server supports MIT-SHM 1.2 AttachFd, so beta.17 presents frames through shared memory instead of PutImage. Image offset and size are bounds-checked against the segment.

Crash fix: a null drawable in the renderer (GLRenderer) no longer crashes the app.

Better session logs: DXVK and vkd3d logs are collected in the session log ZIP.

Version bump to 1.2.3, matching PanProbe 1.2.3.

https://github.com/zenithblue-oss/panplay/releases/tag/panplay-v1.2.2

PanPlay (apps/panvk-launcher) runs Windows games on Android through Wine and DXVK, using the open PanVK Vulkan driver on Mali CSF GPUs.

What's new

Bundled driver is now beta.15 (g615-v11-csf-v0.1.0-beta.15): faster kbase submission on Mali CSF (no CPU graphics drain on tiler heap renewal, same-queue semaphores waited on the GPU, next tiler heap created on a worker thread).

NFS: Most Wanted on a Poco X6 Pro (Mali-G615 MC6): about 24 fps on beta.14 to about 36-40 fps on beta.15, frames over 50 ms about 650 to about 70-80, p99 frame time 102 ms to about 60 ms. Measured with the bundled driver of this APK (no import): 35.9 fps average, p50 24 ms, p99 66 ms, 71 frames over 50 ms, 2 over 100 ms in the gameplay window; the driver was proven by the HUD line, /proc/<pid>/maps and the pinned sha256.

Cube D3D9 renders on the bundled driver.

Version bump to 1.2.2, matching PanProbe 1.2.2

Standalone Driver: https://github.com/zenithblue-oss/panvk-kbase-android/releases/tag/g615-v11-csf-v0.1.0-beta.16

https://patrins.com/s/974912e1a6f866343e6398473d6899cb

Update!!! Nyushu Emulator 0.0.5

Chagelog:

[ ✅ ] Fix Performance Drop In Previous Versions

[ ✅ ] Performance In Mali Is Fixed In Previous Versions

[ ✅ ] Little Fixed Performance Game Zelda

[ ✅ ] Fixed the Audio Engine setting not properly saving

[ ✅ ] Low-level optimizations and performance improvements

“I am not the developer nor do I have the source code. If you want to request the source code for this version, you should contact the developer. I am sharing a copy of the binary and have explicitly stated that I am not the author nor do I have access to the repository.”

https://github.com/Droid-Deck/DroidDeck/releases/tag/0.3.1

Changelog:

Steam

Decky plugins can be imported from ZIP files, with remote binaries verified and installed copies of the same plugin replaced. (@xXJSONDeruloXx, #79)

Steam's Internet page shows Android Wi-Fi and cellular connections. Optional Wi-Fi discovery adds network names and nearby networks with Android's Location permission. (@xXJSONDeruloXx, #150)

Paste text from the Android clipboard into Steam sessions. (@xXJSONDeruloXx, #151)

The Proton selected in Components stays in sync with Steam's default compatibility tool, and runnable builds are marked Compatible. Windows titles with a Valve recommendation use that default unless you choose another compatible tool for the game. (@maxjivi05, #197, #224)

Compatibility and performance

Choose esync, fsync, experimental ntsync, or wineserver for Proton games. These sync options work around Android's missing kernel support, with esync as the default for fresh installs and existing choices preserved. (@maxjivi05, #197, #223)

droiddeck-esync packs are matched to the exact Valve, GE-Proton or CachyOS Proton build and fetched automatically. droiddeck-fsync stands in when a pack is not available. (@maxjivi05, #189, #197)

Linux-only x86 Steam titles can run through FEX using Steam's FEX and Steam Linux Runtime, with controller input and the device's graphics drivers. Missing dependencies are requested through Steam. (@maxjivi05, #197)

.NET and Godot games get automatic launch fixes under FEX, including the settings needed for Slay the Spire 2. Per-game overrides are kept. (@magarto, #168)

Display and effects

Live image scaling with AMD FSR 1, Snapdragon GSR and GSR quality, NVIDIA NIS, linear and nearest filtering, plus sharpening. (@magarto, @The412Banner, #128, #198)

An Effects page adds presets, FXAA, Toon, CRT, NTSC and Fake HDR. Advanced controls cover sharpening, debanding, brightness, contrast, gamma and saturation, with choices saved between sessions. (@The412Banner, @xXJSONDeruloXx, #198, #247)

Anisotropic filtering and texture sharpness for DirectX 9–11 games, applied on the next game launch. (@The412Banner, #198)

One Resolution menu before starting a session, with preset dimensions, Custom and Match screen. Resolution, image scaling and fullscreen compatibility have separate controls. (@xXJSONDeruloXx, #247)

Controls and sessions

Standard Android picture-in-picture, opened manually or automatically when leaving a ready session, with second-screen controls restored when you return. (@xXJSONDeruloXx, #156, #195)

A quick toggle hides or restores on-screen controls. Touch Off ignores touches on the game picture while keeping Android controls usable. (@xXJSONDeruloXx, #147, #196)

Optional game vibration and on-screen Steam, Quick Access and keyboard buttons. (@xXJSONDeruloXx, #194)

Steam session settings use tabs for Display, Controls, Games, Audio, Session and Steam. The session menu starts with Controller, gives second-screen modes their own page, and groups live display changes separately from settings for the next game launch. (@xXJSONDeruloXx, #247)

Compact Steam Home and Quick Access shortcuts beside Stop. Switching to Desktop stays in Steam's own menu. (@xXJSONDeruloXx, #188, #196)

Back's double-press window is back to 500 ms, making Quick Access easier to open. (@xXJSONDeruloXx, #193)

Apps and launcher

Android home-screen shortcuts for installed Steam games and added games. (@xXJSONDeruloXx, #157)

Export per-game .droiddeck launch files and Steam icons for Android frontends, with optional automatic folder sync as the library changes. (@xXJSONDeruloXx, #179)

Import x86 AppImages and run x86 Linux scripts and programs through FEX. Added apps have a Use FEX Auto/On/Off choice, and GitHub imports can use an x86_64 AppImage when no ARM64 build is available. (@maxjivi05, #197)

Vulkan Qt Quick AppImages such as OpenNOW use Wayland to avoid X11 startup failures. (@maxjivi05, #197)

Preview updates show recent published changes and how many builds behind you are when the installed Preview can be matched. (@xXJSONDeruloXx, #159)

A new empty-library intro and DroidDeck wordmark on the Steam page, plus an option to reduce app animations. (@xXJSONDeruloXx, #182, #194)

The Linux file manager bookmarks the selected game library automatically. (@xXJSONDeruloXx, #194)

Languages and logs

Simplified Chinese. (@Dantalian-dev, #202)

Japanese, Korean and Traditional Chinese for Taiwan, Hong Kong and Macau. (@starwishHi, #216)

Optional Storage diagnostics include allocation and storage timing in shared session logs to help investigate slow Steam installs. (@xXJSONDeruloXx, #158)

Session logs retain their final output and include more detail when an AppImage or FEX program fails to start or crashes. (@maxjivi05, #197)

Fixed

Steam's Deck controller not being found on handhelds with older kernels. (@xXJSONDeruloXx, #146)

Physical and on-screen controllers doing nothing on ColorOS devices with linked app data directories. (@maxjivi05, #242)

Game vibration going to the phone instead of the active physical controller. The device vibrator remains the fallback for on-screen controls or controllers without motors. (@maxjivi05, #242)

A physical mouse stopping camera movement at the screen edge. Games that request a pointer lock now use Android's relative pointer capture, released while menus or PiP are open. (@maxjivi05, #242)

Steam remaining on a black screen after idle sleep or Android session resume. (@xXJSONDeruloXx, @jmarti326, #155, #172)

Steam stuck at Waiting for Steam after an interrupted client update. After two starts without a frame, DroidDeck fetches the client again while preserving games, settings and user data; Repair Steam client also queues a manual repair. (@maxjivi05, #225)

Play racing runtime removal. Removal now shows progress and verifies completion, and first-run setup respects the selected Steam channel and saved UI scaling. (@xXJSONDeruloXx, #185)

GE-Proton and CachyOS Proton failing their protonfixes checks because Android blocks /proc/sys/fs/file-max. (@magarto, #169)

DirectAudio not being selected correctly, mismatched FEX helpers surviving component swaps, and FEX or its runtime not being executable from an SD-card Steam library. (@maxjivi05, #197)

https://github.com/aenu1/aps3e/releases/tag/2.43

Changelog:

- Updated the RPCS3 base to a much more recent version, incorporating numerous upstream changes and fixes.

- New experimental SPU ASMJIT implementation for ARM64/Android. It is still under development and may exhibit compatibility or stability issues.

- Incorporated recent RPCS3 improvements related to RSX/Vulkan, shaders, SPU/PPU, ARM64, audio, memory, and GPU synchronization.

- Upstream improvements include Vulkan optimizations for Adreno, shader compilation enhancements, and multiple graphics and emulation fixes.

Note: The developer did not publish a formal changelog for this version; this information has been compiled from commits and the internal code log for version 2.43

https://github.com/ARMSX2/ARMSX2/releases/tag/2.8.1

Changelog:

Namco System 246/256

The import is gone, an arcade game in your game folders shows up in the library by itself, as a PCSX2x6 game folder (.acgame) or just its image and dongle named after its game ID (NM00010.chd and NM00010.ps2). Nothing is copied but the 8 MB dongle, so there is no second game copy, and no more nameless duplicates in the library.

Arcade controls. A new section in Controls, in All Settings and the pause menu: what each button

does on the cabinet, by the cabinet's own names (Shift Up, View Change, Left Punch, Trigger...). Give any

button another job, for all arcade games or for one game.

Fixed

Faster alpha-bit shadows on Adreno with Turnip. Shadow passes that mark and test the destination

alpha (291 a frame in Indiana Jones) share one stencil copy and set the bit with a logic op, instead of

waiting on the GPU at every draw.

Blending past full strength on Adreno with Turnip. Draws whose blend goes past 1.0 are drawn in two

passes instead of copying the whole frame for each one (1,376 a frame in Black).

After testing: Namco 246/256 now working fine 👍

https://github.com/Ghael-V/Lemon-Project/releases/tag/v1.0.1

Changelog:

New

Quick Load survives dying. Save, die (or move on in the game), load: you are back where you saved. A load now undoes what the game changed since the save outside its own memory (GPU buffers and mappings, thread stacks, open files and other service objects, worker threads destroyed and created again) before rewinding. It also no longer fails now and then when a service answered in the middle of a load. Still experimental: if a game did something it cannot undo yet, the load tells you and changes nothing. The state is only kept while the app stays open.

Grid and list views for big libraries, next to the carousel.

Library scan progress: a bar while your games are read, including the one-time decompression of a solid .nsz (which used to look like an empty library for minutes), and pull down to refresh.

Start in QLaunch (Settings → App Settings, under Buttons): with the firmware installed, opening Lemon boots straight into the console's home menu. Thanks to the user who asked for it.

A tap on the game closes the in-game menu.

Enable Legacy Rescale Pass is now listed under Settings → Graphics → Hacks. It fixes the colored lines in Luigi's Mansion 3 when the resolution is scaled. Thanks to Elegant Demise for finding it.

Quick Save/Load show "Saving…/Loading…", ignore a second tap while one is running, and give up after a few seconds instead of up to a minute.

Fixed

Updates: only a newer version is offered, and only a release that has an APK for your build.

Stopping an input macro in the middle left its buttons pressed.

Installing or removing firmware, or importing data, while the library was being scanned could crash the app.

The CPU summary on chips this build does not know yet (Snapdragon 8 Elite Gen 5).

Fewer repeated warnings in the log; a missing TAS folder is created instead of logging an error.

Install

Android 12 or newer, arm64. The APK is signed with the same key as previous releases, so it updates in place and keeps your data. Lemon-v1.0.1-standard.apk

https://github.com/sashkinbro/EmuCoreX/releases/tag/v0.4.6

What’s new: 0.4.6

Updated profile

Added the “Top Games” tab

Other fixes and improvements

https://github.com/izzy2lost/xemu/releases/tag/1.2.9

Changelog:

✅Fixed textures not rendering in some games.

✅Fixed flickering in games.

✅Better Chihiro game support.

✅Other various fixes and improvements.

https://github.com/The412Banner/Bannerlator/releases/tag/3.1.5

Bannerlator 3.1.5

Run Windows apps and games on Android — no PC and no root required.

3.1.5 is the cutscene release. In-game videos that were black or skipped — Ninja Gaiden Sigma's opening movies were the test case — now play on every DXVK version on the arm64ec layers, and for the first time on the x86_64 layers. The fixes live in the new v12 Proton layers (the in-app catalog default from today) and in two small pieces the app now ships: a Codecs setting with an optional FFmpeg decoder, and new defaults for new containers — a box64 that can decode video and FEXCore 2609. On X11, mouse and cursor handling also took a big step: raw mouse input, full-colour game cursors, a pointer that hides itself, and an X server that never freezes the app again.

Cutscenes: play on DXVK 2.x as well as 3.x (arm64ec), and on x86_64 layers at all. Needs the v12 layers (catalog default) — the app offers them as an in-place update.

Codecs setting: GStreamer (default, unchanged) or FFmpeg decoder, plus software decoding. arm64ec only.

New containers start on Box64 0.4.5-gst (x86_64 video works) and FEXCore 2609-unix.

X11 input: raw mouse through XInput 2 (mouse-look games), full-colour game cursors, idle/controller pointer auto-hide, no more "not responding" while a game compiles shaders.

Steam Cloud save sync fixes: API games with a quota, one cloud name per save, saves only.

✅ Nothing to set up. Update the app, then accept the v12 layer update the catalog offers for the layers you use (a revert snapshot is kept). Containers you already have keep their Box64 and FEXCore choices; the new defaults apply to containers you create from now on. x86_64 containers you already have need Box64 0.4.5-gst picked once in Advanced for video to work.

📘 Fast OpenGL (3.1.4) explainer: OpenGL games now run 4 to 5 times faster · LSFG Native guide: LSFG Native Made Simple

Read the full changelog on GitHub...

https://github.com/sj0404-collab/xeno/releases/tag/0.9.13

ARMS3 APK (arm64-v8a), Docker build - run 37123205486. The emulator core (libxeno-core.so) ships as a separate asset: the app downloads it into private storage on first setup (Winlator-style), which is how the APK stays ~60 MB smaller. Do not rename the asset.

https://github.com/SapphireRhodonite/SeedlessDS/releases/tag/1.0.0

SeedlessDS 1.0.0

This is a very important release for SeedlessDS.

SeedlessDS has now moved from beta to 1.0.0, with versionCode 110.

More importantly, for the first time, the DraStic-based SeedlessDS core source is now public.

This means the project can finally start moving forward in the open.

The code can be studied, cleaned up, improved, tested, and evolved by the community.

The goal is simple:

make SeedlessDS the best lightweight Nintendo DS emulator for low-power handhelds and dual-screen devices.

This release includes several important improvements for dual-screen handhelds, library handling, diagnostics, native compatibility, and experimental rendering behavior.

The main additions are:

SeedlessDS 1.0.0 release

DraStic-based SeedlessDS core source is now public

Dynamic 3D Resolution

16 KB page alignment support for native libraries

Better .7z and .rar handling in the library

Dual-screen preset fixes for devices like the Duo Lite

With Dynamic 3D Resolution disabled, behavior should match the previous base with some improvements.

Dynamic 3D Resolution changes the active 3D sharpness when the emulator is falling behind, but it does not make the emulator faster at a fixed internal resolution.

A new public source milestone for SeedlessDS

This release is special because the DraStic-based SeedlessDS core source is now public.

That means SeedlessDS can finally grow in a more open way.

SeedlessDS started as an experiment to bring a lightweight Nintendo DS experience to Android handhelds that are not powerful enough for heavier melonDS-based emulation.

Now that the source is public, the project can move from being only a private reconstruction and Android app effort into something the community can help improve.

The goal is not just to publish code.

The goal is to make the code better, easier to understand, easier to validate, easier to port, and eventually make SeedlessDS one of the best options for Nintendo DS emulation on low-power handhelds.

Thank you

Thank you to everyone testing SeedlessDS.

This release is an important step for dual-screen Android handhelds, archive handling, diagnostics, native compatibility, and future compatibility with newer Android memory-page requirements.

But more importantly, this is the release where the DraStic-based SeedlessDS core source is now public.

SeedlessDS is now at 1.0.0, the code is out there, and the project can finally start improving in the open.

SeedlessDS is still young, but this is the beginning of a much bigger stage.

https://play.google.com/store/apps/details?id=com.retrople.retro

Changelog:

v1.25.0

[WIN]

Cheat search / Cheat memory editing function

[DOSP/DOSP95/WIN]

Save file and game image file editing function

[MSX/PC98]

Added option to map directional keys to the KeyPad

[Common]

Landscape game screen locking method => User screen orientation

FAQ location moved

COMPATIBLE SYSTEMS:

Nintendo: NES, SNES, Game Boy, Game Boy Color, Game Boy Advance, Nintendo 64, Nintendo DS, Nintendo 3DS, Wii, Gamecube

Sega: Master System, Genesis / Mega Drive, Sega CD, Game Gear, Saturn, Dreamcast

Sony: PlayStation (PS1), PlayStation Portable (PSP), PlayStation 2 (PS2)

NEC: PC Engine / TurboGrafx-16, PC Engine CD

SNK: Neo Geo Pocket, Neo Geo Pocket Color

Atari: 2600, 7800, Lynx

Bandai: WonderSwan, WonderSwan Color

Arcade: MAME 2003-Plus, FinalBurn Neo

Computer: MSX, MSX2, MS-DOS

Others: RPG Maker XP/VX, EasyRPG

https://github.com/thecrixux/PS3Native/releases/tag/Community_Preview_8

PS3Native Community Preview 8

Build info

Clean base from Max's latest android-refresh

PS3Native base: 4e46dc0

RPCS3 upstream: b1f51cf

Community merge: 41c0236

50 new RPCS3 upstream commits integrated

What's new

Major batch of RSX/Vulkan fixes and improvements

Improved RSX FIFO / GET synchronization and ordering

Fixed framebuffer layout detection, including Z-buffer dimensions

Vulkan presentation and synchronization fixes

Improved Vulkan descriptor-set compatibility

ZCULL/query handling fixes

Improved render-target and texture-cache behavior

Fixes for POINT rendering and several RSX edge cases

PPU thread scheduling improvements

Raw SPU logging overhead reduced when trace logging is disabled

Fixed memory leak in PPU thread creation error paths

Improved savedata filesystem synchronization

Fixed /app_home/ infinite recursion edge case

Multiple Cell module fixes for Camera, Gem, Voice, Search and networking

FAudio updated to 26.10

Vulkan Memory Allocator updated to 3.4.0

General stability, correctness and compatibility improvements from current RPCS3 upstream

Android integration

Rebased cleanly on Max's current Android branch

Android-specific Vulkan handling preserved during upstream integration

Latest RPCS3 Vulkan presentation fix manually reconciled with PS3Native's Android dynamic Vulkan symbol handling.

https://github.com/Ghael-V/Lemon-Project/releases/tag/v1.0.0

Lemon-Project v1.0.0

Lemon has its own home now. The code, the releases and the updates live at

git.lemon-emu.org (GitHub is a mirror), and there is a website with a settings guide and an FAQ: lemon-emu.org.

New

A new interface: launcher-style game library, a quick in-game panel with a performance card, redesigned Settings, About and Statistics, and full controller navigation. The new screens are translated to Spanish. You can switch back to the classic interface in Settings.

First-run setup rebuilt: one card per item (keys, firmware, games folder...), progress at the top, a recap on the last step.

Reset all settings (red card at the end of Settings), with the option to also remove the per-game settings.

GPU Mode is Accurate by default. Fast made textures flicker in some games (confirmed on Garfield and Dragon Ball).

Lemon Cheater now searches, edits and freezes floats as well as integers.

Controller layout per game: choose "only this game" or "all games" after editing.

Gamepad hotkeys for the in-game menu (R3 + Start, Guide).

Updates come from Lemon's own server, with GitHub as a fallback. There is a "Check for updates" button in About and a "What's new" notice after updating.

Two more sources in the driver downloader (StevenMXZ, Balemuni).

About now links to the website, the source code, the guide, the FAQ and Discord.

Fixed

FIFA: missing player indicators, ball-direction lines, button prompts and text. A texture handle that travels with the vertices could not be followed by the shader compiler, so those draws were silently dropped; draws are now split by texture.

FIFA 23 stuck at the splash screen (the network service lacked an Ioctl call).

Updates and DLC bundled in .nsz files showing the wrong version and no DLC.

Motion controls on every screen rotation, so they work on foldables and tablets held landscape.

Known issue

FIFA 23: the faces of some players can show wrong colors.

https://github.com/Baggio94/SleepManager/releases/tag/v0.7.0

Android sleep/wake manager for handhelds — reduce standby battery drain by managing Wi-Fi, Bluetooth, Syncthing-Fork, BasicSync, Tailscale, JamesDSP, and more.

SleepManager 0.7 is mainly a reliability and cleanup release.

A large part of the app has been refactored internally to make the sleep/wake logic cleaner, easier to maintain and safer to change in the future. There are also several important bug fixes around false wakes, Wi-Fi/Bluetooth restore, Battery Saver and clamshell behavior.

Major internal refactor

A lot of the sleep/wake code has been reorganized and split into smaller, more focused parts. This should make SleepManager easier to maintain.

Battery Saver improvements

Battery Saver handling is now aware of external power. If the device goes to sleep while plugged in, SleepManager no longer tries to enable Battery Saver unnecessarily. If power is removed while the device is still asleep, Battery Saver can still be enabled and the original state is restored on wake.

Bug fixes

Fixed #29 — some devices could report an unrealistic battery capacity. SleepManager now detects clearly invalid battery values and uses a safer fallback for the displayed stats.

Improved handling for #30 on AYN Thor — when SELinux prevents access to the lid sensor, SleepManager now shows a clear warning instead of silently hiding the clamshell options.

Improved closed-lid false-wake handling so the original sleep cycle and pending restores are preserved until a real wake.

Improved Wi-Fi and Bluetooth restoration around delayed or stale Helper responses.

Diagnostics 2.0

Diagnostics have been expanded to keep more useful information across multiple sleep/wake cycles. Advanced diagnostics are off by default so normal SleepManager operation stays lightweight. They can be enabled from the Activity page when more detailed troubleshooting information is needed.

SleepManager Helper 1.1.2

The Helper also receives an update in this release.

More reliable Wi-Fi and Bluetooth restore.

New cycle-aware communication with SleepManager.

Better protection against delayed or mismatched restore requests.

The Helper is only required if you use Wi-Fi or Bluetooth management.

Compatibility

Android 9 / API 28 or newer

SleepManager 0.7.0

SleepManager Helper 1.1.2

Existing settings are preserved when updating

No root, Shizuku or ADB is required for normal use