- Joined
- Jul 31, 2025
- Messages
- 229
- Reaction score
- 445
- Location
- Bay Area, CA
- Cars
- Gravity DE, Model 3
- Gravity DE Number
- 266
People keep on thinking that PaaK will be a flawless solution, but there have already been posts here that quote their head of PR stating that one reason they've been delaying PaaK is b/c of reliability.Doesn't really matter how great the car is if you can't start it and drive it when you need to. No one is denying that lucid has great engineers, but this is their 2nd car and the first one had many key fob issues from what I understand. It seems like this should have been something basic and obvious that their team should have learned from. The simplest fix would have been to have the functional phone as key with ability to drive from app as back up ready for the gravity at launch. If those two things had been there, no one would be complaining about key fob issues or the fact that only one was given at delivery. Lucid also wouldn't be having these supply chain issues with the key fob as it could have potentially been non-essential.
I don't mind living through early adopter problems, but the basics need to work.
If people remember the pre-3.3.20 days, the problems weren't just with keyfob hardware that couldn't reliably ping the car. The car itself didn't use its radio antennas well so didn't receive pings properly, and when it did the startup sequence was either slow or stalled enough to cause blank screens. Meanwhile, the various erroneous errors that popped up either stopped the car from driving or scared the driver in thinking that the vehicle was inoperable. None of these things are solved by using phones instead of keyfobs.