Repository navigation
Android crash related to memcpy vs memmove #1793
Description
Validation
- I have checked the Issues page to see if my problem has already been reported
- I have confirmed that this bug does not occur in the original game running on original Xbox 360 hardware
If you have DLC installed, please specify which ones you have.
- Apotos & Shamar Adventure Pack
- Chun-nan Adventure Pack
- Empire City & Adabat Adventure Pack
- Holoska Adventure Pack
- Mazuri Adventure Pack
- Spagonia Adventure Pack
If you have mods enabled, please specify which ones you have.
No response
If you have codes enabled, please specify which ones you have.
No response
Describe the Bug
Opening this as an upstream issue but when recently trying to get an unofficial port of unleashed recompiled to work on the AYN Thor, I root caused the error down to android implements memory.
Full write up here: SansNope/UnleashedRecomp-Android#158
I wanted to open this to the main repo, to at least get eyes on it as this resolved all the physics related issues and crashing issues that I was experiencing on my device, and it seems like others are reporting the fix works for them too. Please feel free to close and reopen or whatever as you wish!
Steps to Reproduce
Specifically for the current 0.5.3 build of unleased recompiled android, at least on the AYN Thor, you just need to collect a ring or boost a bit and the game should crash before you make it halfway in the first level. Sometimes it crashed for me immediately on ring touch, other times elsewhere, but its quick.
Expected Behavior
No crash
Footage
n/a
Version
n/a
CPU
n/a
GPU
Adreno 740
GPU Driver
n/a
Memory
n/a
Operating System
Android
Additional Context
Again, just leaving this for record for the maintainers
Activity
Dhi20071 commentedon Oct 5, 2026
this this not their issue bruh, also it's vibecoded so please close this issue
puopg commentedon Oct 5, 2026
Happy to close this, and yea for sure that port was vibed, but just wanted to bring attention to the maintainers in case there was something valuable within this memory issue. The core fix which might be isolated to the port, was essentially one line in some of the memory mappings.