Mitigating the effects of a broken (physical) screen

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I don't know how large my screen is exactly, but suppose it's 800 (rows) x 1200 (columns). Around 50 columns about 900 columns to the right from the left side are corrupted. It's not quite clear what the error is, but some colors are better represented than others.



(I do know that the corrupted pixels all seem to behave in the same way: if they are asked to show a color C, they instead show a color C'. The mapping C->C' seems to be the same for all pixels.)



I don't want to fix the computer physically. Instead I have a two-step plan:



1) Check what the error is exactly, by checking how various colors are represented (manually, of course, by necessity).



2) Once I have an idea of what colors to replace by others, do that automatically.



My question is primarily how to achieve 2 in the most 'Linux correct' way. Tips on how to do 1 are most welcome!










share|improve this question





















  • I don't think there's an easy way to do this, but with many kinds of screen damage, the damage will not be mitigatable - e.g. if all the green values of the pixels are set to 0. So it depends on the kind of damage.
    – mwfearnley
    Mar 29 at 19:20














up vote
0
down vote

favorite












I don't know how large my screen is exactly, but suppose it's 800 (rows) x 1200 (columns). Around 50 columns about 900 columns to the right from the left side are corrupted. It's not quite clear what the error is, but some colors are better represented than others.



(I do know that the corrupted pixels all seem to behave in the same way: if they are asked to show a color C, they instead show a color C'. The mapping C->C' seems to be the same for all pixels.)



I don't want to fix the computer physically. Instead I have a two-step plan:



1) Check what the error is exactly, by checking how various colors are represented (manually, of course, by necessity).



2) Once I have an idea of what colors to replace by others, do that automatically.



My question is primarily how to achieve 2 in the most 'Linux correct' way. Tips on how to do 1 are most welcome!










share|improve this question





















  • I don't think there's an easy way to do this, but with many kinds of screen damage, the damage will not be mitigatable - e.g. if all the green values of the pixels are set to 0. So it depends on the kind of damage.
    – mwfearnley
    Mar 29 at 19:20












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I don't know how large my screen is exactly, but suppose it's 800 (rows) x 1200 (columns). Around 50 columns about 900 columns to the right from the left side are corrupted. It's not quite clear what the error is, but some colors are better represented than others.



(I do know that the corrupted pixels all seem to behave in the same way: if they are asked to show a color C, they instead show a color C'. The mapping C->C' seems to be the same for all pixels.)



I don't want to fix the computer physically. Instead I have a two-step plan:



1) Check what the error is exactly, by checking how various colors are represented (manually, of course, by necessity).



2) Once I have an idea of what colors to replace by others, do that automatically.



My question is primarily how to achieve 2 in the most 'Linux correct' way. Tips on how to do 1 are most welcome!










share|improve this question













I don't know how large my screen is exactly, but suppose it's 800 (rows) x 1200 (columns). Around 50 columns about 900 columns to the right from the left side are corrupted. It's not quite clear what the error is, but some colors are better represented than others.



(I do know that the corrupted pixels all seem to behave in the same way: if they are asked to show a color C, they instead show a color C'. The mapping C->C' seems to be the same for all pixels.)



I don't want to fix the computer physically. Instead I have a two-step plan:



1) Check what the error is exactly, by checking how various colors are represented (manually, of course, by necessity).



2) Once I have an idea of what colors to replace by others, do that automatically.



My question is primarily how to achieve 2 in the most 'Linux correct' way. Tips on how to do 1 are most welcome!







16.04 xorg display screen






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 29 at 14:45









arrowturnips

1




1











  • I don't think there's an easy way to do this, but with many kinds of screen damage, the damage will not be mitigatable - e.g. if all the green values of the pixels are set to 0. So it depends on the kind of damage.
    – mwfearnley
    Mar 29 at 19:20
















  • I don't think there's an easy way to do this, but with many kinds of screen damage, the damage will not be mitigatable - e.g. if all the green values of the pixels are set to 0. So it depends on the kind of damage.
    – mwfearnley
    Mar 29 at 19:20















I don't think there's an easy way to do this, but with many kinds of screen damage, the damage will not be mitigatable - e.g. if all the green values of the pixels are set to 0. So it depends on the kind of damage.
– mwfearnley
Mar 29 at 19:20




I don't think there's an easy way to do this, but with many kinds of screen damage, the damage will not be mitigatable - e.g. if all the green values of the pixels are set to 0. So it depends on the kind of damage.
– mwfearnley
Mar 29 at 19:20















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020292%2fmitigating-the-effects-of-a-broken-physical-screen%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020292%2fmitigating-the-effects-of-a-broken-physical-screen%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491