Completely green pictures with stock camera and A-HDR

[Frankenscript]

Hi folks,

Using stock OOS (4.1.6 from last year) and the stock camera, I get a green screen instead of the picture for any picture taken with A-HDR mode, which seems to be the default and I can't get it to persistently turn off.

Anybody else seeing this, and is there a fix? I've updated to a recent version of the camera without solving it (though, if I open camera, and change to HDR instead of A-HDR, it works for a while).

PRobably time to update my OS but everything else is working...

 

[rdNNNN]

Had the same thing happening me before. Fixed it by setting the right permissions on build.prop rw-r--r-- AFAIK

 

[Frankenscript]

Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.

 

[Frankenscript]

Had the same thing happening me before. Fixed it by setting the right permissions on build.prop rw-r--r-- AFAIK

Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.

HOT DAMN!

That seems to have fixed it. No idea why, but THANKS MATE!

 

[SlaJaZz]

may i know how to fix this? what build.prop file? can someone guide me step by step on this?

 

[nvertigo67]

Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.

/system/build.prop is definitely installed with 0644. There is no conspiracy "they", who changed the shipped permissions, but it has been done by you. Most probably: build prop editor, copy build.prop with something, that doesn't honor the perms of the existing file, but unlinks and recreates the file with a umask of 666 (i.e. esexplorer) or a flashable zip manupulating build.prop. This list is far way from completeness.

BTW: you'd also check (and fix if necessary) the selinux context!

may i know how to fix this? what build.prop file? can someone guide me step by step on this?

As you can see above, many things can go wrong when messing with build.prop. As long as you don't know what you are doing, I highly recommend to enpower yourself to check and change permissions on a system file by knowledge. For now do a clean flash (including format of system), and all system files will have the shipped (and correct) permissions and sepolicy context - until you do something, that changes these.