Tags: ARMSX2/ARMSX1

Host the app in one task, not one per launch source

Main was singleTop, which only dedupes inside a single task, so a game opened
from a file manager or a home-screen shortcut started a second Main in the
caller's task alongside the launcher's copy — two Activities driving one
process-wide runtime and one native VM. A user's logcat caught it: taskId=20
and taskId=4 both hosting com.armsx2.Main. singleTask keeps one instance and
routes the incoming URI through onNewIntent, which already boots it.

Changelog for 0.1.2

Changelog for 0.1.1

Reject non-PS1 images in the BIOS picker instead of accepting any 128…

…KB-8MB file