libretro / libretro/RetroArch

RetroArch only lists and accepts input from one controller connected to a WebOS TV (when two are connected)

Open
#16,912 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

RetroArch only detects one controller connected at the time. When I connect more than one controller to the TV, be it via USB or Bluetooth, although WebOS detect them all, RetroArch only detects one and accepts input from one. (I used Xbox 360 wired controllers and XBox One via Bluetooth).

Expected behavior

List and accept input from all the game controllers connected to the TV.

Actual behavior

Only lists and accepts input from one controller when one or more are connected to the TV.

Steps to reproduce the bug
  1. Install RetroArch on a WebOS TV (I did ir via Homebrew Channel on a rooted TV)
  2. Connect one controller to the TV via the WebOS Settings Menu (Bluetooth) or simply to the USB port.
  3. Open RetroArch
Bisect Results

Only ever tried connecting more than one controller now, so can't trace if it was always like this or added later.

Version/Commit
  • RetroArch: 1.17.0 [WebOS]
Environment information
  • OS: WebOS

Contributor guide

Open the contributing guide

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 issue on a WebOS TV with multiple USB or Bluetooth controllers, using the controller enumeration and input-handling entry points in RetroArch. Confirm where only one controller is listed or accepted, then verify that all connected controllers appear and provide input.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.