Having homebrew compiled with the MEMSIZE=1flag by default can cause all sorts of issues.
- It can mask out-of-memory errors on 1k since the developer is unaware that the feature is turned on.
- It can and will cause random issues on PS Vita, where the upper 16MB of extra ram is used by other native vita processes as well as flash0 ramfs and that can cause double-tapping.
Many homebrew will stop working, or will be extremely unstable, on PS Vita due to this, and ARK's Custom Launcher is one such case.
The MEMSIZE flag should only be set if the developer sets it via the Makefile.
I also suggest adding MEMSIZE=2 as an option, to tell the CFW to unlock only the first extra 16MB for stability on ps vita.
Having homebrew compiled with the MEMSIZE=1flag by default can cause all sorts of issues.
Many homebrew will stop working, or will be extremely unstable, on PS Vita due to this, and ARK's Custom Launcher is one such case.
The MEMSIZE flag should only be set if the developer sets it via the Makefile.
I also suggest adding MEMSIZE=2 as an option, to tell the CFW to unlock only the first extra 16MB for stability on ps vita.