1.1.7 Release Notes

[Paladin732]

WTF? How is Porsche doing that not a bigger story?

Not really sure, it should be. As much as we love our Taycan, we would never buy another Porsche with this treatment

https://www.taycanforum.com/forum/threads/%F0%9F%93%A3-pcm-6-update-announcement-update-retrofit-being-explored-for-existing-taycans.9022/

 

[eurekaboo]

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

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.

 

[borski]

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.

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.

 

[copper]

I thought Lucid was using Android Automotive for their UX?

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

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.

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.

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)

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.

 

[Neurio]

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.

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:

 

[borski]

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.

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

 

[Neurio]

For Carplay/Android Auto to be wired, wouldn't the USB port need to have data access? Is that something actually on the horizon?

 

[borski]

For Carplay/Android Auto to be wired, wouldn't the USB port need to have data access? Is that something actually on the horizon?

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.

 

[Paladin732]

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

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

 

[borski]

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

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.

 

[Paladin732]

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.

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)

 

[borski]

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)

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

[1] https://octopus.com/blog/semver2

 

[copper]

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

Same! I thought I was going mad when I first saw that.

 

[copper]

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.

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.

 

[copper]

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

[1] https://octopus.com/blog/semver2

I feel like there should be an XKCD about this.

 

[PhotoEye]

I feel like there should be an XKCD about this.

Anyone speak Greek on this forum?

 

[copper]

Anyone speak Greek on this forum?

Nightmare Code

xkcd.com

 

[borski]

I feel like there should be an XKCD about this.

Two that sort of apply:

Standards

xkcd.com

Documents

xkcd.com

 

[dawktah LucidGT]

For Carplay/Android Auto to be wired, wouldn't the USB port need to have data access? Is that something actually on the horizon?

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.

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.

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?

 

[CLTGT]

I was told the same thing, no wired data.