u/LeadershipUsual8634

Long story short, car dealer service center uses Lyft through Xtime for pickups and dropoffs.

My car was ready, so dealership sent the Lyft. It was rush hour, so I thought the Lyft was rerouting us via a quicker option, it wasn't until we passed the turn towards the dealership that I asked the driver where we were going. My Lyft app AND the Driver's Lyft app was sending us to a city park miles away from the dealership, DESPITE the correct address showing on the app. For some reason, the Lyft GPS thought a car dealership on a major hwy in Houston was in a park in the middle of the city!

I told the driver that this made no sense, but she insisted on following the Lyft GPS instructions until we ended up at a city park staring at some kids on the playground (no car dealership in sight!!)

I finally convinced her NOT to use the Lyft GPS and her car's built in google maps to get us to the right direction. All through this extra 30 minute diversion, the Lyft GPS is yelling at her to go back to the park. The only options for me are to call 911 or ADT, both of which are overkill for a GPS kidnapping.

Today, just for grins, I put in the name of the dealership again into the Lyft app, and the park comes up!

I have no idea how to tell Lyft that there GPS is messed up, and the dealership is just as baffled as I am!

I, and I think, many others, will pay for a decent audio book player (especially one that access audiobookshelf) for AAOS. To date, there is not one.

Apologies for the all caps & bold, as when I discuss this on different forums, people just don't get it.

Android Automotive Operating System (AAOS) is DIFFERENT from Android Auto (AA).

AAOS is the standard operating system EVs from GM, Polestar, Volvo, Acura, Honda. SOME of these allow dual use with AA, others do not.

I don't know a single thing about programming, though I was pretty good with BASIC back in the 80s.

Per Google:
Android Auto and AAOS should be thought of as different products, not the same app in two places. Android Auto is phone-projected, while AAOS runs natively inside the car, so the app has to be designed for vehicle hardware, system bars, fixed screen behavior, car-specific UX limits, and the automotive Play distribution requirements. In practice, that means rebuilding around Google’s car app templates and quality rules, keeping driving tasks simple and safe, handling parked-only features where needed, testing in the AAOS environment, and meeting car-app standards like no blocked screens, no dead ends, fast response times, and category-specific restrictions before release.

Thanks in Advance!