Weird systemui bug when using system scale settings close to tablet boundaries

[EtzBetz]

Bug description

We noticed a bug where a users system ui, in particular the 3-button-navigation on his pixel 7 pro would bug out, so that the buttons would behave like in a tablet ui, while not having tablet ui enabled, just being close to the ui scale of it.

I also had opened an issue at the flutter repo, but am having issues to provide a reproducible example or finding where the issue stems from: flutter/flutter#173457

Since the issue originally occurred in interaction with syncfusion charts and only there, I am wondering whether the issue arises here.

I would like to get this issue fixed, but I am not sure on how to progress on this further, especially because I myself do own a Pixel 10 Pro and Pixel 6 and cannot reproduce the issue on these two devices. Only a colleague of mine has a Pixel 9 Pro on which I was able to reproduce the issue, but I cannot borrow his phone continuously.

Steps to reproduce

1. Have Pixel 7 Pro/Pixel 9 Pro (cannot reproduce on P6, P10Pro, 7Pro und 9Pro are the only ones a customer and we could reproduce it with)
2. Use the Pixel Launcher
3. Set system resolution to high, not maximum
4. Set Fontsize and Displaysize to minimum in Android OS settings
5. Use 3-button-navigation instead of gesture navigation
6. Use a SfCartesianChart (we have this in a bottom sheet, not sure whether this is a requirement)
7. open the app
8. navigate to render the SfCartesianChart
9. go to homescreen
10. go back to the app
11. switch to another app
12. repeat the 3 last steps in a random order

Code sample

Can provide this later, I need to work this out...

Code sample

[Add your code here]

Screenshots or Video

Screenshots / Video demonstration

Stack Traces

Stack Traces

[Add the Stack Traces here]

On which target platforms have you observed this bug?

Android

Flutter Doctor output

Doctor output

[✓] Flutter (Channel stable, 3.38.3, on macOS 26.2 25C56 darwin-arm64, locale de-DE) [507ms]
    • Flutter version 3.38.3 on channel stable at /Users/raphael/Documents/Coding/Flutter/flutter_sdk
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 19074d12f7 (10 weeks ago), 2025-11-20 17:53:13 -0500
    • Engine revision 13e658725d
    • Dart version 3.10.1
    • DevTools version 2.51.1
    • Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations,
      enable-native-assets, omit-legacy-version-file, enable-lldb-debugging

[✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0) [7,9s]
    • Android SDK at /Users/raphael/Library/Android/sdk
    • Emulator version 36.3.10.0 (build_id 14472402) (CL:N/A)
    • Platform android-36, build-tools 36.1.0
    • Java binary at: /Users/raphael/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
      This is the JDK bundled with the latest Android Studio installation on this machine.
      To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
    • Java version OpenJDK Runtime Environment (build 21.0.8+-14196175-b1038.72)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 26.2) [1.654ms]
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 17C52
    • CocoaPods version 1.16.2

[✓] Chrome - develop for the web [4ms]
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Connected device (2 available) [9,2s]
    • macOS (desktop) • macos  • darwin-arm64   • macOS 26.2 25C56 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 144.0.7559.109
    ! Error: Browsing on the local area network for iPhone von Raphael. Ensure the device is unlocked and attached with a cable or associated with the same local
      area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] Network resources [220ms]
    • All expected network resources are available.

• No issues found!

[Harsha-SF4223]

Hi @EtzBetz,

We reviewed the reproduction steps in detail and applied all the specified system settings. We also validated the behavior using a sample application on a Pixel 7 Pro emulator. However, we were unable to reproduce the reported behavior in the emulator environment.

At the moment, we do not have access to the required physical devices to test this scenario. We are checking internally for device availability and will update you at the earliest once we obtain a suitable physical device for testing.

In the meantime, we have attached the sample application below. Kindly modify this sample to reproduce the reported behavior and share the updated version with us. This will greatly help us analyze the behavior further within the emulator setup.

Regards,
Harsha.

BD_807799.zip