I think you’re allowed to send suggestions to the customer feedback email. I was going to send a summary of improvements etc. after 3 to 4 weeks of ownership.
Give it some time.
So if you approach your car quickly with only your phone in your pocket and it’s in a dead sleep, it wakes up perfectly every time and the handles come out etc? Mine usually does but not always. If it’s already awake, then it responds to the proximity sensor every single time
You’re lucky. Doesn’t work at all for me whether the car is asleep or awake
Yup yup I have a list of suggestions I will be giving them and I will add this to the list.
The issue is the app, not the car. iOS has restrictions for background bluetooth services and you have to set it up just right to make it work. Apple Car Key support will resolve this. can't wait until they add it.
Oh, I see! Good to know!
So it has been running inside a VM instead of the metal? That’s quite unexpected, and I’m guessing due to several different types of hardware used initially. Maybe easier to virtualize into a single environment at the start instead of developing for several different sets of hardware. Once they got enough scale and could have enough engineers along with larger semiconductor orders they could start to optimize and remove the VM.
I was wondering if they’d get this. Car Key looks like an excellent standard, and has vastly responsiveness.
Faster development, quicker/easier testing. Can run multiple iterations of software releases on different VMs. Final acceptance testing has to be done on "real" environments but for dev, VM is the way to go. Only drawback I've run into is when an instruction doesn't execute exactly the same under the emulator as natively. OK, there can also be instances where someone confuses which partition/VM should be used even when it is plainly documented...which can happen when you've worked 80 hour weeks for months.
Agreed VM is the way to go in dev, but never encountered on embedded devices
As I’ve been saying for a couple of months, it’s almost like they never tried driving their own car before selling it to us. It only takes a few hours of using it as a real car to realize the software is all screwed up.
Oh I think they know. But you know how it is. Pressure from investors to start delivering. Engineers usually end up getting screwed and have to make it “good enough” and fix it later. Same story at every company I’ve worked for. Especially startups.
Yea we will probably never know. But I do know that just about everything you mentioned they are already working on. If you look at the manual, the “Air” logo will have nav directions in that spot. And multiple “apps” open is also coming. I’m confident they will get there. Should it have been more solid from the begging? Yes. But at least they are actually updating it unlike my Taycan which promised OTA updates and never delivered a single one.
Didn’t you get that email about a “software update” coming on the 27th that require relogging in? The one that I’m convinced is just changing the auth server
I have not gotten an email about a software update. Should that have been distributed widely to all that have had their vehicles delivered?Didn’t you get that email about a “software update” coming on the 27th that require relogging in? The one that I’m convinced is just changing the auth server
Yea I’ve already got that update. It also adds some permission changes for Bluetooth.Didn’t you get that email about a “software update” coming on the 27th that require relogging in? The one that I’m convinced is just changing the auth server
I think they are referring to Porsche
