| || |
Re: google maps bug?
Oh, I was hoping you were reporting *my* bug because it's so crazy, it's embarrassing. I was in the San Francisco Bay Area last weekend, and set Google Navigation to take me from the East Bay to a funeral home in the city. Google did fine getting me across the Bay Bridge, but then it told me to take the first (left-hand) exit, Harrison Street. Now, even I knew that this funereal place was well into the city, but I got off at Harrison Street. Then Google Navy told me turn turn left off Harrison and get back on the bridge, going back to the east bay. Then it told me to get off the bridge at Treasure Island, about halfway across the bridge. I was to turn around and get back on the bridge going west. The right way. Then I was to get off at Harrison. Get back on the bridge, going east again (wrong way), turn at treasure island and take the bridge back to San Francisco, get off at Harrison. Get back... endless loop. The funny thing is that once I passed the Harrison exit, Google Nav just picked up as if it had always wanted me to go the correct way which was wait until the Ninth Street exit.
Afraid this problem was caused by the nut behind the wheel, I asked someone else to use my phone to navigate to that funeral parlor, and, sure enough, Google tried to send her on that endless loop.
So, at the most, it's something weird with my Galaxy GT i9300.