Bob McCormick
My feedback
107 results found
-
118 votes
-
17 votes
An error occurred while saving the comment -
253 votes
Hey!
Thank you for this suggestion.
This is not a priority for the team at the moment and we won’t move forward with it.
We encourage you to keep on coming up with great suggestions
Best,
-
125 votes
Currently working on N. America. will be implanted in the world server in the future.
-
387 votes
-
7,033 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment Duplicate of other similar suggestions. Indeed driving an EV at lower speeds will take less power from the battery. If one route is over FW types and another route uses non-FW types, the latter will likely conserve battery. The navigation apps in most EVs can take this into account and suggest routes accordingly (mine does) - Waze should be able to as well.
-
245 votes
An error occurred while saving the comment If you drive an EV, battery drain is larger on the higher speed routes. For my commute, I can drive on non-FW type roads and save a lot of battery, only taking 2 minutes longer. This could easily fold into better EV support in Waze.
-
114 votes
-
327 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
1,266 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
280 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
821 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
300 votes
An error occurred while saving the comment Technically Waze wouldn't be using the vehicle's antenna through Android Auto, but instead location information that can be provided by the vehicle to Waze over the Android Auto connection.
I believe this is already working. It does require compatibility between the app, the device the app is running on and the vehicle.
-
1,262 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
300 votes
-
463 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
960 votes
An error occurred while saving the comment This also exists in the US. In some states, many towns have sub-village names and street names are duplicated within those villages. House numbers on those streets are also duplicated. But only the town/city name is used on segments - not village names. Waze has to rely totally on Google Maps search results.
-
1,992 votes
-
4 votes
Hey!
This seems to be a bug.
A bug was opened to the relevant teams in the HQ.Thanks,
Hezi -
24 votes
Hey!
Thank you very much for this great suggestion.
As we believe this will be solved with a release of related features, we added to our backlog to track and make sure it was solved.Best,
Hezi
There needs to be parity between running just the app on a mobile device and connecting it to Android Auto / Carplay. More and more vehicles have head units and this interface ...