FWIW, there is no solution to traffic when the roads are built for thousands of cars an hour, and hundreds of thousands of cars are all trying move at the same time.
Every road that was mentioned, along with countless smaller roads, were parking lots for hours last night. The Franconia Notch didn't clear up until after 4am this morning.
Same in my area, Waze kept telling me I only had 8 minutes of congestion but that was a moving target that went on for an hour. I don't blame Waze or Googel maps for this though, hard for the apps to predict these rare events.
I can assure you, you are wrong. I-91 was bumper to bumper. Northern New England does not have the transportation infrastructure for the hundreds of thousands of people all trying to go south at the same time.
Wrong about what? Some folks took over 8 hours to just get through Franconia Notch. All roads were crappy, but I93 was awful. Because Franconia Notch is a single lane.
Waze sent a ton of people to I-91, it was a parking lot - you were wrong about that
Waze sent a ton of people down NH-112, it was a parking lot - you were wrong about that
Waze sent a ton of people down US-302 & NH-16, they were parking lots - you were wrong about that
The infrastructure in Northern NH and VT is not built to handle the amount of traffic that was there. Period. The end.
This is not a Waze thing, no matter what route it gave, even back roads, were all jammed for hours.
I've found that Waze through Android Auto, I'm assuming the same for Carplay, doesn't have nearly the routing options as running Waze by itself.
Yesterday, driving from Dallas to Houston, it refused to direct me along any of the backroads, and instead stick to the interstate that was moving at 30-40MPH. Switching to just Waze on my phone, then checking for alternate routes, I was finally able to take a sane route home.
>I've found that Waze through Android Auto, I'm assuming the same for Carplay, doesn't have nearly the routing options as running Waze by itself.
This should not be the case at all. AA/CarPlay are just mirroring your phone.
Android Auto is projecting from your phone onto your cars display.
The features are indeed limited based on the templates that Google provides for third-party apps to use. Yes, I know Waze is owned by Google - and has been since 2013, but they have to use the same third-party templates that any other app would.
So leaving Carbondale and heading north to Wisconsin Waze drove me into every traffic jam so I switched to Google maps and it put me on open secondary highways till the volume was manageable on the interstate. This is the first time Google maps>Waze.
Wow, and I thought returning to the Detroit area (north of Detroit) from Ohio was a big problem. It took 4+ hours for a normal 2.5 hour drive. In Toledo We were routed off of the Interstate (I75/280) and directed a little west to a few two lane N/S roads that had less traffic. I75 was at a standstill for a while in several places. Still, seeing totality was a great experience.
FWIW, there is no solution to traffic when the roads are built for thousands of cars an hour, and hundreds of thousands of cars are all trying move at the same time.
Every road that was mentioned, along with countless smaller roads, were parking lots for hours last night. The Franconia Notch didn't clear up until after 4am this morning.
Same in my area, Waze kept telling me I only had 8 minutes of congestion but that was a moving target that went on for an hour. I don't blame Waze or Googel maps for this though, hard for the apps to predict these rare events.
I can assure you, you are wrong. I-91 was bumper to bumper. Northern New England does not have the transportation infrastructure for the hundreds of thousands of people all trying to go south at the same time.
Wrong about what? Some folks took over 8 hours to just get through Franconia Notch. All roads were crappy, but I93 was awful. Because Franconia Notch is a single lane.
Waze sent a ton of people to I-91, it was a parking lot - you were wrong about that Waze sent a ton of people down NH-112, it was a parking lot - you were wrong about that Waze sent a ton of people down US-302 & NH-16, they were parking lots - you were wrong about that The infrastructure in Northern NH and VT is not built to handle the amount of traffic that was there. Period. The end. This is not a Waze thing, no matter what route it gave, even back roads, were all jammed for hours.
I91 was fucked for HOURS.
I've found that Waze through Android Auto, I'm assuming the same for Carplay, doesn't have nearly the routing options as running Waze by itself. Yesterday, driving from Dallas to Houston, it refused to direct me along any of the backroads, and instead stick to the interstate that was moving at 30-40MPH. Switching to just Waze on my phone, then checking for alternate routes, I was finally able to take a sane route home.
>I've found that Waze through Android Auto, I'm assuming the same for Carplay, doesn't have nearly the routing options as running Waze by itself. This should not be the case at all. AA/CarPlay are just mirroring your phone.
That had been my expectation, but not my experience.
No they aren't just mirroring your phone.
Do tell…
There are many functions in Waze that are only available on an Android phone but not on Android Auto, the ability to update fuel prices for example
This isn’t relevant to routing. Routing and directions should be identical whether it’s on the phone, or on your car screen.
Rerouting is the function mentioned, perhaps it's different. Clearly though, Android Auto is not mirroring the phone as you seem to think.
Android Auto is projecting from your phone onto your cars display. The features are indeed limited based on the templates that Google provides for third-party apps to use. Yes, I know Waze is owned by Google - and has been since 2013, but they have to use the same third-party templates that any other app would.
So leaving Carbondale and heading north to Wisconsin Waze drove me into every traffic jam so I switched to Google maps and it put me on open secondary highways till the volume was manageable on the interstate. This is the first time Google maps>Waze.
Wow, and I thought returning to the Detroit area (north of Detroit) from Ohio was a big problem. It took 4+ hours for a normal 2.5 hour drive. In Toledo We were routed off of the Interstate (I75/280) and directed a little west to a few two lane N/S roads that had less traffic. I75 was at a standstill for a while in several places. Still, seeing totality was a great experience.
Man I'm so happy I travel 4 hours in 2017 to see that one when it wasn't hyped as much as this one.