View Single Post
Old 10-02-2019, 03:13 PM   #23
DomesticExtremis
Addict
DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.DomesticExtremis ought to be getting tired of karma fortunes by now.
 
DomesticExtremis's Avatar
 
Posts: 243
Karma: 359054
Join Date: Nov 2012
Device: default
Quote:
Originally Posted by pazos View Post
I think I don't follow because you're talking about disconnecting the screen as a good diagnostic test and at the same time you said that you don't find any difference with the screen disconnected?

I'm sorry but my english is not good and this is a bidirectional problem, both Input and Output
Well I didn't explain it too well.
If disconnecting the screen has made a difference to the errors seen, we might conclude that the screen is the problem. It did not change any errors, so I inferred that the problem was with the chip, not the screen.
Really, we need one with a known broken screen to repeat the test and see for sure what happens. (i'm not planning to break my screen just for that though ).
DomesticExtremis is offline   Reply With Quote