Pico 4 Android controls fire on point not on touch, screen rotation changes by itself, gamepad sometimes disabled

Description

Touch controls:
On Pico 4 Android the controls of the menu behave awkward.
As soon as the controller points to the menu it behaves as touched.
Navigation works ok with a wired controller but not with the system controllers.
Retroarch is the first app that shows this behaviour.
The overlay display exposes the same behaviour.
The trigger does nothing so the menu can only be navigated by an extra controller.

Screen rotation:
the set screen rotation of 90 degrees does not stick.
On minimizing the app the screen returns back to portrait
and sometimes back to landscape.

gamepad:
The wired gamepad works when starting the core and in the menu.
After minimizing or going to the menu it suddenly does not work.
Changing between menu and game gets the gamepad working again.

[Description of the bug]

Expected behavior

Touch controls:
Pointing to the controls and use the trigger as touch (same as with all other android apps)

Screen rotation:
rotation should stay as set

Controls:
controls should keep working

Steps to reproduce the bug

1. Open app
2. feel awkward with controls

Bisect Results

It seems to be the default behavior most likely because it will work on other android devices well and a VR headset is not in the scope.

Version/Commit

You can find this information under Information/System Information

• RetroArch: 1.13.0 64bit

Environment information

• OS: Android 10, Pico 4 v5.2.7

Start by reproducing the behavior in the Android app's menu, overlay, screen-rotation, and gamepad paths on a Pico 4. Compare pointing and trigger input, rotation after minimizing, and gamepad behavior when switching between the menu and a core. Done means trigger-based touch works, the selected rotation persists, and the wired gamepad remains usable.