Google Maps Can Now Plan EV Road Trips With Charging Stops via Android Auto


A Google Maps update unveiled Monday aims to streamline long-range electric vehicle road trips for Android Auto users. The navigation and mapping software can now automatically suggest charging stops when planning longer journeys in EVs, with more accurate arrival time and state-of-charge estimates based on how long its AI-powered routing algorithm thinks you’ll need to plug in. Google says it has compatibility with EVs from 16 automakers — comprising over 350 models and trim levels — in the US.

Route-planning software has gotten significantly more sophisticated since the early days of electric motoring. Back in the day, going on an EV road trip required multiple mapping and EV charging network apps and careful planning to ensure you got where you were going. Even for those of us who knew what we were doing, it could be very stressful. 

Today, nearly all modern EVs feature connected navigation that automatically suggests charging stops (often with live station availability) when planning routes longer than the vehicle’s cruising range. Google Maps’ new EV route planning function brings some of that new EV convenience to older models and to drivers who prefer the Google Maps and Android Auto ecosystem to their vehicle’s onboard software. 

Google Maps can use AI to estimate where and for how long you’ll need to charge when planning a long EV trip.

Google

To get the new EV route planning, go to the Google Maps app on your phone, find the settings and set your vehicle type to “Electric.” Then add the year, make, model and trim and confirm what type of plug your EV uses (NACS, CCS, J1772, etc.) Now, when planning a long route via Android Auto in your car, Google Maps (version 25.44 and up) will display the estimated battery usage for your trip, recommended charging stops (if any), charge time estimates, and the estimated time and battery percentage on arrival. 

Unlike vehicles with “Google Built-in” — such as Volvo EVsPolestar EVs, and GM models like the Blazer EV and Equinox EV — phone-based Android Auto is currently unable to automatically pull live battery information from most cars. Instead, you’ll be asked to manually input your current battery percentage before starting a trip. Google will use that number along with the EV’s weight, battery size and EPA range, real-time traffic information, road elevation changes and weather data to deliver “accurate AI-powered predictions” for the route chosen.

Because phone-based Android Auto can’t pull live battery data from the host car, you’ll have to input (and update) your starting battery percentage before taking off.

Google

However, that means Maps may not automatically update that estimate if your car doesn’t perform like its AI model predicts. For example, if a heavier-than-average payload, additional equipment like a roof rack or trailer or under-inflated tires are dramatically reducing your efficiency, Android Auto and Google Maps may be blind to your range dropping faster than expected. As the saying goes, your mileage may (nay, it will almost certainly) vary, so I’d advise you to keep a close eye on your range.

Still, this new automatic charge plan generation sounds like a promising tool to boost convenience and reduce range anxiety at the beginning of a long journey. Being able to hop into an EV and hit the road with confidence is pretty sweet, especially for owners of older EVs who don’t have access to onboard software for this sort of dynamic route planning. 

You can check Google’s site (or the settings page in the most recent Google Maps app) to see if your EV is among the 16 makes and 350-plus models and trim levels supported.





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Amazon Fire Phone Jeff Bezos

Bloomberg / Getty Images

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • Amazon is reportedly developing a new Fire Phone.
  • The previous model had several issues, including an inferior app store experience.
  • Under new supervision (and with more experience), Amazon can do better this time.

Well, I don’t know about you, but I certainly didn’t have “new Amazon smartphone” on my 2026 bingo card. As it turns out, according to Reuters, the retailer may be developing a new smartphone, internally known as “Transformer.” 

Those familiar with the industry will instantly draw parallels to Amazon’s previous smartphone effort, the Fire Phone from 2014. Appropriately, that phone ended up as part of a fire sale about a year later.

Now, in 2026, with no fewer than five phone brands in the US — Apple, Samsung, Google, Motorola, and OnePlus — Amazon faces a lot of competition. In fairness, it also has two fewer platforms to compete against. In 2014, Windows Phone and BlackBerry were still very much part of the smartphone conversation; these days, not so much.

The AppStore problem

But there’s one mistake Amazon made in its first effort that will absolutely torpedo its chances at succeeding — the Amazon AppStore and specifically the decision to forego Google Play services. Google is simply too valuable in too many lives to not support the platform. Oh, and the Amazon AppStore is terrible.

Also: What’s right (and wrong) with the Amazon Fire Phone

It has admittedly been a few years since I last inventoried the Amazon AppStore, but when I last checked, the Amazon AppStore was a wasteland of half-supported or unsupported apps, with two notable exceptions. Finance, home control, and communication apps were either absent or had not received updates for years prior.

The only apps in the Amazon AppStore that remained up to date were productivity apps (largely powered by Microsoft) and streaming apps. Those two categories work very well on the cheap, underpowered hardware that Amazon usually launches, and that’s fine. A coffee-table tablet is a nice thing to have lying around.

A spark of hope

Amazon Fire Phone

Liam Tung/ZDNET

But a phone is another animal entirely. If a tablet is a device to entertain, a phone is a device for everything else. One of the key reasons Windows Phone failed was its lack of an app ecosystem. The Senior Vice President of Devices and Services,  Panos Panay, is very familiar with that saga, so I’m hopeful that he will make the same arguments to the powers that be at Amazon. 

Honestly, if there is anyone who I think can pull off an Amazon phone revival, it’s probably Panay, who understands design and product development better than most, and to be perfectly honest, he’s my absolute favorite product presenter.

Also: Amazon Fire Phone review: Not a great smartphone

Of course, all of this is early days. This phone is being worked on internally, and even Reuters reports that it could get the axe long before it sees the light of day. Personally, I’m intrigued by the idea, but I sincerely hope that Amazon doesn’t make this the shopping phone it tried to build in 2014. 

If Amazon just wants to make a nice, well-built smartphone, with a skin that pushes Amazon content to the fore, I’m fine with that. But leaving Google behind is a mistake that Amazon cannot afford to make again. Fool me once, and all that.

So, if this phone is to have a chance at success, it needs to embrace Google services so it can be a phone that everyone can use. Amazon has the brand power to make a phone like this work, even up against juggernauts like Apple and Samsung, but it needs to approach this correctly, lest it end up in yet another Fire phone fire sale.





Source link