From a former call-center phone operator, I think the 10 1-sec pushes, is just a way to make sure the customer presses the buttons long enough. In our callcenter we often had to ask customer to hold the reset button on their router for 3 seconds. When the router didn't reboot, I would send replacements, until a colleague advised me to tell customers to hold the button for 10 seconds. Apparently when you ask customers to hold the button for 3 seconds, some will actually only hold it for 1 or 2 seconds. Suddenly most customers were able to reset their routers.
Its a standard step in troubleshooting "bricked" devices, not specifically the amount of pushes but the unplug any power source and then hit the power on button to discharge power left in the system (caps)
Correct on all counts. Static discharge is a strange way for the article (and tech on the phone) to say discharging capacitors but that's what it's doing.
The problem is if you sound too smart to the customer, it's an insult to their intelligence.
Telling them "we're draining the flea power" and now the customer's freaking out they have a bug infestation and Dell has unleashed a storm of locusts upon them.
I had a Microsoft Sidewinder 2 joystick that suffered from static buildup. Shelving it for a month always fixed the issue by itself. I wonder if there were hidden tricks like this to unbrick the controller.
My ThinkPad (X280) has a much simpler way of dealing with this: There's a tiny hole in the bottom, and if you stick something sharp into it and hold for a while, the embedded controller will reboot (or was it turn off?).
It basically saved me from buying a new laptop at some point, when it completely refused to charge the battery for whatever weird reason (it would charge for a second or so, and then cut off, then the charger would restart it, new cut, etc.).
I have a dead Lenovo gaming laptop that has been sitting around for the last year. Literally just tried this. And it posted for the first time since it bricked and booted right into my drive once I plugged it back in.
I knew about discharging capacitors and tried holding the power button down and pulsing it before. But I guess this time its magic?
I bet it'll stop working again shortly, but was funny to see.
It works even for non-ThinkPads. My coworker was looking clueless at his open Asus laptop. I said the first thing I’d try is unplugging the battery and holding the power button. He still thinks I’m a wizard.
A lot of laptops reset the EC if you hold the power button long enough, so it's always worth trying. I've had to do this on my MSI gaming laptop because Linux wasn't able to set power states on the Nvidia GPU, which was magically resolved with an EC reset.
same for my X1 Carbon Gen6, except that you need to unscrew the backplate, and disconnect the battery wiring inside. and of course no need to keep pressing the power button, just hold it down long enough to discharge the capacitors.
happens about once a year; i.e. rare enough to scare me each time...
i used to have an LG screen that had to be unplugged once every year or two. it acted completely dead until unplugged.
Not limited to thinkpads by any means, this is I believe common to most laptops. On my last MSI (no removable battery), the trick was to unplug, hold down the power button for 30 seconds, maybe press the power button a couple of times. I froget what the issue it fixed was, but it wasn't totally dead. but the logic was static discharge.
That was the standard way to power up my Dell XPS as otherwise it wouldn't. Such a chore. So many stand ups missed because it would often take half an hour for it to "click" and power on.
This sounds very similar to “do the prongs on your power cable have holes in them?”
Which, of course, doesn’t matter. It just forces you to actually unplug your device and plug it back in.
This mostly sounds like a way to get the user to wait a solid minute before plugging the battery back in for capacitors to dissipate. There’s no way the number or duration of power button presses matters.
Same as it ever was. Who here is old enough to remember the four key boot combo for clearing the PRAM contents stored on the logic board in New World PPC Macintoshes?
I'm currently using an Omen that "died" because I opened and cleaned it without properly discharging and slightly buzzed a random chip, which happened to be the embedded controller that operates before the BIOS does. This is basically the reason you can use USB and do some other stuff before your laptop is actually on. The problem is that when I touched that chip I scrambled some bits that stay powered via a separate internal battery that cannot be disconnected.
At the time I did not know the secret power trick for this laptop, which is a similar way of holding the power button while inserting the charger. Instead I tried a few things and gave up because the behavior was inconsistent and frustrating. I stuffed it in a drawer and moved on with other things for a few months.
Randomly probably two months later I opened that drawer and went "oh yeah", then proceeded to kind of just get back into the same mindset of the problem and make sure I remember it correctly, since I'm too lazy to keep notes sometimes. To my rekindled frustration I pressed the power button and it came on normally - minus a BIOS battery CMOS time thing. Sure, I was happy it worked, but I now randomly think about the fucking hours of dedicated and methodical attempts at isolating hardware components that had potentially failed in vain because this piece of shit was now running some scrambled undefined behavior code on a shadow chip.
Many a computer has been saved by unplugging it and holding the power button, and then clicking it over and over again, and flicking the switch back and forth etc before plugging it back in. :)
My washing machine has a "debug mode" you can get to by turning the dial left/right a specific number of clicks. In this debug mode, you turn the dial to access different "options" which are shown by specific patterns on the lights. I did it once when my machine was having issues, then I realized that I didn't know what I was doing and used my warranty to have someone come and fix it (they had to replace the "control board").
Telling them "we're draining the flea power" and now the customer's freaking out they have a bug infestation and Dell has unleashed a storm of locusts upon them.
It basically saved me from buying a new laptop at some point, when it completely refused to charge the battery for whatever weird reason (it would charge for a second or so, and then cut off, then the charger would restart it, new cut, etc.).
I knew about discharging capacitors and tried holding the power button down and pulsing it before. But I guess this time its magic?
I bet it'll stop working again shortly, but was funny to see.
happens about once a year; i.e. rare enough to scare me each time...
i used to have an LG screen that had to be unplugged once every year or two. it acted completely dead until unplugged.
Which, of course, doesn’t matter. It just forces you to actually unplug your device and plug it back in.
This mostly sounds like a way to get the user to wait a solid minute before plugging the battery back in for capacitors to dissipate. There’s no way the number or duration of power button presses matters.
At the time I did not know the secret power trick for this laptop, which is a similar way of holding the power button while inserting the charger. Instead I tried a few things and gave up because the behavior was inconsistent and frustrating. I stuffed it in a drawer and moved on with other things for a few months.
Randomly probably two months later I opened that drawer and went "oh yeah", then proceeded to kind of just get back into the same mindset of the problem and make sure I remember it correctly, since I'm too lazy to keep notes sometimes. To my rekindled frustration I pressed the power button and it came on normally - minus a BIOS battery CMOS time thing. Sure, I was happy it worked, but I now randomly think about the fucking hours of dedicated and methodical attempts at isolating hardware components that had potentially failed in vain because this piece of shit was now running some scrambled undefined behavior code on a shadow chip.
I kind of wonder, every time, whether this is a uboot thing.
What a world we live in that our washing machines have a magic-sysreq thing going on ..