-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ppsspp on Android screen auto rotate crash #11739
Comments
Thanks, will investigate. Just got myself an F1 :) Does it happen both with OpenGL and Vulkan graphics backends? |
Sorry for the late reply. Gmail didn't display the whole message. Currently installed 1.7.5-433. If it helps, Vulkan doesn't crash during rotation but the screen doesn't scale down or up when rotating from either landscape or portrait. For example, the screen would stay in landscape size when rotating to portrait therby cutting the screen in half. Portrait to landscape would lock the screen to the size that it was when in portrait mode also the screen would be off center. Also installed 433 on my old K3 Note, which only has OpenGL, with custom rom based on Nougat 7.1.2. Screen rotation and screen scaling works perfect. My F1 is still on 10.2.2 stable. BTW, even with this, ppsspp is still the best emulator out there. ☺ Cheers |
The crash should be fixed in the latest git builds. The rest is probably the same issue as #11526. It's an annoying workaround, but going into the settings and changing the immersive option back and forth fixes it. -[Unknown] |
What happens?
Setting screen rotation to "Auto" in the settings crashes ppsspp.
What should happen?
Screen orientation should just auto rotate as normal.
What hardware, operating system, and PPSSPP version?
Pocophone F1
MIUI 10.2 Global Stable
10.2.2.0(PEJMIXM)
I can confirm that PPSSPP 1.7.5-277 screen auto rotation works fine as I'm using it right now. The problem is 1.7.5-363(or maybe somewhere between 277 and 363). That's where it crashes whenever I set screen rotation to auto.
I've installed/uninstalled and cleared data of 1.7.5-363 to no avail.
The text was updated successfully, but these errors were encountered: