Navigation unresponsive/freezes both Lucid and CarPlay

[jbrichgels]

We have been having on-and-off problems with the whole navigation system freezing or not being responsive. It happens with both Lucid native navigation and CarPlay. The navigation doesn't work to begin with or stops working mid-trip. I will use today's trip as an example of the problem. I left home and used CarPlay to navigate to my destination. I basically knew where I was going and didn't pay attention to the Lucid navigation. Google maps worked on CarPlay to get me to my destination. I was picking up my kid and didn't get out of the car for it to shut down. I then tried to use Lucid's navigation to get me home and discovered that it still thought I was at home/at my point of origin. The Lucid system never moved from our point of origin location. CarPlay worked for a bit, but then it stopped following the navigation and when I closed out the app and tried to reset, Google Maps in CarPlay also thought I was at home. It was fine for this trip because I knew how to get home, but it has been problematic other times.

Anyone have a suggestion, beyond rebooting?

 

[slidingmike]

Interesting. I understand that only one can be active at a time (Lucid's Google nav, Apple's Google or Apple nav, Android's Google nav); perhaps switching between them in a single drive session, especially if a trip is still considered active by the initial nav choice (even if you've reached your destination), exposes some edge cases that were never expected. Keep pushing, testing, documenting -- and then file a bug when you understand exactly what caused it.

If you don't want it to happen, you already know several ways to work around it: reboot, stick to one nav, etc etc.

 

[jbrichgels]

Interesting. I understand that only one can be active at a time (Lucid's Google nav, Apple's Google or Apple nav, Android's Google nav); perhaps switching between them in a single drive session, especially if a trip is still considered active by the initial nav choice (even if you've reached your destination), exposes some edge cases that were never expected. Keep pushing, testing, documenting -- and then file a bug when you understand exactly what caused it.

If you don't want it to happen, you already know several ways to work around it: reboot, stick to one nav, etc etc.

That's plausible. Except that I don't think the Lucid navigation ever started at the beginning of the trip to be affected by a transition. But we will explore whether switching mid trip matters.

 

[segbrk]

I have the same bug, though it sounds like less frequently than you. It's some kind of problem with the TCU, and I can confirm it has nothing to do with using Lucid nav sometimes (I don't). The only way I'm aware of to fix it is a reboot.
Here's what I know: The TCU is the computer in the car that processes GPS and cell signals, giving you your location. When it stops working your location will either be fixed in place, wherever it had you last, or it will default to Lucid HQ. Your phone gets its location from the car via the CarPlay connection, until for whatever reason your phone notices that the car's location is bogus. Then your phone falls back to using its own location, which is why CarPlay initially worked for you. It really wants to use the car's though, so it will absolutely switch back and stop working again.

 

[jbrichgels]

I have the same bug, though it sounds like less frequently than you. It's some kind of problem with the TCU, and I can confirm it has nothing to do with using Lucid nav sometimes (I don't). The only way I'm aware of to fix it is a reboot.
Here's what I know: The TCU is the computer in the car that processes GPS and cell signals, giving you your location. When it stops working your location will either be fixed in place, wherever it had you last, or it will default to Lucid HQ. Your phone gets its location from the car via the CarPlay connection, until for whatever reason your phone notices that the car's location is bogus. Then your phone falls back to using its own location, which is why CarPlay initially worked for you. It really wants to use the car's though, so it will absolutely switch back and stop working again.

This makes sense. We did have it revert to Lucid HQ once. I guess we need to report this to software feedback. Thanks for the explanation.