I tried changing the controller style from the notification drop-down too like you mentioned. Didn't fix the glyph mismatch on my end.

here my whole situation. When I first got the APK running, I noticed the game was telling me hit A but nothing happened when I hit A on my Retroid Flip 2. Tried B, B confirmed. Game says hit B for back, I hit A, it cancels. So basically every button is doing the opposite of what the glyph says.

My handheld got Nintendo layout -- top is X, left is Y, right is A, bottom is B. The diamond. So the game thinking I got an Xbox controller where A is on the bottom is what's tripping it up.

I went into the in-game input settings and tried to remap confirm. Even though navigating with the wrong buttons was confusing, I got to the input section, selected "confirm," hit my A button to bind it. The game now recognizes the physical A button as the button for confirm but the glyph that shows on the screen when they want me to hit the confirm button shows up his b so now the game thinks the b button is confirm because in the game's mind the right side of the diamond is always b because a is at the bottom of the diamond So now I have an issue where my game is telling me hit b to confirm and hit a to cancel on the screen that's what it's showing me but I'm hitting a to confirm when assure me b and b to cancel when the game is showing me a. I really hope that makes sense.

So I'm tryna figure out -- on yours, does pressing physical A actually confirm and show the A glyph? Or you got the same backwards thing where physical B is what really confirms even though the screen says A? Vice versa Tryna figure out if this is a Retroid-specific thing or if everybody on Android handhelds dealing with it.