In Minecraft Bedrock Edition, the game does not allow scrolling within the Storage section of the Settings menu. This makes it extremely difficult — and in some cases impossible — to manage downloads, worlds, resource packs, and behavior packs properly. After testing various device settings, I discovered that the issue is caused by the game being locked in landscape mode, which breaks the layout specifically in the Storage menu.
To work around this issue, I had to install a third-party rotation manager app to force the game into portrait mode. Only then was I able to scroll through the Storage section normally. However, the moment the device is allowed to return to landscape mode, the bug returns and scrolling breaks again. This is clearly not intended behavior and presents a serious usability issue, especially for players using phones that don't allow fine control over screen orientation or have restricted rotation settings (like ColorOS devices).
Steps to Reproduce:
1. Launch Minecraft Bedrock Edition on a ColorOS (Oppo) phone.
2. Open the game’s Settings and go to the “Storage” tab.
3. Notice the scroll function does not work at all in this menu.
4. Attempt to rotate the device to landscape — Minecraft stays in portrait mode.
5. Install and use a third-party rotation manager to force landscape mode.
6. Open the Storage menu again — scrolling now works as expected.
7. Allow the device to revert to portrait — scrolling breaks again.
Expected Behavior:
Minecraft should follow the system orientation setting.
The Storage settings menu should be fully scrollable regardless of orientation.
Additional Notes:
This issue is particularly frustrating when managing resource packs, behavior packs, or any downloaded content, which gradually pile up and need manual cleanup.
The bug seems to be connected to UI scaling/layout conflicts caused by Minecraft not respecting orientation settings on ColorOS devices.
I hope this bug can be addressed in a future update for better compatibility with ColorOS-based Android phones. Thanks for your time!
This issue is being tracked at MCPE-187962. It will be fixed in 1.21.90.