libretro / libretro/parallel-n64

No physical button input when launching from other frontends on android #485

Open
#758 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
407
Forks
151
Avg merge
11h 53m
Merged PRs (30d)
11

Description

I hope this is the right repo. Sorry if it aint.. I'm having an issue with Parallel-n64. Whenever I launch this particular core from a frontend different from retroarch. I sometimes don't have have input.

Expected behavior
core launched from command runs the game with buttons working

Actual behavior
core launched from command core runs the game without buttons working. Not even retroarch overlay's and such can be opened.

Steps to reproduce:
Launch an instance of parallel using the following config::

-n com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture
-e ROM {file.path}
-e LIBRETRO /data/data/com.retroarch.aarch64/cores/parallel_n64_libretro_android.so
-e CONFIGFILE /storage/emulated/0/Android/data/com.retroarch.aarch64/files/retroarch.cfg
-e IME com.android.inputmethod.latin/.LatinIME\n  -e DATADIR /data/data/com.retroarch.aarch64
-e APK /data/app/com.retroarch.aarch64-1/base.apk
-e SDCARD /storage/emulated/0
-e EXTERNAL /storage/emulated/0/Android/data/com.retroarch.aarch64/files
--activity-clear-task
--activity-clear-top

Issue has been confirmed on the following devices:

  • OS: Android 11, device: Retroid Pocket 3+
  • Retroid Pocket 2+

Important
This issue does not happen with every game.

Try one of the following

  • Harvest Moon 64(USA)
  • Star Wars: Rogue Squadrons(USA)
  • Super Smash Bros(USA)
  • Tonic Trouble(USA)
  • Rakugakids(EU)

Mentions
This issue has been mentioned multiple times before in other locations:

Frontends where this happens

  • Retroid Launcher
  • Daijisho
  • Dig
  • Launchbox

CANNOT reproduce this on the following device
OS: Google Pixel 3A with Xbox controller. works perfectly there..

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the launch through RetroActivityFuture with the provided Android configuration and affected ROMs, comparing it with a direct RetroArch launch. Investigate the parallel_n64_libretro_android.so entry point and the frontend-provided input path. Done means physical buttons and the RetroArch overlay work reliably across the listed frontends and affected games.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c
Domain
game-dev, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.