libretro / libretro/RetroArch

Haptic feedback/Vibration strength parameter is ignored

Open
#16,896 2 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

Android devices.
Haptic feedback/Vibration strength parameter is ignored

Expected behavior

the "Vibration strenght" for the touch input can be set between 0% and 100% in 5% steps.
That should affect how the vibration is executed.

Actual behavior

In fact, nothing changes at all. Vibration intensity stays the same.

Steps to reproduce the bug

1 ) Open Retroarch 1.19.1 (this happens since several versions actually) on Android
2) Run a game with any core
3) use a touch overlay. The default is fine, or anyone else for what it's worth it.
4) go to Settings -> -> Input -> Haptic Feedback/Vibration and ensure that "Vibrate on keypress" is enabled
5) on the same configuration screen, change the vibration strength from "100%" to any other value and see that the vibration is the same.

Bisect Results

This happens since I started using Retroarch on Android in 2022.

Version/Commit
  • RetroArch: 1.19.1 stable

  • Environment information
  • OS: Android 13. This happened on older versions of Android too.

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 in RetroArch 1.19.1 on Android through Settings → Input → Haptic Feedback/Vibration, using a touch overlay and changing Vibration strength. Trace the Android touch-input haptic path from that setting and verify that values from 0% to 100% in 5% steps produce different vibration intensities. Done means the configured strength affects vibration execution on supported Android versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.