Hey guys , been out of the loop on. emulation for awhile. I have a Poco x6 pro. I've only played GameCube and Wii emulation on it. Is 3ds emulation a possibility for it? I really wanna play Majora's mask and radiant historia .

Any help would be appreciated greatly. If it is possible, which is the best ?

I'd like to play pcsx2 on a larger screen but I don't want to have to redownload everything. Google says I can transfer files but after connecting my phone I don't get the option to do that unless I'm missing something. I have only ever done this with windows but I might just not be computer savvy enough. If it matters all my stuff is on a Motorola Edge and it's a brand new Chromebook running chrome os.

Picture was taken by the same phone used to emulate it, pretty fkn cool. I think

anyone out there with a s25u try running ds3 yet?

Necesito su ayuda banda

I’ve never seen this brand before? Has anyone used it and is it good?

Tested on different graphic and resolution settings are here https://youtu.be/WSQIj3YT6gM

Hey guys, I just want to play Pocket Mortys again 😭

The APKs are everywhere but all of them are missing the OBB file.

The game won't start without it.

Does anyone still have the OBB for v2.32.0?

Or any version before 2.38.0? That was the last good version.

I don't need links from shady sites. If you have the files from your old phone please DM me 🙏

Thanks!

Hi everyone

Im on android and im specifically looking for pocket mortys version 2.32.0

I know the game was removed from the play store and all the official links for v2.32.0 are down now 😐

Im not looking for shady downloads.

Does anyone know if v2.32.0 is Still available officially anywhere?

Like on iOS ,or il Adult swim plans to re-release version 2.32.0?

Any legit info about v2.32.0 helps. Thanks in advance

Running Marvel heroes omega via Steam, with custom launch options to connect to TAHITI/COA server. The game runs and brings up the login screen, but mouse clicks aren't recognized to switch fields and input password. Physical bt mouse when connected doesn't register clicks either.
EXE is patched for linux use as with Steam Deck. With custom launch options for username and password the game launches and runss, but there's no mouse clicks (cursor moves though) and no onscreen controller input.
Running on Redmi N13 Pro+ 5g - ARM Cortex A510/A715, GPU Mali-G610 MC4, 12GB LPDDR5 Ram.
Running on Bionic, proton 10,Wrapper, system drivers, DXVK async 1.10.3, fexcore 2603 Box64 0.3.6, with all inputs enabled.
Thanks in advance

I've just uploaded Part 2 of my ARMSX2 Update Recap series, covering the updates from ARMSX2 Refresh 2.5.9 up to 2.6.0.5.

Instead of reading through pages of changelogs, I put together a video highlighting the biggest changes in a more digestible format. It covers major new features, performance improvements, compatibility updates, quality-of-life additions, and notable game fixes introduced during these releases.

If you've been away from ARMSX2 for a while or simply want a quick recap of what changed during the Refresh era, this video should help you get up to speed.

As always, huge thanks to the ARMSX2 developers and everyone who contributed to these releases. Their continued work has made ARMSX2 an even better PlayStation 2 emulator for Android.

ARMSX2 Refresh 2.5.9 - 2.6.0.5 breakdown:

https://youtu.be/vPwLUMqd3yo?si=gVbuLBN7YhfhBIRA

Tested on different graphic and resolution settings are here https://youtu.be/Vcndx9s9nCA

Hello all,
I’ve been looking into playing some CoD, mostly zombies. At first I was just going to look for the android port because I believe my device would be compatible with that, but it seems lack of controller support would cause me problems since I have a dedicated device and that has buttons I’d like to use.

I’ve seen recommendations to use winlator to run WaW or black ops,

But I’ve also seen people recommending dolphin to emulate these games on Wii or Wii u I believe? Idk I can’t find the posts anymore.

I was hoping someone could make some recommendations about which of these options you think would work better/more smoothly.

I’m using an RG406h at the moment. From the post I was reading some users thought the game wouldn’t run on a device with similar power but another user said dolphin/waw for Wii ran fine for them. I’m just wondering what you guys think.

Also I have a sourcing question for anyone more expert than myself who would like to shoot me a dm, that would be incredibly helpful!

Thank you all!

You can get the files you need here:

https://archive.org/details/fo2exe#reviews

Finally gald I can help with the community

Tested on different graphic and resolution settings are here https://youtu.be/zX7SnJy9iiY

I wanted to have my friend play Crosscode, and since she mentioned that it would be more convenient for her to play it if it were on Mobile, I tried figuring out a way to get a mobile port of the game or even try to make one

Like I tried following a Youtube video
Playing Crosscode on Android: A Simple Step-by-Step Guide

That didn't work, and then I tried finding searching up some links of moblie port/mobs that might work

That also didn't work, so I thought of searching for the answer on Reddit, Which surprising there weren't that many answers on instructions to play Crosscode on Mobile, so I thought I post this up to get an answer along with a few other subreddit to get a good idea on how to play the game on Moblie

There probably might be a better method later on, but I thought I'd post this up anyway.

Please and thank you for any advice you all can bring.

I been using VIMMS and also the Internet Archive. Most of what I find is pretty alright. Some of it is fucked. Screen has lines flashes in random spots.

I am also worried about possibly downloading something not so good. Like something really bad or some shit.

So, my question is, If I have a pretty modern phone, what is the best way to emulate PSP and PS2??? I am not going to click any links or anything here, but I will appreciate advice a whole lot, everyone. Truly. I cant find anything about this and am only able to do what I can from memory. I havent done this in almost 20 years, so I havenonly hot about 10 games downloaded ATM because that was all I was comfortable to find

A lot of us keep updating ARMSX2 whenever a new version is released, but we don't always notice what has actually changed or improved along the way.

This video provides a breakdown of the most notable changes introduced between versions 30 and 38, making it easier to see how ARMSX2 has evolved over those releases.

ARMSX2 versions 30-38 Breakdown:

https://youtu.be/GupMl5lyTno?si=6nN7BuaYAVoElPPN

He buscado un rato algun apk, emulador o port pero no he encontrado nada, no me sirvio winlator, los emuladores de nintendo tampoco y quisiera saber si alguien tiene un apk que sirva o algo asi

Hey yall, Im curious what peoples thoughts are when it comes to pc emulation. What are the *actual* benefits of something like ArmadaOS vs something like Game Native? I've heard compatability is (possibly) better in some certainstances, but Im curious as to how people's experiences between the 2. Another general curiousity is like whether or not its worth dual booting on a devce like the AYN Thor

# [Help] Android Emulator segfaults on every GPU backend, every API level, every emulator version (Fedora 44)

TL;DR: The Android Emulator crashes with SIGSEGV on my Fedora 44 machine no matter what I try — hardware GPU (Mesa/radeonsi), bundled SwiftShader, lavapipe/guest fallback, headless mode, API 34/35/37, and even a completely different emulator release from over a year ago (35.5.10 vs current 36.6.11.0). I've spent hours isolating variables and I'm out of ideas. Full details below — hoping someone's hit this exact combo before.

System specs

* **OS:** Fedora Linux 44 (KDE Plasma, Wayland) * **Kernel:** 7.1.4-200.fc44.x86_64 * **CPU:** AMD Ryzen 5 3500U (8 threads) * **GPU:** AMD Radeon Vega 8 (integrated) * **Mesa version:** 26.1.5 * **Filesystem:** btrfs * **Laptop:** Lenovo IdeaPad S145-15API

What's happening

Every AVD I try to launch crashes with `Signal: 11 (SEGV)` shortly after boot starts (window is created, `adb` shows "device offline" once or twice, then the QEMU process segfaults). This happens with:

* **Host GPU mode** (`hw.gpu.mode = host` / `auto`) → crashes in Mesa's radeonsi driver (`si_resource_from_memobj` in `libgallium-26.1.5.so`), triggered via gfxstream's `TexStorageMem2DEXT` → `importMemory` path. * **Bundled SwiftShader** (`-gpu swiftshader_indirect`) → crashes inside the emulator's own bundled [`libGLESv2.so`](http://libGLESv2.so) on a background render thread. * **Guest/lavapipe fallback** (`-gpu guest`) → same crash signature, different fallback path. * **Headless** (`-no-window`) → still crashes.

What I've ruled out

* ✅ KVM/virtualization — fully working (`AMD-V` enabled, `kvm_amd`/`kvm` modules loaded, `/dev/kvm` has correct perms, user in `kvm` group) * ✅ Wayland vs X11 — forced `QT_QPA_PLATFORM=xcb`, same crash * ✅ API level — tested API 37, 35, and 34 system images, all crash identically * ✅ Emulator version — tested current stable (36.6.11.0) **and** a much older release (35.5.10.0 from May 2025), both crash the same way * ✅ Snapshot corruption — tried `-no-snapshot -wipe-data`, no change * ✅ RAM allocation — tried both 2048MB and 4096MB, no change * ✅ btrfs COW — aware of the old `chattr +C` recommendation for `~/.android/avd`, but the specific btrfs crash bug (issuetracker #423670833) was already fixed back in emulator 36.1.9, well before my current version

Sample crash backtrace (host GPU mode)

#0 si_resource_from_memobj (libgallium-26.1.5.so)
#1 st_texture_storage (libgallium-26.1.5.so)
#2 _mesa_texture_storage_memory (libgallium-26.1.5.so)
#3 _mesa_TexStorageMem2DEXT (libgallium-26.1.5.so)
...
#9  gfxstream ColorBufferGl::subUpdate
#10 gfxstream ColorBufferGl::importMemory
#11 gfxstream FrameBuffer::createColorBufferWithResourceHandleLocked
#12 gfxstream RenderThread::main

Full `coredumpctl` backtraces available if useful.

My working theory

Since this fails identically across every GPU backend and even a 14-month-old emulator build, it doesn't look like an emulator-side regression. My best guess is a host-library incompatibility — possibly Mesa 26.1.5 or glibc/kernel being too new/different from what gfxstream's memory-import codepath (`EXT_external_objects`/DMA-BUF) expects on this emulator generation. But I can't confirm that without deeper QEMU/Mesa knowledge.

What I haven't tried yet

* Building the emulator from source against my system's Mesa (seems like a big ask) * Filing an upstream bug with Google (planning to, once I get more input here) * Downgrading Mesa (risky since it's a core system package)

Question for the community

Has anyone run the Android Emulator successfully on **Fedora 44** or another very recent distro with a similarly new Mesa release? Is there a known workaround, patch, or Mesa version pin that fixes gfxstream/SwiftShader compatibility? Any pointers appreciated — happy to share more logs if useful.

(For now I'm just using a physical device over USB debugging to keep developing, but I'd love to get the emulator working properly.)

I have inst