What's new
By:

1.1.7 Release Notes

borski said:
Getting it tinted next Thursday. Excited for that. Will post photos and the shop (JLenin here in San Jose) is gonna do a video.
Click to expand...

Did you consider doing the tint at OCDetailing when you had the PPF done? I'm curious whether you've used JLenin before and maybe find their prices/work better.
 
eurekaboo said:
Did you consider doing the tint at OCDetailing when you had the PPF done? I'm curious whether you've used JLenin before and maybe find their prices/work better.
Click to expand...

I hadn’t considered tint previously, but John (JLenin) reached out (he’s a friend of a friend) and has spectacular reviews; basically does every tinted Tesla in the Bay Area, haha. I’ll post shots / video of the car when it’s done (doing it next Thursday); he also mentioned he’s going to join the forums at some point and answer questions, etc.
 
hydbob said:
I thought Lucid was using Android Automotive for their UX?
Click to expand...
Putting on my SWE hat, I am 99% sure they are.
FFT said:
Thank you. That makes sense. I am assuming that it will be wireless. Would be a major setback if it has to be wired. I will wait impatiently and hope that it will be implemented by the time my AGT is being delivered. :)
Click to expand...
CarPlay isn't only wired or wireless - it is up to the automaker to allow a data connection via either method to the car. Both are easy to implement and I'd be surprised if they didn't allow a wired connection.
Paladin732 said:
I have wireless CarPlay in my Taycan and absolutely hate it being wireless. A few problems (which I’m hoping are Porsches poor implementation and not CarPlay)
Click to expand...
The issues you're having with the Taycan are most likely due to the hardware used for the wireless connection or Porsche's own lack of optimization for wireless CarPlay. As @FFT noted, there are other implementations that are quite seamless.

The issue with most infotainment systems nowadays is that they require a lot of investment to get right and Lucid is no exception. Especially with a new car there are a lot of low-level optimizations that need to be done in order to improve responsiveness, but then what about the features that customers want/need? Having been in tech for 20 years, this stuff is really hard to balance.

To set some expectations around CarPlay, here's my outlook:
  1. No sooner than 1.2; there's a lot of work to be done prior to CarPlay dropping on basics of the UX
  2. Wired + wireless unless they can really nail the sync rate, which would make wireless alone a possibility
  3. CarPlay will not look very good as the tapered screen messes with the aspect ratio, unless they do a dual screen setup and put the secondary display on the nav screen and the controls on the lower screen
  4. All this could go out the window if they're waiting on a newer version of CarPlay that is going to be released in WWDC. Lucid's engineers have pretty good ties to Apple so if they don't make a statement on CarPlay release in the next few month, then it will likely be delayed until after WWDC. This new version might allow for flexible aspect ratios or more control of the on-screen elements in the Nav to account for the tapered screen.
 
Jon_Rettinger said:
I know I hijacked aked my own thread but any Dream Edition owners who wrapped their cars in southern California? I'm so nervous to let a shop that never worked on a Lucid wrap mine.
Click to expand...
Not sure where you are in So Cal, but I'm likely going to use American Wrap Company in Thousand Oaks for my GT. He posted a video of a black DE that he wrapped in XPEL Stealth this week:

 
copper said:
Putting on my SWE hat, I am 99% sure they are.

CarPlay isn't only wired or wireless - it is up to the automaker to allow a data connection via either method to the car. Both are easy to implement and I'd be surprised if they didn't allow a wired connection.

The issues you're having with the Taycan are most likely due to the hardware used for the wireless connection or Porsche's own lack of optimization for wireless CarPlay. As @FFT noted, there are other implementations that are quite seamless.

The issue with most infotainment systems nowadays is that they require a lot of investment to get right and Lucid is no exception. Especially with a new car there are a lot of low-level optimizations that need to be done in order to improve responsiveness, but then what about the features that customers want/need? Having been in tech for 20 years, this stuff is really hard to balance.

To set some expectations around CarPlay, here's my outlook:
  1. No sooner than 1.2; there's a lot of work to be done prior to CarPlay dropping on basics of the UX
  2. Wired + wireless unless they can really nail the sync rate, which would make wireless alone a possibility
  3. CarPlay will not look very good as the tapered screen messes with the aspect ratio, unless they do a dual screen setup and put the secondary display on the nav screen and the controls on the lower screen
  4. All this could go out the window if they're waiting on a newer version of CarPlay that is going to be released in WWDC. Lucid's engineers have pretty good ties to Apple so if they don't make a statement on CarPlay release in the next few month, then it will likely be delayed until after WWDC. This new version might allow for flexible aspect ratios or more control of the on-screen elements in the Nav to account for the tapered screen.
Click to expand...

For what it’s worth, I agree with everything you said. On point.

As a separate funny note, I was amused that they’re versioning lexicographically and not using semver. 1.1.36 being before 1.1.4 legitimately made me laugh out loud haha
 
For Carplay/Android Auto to be wired, wouldn't the USB port need to have data access? Is that something actually on the horizon?
 
Neurio said:
For Carplay/Android Auto to be wired, wouldn't the USB port need to have data access? Is that something actually on the horizon?
Click to expand...

Yes. But I would be *extremely* surprised if it isn’t already wired for data (at least some of them). It’s not really any extra work, and would have been a major oversight. I suspect they simply haven’t built the functionality into the software, and I do believe someone else on the forums mentioned it would arrive in an OTA, so my guess is it will.
 
borski said:
For what it’s worth, I agree with everything you said. On point.

As a separate funny note, I was amused that they’re versioning lexicographically and not using semver. 1.1.36 being before 1.1.4 legitimately made me laugh out loud haha
Click to expand...
We went from 1.1.2 to 1.1.36 to 1.1.4 to 1.1.5 and will go to 1.1.6 then 1.1.7. That holds up logically, right :)
 
Paladin732 said:
We went from 1.1.2 to 1.1.36 to 1.1.4 to 1.1.5 and will go to 1.1.6 then 1.1.7. That holds up logically, right :)
Click to expand...

It holds up *lexicographically*. In ASCII, the 3 in “36” comes before “4” and is thus alphabetically earlier. So in that frame of reference it holds up, haha.

Of course, ~nobody versions that way anymore because it’s confusing af for consumers.
 
borski said:
It holds up *lexicographically*. In ASCII, the 3 in “36” comes before “4” and is thus alphabetically earlier. So in that frame of reference it holds up, haha.

Of course, ~nobody versions that way anymore because it’s confusing af for consumers.
Click to expand...
If these are manually versioned, I feel like someone tried to do 1.1.3.6 and got 1.1.36 instead, that would make sense (sort of)
 
Paladin732 said:
If these are manually versioned, I feel like someone tried to do 1.1.3.6 and got 1.1.36 instead, that would make sense (sort of)
Click to expand...

To be fair, even semver had issues like this in semver 1.0. [1]

For prerelease tags, semver versions lexicographically, but in the first version of semver they ran into an issue: 1.2.3-beta10 would come before 1.2.3-beta2, which was clearly not what was intended!

So now every release has to have dot-delimited identifiers even after the prerelease tag: so 1.2.3-beta.10 would come after 1.2.3-beta.2, and only the prerelease tags themselves would be sorted lexicographically (aka alpha comes before beta).

Basically, versioning is hard :p

[1] https://octopus.com/blog/semver2
 
borski said:
For what it’s worth, I agree with everything you said. On point.

As a separate funny note, I was amused that they’re versioning lexicographically and not using semver. 1.1.36 being before 1.1.4 legitimately made me laugh out loud haha
Click to expand...
Same! I thought I was going mad when I first saw that.
 
borski said:
Yes. But I would be *extremely* surprised if it isn’t already wired for data (at least some of them). It’s not really any extra work, and would have been a major oversight. I suspect they simply haven’t built the functionality into the software, and I do believe someone else on the forums mentioned it would arrive in an OTA, so my guess is it will.
Click to expand...
That’s my thinking too. I’d be shocked if there wasn’t any USB wired for data.

You could probably plug a locked iPhone into the USB ports and see if it prompts you to unlock to use USB accessories. That could denote a data connection, even if inactive.
 
borski said:
To be fair, even semver had issues like this in semver 1.0. [1]

For prerelease tags, semver versions lexicographically, but in the first version of semver they ran into an issue: 1.2.3-beta10 would come before 1.2.3-beta2, which was clearly not what was intended!

So now every release has to have dot-delimited identifiers even after the prerelease tag: so 1.2.3-beta.10 would come after 1.2.3-beta.2, and only the prerelease tags themselves would be sorted lexicographically (aka alpha comes before beta).

Basically, versioning is hard :p

[1] https://octopus.com/blog/semver2
Click to expand...
I feel like there should be an XKCD about this.
 
Neurio said:
For Carplay/Android Auto to be wired, wouldn't the USB port need to have data access? Is that something actually on the horizon?
Click to expand...

borski said:
Yes. But I would be *extremely* surprised if it isn’t already wired for data (at least some of them). It’s not really any extra work, and would have been a major oversight. I suspect they simply haven’t built the functionality into the software, and I do believe someone else on the forums mentioned it would arrive in an OTA, so my guess is it will.
Click to expand...

copper said:
That’s my thinking too. I’d be shocked if there wasn’t any USB wired for data.

You could probably plug a locked iPhone into the USB ports and see if it prompts you to unlock to use USB accessories. That could denote a data connection, even if inactive.
Click to expand...
I've asked about this a few times. Right now no wired data. No one has given me an definitive answer as to whether it CAN be turned on.

Did they run USB 4 wire 2.0 or USB 3.0 or USB-C 3.1?
 
I was told the same thing, no wired data.
 
You must log in or register to reply here.
Back
Top