What's new
By:

Air Version 2.9.0

drb3333 said:
The term comes from electronics; I have used it much of my working career. [Definitely not the "value of a brick"]

It means you have screwed up so much that you are totally locked out of an electronic device, with no hope of recovery ever. There is no way to access the electronics from the outside at all due to semiconductor protections, etc, so you cannot log in or reprogram in any way. There is no concept of a temporary bricking--only permanent, irreparable damage.

en.wikipedia.org

Brick (electronics) - Wikipedia

en.wikipedia.org en.wikipedia.org
Click to expand...
From the wiki article: “A brick or bricked device is an electronic device… that is no longer functional. It could be due to corrupted firmware, failed operating system, a hardware problem, or other damage. The term is an analogy to a construction brick and its lack of modern technological usefulness.” Maybe there needs to be a new term. My point is, as I stated earlier, “rendered to a point where the product is unusable for its intended purpose.” So, for instance, if I do an update after which my car won’t move no matter what I do, it is as useful to me as a brick. Maybe an OTA tomorrow will fix it but that doesn’t help me today. Especially if I need the car for an urgent purpose. My proposal for a new term: FUBU. Fucked Up Beyond Usefulness.
 
Well, rack up another win for the forum - the definition of "bricked". My life is complete! ☺️
 
mwscan said:
...Maybe there needs to be a new term. My point is, as I stated earlier, “rendered to a point where the product is unusable for its intended purpose.” ... My proposal for a new term: FUBU. Fucked Up Beyond Usefulness.
Click to expand...
Regretfully, no go on your new term. Politicians already appropriated that one for our governing bodies. 🤣
 
mwscan said:
I’ve been all over the Internet, trying to find a common definition for brick in the sense we’re talking about. The consensus of all definitions is that the device is rendered completely inoperable. Not just slowed down or not working well. Not working at all. For an automobile that would mean that it is incapable of performing its most basic function: a means of transportation. It won’t go anywhere. At all. Will not move. Compared to its intended, designed, and advertised function, it has all the value of a common brick. The question then becomes, “for how long?“ If a software fix went to only those cars that were rendered inoperable (and no others) 24 hours later, then I would say that the car was bricked for 24 hours. So, if one wishes to be precise, one could say that the device – whatever it is – is bricked for (whatever time period.)
Click to expand...
But we already have plenty of words for that. When we start using a word to be over dramatic to describe a common situation, and use the word in a way that's essentially meaningless because it would apply to a flat tire, then why not stick to words that represent the actual situation? Bricked has a very specific definition for electronics. It can be looked up in an encyclopedia. If I say that my phone is bricked, it can't be fixed. I don't have to say anything else. If my phone battery is dead, I can say that my battery is dead. It's a given that it's inoperable. If my car's battery is dead, or won't start, or has a flat tire, or has a broken hose, or has a bad starter, any of those phrases can describe the situation far better than calling it bricked. So why use a word in a way that tells nobody about anything when it already has a meaning that tells people something specific?
 
Haggy said:
But we already have plenty of words for that. When we start using a word to be over dramatic to describe a common situation, and use the word in a way that's essentially meaningless because it would apply to a flat tire, then why not stick to words that represent the actual situation? Bricked has a very specific definition for electronics. It can be looked up in an encyclopedia. If I say that my phone is bricked, it can't be fixed. I don't have to say anything else. If my phone battery is dead, I can say that my battery is dead. It's a given that it's inoperable. If my car's battery is dead, or won't start, or has a flat tire, or has a broken hose, or has a bad starter, any of those phrases can describe the situation far better than calling it bricked. So why use a word in a way that tells nobody about anything when it already has a meaning that tells people something specific?
Click to expand...
IMG_0022.webp
 
drb3333 said:
Regretfully, no go on your new term. Politicians already appropriated that one for our governing bodies. 🤣
Click to expand...
Well, you got me. I have to agree. So we’ll just have to come up with another term. How about RINOP: Rendered Inoperable. My car was RINOPed. Or to avoid being confused with the political term, LINOP: Left Inoperable. This leaves it open to the possibility that a new OTA might fix it, but unless/until it does, it’s a 5000 pound paper weight. (4500 if it’s a RWD Pure.)
 
Last edited:
Back on topic, this update seems to be paused, still haven't received the update for 23 Air Touring
 
Back to 2.9, mine has become really buggy. I’m getting random reboots I hadn’t had before. CarPlay stops working occasionally. My audio track info sometimes doesn’t display on the drivers center screen when I have maps up on the drivers right-side screen, and more. It ran great for the first week or so, but since then, not so much
 
JGard18 said:
Back to 2.9, mine has become really buggy. I’m getting random reboots I hadn’t had before. CarPlay stops working occasionally. My audio track info sometimes doesn’t display on the drivers center screen when I have maps up on the drivers right-side screen, and more. It ran great for the first week or so, but since then, not so much
Click to expand...

I’ve had some weird CarPlay things as well. Yesterday it sort of blackout while still playing media. I rebooted and that fixed it.
 
I've had a couple instances of CarPlay blacking out since I went from 2.8.16-->2.9.0. Prior to the updates, everything was working fine.
 
Fun piece of 2.9.0 (2.9.2 actually) feedback. Every time I get in the car now, the dash displays a message about adjusting seating position, implying its profile switching.

I’m the only one that drives the car, no amount of switching around profiles or resets has stopped this message from showing every single time.
 
JGard18 said:
Back to 2.9, mine has become really buggy. I’m getting random reboots I hadn’t had before. CarPlay stops working occasionally. My audio track info sometimes doesn’t display on the drivers center screen when I have maps up on the drivers right-side screen, and more. It ran great for the first week or so, but since then, not so much
Click to expand...

Yeah I've had two screen restarts, 1 that completely made all screens blank an required a reset, 1 where I entered the vehicle and the left/center cockpit panel behind the steering reset and I had to wait before I could drive. Not had any of those before 2.9.0 so clearly there's some bugs. Hopefully a 2.9.3 will fix it
 
Cabonzhp said:
Fun piece of 2.9.0 (2.9.2 actually) feedback. Every time I get in the car now, the dash displays a message about adjusting seating position, implying its profile switching.

I’m the only one that drives the car, no amount of switching around profiles or resets has stopped this message from showing every single time.
Click to expand...
Do you have easy access enabled? I get the same message but only when I have easy access enabled and it's moving the seat back to my position from the easy-access position.
 
doubletwist said:
Do you have easy access enabled? I get the same message but only when I have easy access enabled and it's moving the seat back to my position from the easy-access position.
Click to expand...
I do not and never have. Also the seat never actually moves when it displays the message.

2.9.0 related, I just received a 2.9.3. The only notes are that it fixes a prior 2.9.2 issue. Strange considering they already repushed 2.9.2 to the users whose cars were bricked.
 

Attachments

  • IMG_8947.webp
    IMG_8947.webp
    168.8 KB · Views: 62
You must log in or register to reply here.
Back
Top