crwdns2933423:0crwdne2933423:0
crwdns2947577:0crwdnd2947577:0crwdne2947577:0

Touchbar flickering even when unplugged

So this MacBook Pro 15" touchbar 2019 has a faulty touchbar which flickers green and black. After opening up the MacBook and unplugging the touchbar, the flickering continues! What the !&&* is going on? Where does it even get power from? This is spooky.

crwdns2934081:0crwdne2934081:0 crwdns2934083:0crwdne2934083:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

crwdns2933313:01crwdne2933313:0

crwdns2934051:0crwdne2934051:0

Hi

From what you have told me I think the touch-bars OLED display has been damaged

The flickering that you are seeing when it’s off is due to spare electricity that hast been used yet making its way out(OLEDS are quite power efficient so it will take a while to stop after being unplugged)

EBay and AliExpress have some good replacements for a reasonable price;-)

Hopefully this answers your question

Thanks:-)

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0

crwdns2947414:01crwdne2947414:0:

I'm wary of the phrase "spare electricity that hast been used yet making its way out".

If, indeed, the touchBar screen or driver electronics are damaged, one of the two below is likely true:

1. When macOS intends for the touchBar screen to have black pixels, the driver electronics misinterprets correct control signals from macOS and drives the touchBar with white pixels for some of the refresh cycles (typically 60 Hz on MBPs of this era), resulting in flickering.

2. If the touchBar screen is damaged, correct control signals from macOS have resulted in correct electrical signals being generated by the driver electronics, but damage to the internal wiring of the touchBar screen is resulting in control signals driving pixels that were not intended to be turned on, at unintended parts of the refresh cycle.

Note: Flickering is also present on MacBookPros with touchbars that are not physically damaged. Could be a software or SMC issue, and those have some known suggested (free) fixes.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

Sam crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 0

crwdns2936753:07crwdne2936753:0 6

crwdns2936753:030crwdne2936753:0 14

crwdns2942667:0crwdne2942667:0 868