- Joined
- Dec 31, 2021
- Messages
- 724
- Cars
- Lucid Air Grand Touring
That is very good to know. Thank you!If you get a note from your dermatologist, you can go darker in the front. The law was updated to allow for exceptions due to skin conditions.
That is very good to know. Thank you!If you get a note from your dermatologist, you can go darker in the front. The law was updated to allow for exceptions due to skin conditions.
Tint shops get this wrong a lot...for the front windshield/windows the max tint allowed is 88% with the max allowed for glazing (that's the term in the law but it just means glass) + tint at 70%. The glass itself blocks some light. If the car already has slightly tinted glass, then the shop would have to measure light transmission to determine the film tint that can be applied if you wanted to be strictly legal. Back side and rear windscreen can be as dark as you want as long as you have both side mirrors.
If you get a note from your dermatologist, you can go darker in the front. The law was updated to allow for exceptions due to skin conditions.
That is very good to know. Thank you!
I’ve been told 1.2 at the earliest. The right hand screen has a non standard size which limits the CarPlay screen to a perfect rectangle inside the screen.With that in mind and all the recent progress with DreamDrive, does anyone have any insight on which upcoming version is likely to activate Apple Carplay ? 1.2.?
i could be way off here but Lucid seems to be using Flutter for building iOS/Android apps (checked their job openings a while back and they have mentions of flutter). AFAIK Flutter doesn't officially support CarPlay but there is an open source project that helps you integrate it. I'm not familiar with CarPlay development but it does seems like that's the only option right now. I don't know if Lucid's legal department is okay with using a 'random' open source project in their apps.I’ve been told 1.2 at the earliest. The right hand screen has a non standard size which limits the CarPlay screen to a perfect rectangle inside the screen.
CarPlay does work with dual-screen setups with a main screen and instrument cluster, but there could be a neat trick to it. I think Lucid wants the right hand nav screen to be the instrument cluster in CarPlay and the lower screen to be the controls. This would mean you adjust CarPlay on the lower screen and the upper one shows nav, tracks, etc. This may be why it is delayed, because CarPlay is otherwise quite straightforward to implement.
i could be way off here but Lucid seems to be using Flutter for building iOS/Android apps (checked their job openings a while back and they have mentions of flutter). AFAIK Flutter doesn't officially support CarPlay but there is an open source project that helps you integrate it. I'm not familiar with CarPlay development but it does seems like that's the only option right now. I don't know if Lucid's legal department is okay with using a 'random' open source project in their apps.
yeah i saw that. they may not be comfortable using an unofficial SDK (again, i'm guessing here). i have worked with companies where their clients were not comfortable using popular third party open source libraries.Neat! The open source package [1] is MIT-licensed so should pose absolutely no legal issues if they choose to use it.
[1] https://github.com/oguzhnatly/flutter_carplay
they do. their Infotainment system is based off android. their iOS and Android apps are written in Flutter which is a 'write once, deploy it to iOS and Android' sorta framework. it's developed by Google. that framework currently doesn't natively support Apple CarPlay.I thought Lucid was using Android Automotive for their UX?
yeah i saw that. they may not be comfortable using an unofficial SDK (again, i'm guessing here). i have worked with companies where their clients were not comfortable using popular third party open source libraries.
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.I’ve been told 1.2 at the earliest. The right hand screen has a non standard size which limits the CarPlay screen to a perfect rectangle inside the screen.
CarPlay does work with dual-screen setups with a main screen and instrument cluster, but there could be a neat trick to it. I think Lucid wants the right hand nav screen to be the instrument cluster in CarPlay and the lower screen to be the controls. This would mean you adjust CarPlay on the lower screen and the upper one shows nav, tracks, etc. This may be why it is delayed, because CarPlay is otherwise quite straightforward to implement.
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)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.
It’s also the reason OTA are so important. Porsche has said “F U” to the 2020 and 2021 Taycan buyers and will not be delivering further updates to the vehicles for newer features (Android auto, nav improvements, bug fixes, etc)Interesting. It works flawlessly and connects quickly in my Audi Etron and my wife BMW X7. I have to assume as you said that it's likely an issue with Porsche's implementation.
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)
* when my phone is connected to the car, the network connection on the phone becomes super janky and stops loading websites a good portion of the time
* sometimes when the car is off, the phone still thinks it’s connected to CarPlay and refuses to disconnect
* connecting to CarPlay is super duper slow. I’m talking like 5-10 minutes sometimes after it connects to Bluetooth.
As for the above questions about Flutter: if the Lucid app is written in Flutter, why does that matter for CarPlay and/or Android Auto? The app is totally separate from the CarPlay/Android Auto implementation.
Got it. The infotainment definitely has other systems embedded within it (just take a look at the settings for any of the apps, it’s 100% loading a frame)It doesn’t necessarily, but their infotainment *might* also be written in Flutter. Toyota’s new infotainment systems are, for example.
WTF? How is Porsche doing that not a bigger story?It’s also the reason OTA are so important. Porsche has said “F U” to the 2020 and 2021 Taycan buyers and will not be delivering further updates to the vehicles for newer features (Android auto, nav improvements, bug fixes, etc)
I got mine does at Autoskinz in Valencia, but that's a treck for you. I got a quote from PFS. They do A LOT of high end custom wraps and are very well known. But they are super busy and couldn't get me in for a couple months.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.