Software Bugs

[hmp10]

Screen freeze could be cable or bad solder joint

But the lower Pilot Screen froze (still displaying) at the same time that the right-side of the Glass Cockpit blacked out. Could a freeze on one screen at the same time as a blackout on another screen be caused by a hardware wiring issue?

 

[dawktah LucidGT]

What was particularly annoying is that it occurred during a family visit from Poland during which we had plans to use the car frequently for outings. As the Tesla was too cramped, we were left with the Honda minivan, which soldiers ever onward problem-free.

Lucid did update the software to 1.2.17, so I'm hoping something in the three new releases they uploaded will deal with the issues I was having. Probably a long shot, though, as some posters have reported an onset of problems with the 1.2.10 installation.

I'm beginning to get the feeling this is related to a bad chip(s) there maybe so many in the car and its intermittent hard to detect?

 

[dawktah LucidGT]

But the lower Pilot Screen froze (still displaying) at the same time that the right-side of the Glass Cockpit blacked out. Could a freeze on one screen at the same time as a blackout on another screen be caused by a hardware wiring issue?

I would think so.

 

[hmp10]

I would think so.

In earlier service calls for the same issues Lucid replaced the MCU, said they checked the screens, and flushed the screen cooling system in case the problem was caused by overheating. Would a wiring issue not show up in all this?

And the A/C shutoff occurred in the same freeze/blackout event, but not until a couple of minutes into it. Could all that be related to wiring? (I'm not trying to be argumentative. I'm just trying to figure out what Lucid could have missed here.)

 

[dawktah LucidGT]

In earlier service calls for the same issues Lucid replaced the MCU, said they checked the screens, and flushed the screen cooling system in case the problem was caused by overheating. Would a wiring issue not show up in all this?

And the A/C shutoff occurred in the same freeze/blackout event, but not until a couple of minutes into it. Could all that be related to wiring? (I'm not trying to be argumentative. I'm just trying to figure out what Lucid could have missed here.)

I am only using my limited understanding but until Munro cuts one open we won't know what wiring harnesses and or cables they are using.

My seat squeak was from a cable being run too close or in-between something tech said.

 

[hydbob]

In earlier service calls for the same issues Lucid replaced the MCU, said they checked the screens, and flushed the screen cooling system in case the problem was caused by overheating. Would a wiring issue not show up in all this?

And the A/C shutoff occurred in the same freeze/blackout event, but not until a couple of minutes into it. Could all that be related to wiring? (I'm not trying to be argumentative. I'm just trying to figure out what Lucid could have missed here.)

I'm fairly certain the AC issue is a fairly new bug introduced after the 1.2.10 update. Pretty much everyone is experiencing it now with random shutoff and more impromptu defroster mode enabling. The other items are a mystery to everyone apparently!

 

[Percentage]

What was particularly annoying is that it occurred during a family visit from Poland during which we had plans to use the car frequently for outings. As the Tesla was too cramped, we were left with the Honda minivan, which soldiers ever onward problem-free.

Lucid did update the software to 1.2.17, so I'm hoping something in the three new releases they uploaded will deal with the issues I was having. Probably a long shot, though, as some posters have reported an onset of problems with the 1.2.10 installat

When I got my AGT back on Wednesday, they updated to 1.2.17 and it has fixed most of the software problems for now.

 

[joec]

I would say it's almost zero if there are no logs unless they can reproduce it somehow.

it's quite possible that they don't have a robust logging system. i have worked at companies where logging was an after thought and they missed critical paths so it took longer to debug an issue or find out the real root cause. as company matures, logging (usually) gets better.

Given the way the software was cobbled together for release, I'd say it's likely logging was indeed given lower priority than it should have had.

Ironically, when you are rushing out software you know is buggy (because the higher ups are demanding it) you tend to not have time to put in the sort of detailed logging you'd expect to need to fully detect every bug that's bound to occur.

I imagine that team was super frustrated last fall when all of this was going down.

This is why it's so important for your software leadership to have enough power in the room to push back on unreasonable release schedules. But you don't always win those battles, regardless. Even companies like Apple are struggling with this sort of thing lately. Which is why so many iOS and macOS bugs go unfixed for so long.

 

[hmp10]

I'm fairly certain the AC issue is a fairly new bug introduced after the 1.2.10 update. Pretty much everyone is experiencing it now with random shutoff and more impromptu defroster mode enabling. The other items are a mystery to everyone apparently!

My A/C shutdown occurred before the 1.2.10 download to my car.

 

[abbas2099]

Had a very unusual bug today... I am on 1.2.17. Tidal wasnt playing nice so I switched to Bluetooth. About 15 minutes of listening to Bluetooth, Tidal kicked in as well. I was hearing Pink Floyd from Bluetooth superimposed with U2 from Tidal. They both played over each other until I got to work.

 

[Mkatz]

Had a very unusual bug today... I am on 1.2.17. Tidal wasnt playing nice so I switched to Bluetooth. About 15 minutes of listening to Bluetooth, Tidal kicked in as well. I was hearing Pink Floyd from Bluetooth superimposed with U2 from Tidal. They both played over each other until I got to work.

Had similar issue about a week ago with Tune in and Spotify playing simultaneously.

 

[abbas2099]

My biggest issue that has come for me with 1.2.17 is that if you drive over 85 mph and wearing sun glasses, you keep getting dinged with the errors that you are not watching the road, or pay attention. It doesnt happen if I remove my sunglasses. Not sure , why they would add this in. I turned on off those warnings in the DreamDrive settings and all seems to be good for now.

 

[hmp10]

Okay, I just got my car back yesterday from almost two weeks at a Service Center for yet another round of software bugs. I drove the car to dinner last evening, and everything seemed to work fine.

Today I took the car out for a bunch of errand stopovers and found the outside cameras and the surround view were not working. On one of the stops I was out of the car long enough for it to reboot, but the problem did not correct. Even sitting in the car for more than a minute to let things spool up, all I got was the spinning wheel on the surround view. The back-up camera image displayed on the upper screen, but it would not switch to front view. Then, if I pressed the "X" icon to kill the cameras and then hit the "P" icon to display them again, even the upper screen just gave me a blank screen.

I'm now at home where I will leave the car parked for a few hours to see what happens. But even if another reboot does fix the problem, I'm just so damned sick and tired of having to worry about what feature will crap out on each drive, requiring yet another of the endless reboots to reset things in this car. It's getting ridiculous, and I'm becoming convinced these problems are beyond the reach of Lucid's software group to fix, especially now that I know they don't have logs they can access to diagnose these events.

I really, really don't want to go down the Lemon Law route, because I love everything else about this car, but I'm having to think seriously about it. For me, it's becoming a race to see whether Lucid shows evidence they can fix these problems before Lemon Law filing windows close. I'm at software version 1.2.17 and still don't see any evidence that they can.

 

[Sam6062]

My biggest issue that has come for me with 1.2.17 is that if you drive over 85 mph and wearing sun glasses, you keep getting dinged with the errors that you are not watching the road, or pay attention. It doesnt happen if I remove my sunglasses. Not sure , why they would add this in. I turned on off those warnings in the DreamDrive settings and all seems to be good for now.

I have not driven any distance after the 1.2.17 update but looks like they made that feature overly sensitive.

Sad to hear about more issues cropping up.

The scared cat that I am, I am now rethinking if I want to take the car on a 85 mile one way day trip tomorrow.

Thankfully I do it need to charge at an EA station or need 100% range but wasn’t that the point of us buying Lucid, the range?

I suppose my AC issue sounds trivial in comparison.

 

[dawktah LucidGT]

My biggest issue that has come for me with 1.2.17 is that if you drive over 85 mph and wearing sun glasses, you keep getting dinged with the errors that you are not watching the road, or pay attention. It doesnt happen if I remove my sunglasses. Not sure , why they would add this in. I turned on off those warnings in the DreamDrive settings and all seems to be good for now.

I had this issue before 1.2.17 As a matter of fact I got the pay attention warning with no sunglasses just driving into the sun.

Okay, I just got my car back yesterday from almost two weeks at a Service Center for yet another round of software bugs. I drove the car to dinner last evening, and everything seemed to work fine.

Today I took the car out for a bunch of errand stopovers and found the outside cameras and the surround view were not working. On one of the stops I was out of the car long enough for it to reboot, but the problem did not correct. Even sitting in the car for more than a minute to let things spool up, all I got was the spinning wheel on the surround view. The back-up camera image displayed on the upper screen, but it would not switch to front view. Then, if I pressed the "X" icon to kill the cameras and then hit the "P" icon to display them again, even the upper screen just gave me a blank screen.

I'm now at home where I will leave the car parked for a few hours to see what happens. But even if another reboot does fix the problem, I'm just so damned sick and tired of having to worry about what feature will crap out on each drive, requiring yet another of the endless reboots to reset things in this car. It's getting ridiculous, and I'm becoming convinced these problems are beyond the reach of Lucid's software group to fix, especially now that I know they don't have logs they can access to diagnose these events.

I really, really don't want to go down the Lemon Law route, because I love everything else about this car, but I'm having to think seriously about it. For me, it's becoming a race to see whether Lucid shows evidence they can fix these problems before Lemon Law filing windows close. I'm at software version 1.2.17 and still don't see any evidence that they can.

This is why they need a OBD II port at least a third party could potentially look at error codes.

 

[dawktah LucidGT]

I have not driven any distance after the 1.2.17 update but looks like they made that feature overly sensitive.

Sad to hear about more issues cropping up.

The scared cat that I am, I am now rethinking if I want to take the car on a 85 mile one way day trip tomorrow.

Thankfully I do it need to charge at an EA station or need 100% range but wasn’t that the point of us buying Lucid, the range?

I suppose my AC issue sounds trivial in comparison.

Headed to Louisville in a couple of hours from Indy. I'll post if I have any issues.

 

[abbas2099]

Okay, I just got my car back yesterday from almost two weeks at a Service Center for yet another round of software bugs. I drove the car to dinner last evening, and everything seemed to work fine.

Today I took the car out for a bunch of errand stopovers and found the outside cameras and the surround view were not working. On one of the stops I was out of the car long enough for it to reboot, but the problem did not correct. Even sitting in the car for more than a minute to let things spool up, all I got was the spinning wheel on the surround view. The back-up camera image displayed on the upper screen, but it would not switch to front view. Then, if I pressed the "X" icon to kill the cameras and then hit the "P" icon to display them again, even the upper screen just gave me a blank screen.

I'm now at home where I will leave the car parked for a few hours to see what happens. But even if another reboot does fix the problem, I'm just so damned sick and tired of having to worry about what feature will crap out on each drive, requiring yet another of the endless reboots to reset things in this car. It's getting ridiculous, and I'm becoming convinced these problems are beyond the reach of Lucid's software group to fix, especially now that I know they don't have logs they can access to diagnose these events.

I really, really don't want to go down the Lemon Law route, because I love everything else about this car, but I'm having to think seriously about it. For me, it's becoming a race to see whether Lucid shows evidence they can fix these problems before Lemon Law filing windows close. I'm at software version 1.2.17 and still don't see any evidence that they can.

I have noticed my backup camera goes out more now with 1.2.17. Once that happens, clicking the front camera doesnt work as it seems the screen froze up.

 

[hmp10]

I have noticed my backup camera goes out more now with 1.2.17. Once that happens, clicking the front camera doesnt work as it seems the screen froze up.

It seems my surround view may be failing because it's not getting a signal from the front view camera. I'll get a backup view on the upper screen until I turn surround view off and try to turn it back on, at which point I can't get a front or back view on the upper display.

Since my car now has 1.2.17 it could well originate with that update, as it's a new problem with my car.

 

[WildRide47]

Okay, I just got my car back yesterday from almost two weeks at a Service Center for yet another round of software bugs. I drove the car to dinner last evening, and everything seemed to work fine.

Today I took the car out for a bunch of errand stopovers and found the outside cameras and the surround view were not working. On one of the stops I was out of the car long enough for it to reboot, but the problem did not correct. Even sitting in the car for more than a minute to let things spool up, all I got was the spinning wheel on the surround view. The back-up camera image displayed on the upper screen, but it would not switch to front view. Then, if I pressed the "X" icon to kill the cameras and then hit the "P" icon to display them again, even the upper screen just gave me a blank screen.

I'm now at home where I will leave the car parked for a few hours to see what happens. But even if another reboot does fix the problem, I'm just so damned sick and tired of having to worry about what feature will crap out on each drive, requiring yet another of the endless reboots to reset things in this car. It's getting ridiculous, and I'm becoming convinced these problems are beyond the reach of Lucid's software group to fix, especially now that I know they don't have logs they can access to diagnose these events.

I really, really don't want to go down the Lemon Law route, because I love everything else about this car, but I'm having to think seriously about it. For me, it's becoming a race to see whether Lucid shows evidence they can fix these problems before Lemon Law filing windows close. I'm at software version 1.2.17 and still don't see any evidence that they can.

You have the patience of a saint with all the problems you have experienced. I know I would not have handled it as well as you if this had happened to me.

I think it would be more than fair at this point for Lucid to give you full credit back for your car and apply it to a Sapphire when it is released.(assuming you can afford it or want it.) Your previous posts indicated you were considering trading in for one in the future

I would love a Sapphire, but is above my means as I am looking to maybe buy a condo in Scottsdale AZ to escape the winters here in Oregon. Renting a condo there for 7 nights in early Feb. as a preliminary scouting expedition. A lot depends on the state of the stock market whether my finances will allow me to consider this.

Since you have multiple cars, maybe this is something you may want to pursue with Lucid. Personally, I would think you deserve even more that considering all the aggravation you have endured

 

[borski]

I got my car back from two weeks in the Riviera Service Center yesterday afternoon. My car had been having another swarm of software malfunctions: screen freezes and blackouts, A/C quitting mid-drive, white noise blasts from rear speakers.

As usual, the car did not present the same faults while they had it, as the malfunctions are usually intermittent and widely spaced (although the above trio occurred inside of 24 hours). What did surprise me is that they could find no trace of the malfunctions in the computer logs, even though I was able to give them dates and times of each event within a 15-30 minute range.

I'm fairly ignorant about computer hardware and software, but what are the chances that Lucid can chase down software malfunctions that are leaving no traces in computer logs?

In order to be able to trace a bug in the logs, they need to have been logging for that particular thing in the first place. For example, they might log crashes, but may not be logging specific memory leaks if they don't know about them, and it's not like there is some 'master log' of every single thing that had ever occurred, because that would get very massive very fast.