I had two Select pings today. The first pax canceled, because I guess it took me too long to get there. Guess why?
Ubers lousy Navigation couldn't find it. So I punched Pax's Address in my own Navigation System, went on my way, two minutes later: Cancel.
An hour later, I'll get one of those "long Ride" Requests. I am on it.
Again, the Uber Navigation doesn't get it. I quickly enter the address in my own Navi, and 5 minutes later I am at the Pax Home.
I check "arrived" and the Uber Navi tells me Rider has been notified.
Nothing happens.
After 4 minutes I call the pax, it is, after all a Select Ride.
She says "Oh, I had no idea you were waiting outside."
I ask her if she has been notified that I arrived.
She says no.
Alright, I ask her what the exact Address of her Destination is. At this point I no longer trust the Uber Navigation.
My own Pioneer Navigation (AVIC 7201 NEX) has never let me down. It also has traffic built in, which is nice. Turns out, we're going to Encino.
I start the Trip, and follow my own Navi.
I am hitting the 605 North, But Uber Navi still thinks I am on Los Coyotes.
I try to re-boot my Phone, nothing happens.
I get the dreaded "NAVIGATION ERROR"
I swipe the "Start Trip" twice, and Uber Navi is trying to catch up, nada.
We're following the 105, and Uber Navi has finally caught up. I leave mine running, you never know.
Suddenly, the Uber Navi wants me to turn right on Imperial. LOL!
I guess I am no longer on the 105.
As we get off on Mulholland Drive, (off the 405) the Uber Navi completely loses it.
It goes sideways, up and down.
When I finally arrive at Pax Destination, Uber still thinks I'm at the Getty Museum.
Pax was very cool about it the entire Time.
We laughed about Ubers Navi (She was able to see what was going on) we gave ourselves 5 Stars and went our ways.
I got in DF Mode with Uber and Lyft and pretty much deadmiled home.
Traffic wasn't really bad, and surprisingly, Ubers Navi was working again.
Anyone had this happen before?
What a friggin' Nightmare. Sorry about the long post.
Ubers lousy Navigation couldn't find it. So I punched Pax's Address in my own Navigation System, went on my way, two minutes later: Cancel.
An hour later, I'll get one of those "long Ride" Requests. I am on it.
Again, the Uber Navigation doesn't get it. I quickly enter the address in my own Navi, and 5 minutes later I am at the Pax Home.
I check "arrived" and the Uber Navi tells me Rider has been notified.
Nothing happens.
After 4 minutes I call the pax, it is, after all a Select Ride.
She says "Oh, I had no idea you were waiting outside."
I ask her if she has been notified that I arrived.
She says no.
Alright, I ask her what the exact Address of her Destination is. At this point I no longer trust the Uber Navigation.
My own Pioneer Navigation (AVIC 7201 NEX) has never let me down. It also has traffic built in, which is nice. Turns out, we're going to Encino.
I start the Trip, and follow my own Navi.
I am hitting the 605 North, But Uber Navi still thinks I am on Los Coyotes.
I try to re-boot my Phone, nothing happens.
I get the dreaded "NAVIGATION ERROR"
I swipe the "Start Trip" twice, and Uber Navi is trying to catch up, nada.
We're following the 105, and Uber Navi has finally caught up. I leave mine running, you never know.
Suddenly, the Uber Navi wants me to turn right on Imperial. LOL!
I guess I am no longer on the 105.
As we get off on Mulholland Drive, (off the 405) the Uber Navi completely loses it.
It goes sideways, up and down.
When I finally arrive at Pax Destination, Uber still thinks I'm at the Getty Museum.
Pax was very cool about it the entire Time.
We laughed about Ubers Navi (She was able to see what was going on) we gave ourselves 5 Stars and went our ways.
I got in DF Mode with Uber and Lyft and pretty much deadmiled home.
Traffic wasn't really bad, and surprisingly, Ubers Navi was working again.
Anyone had this happen before?
What a friggin' Nightmare. Sorry about the long post.
