Use case

Developers that want to add support for Android 16 features might see a behavioral differences when working with screen orientations.

Apparently there is a change that is scheduled for Android 16: https://developer.android.com/about/versions/16/behavior-changes-16

Proposal

Audit the required steps to adhere to the API changes in https://developer.android.com/about/versions/16/behavior-changes-16#implementation-details

This will probably affect the https://api.flutter.dev/flutter/services/SystemChrome/setPreferredOrientations.html API.

One thing that I'm not sure about it how we should handle the following:

The Android 16 orientation, resizability, and aspect ratio restrictions don't apply in the following situations:

...

- Screens that are smaller than sw600dp

How will we handle this in the Flutter-faced API ? Users might be confused when the SystemChrome API does work on some devices, but not others.