I was an apple tech for a time. With iPads that were out of warranty (basically go buy a new one or GTFO) and exhibiting a certain display issue, I would take it in the back and slam the thing on a counter at a certain angle. Worked every time for that particular problem.
why and how did that work, how hard were you slamming it, I am presuming not hard enough to break glass, but than, what would such a slam do? I am going to presume these were LCDs, and maybe the the liquid crystals would have gone too cold, and maybe by smacking, you somehow freed them or something. I would like to know more.
I had a similar thing on an old crt monitor. The screen would start to flicker badly after a while, and 8 year old me found if you banged the side, just right, it would keep working for a couple of hours.
Turns out the circuit board had some dry solders on it and when I hit it on the side where the board was, it got the connection back for a while.
First things first: if people call me they really have a problem and 9 times out of 10 it is not their fault. But, me standing next to the machine while they reproduce the problem “fixes” it about half the time.
Seems like random glitches that only last a minute or two.
I have possibly the dumbest workaround to anything in history
bindntr=CTRL,C,exec,hyprctl activewindow | rg -q "class: Wfica" && ( sleep 0.02 && hyprctl closewindow class:alacrittyclipboard ; alacritty -qq --config-file ~/.config/alacritty/alacrittyclipboard.toml --class 'alacrittyclipboard' --title 'Office 365 Desktop (SSL/TLS Secured, 256 bit)' -e sh -c 'sleep 0.03 && xclip -o | copyq copy - ; copyq clipboard | xclip -i' ) & ( sleep 0.2 && closewindow class:alacrittyclipboard )
windowrulev2 = float,class:(alacrittyclipboard)
windowrulev2 = stayfocused,class:(alacrittyclipboard)
windowrulev2 = noborder,class:(alacrittyclipboard)
windowrulev2 = noanim,class:(alacrittyclipboard)
windowrulev2 = noblur,class:(alacrittyclipboard)
windowrulev2 = opacity 0,class:(alacrittyclipboard)
windowrulev2 = maxsize 1 1,class:(alacrittyclipboard)
allow me to explain this monstrocity… the clipboard in citrix workspace is broken in a stupid way
it doesn’t update the system clipboard unless you move focus away from the window… and out of focus windows can’t update the clipboard for security reasons… this makes it so that if I hit ctrl c when citrix is open it opens a terminal window that’s tiny, invisible and steals focus that essentially forces the clipboard to work.
nonsense hack, but it works
Stopped using the PC for a week. Came back and an update came out and everything was good. Sometimes theres nothing you can do.
Lots of percussive maintenance going on around here, but one that sticks in my mind was testing some of the first 486DX PCs in 1990. One particular specimen from Compaq would only boot after hard power off by taking the lid off and tapping the CPU with a screwdriver. Worked fine after that.