Skip to content
Boring Doc
BreakingHigh impactOfficial migration guidesince 3.27.0android

Set default for SystemUiMode to Edge-to-Edge

Framework · Official source

Edge-to-edge mode is Android's default display behavior as of Android version 15 and above. In Android 15, you could opt out of this behavior but, as of Android 16, you can't. To learn more about this change, check out the Android 16 release notes.

Original behavior

By default, Android enforces edge-to-edge mode for all apps that target Android 15 or later. To learn more about this change, check out the Android 15 release notes. This impacts devices running on Android SDK 15+ or API 35+.

New behavior

Not stated in the source.

Who is affected
Applications and packages relying on the previous behaviour or signature. Code that uses SystemUiMode, SystemUiMode.edgeToEdge, SystemChrome.setEnabledSystemUIMode.
Practical impact
Behaviour or API differences that can break builds or change runtime behaviour.
What action should I take?
Follow the official migration guide below, update affected call sites, run `dart fix --apply` where a fix is available, then run your tests.
Official migration guide (excerpt, © The Flutter Authors, CC BY 3.0)

To opt out of edge-to-edge on Android SDK 15, specify the new style attribute in each activity that requires it. If you have a parent style that child styles need to opt out of, you can modify the parent only. In the following example, update the style configuration generated from flutter create.

By default, the styles used in a Flutter app are set in the Android manifest file (your_app/android/app/src/main/AndroidManifest.xml). Generally, styles are denoted by @style and help theme your app. Modify these default styles in your manifest file:

<manifest xmlns:android="http://schemas.android.com/apk/res/android">
    <application ...>
        <activity ...>
            <!-- Style to modify: -->
            <meta-data
              android:name="io.flutter.embedding.android.NormalTheme"
              android:resource="@style/NormalTheme"
            />
        </activity>
    </application>
</manifest>

Locate the style definition in: your_app/android/app/src/main/res/values/styles.xml.

Add the following attribute to the appropriate styles:

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <style name="LaunchTheme" parent="@android:style/Theme.Light.NoTitleBar">
        ...
        <!-- Add the following line: -->
        <item name="android:windowOptOutEdgeToEdgeEnforcement">true</item>
    </style>
    ...
    <style name="NormalTheme" parent="@android:style/Theme.Light.NoTitleBar">
        ...
	      <!-- Add the following line: -->
        <item name="android:windowOptOutEdgeToEdgeEnforcement">true</item>
    </style>
</resources>

Make sure to apply the same change in the night mode styles file as well: your_app/android/app/src/main/res/values-night/styles.xml.

Ensure both styles are updated consistently in both files.

This modified style opts your app out of edge-to-edge for apps targeting Android SDK 15.

create a your_app/android/app/src/main/res/values-35 resource directory that contains styles without the android:windowOptOutEdgeToEdgeEnforcement attribute.

Starting in Flutter 3.27, Flutter apps target Android 15 by default, so if you wish to use this version and not manually set a lower target SDK version for your Flutter app, follow the preceding migration steps to maintain an unset or non-edge-to-edge SystemUiMode.

Landed in version: 3.26.0-0.0.pre Stable release: 3.27

Migration assistantAI-generated · grounded in cited sources
AI explanations are not configured
Set AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.
Official migration guide·Verified classification (95%)

Listed in the official breaking-changes index (docs.flutter.dev/release/breaking-changes).

An official announcement or migration guide documents an intended behaviour or API change. A verified source change (git diff) shows code changed but does not by itself prove a public API is breaking. AI interpretations are labelled and never used to classify a change.

Source commit
b3045439b7c0
Source last updated
Oct 21, 2026
Last synchronized
Oct 21, 2026
Publication status
published
Publication history
  • Oct 21, 2026, 8:31 PM: new → published (ingestion) — Backed by an official breaking-change/migration guide.
AI explanationAI-generated · grounded in cited sources
AI explanations are not configured
Set AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.
Was this useful?
Set default for SystemUiMode to Edge-to-Edge · Boring Doc