[MAPSAND-2265] Fix MapSurface.setMaximumFps not working on secondary displays (#10405)

### Summary

Fixes https://mapbox.atlassian.net/browse/MAPSAND-2265

- Fix `MapSurface.setMaximumFps` returning wrong FPS on secondary
displays (e.g. Android Auto)
- Use `Context.getDisplay()` on API 30+ instead of
`WindowManager.defaultDisplay`
- Change is confined to a single method in `MapSurface.kt`

### Problem

`MapSurface.surfaceCreated()` reads the screen refresh rate via
`WindowManager.defaultDisplay.refreshRate`, which always returns the
**primary display's** refresh rate. When `MapSurface` runs on a
secondary display (e.g. Android Auto at 60Hz) with a 120Hz primary
display, `setMaximumFps(30)` produces ~60fps instead of 30fps. The
`FpsManager` receives 120Hz as the screen rate, yielding a ratio of
30/120=0.25 instead of the correct 30/60=0.5.

### Solution

On API 30+ (`Build.VERSION_CODES.R`), use `Context.getDisplay()` to
obtain the display the surface is actually attached to, consistent with
how `MapView.onStart()` already uses `View.getDisplay()`. Fall back to
the deprecated `WindowManager.defaultDisplay` on older APIs.

### Key Changes

- **`MapSurface.kt` `surfaceCreated()`**:
`WindowManager.defaultDisplay.refreshRate` →
`Context.getDisplay().refreshRate` (API 30+)

### Note on reproduction

I was not able to reproduce the exact issue described in the ticket. My
test setup: phone with 120Hz display + Android Auto emulator supporting
60fps. Both `context.display.refreshRate` and
`(context.getSystemService(Context.WINDOW_SERVICE) as
WindowManager?)?.defaultDisplay?.refreshRate` returned 60, and the
Android Auto refresh rate can be correctly set to 30fps both before and
after the change. It might require a specific device/head unit
combination to reproduce the discrepancy.

### Validation

- [x] Manual test: `setMaximumFps(30)` on a 60Hz secondary display
produces ~30fps as expected

cc @mapbox/maps-android

GitOrigin-RevId: ab04871940ea3b605a7c0e6894a1975fb6f448ba

Author: pengdev

CHANGELOG.md

@@ -11,11 +11,12 @@ Mapbox welcomes participation and contributions from everyone.
 
 ## Bug fixes 🐞
 * Fix NPE crash in `PointAnnotationClusterActivity` example when the remote GeoJSON endpoint returns a non-successful HTTP response.
+* Fix `MapSurface.setMaximumFps` not working correctly on secondary displays (e.g. Android Auto). Use `Context.getDisplay()` on API 30+ to get the actual display refresh rate instead of always using the primary display's rate.
+
 # 11.19.0 February 24, 2026
 ## Dependencies
 * Update gl-native to [v11.19.0](https://github.com/mapbox/mapbox-maps-android/releases/tag/v11.19.0), common to [v24.19.0](https://github.com/mapbox/mapbox-maps-android/releases/tag/v11.19.0).
 
-
 # 11.19.0-rc.1 February 12, 2026
 
 ## Features ✨ and improvements 🏁

maps-sdk/src/main/java/com/mapbox/maps/MapSurface.kt

@@ -2,6 +2,7 @@ package com.mapbox.maps
 
 import android.content.Context
 import android.graphics.Bitmap
+import android.os.Build
 import android.view.MotionEvent
 import android.view.Surface
 import android.view.WindowManager
@@ -95,9 +96,13 @@ class MapSurface : MapPluginProviderDelegate, MapControllable {
         fallback = MapView.DEFAULT_FPS,
         logTag = TAG,
         operation = {
-          @Suppress("DEPRECATION")
-          (context.getSystemService(Context.WINDOW_SERVICE) as WindowManager?)
-            ?.defaultDisplay?.refreshRate?.toInt() ?: MapView.DEFAULT_FPS
+          if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {
+            context.display.refreshRate.toInt()
+          } else {
+            @Suppress("DEPRECATION")
+            (context.getSystemService(Context.WINDOW_SERVICE) as WindowManager?)
+              ?.defaultDisplay?.refreshRate?.toInt() ?: MapView.DEFAULT_FPS
+          }
         }
       ) { screenRefreshRate ->
         mapController.setScreenRefreshRate(screenRefreshRate)