[Bug]: Android Auto - Unexpected close (X) button in ETA

[bderrien]

Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

With the latest version, I have a “close” (X) button in the ETA panel.

However, clicking it doesn’t do anything.
Do you know if it’s possible to remove this button, or to attach a callback to it?

I couldn’t find any information about it in the Android documentation.

Flutter version

3.38.5

Package version

0.9.3

Native SDK versions

• I haven't changed the version of the native SDKs

Flutter Doctor Output

[✓] Flutter (Channel stable, 3.38.5, on macOS 26.5 25F71 darwin-arm64, locale en-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0)
[✓] Xcode - develop for iOS and macOS (Xcode 26.4)
[✓] Chrome - develop for the web
[✓] Connected device (4 available)
[✓] Network resources

Steps to reproduce

apply this patch :

diff --git forkSrcPrefix/example/android/app/src/main/kotlin/com/google/maps/flutter/navigation_example/SampleAndroidAutoScreen.kt forkDstPrefix/example/android/app/src/main/kotlin/com/google/maps/flutter/navigation_example/SampleAndroidAutoScreen.kt
index 20c1520bcae9cd91cfd229a1e2324a133ae86c56..8817fe4b96fad29f439cd344e2202bc4f506c7a5 100644
--- forkSrcPrefix/example/android/app/src/main/kotlin/com/google/maps/flutter/navigation_example/SampleAndroidAutoScreen.kt
+++ forkDstPrefix/example/android/app/src/main/kotlin/com/google/maps/flutter/navigation_example/SampleAndroidAutoScreen.kt
@@ -22,12 +22,14 @@ import androidx.car.app.CarContext
 import androidx.car.app.model.Action
 import androidx.car.app.model.ActionStrip
 import androidx.car.app.model.CarIcon
+import androidx.car.app.model.DateTimeWithZone
 import androidx.car.app.model.Distance
 import androidx.car.app.model.Template
 import androidx.car.app.navigation.model.Maneuver
 import androidx.car.app.navigation.model.NavigationTemplate
 import androidx.car.app.navigation.model.RoutingInfo
 import androidx.car.app.navigation.model.Step
+import androidx.car.app.navigation.model.TravelEstimate
 import androidx.core.graphics.drawable.IconCompat
 import com.google.android.gms.maps.GoogleMap
 import com.google.android.libraries.mapsplatform.turnbyturn.model.NavInfo
@@ -35,6 +37,7 @@ import com.google.android.libraries.mapsplatform.turnbyturn.model.StepInfo
 import com.google.maps.flutter.navigation.AndroidAutoBaseScreen
 import com.google.maps.flutter.navigation.AutoMapViewOptions
 import com.google.maps.flutter.navigation.GoogleMapsNavigationNavUpdatesService
+import java.util.TimeZone
 
 
 class SampleAndroidAutoScreen(carContext: CarContext): AndroidAutoBaseScreen(carContext) {
@@ -170,6 +173,14 @@ class SampleAndroidAutoScreen(carContext: CarContext): AndroidAutoBaseScreen(car
             navigationTemplateBuilder.setNavigationInfo(mNavInfo!!)
         }
 
+        navigationTemplateBuilder.setDestinationTravelEstimate(TravelEstimate.Builder(
+            Distance.create(
+                10.0,
+                Distance.UNIT_KILOMETERS
+            ),
+            DateTimeWithZone.create(System.currentTimeMillis(), TimeZone.getDefault())
+        ).build())
+
         return navigationTemplateBuilder.build()
     }
 }
\ No newline at end of file

then start a turn-by-turn NavInfo

Expected vs Actual Behavior

Actual behavior

• A close (X) button is displayed.

Expected behavior

• The close (X) button should not be displayed.
  or
• It should be possible to handle clicks on the close (X) button.

Code Sample

/

Additional Context

No response

[IvelinKrastev]

What I found useful is to override onStopNavigation from NavigationManagerCallback inside your auto session.

Something like this:

  private val navigationManagerCallback =
    object : NavigationManagerCallback {
      override fun onStopNavigation() {
        bridge?.sendEvent("stopNavigation", emptyMap())
        ...
        }
      }

And then, on the Flutter/Dart side, stop the guidance and perform any necessary post-processing. That worked for me at least.

[bderrien]

Hi,

I tried adding this callback, but it didn’t change anything. Clicking the cross button does nothing, and no logs are printed
(It’s happening on the Android Auto Desktop Head Unit (DHU) simulator while connected to a real Android phone (api 14))

diff --git forkSrcPrefix/android/src/main/kotlin/com/google/maps/flutter/navigation/AndroidAutoBaseScreen.kt forkDstPrefix/android/src/main/kotlin/com/google/maps/flutter/navigation/AndroidAutoBaseScreen.kt
index 8126bf957cb6d25a96dc12e12bae7b94474bcaa5..9d32b63069b11da891c0e2c01338f9204ac4b73d 100644
--- forkSrcPrefix/android/src/main/kotlin/com/google/maps/flutter/navigation/AndroidAutoBaseScreen.kt
+++ forkDstPrefix/android/src/main/kotlin/com/google/maps/flutter/navigation/AndroidAutoBaseScreen.kt
@@ -20,6 +20,7 @@ import android.app.Presentation
 import android.graphics.Point
 import android.hardware.display.DisplayManager
 import android.hardware.display.VirtualDisplay
+import android.util.Log
 import androidx.car.app.AppManager
 import androidx.car.app.CarContext
 import androidx.car.app.Screen
@@ -28,6 +29,8 @@ import androidx.car.app.SurfaceContainer
 import androidx.car.app.model.Action
 import androidx.car.app.model.ActionStrip
 import androidx.car.app.model.Template
+import androidx.car.app.navigation.NavigationManager
+import androidx.car.app.navigation.NavigationManagerCallback
 import androidx.car.app.navigation.model.NavigationTemplate
 import androidx.lifecycle.DefaultLifecycleObserver
 import androidx.lifecycle.LifecycleObserver
@@ -119,6 +122,12 @@ open class AndroidAutoBaseScreen(carContext: CarContext) :
     initializeNavigationListener()
 
     registerFlutterEventHandler(flutterEventForwarderForThisScreen)
+
+    carContext.getCarService(NavigationManager::class.java).setNavigationManagerCallback(object : NavigationManagerCallback {
+      override fun onStopNavigation() {
+        Log.d("AndroidAuto", "onStopNavigation from host")
+      }
+    })
   }
 
   private fun initializeNavigationListener() {

[illuminati1911]

@bderrien Thank you for opening the issue. We'll take a look at this and update you when we have more to share.

[IvelinKrastev]

Hey @illuminati1911

I just tested this on a real phone connected to a real Android Auto system in a car. I confirm what @bderrien said. It does not work. Even with my solution.

Note: What I implemented worked on the Android Auto Desktop Head Unit (DHU) simulator while connected to the Android Emulator.