Melonds single screen mode registers inputs on both screens at the same time on Android using touch controls

Description

On Android, if you select single screen mode for melonds and use touch controls, and select Touch for the second screen, it will register inputs on both the main screen and the second screen when using touch controls on Retro pad.

Expected behavior

When you select single screen mode, touch controls should only work on the active screen.

Actual behavior

Touch inputs are registered on both screens at the same time on melonds single screen mode. For example, playing Super Mario Bros DS and using the main game screen, you can move Mario normally, however jump button activates both the jump button but also activates de power up button on the second screen, producing the power up constantly.

Steps to reproduce the bug

1. Select single screen mode.
2. Select touch for the second screen.
3. Play any game where Retro pad touch controls are located in the same position as a touch screen input, and both inputs will activate at the same time.

Version/Commit

• RetroArch: [version/commit]
  Using stable 1.10.3 since latest versions still haven't fixed Retro achievements slow saving / loading mentioned here: https://github.com/libretro/RetroArch/pull/14712

Environment information

• OS: Android 12, LG g8x

No source file, test, or entry point is named. Reproduce on Android 12 with Melonds in single-screen mode, Touch selected for the second screen, and overlapping RetroPad controls; trace where those touch inputs are dispatched and verify that only the active screen responds.