zlacker

>>dang+yy1
> In short, it was remote bricked, by giving it commands to rotate a bit. > But luckily it automatically readjust itself to earth automatically every half year exactly for these events.

I remember when bricking something meant it was totally unrecoverable. Now it means "temporarily not working but will automatically heal".

>>burnte+AB
A device that is acting as a brick cannot receive commands and is not useful at all. That is the current status of voyager 2.

"Unbricking" will hopefully work automatically, because there is no other option. But that can also fail and there is no way to know, or influence it.

I use bricking in the definition of mobile phone tinkerers .. there are many results for unbricking btw, but I just checked and with the first result it seems that Apple now uses unbricking for activating a new device. Because technically before, it is also just a brick - but here I would agree, that it is not a appropriate term, but rather should be for somehow broken devices.

>>hutzli+zE
It’s not bricked, it’s operating autonomously for some time. They’re incredibly different modes of operation.

>>nomel+c51
After trying to optimize my laptops energy settings under linux, I once also ended up with a device that was operating low level autonomously for some time. It just would not accept commands from me, nor the power button, nor anything else. The CPU also wasn't running, but something was.

In other words it was effectivly a brick to me.

But since it was not a surface pro (I considered buying instead of that one), I could open it and disconnect the battery.

And in effect, unbricking it. Quite trivial fix sure, but nearly impossible with many modern devices, where the battery is glued in.

My point is, not every mode of operation is desired, especially if you cannot change it. Then you might as well have a brick in terms of usefulness.

>>hutzli+Ra1
No. Your laptop was not operating autonomously, by definition.

It was not making its own decisions, to achieve some goal.

>>nomel+0c1
Parts of it were. To make some checks for some hardware (as part of an automatic comand line tool). They just got into an infinite loop. Down on the hardware level.

>>belter+(OP)
Stub for arguing about what "bricked" means. These comments were originally replies to >>36941191 , but we moved them because the offtopic discussion was choking the thread.

Normally I'd have marked the entire subthread offtopic, but hutzlibu's comment deserves to be at the top, even if it does use the word "bricked" wrong.