https://www.bmw.co.uk/en/shop/en/shop/ls/dp/Base_CarPlay_gb
It also seems that (after an extremely cursory Google) you can indeed retrofit a BMW Head Unit to enable CarPlay in older unsupported models.
https://www.bimmer-tech.net/blog/item/49-how-to-retrofit-car...
Are you sure it was a BMW you were driving?
I don't think the fact that BMW _now_ offers it for _some_ cars (and most importantly, not for my car) disproves my point that automotive companies should be more willing to retrofit parts for you OR offer them via paid software upgrades instead of encouraging you to purchase a whole new vehicle
To me, it seems the downsides generally outweigh the benefits, but I totally agree that its something people need to individually weigh up the pros and cons.
> It's what enables Tesla to turn off features that it doesn't think certain users should have
the misleading part is the phrase "doesn't think certain users should have" it sounds like it's at tesla's discretion but in fact they are referring to a single accident.
I’m not sure I understand the “but in fact”, qualifier because the example that you point to exactly demonstrates that Tesla has the capability to make these changes at their discretion.
It sounds like it’s that way because it is!
Tesla has the capability to turn off features at their discretion, by altering a row in the database.
So…yes, if Tesla doesn’t think a user should have a capability that’s managed remotely, they update a database row (that they have exclusive control over), and that vehicle no longer has that capability.
The statement still reads as totally accurate to me.
The typical use is not malicious (oh, this free trial is now over, so disable that capability), but that’s still a demonstration of Tesla remotely disabling a feature that they don’t think a certain user should have.
My objection is to the capability, rather than a pattern of malicious use. I think the article was correct to point out the capability, and did so by relying on a well known example.
To me, I didn’t read it as an implication that this inaccurate remote disabling was a widespread problem for Tesla but I understand if you read it differently.
It could have read...
"It's what enabled Tesla to once accidentally turn off a feature for a user."
This would still make your point... that they have the capability, but wouldn't be misleading.
Tesla responded by downgrading his firmware remotely, locking his vehicle from future upgrades, and disabling the car's ethernet port.
It doesn’t matter to me that Tesla has only done it once (that we know of), the thing that is disturbing is the capability of Tesla to do this.
The fact that vehicle functionality can be locked behind a Boolean column in the Tesla database is itself the thing that is problematic and disturbing.
And the article in this instance seems accurate, in that they were referring to the capability for Tesla to do this (by pointing at an extant example), rather than claiming that Tesla had a widespread issue of abusing this functionality.