Force Screen orientation not affecting accelerometer input [Android]
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
Force Screen Orientation under video settings doesn't affect Accelerometer as expected.
Playing Kirby Tilt N Tumble on mGBA supports Android accelerometer, but it is off by 90°. (Ex. Left is down)
I found this fix: https://github.com/libretro/RetroArch/issues/6535#issuecomment-495315228
However, when forcing screen orientation the accelerometer gives the same results no matter the orientation I pick.
Force Video orientation allows me to play correctly, but then I have to hold my device sideways, which isn't ideal.
Expected behavior
Force Screen Orientation should also set the on device Accelerometer orientation.
Steps to reproduce the bug
- Load an accelerometer-based game (tilt n tumble)
- Switch Force Screen Orientation in video settings
Version/Commit
1.22.2 (69a4f0e)
Bisect Results
No response
Present in the nightly version
Yes, this is reproduced in the nightly build
Platform & operating system
Android
Affected Cores
mGBA
Environment information
*Retroid Pocket 5
Relevant log output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue on Android with Kirby Tilt ’n’ Tumble in mGBA, then trace the Force Screen Orientation video setting and the accelerometer input path. Done means changing the forced orientation also rotates the accelerometer input consistently, without requiring the device to be held sideways.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100