## Why is there an increase in both trip time and distance?

A large spike in the expected distance and time often indicates that the driver
deviated from the route, chose an alternate route, or added a stop. For more
information on added stops, see [Handle added stops](https://developers.google.com/maps/documentation/navigation/connect/handle-trip-data.md.txt#handle-added-stops).

## Why is the ETA different from the Directions API (Legacy) or Routes API?

Google Maps or Waze may calculate a different route from the
Directions API (Legacy) or Routes API depending on your selected
parameters or due to traffic conditions changing after the API call.

Because Navigation Connect continuously calculates the route using the driver's
real-time position, it usually provides more accurate ETAs.

## Why did the ETA jump suddenly?

Sudden changes in the ETA occur for several reasons:

- **Real-world conditions:** Traffic, road closures, or other external events can affect the ETA. These conditions typically don't affect the expected distance unless Google Maps or Waze calculates a reroute.
- **Driver actions:** The driver might deviate from the route, choose an alternate route, or add a stop. These actions typically change both the expected distance and the remaining time. For more information on added stops, see [Handle added stops](https://developers.google.com/maps/documentation/navigation/connect/handle-trip-data.md.txt#handle-added-stops).

## Why does the trip status show `SUSPENDED` when distance or time remains?

This status appears when the driver ends the trip early, such as by exiting
navigation or closing the navigation app. For more information on the
`SUSPENDED` status, see [Handle trip end states](https://developers.google.com/maps/documentation/navigation/connect/handle-trip-data.md.txt#handle_trip_end_states).

To help the driver reach their intended destination, provide a button or link in
your app that lets the driver resume the Navigation Connect session to
the same destination. For more information about mid-trip app switching, see
[Handle mid-trip app switching](https://developers.google.com/maps/documentation/navigation/connect/mid-trip-app-switching.md.txt).

## Does Navigation Connect affect battery life?

No. Navigation Connect doesn't consume more battery life than a standard
navigation session on Google Maps or Waze.

## Does Navigation Connect support Incognito mode?

No. Navigation Connect doesn't support Incognito mode in Google Maps. If the driver
uses Incognito mode, the app displays an error and the session fails to start.

## Which travel modes does Navigation Connect support?

Navigation Connect only supports driving travel modes (including Taxi). If the
driver navigates using a non-driving mode (such as walking, bicycling, or
transit), Navigation Connect won't return telemetry updates or traffic
information.

## How does Navigation Connect handle route adherence?

Active routes change dynamically based on real-time traffic and road
conditions, so Google Maps Platform doesn't guarantee route adherence to
static, pre-calculated routes.

Navigation Connect calculates routing using the active navigation session in
Google Maps or Waze. This session routes the driver dynamically, so it might differ
from routes your backend pre-calculates before the trip starts (using the
Directions API (Legacy) or Routes API).