Related
Issue: http://code.google.com/p/cyanogenmod/issues/detail?id=2298
After toying around with the automatic brightness I'm now here to share my settings ...
I use the following settings:
Light sensor filter enabled.
Window length 10 seconds.
Reset threshold 400 lux.
Sample interval to 0.5s.
Light levels use custom checked.
Screen dim level, not sure what it is for but I have it on 1 instead of 20. ((edit: I found what it is for, it's the step size the filter takes? Or not? :s))
Edit other levels...
Number of levels: 18
0 1
10 1
117 17
225 33
272 49
320 65
480 80
640 96
960 112
1280 128
1940 144
2600 160
4200 175
5800 192
6900 207
8000 223
9120 239
10240 255
Allow light decrease checked.
Decrease hysteresis to 10%.
I hope people like my light settings, if you don't please tell me why
Reasons why some settings should be altered:
Reset threshold, should be able to set to 100 and 200 lux. At the moment if you walk into light it takes the filter some time to go up, so 100 or 200 lux would trigger a reset faster. Also the sensor starts at 225 lux so why 400 as a minimum in the first place?
Window length, as for the above, if you walk into light a smaller window length would help put brightness up much quicker in combination with a smaller reset threshold.
If the above two settings could be added in CMParts/ODParts that be great as the filter would be much more responsive to short period light changes. For example if you go from outside to inside or visa versa.
And maybe it would even be a better idea to remove the whole custom light levels and add a linear function to it to go with the filter (configurable) and just have 254 steps (1-255) over 10-10240?
Adding 254 steps yourself is ... A PAIN ><
English please
guys i know there is a problem with the light sensor in desire and i have the same case with mine it this is all about it please let me know how to fix it please.
shazan said:
guys i know there is a problem with the light sensor in desire and i have the same case with mine it this is all about it please let me know how to fix it please.
Click to expand...
Click to collapse
What ROM are you using? CyanogenMod and forks of it (OpenDesire, DeFrost etc) have a custom preferences menu where you can check out the light sensor values. That is when you leave the filter off and goto edit other levels. Hold your phone in line with a TL light and it should jump to 1280.
Do you see the top most number change when light changes?
Call me crazy, but I am ><
I put the whole table into the automatic backlight custom levels: http://www.linux-box.nl/~sjoer/1to255/1to255.php
And it works really well with light changes, it should work even better if reset threshold can be lower (200 or maybe 100) as it will respond to bright light <> no light much better.
how did you did that?
without typing lol
This is insane..... so much trouble for such a simple task. Automatic Brightness. On winMO i used g-lite wich was satisfacatory. A have the desire for a month now. I searched from a similar soft and i didn't find. But i'm not gooing to try this much trouble for something that should be easy. Thank you.
Im sorry but....HOW do I apply this ?
Can this be applied to other roms?
I am using Pinky desire and would love to do this.
Phil
philje123 said:
Can this be applied to other roms?
I am using Pinky desire and would love to do this.
Phil
Click to expand...
Click to collapse
yes and for stock roms please
The screen minimum value is 10-255, so how can I set "1" to the first 2 levels?
I set 10, and I like the settings overall.
sfjuocekr said:
I hope people like my light settings, if you don't please tell me why
Click to expand...
Click to collapse
First off, "10 1" is redundant as you already cover that from 0 to 9. So 17 levels should be enough. Second, on the last line "10240 225" you probably meant "10240 255". Testing your settings with these modifications now. I find you have a lot of levels, probably can do with less to reduce flickering, but as I said, testing these first.
Can we use these settings in a Sense rom and if yes how?What file do we have to edit?
so useless guys.
setup max brightness and enjoy the brilliant screen.
it takes less battery than this tool to constantly check your ambient brightness.
Can someone please make a post about how to use this (and especially on Sense Roms)? So far it only shows us "which sensor-level should be what brightness" but it doesn't provide any information on how to apply it.
I assume CM either has an app for this installed (if so, please tell us WHICH so we can use it too) or a shell-script in background (if so, tell us WHICH) adjusting the settings.
Could anyone post a how-to use these settings?
Edit: Nvm, it's under: Cyanogen Settings.
Btw under "Edit other levels" you should only change the boxes that's under "Lower"? You shouldn't touch "Screen" and "Button"?
Trying this out, and will see how it goes. Only have 5 levels on my current setup, so this should be a lot smoother
snudel said:
so useless guys.
setup max brightness and enjoy the brilliant screen.
it takes less battery than this tool to constantly check your ambient brightness.
Click to expand...
Click to collapse
Is that true?
any more improvements?
and how can i backup this setting?
i wont to input it again when i flash a new rom :-(
sfjuocekr said:
Issue: http://code.google.com/p/cyanogenmod/issues/detail?id=2298
After toying around with the automatic brightness I'm now here to share my settings ...
I hope people like my light settings, if you don't please tell me why
Click to expand...
Click to collapse
Since the source code of Sense kernels is available now, would it be possible to write the tool for Sense ROMs too? You sure would do a lot of people a big favor
As you have noticed the SGS2 screen can be too oversaturated in colors, choosing the ''Movie'' effect in Settings-Display-Background Effect is the best setting to have natural colors.
Though I found we can still decrease saturation a little and increase brightness, some wallpapers are really dark
We have to find the files responsible for the background effect and edit them if xml...
Let's begin work
Great idea, really looking forward to this!
This is what you have to edit.
mdnie_tune_dynamic_mode
//start
0x003F,0x012c, //CS GAIN
0x003B,0x03ff, //DE SHARPNESS
0x0042,0x0020, //DE TH (MAX DIFF)
0x004d,0x0100, //pcc strength
0x00c8,0x0000, //kb R SCR
0x00c9,0x0000, //gc R
0x00ca,0xffff, //rm R
0x00cb,0xffff, //yw R
0x00cc,0x0000, //kb G
0x00cd,0xffff, //gc G
0x00ce,0x0000, //rm G
0x00cf,0xffff, //yw G
0x00d0,0x00ff, //kb B
0x00d1,0x00ff, //gc B
0x00d2,0x00ff, //rm B
0x00d3,0x00ff, //yw B
0x00D6,0x1d00, //GAMMA start
0x00D7,0x1d00,
0x00D8,0x1d00,
0x00D9,0x1d00,
0x00DA,0x1d00,
0x00DB,0x1d00,
0x00DC,0x1d00,
0x00DD,0x1d00,
0x00DE,0x1d00,
0x00DF,0x1d00,
0x00E0,0x1d00,
0x00E1,0x1d00,
0x00E2,0x1d00,
0x00E3,0x1d00,
0x00E4,0x1d00,
0x00E5,0xa40e,
0x00E6,0xa40e,
0x00E7,0xa40e,
0x00E8,0xa819,
0x00E9,0xa40a,
0x00EA,0x2200,
0x00EB,0x1c25,
0x00EC,0x1842,
0x00ED,0xFF00,
0x00D5,0x0001, //GAMMA end
//end
Click to expand...
Click to collapse
Thanks!
Now let's try to find if we can boost brightness(whites) and decrease saturation in all this mess
Ok I took some lines from the outdoor mode file and added them to the dynamic mode...could it work?
//start
0x0001,0x0002, //OVE
0x002c,0x0fff, //DNR bypass 0x003C
0x002d,0x1900, //DNR bypass 0x0a08
0x002e,0x0000, //DNR bypass 0x1010
0x002f,0x0fff, //DNR bypass 0x0400
0x003A,0x0009, //HDTR DE CS
0x0054,0x5a50, //ove
0x0028,0x0000, //Register Mask
0x003F,0x012c, //CS GAIN
0x003B,0x03ff, //DE SHARPNESS
0x0042,0x0020, //DE TH (MAX DIFF)
0x004d,0x0100, //pcc strength
0x00c8,0x0000, //kb R SCR
0x00c9,0x0000, //gc R
0x00ca,0xffff, //rm R
0x00cb,0xffff, //yw R
0x00cc,0x0000, //kb G
0x00cd,0xffff, //gc G
0x00ce,0x0000, //rm G
0x00cf,0xffff, //yw G
0x00d0,0x00ff, //kb B
0x00d1,0x00ff, //gc B
0x00d2,0x00ff, //rm B
0x00d3,0x00ff, //yw B
0x00D6,0x1d00, //GAMMA start
0x00D7,0x1d00,
0x00D8,0x1d00,
0x00D9,0x1d00,
0x00DA,0x1d00,
0x00DB,0x1d00,
0x00DC,0x1d00,
0x00DD,0x1d00,
0x00DE,0x1d00,
0x00DF,0x1d00,
0x00E0,0x1d00,
0x00E1,0x1d00,
0x00E2,0x1d00,
0x00E3,0x1d00,
0x00E4,0x1d00,
0x00E5,0xa40e,
0x00E6,0xa40e,
0x00E7,0xa40e,
0x00E8,0xa819,
0x00E9,0xa40a,
0x00EA,0x2200,
0x00EB,0x1c25,
0x00EC,0x1842,
0x00ED,0xFF00,
0x00D5,0x0001, //GAMMA end
//end
Click to expand...
Click to collapse
Oh man, I replaced the original tune_gallery_mode with the one ui_movie_mode And got rid of that horrible horrible sharpness.
Thanks everyone, I'm also gonna start editing, however it would be much better tp know what these values do (there are 2 for each row and some are not commented"
It's all for Gamma I think, it begins with gamma start and finish with gamma end.
Somebody tried to replace the dynamic tune with mine?
No, but I did replace the whole file with outdoor and the result was very very bright.
But at least we have a start.
Damn, I think I am going to spend days coming up with a color mod suited for this phone. Like standard, with less saturation (I see it's all done from gamma) and a bit more bright on the dark levels. Something inbetween sgs1 with voodoo color and standard sgs2.
so the first hexa values are keys meaning something. I think we can take the coments from all files and come up with a complete dictionary (except gamma, this one seems to be very tricky as it seems to be a range. maybe it's values for al brightess levels or steps on the gamma curve... I don't know).
The outdoor file is lacking gamma corrections, I don't think we can use it as everyday profile, does it work better under sunlight when you tried it??
This is great guys. Would love to help. Need testers?
Sent from my GT-I9100 using XDA Premium App
The trick for general saturation is in other file:
mdnie_tune_ui_dynamic_mode
0x003F,0x0fff, - this gives maximum saturation
0x003F,0x0000, - this gives no extra saturation
however the diference from standard is minimal, standard is
0x003F,0x001e, //CS GAIN 30
(cs gain means color saturation gain).
And movie actualy has more saturation, however the colors are tweaked from the main file and just gives the impresion of less saturation. The colors are shifted torwards yellow and are more uniform.
However with the saturation let's say I am now happy. I'l see how the gain thing works.
edit:
Just delete everything from "mdnie_tune_ui_dynamic_mode" and just work on the main file. For some reason it is split up into 2 files and the "UI" one overrides the main one. I hope this does not cause trouble.
hello,
also if you have oversatured colors when you watch a video, press menu -> config (parameters) -> external view and turn it off.
I'm not sure of translation because i'm french.
It's weird but I don't have this option in the video player
I am using mp4
aurelm said:
[...]
edit:
Just delete everything from "mdnie_tune_ui_dynamic_mode" and just work on the main file. For some reason it is split up into 2 files and the "UI" one overrides the main one. I hope this does not cause trouble.
Click to expand...
Click to collapse
Hi there,
I'm very interrested in your findings, correct me if I'm wrong, you get the best result doing 2things in /system/etc :
1. replace original "mdnie_tune_gallery_mode" with "mdnie_tune_ui_movie_mode"
2. delete everything from "mdnie_tune_ui_dynamic_mode" - i.e. "mdnie_tune_ui_dynamic_mode" becomes an empty file
Am I right ? I'm not really happy with the colors rendering of this i9100 beast
Looks you know what you're talking about so, would be gratefull if you could help me get the most naturel/faithfull coulors out from this display ...
Thanks !
The outdoor mode of the camera only increase the saturation or brightness too?
I hope to find the values related to both saturation and brightness, also hue need a little correction because the red colors are too heavy
After using the Galaxy Nexus for two weeks, I found the screen color of the new amoled+ is much better than the Nexus S, but still inaccuracy. I'm a part-time photographer who keen on the right Gamma, color accuracy and color temperature.
So I just finished some test with such things:
Galaxy Nexus
franco Kernel 18.5 nightly(with the ColorControl from Ezekeel)
Voodoo Screen Test app
x-rite i1 Display 2 color meter
HCFR software
The test result was not so good...
Average Gammar value is about 1.9, far from the ISO stand 2.2. So the color is just too bright (I'm not saying screen brightness).
The shadow part (0-40% gray level) of 3 color curve were almost out of trim. In another words, incaauracy color balance.
As the color unbalance. The color temperature is starting from lower than 5500K to 6500K, which the ISO stand is 6500K at any color level.
I also tested the ColorControl in franco Kernel. After the adjustments, Gammar value is still bad, but I save the (most part of) color balance & color temperature in the end.
The adjustments step by step:
Make sure you have a rom/mod with /init.d autorun function.
Bye, stock rom...
Make sure you have a kernel with ColorControl function.
Such like Ezekeel, franco...Else? I don't know.
Set the screen brightness to 50%.
It's the mesurement "baseline". But why 50%?
Because, at this point the screen has a brightness about 120 Lux--also a ISO stand. So, it's very close to our desktop LCD.
Make a new file as /etc/init.d/900colorcontrol-b50
Which could be done by Root Explorer or adb.
Inside the file, type such line:
Code:
echo "-10 0 -10" > /sys/class/misc/colorcontrol/v1_offset
echo "1820000000 1900000000 2000000000" > /sys/class/misc/colorcontrol/multiplier
I choose "182 190 200" here, because the default value was about 200. Rising will increase the risk of LED Burn-in.
And, don't forget the 7 zero!!!
Just reboot & enjoy the almost right color temperature.
It's (6500±300)K at any color level in my device. Not perfect, but much better indeed.
Done, that's all I can do for you.
Thanks so much for the mod.
I'm willing to test your new calibration for the GNex color but how can I revert back to stock in case of problem ?
So I guess we can only use this modification at 50% of brightness ? If we change to auto, how could it be ?
Sorry for being a noob here, but this is compatible with any rom/kernel right? I'm currently running on AOKP Build 25 and Popcorn kernel 7.1
Thanks,
Mosh
Hi, and thank you for offering your expertise. I'm not confident in doing the above.... Can you offer a little bit more step by step?
I've played around with root explorer which I imagine is what is necessary to change these values.you lost me at the 2nd step.....
Also, is 50% necessary?
Thanks kindly,
_______________________________
frAncO Kernel ;-P
mazubo said:
Hi, and thank you for offering your expertise. I'm not confident in doing the above.... Can you offer a little bit more step by step?
I've played around with root explorer which I imagine is what is necessary to change these values.you lost me at the 2nd step.....
Also, is 50% necessary?
Thanks kindly,
_______________________________
frAncO Kernel ;-P
Click to expand...
Click to collapse
mohitrocks said:
Sorry for being a noob here, but this is compatible with any rom/kernel right? I'm currently running on AOKP Build 25 and Popcorn kernel 7.1
Thanks,
Mosh
Click to expand...
Click to collapse
heo_con184 said:
Thanks so much for the mod.
I'm willing to test your new calibration for the GNex color but how can I revert back to stock in case of problem ?
So I guess we can only use this modification at 50% of brightness ? If we change to auto, how could it be ?
Click to expand...
Click to collapse
Step by step detail added. Thx for reading~
Thanks for the guide!
Sent from my Galaxy Nexus using XDA App
You can change all of these settings from Franco's kernel updater program directly without modifying any files.
The OP's settings appear a little warm at first but I'm liking them so far...
Sent from my Galaxy Nexus using xda premium
Can you please add this file 900colorcontrol-b50
sooooo do i make a folder in system like this?
system/etc/init.d/900colorcontrol-b50 and then add that text above or??
Instead of making that script, can we just input those numbers into the Color Control?
-10, 0, -10 for Gamma (RGB);
182, 190, 200 for Multiplier (RGB)
Right?
Thank!
your feeling about color is exactly. Gray is dirty, it's not sync at all pixels.
I hope someone changes this by kernel - easy for me control everything
After flash franco kernel it's better more but not perfect.
If this problem is not improved, i'll buy other phone that uses Superamoled PLUS replace this one . HIZzzz
These settings look green to me
Sent from my Galaxy Nexus using Tapatalk
Indeed... especially settings menu looks very greenish!
But maybe I get used to it...
Edit: Maybe a typo? '-10 0 10' looks not that bad at all ;-)
jornbjorn said:
These settings look green to me
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
phunghoang24 said:
Thank!
your feeling about color is exactly. Gray is dirty, it's not sync at all pixels.
I hope someone changes this by kernel - easy for me control everything
After flash franco kernel it's better more but not perfect.
If this problem is not improved, i'll buy other phone that uses Superamoled PLUS replace this one . HIZzzz
Click to expand...
Click to collapse
And that would do absolutely nothing
SAMOLED Plus displays are identical to the SAMOLED HD displays when it comes to colors and such.
It would be better and more easy if someone was able to do an app like this one that works for the Nexus One :
http://forum.xda-developers.com/showthread.php?t=745248
I really miss this app since I've bought my Galaxy Nexus
Thanks for the info. I had mine looking very similar but with a combination of lower brightness and higher multiplier values. Nice to have it set now without the additional risk of burn in. Thanks a ton.
screen looks greenish compared to franco's recommended value, using his instead but thanks for the write up.
kashix said:
screen looks greenish compared to franco's recommended value, using his instead but thanks for the write up.
Click to expand...
Click to collapse
must be a typo in his gamma settings -10,0,10 is ALOT better (=
Great find colors are much more accurate now
These settings are way off on my device, its too green.
Today is the very first time ever for me to root an android device and thank God it run perfectly.
Now i am using AIC kernel for V500 4.4.2 stock ROM. (http://forum.xda-developers.com/showthread.php?t=2741405)
Gamma correction in it really improved screen and picture quality. (plus 8000 antutu point increase bonus)
Before, i can barely see anything in Bloodborne trailer video. (http://www.youtube.com/watch?v=G203e1HhixY)
Since i cant post in development thread, i hope i can find answers to the followings:
Is it possible to further improve gamma in the future?
Even though currently gamma is improved, but the brightness level issue still persist. Is it hardware or software issue?
Is there any possibility for brightness level improvement in the near future (kernel) update?
All in all, i really like my G Pad and really hope for the possibility to receive screen improvement update in the near future.
uchihamonkey said:
Today is the very first time ever for me to root an android device and thank God it run perfectly.
Now i am using AIC kernel for V500 4.4.2 stock ROM. (http://forum.xda-developers.com/showthread.php?t=2741405)
Gamma correction in it really improved screen and picture quality. (plus 8000 antutu point increase bonus)
Before, i can barely see anything in Bloodborne trailer video. (http://www.youtube.com/watch?v=G203e1HhixY)
Since i cant post in development thread, i hope i can find answers to the followings:
Is it possible to further improve gamma in the future?
Even though currently gamma is improved, but the brightness level issue still persist. Is it hardware or software issue?
Is there any possibility for brightness level improvement in the near future (kernel) update?
All in all, i really like my G Pad and really hope for the possibility to receive screen improvement update in the near future.
Click to expand...
Click to collapse
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).
aicjofs said:
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).
Click to expand...
Click to collapse
Tks for the reply and also thank you very much for the kernel, it really is helping a lot!
Rather than issue, i should have worded it as G Pad having a relatively low brightness level/dim display.
Compare to my nexus 7 1st gen, G Pad at 70% brightness level still not as bright as nexus at 30%.
Actually i dont really mind it, 70-80% G Pad brightness level is my sweet spot.
However, it would be great if the number is 30% rather than 70% (i am just feeling paranoid of having big number for a display setting).
I also realized that colours (might be) a bit off, especially red that looks orange-ish.
In general display seems lean toward yellow (yellowish-white).
Wonder if this is a common thing for all unit?
Hopefully it is just a matter of colours calibration that can be solved through software update not a hardware characteristic.
I tried Screen Adjuster and added more blue and red, but i just cant seems to find the proper setting to create a whiter white or redder red...
All in all, it is nice to hear version 20d may be coming soon.
Hopefully LG will address all these screen related things.
Also, really look forward to your another great work, especially when LG get it all wrong again this time
aicjofs said:
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).
Click to expand...
Click to collapse
It would be great if you could add row scheduler when you next update your kernel.
Thanks in advance rich ?
Sent from my LG-V500 using XDA Premium HD app
uchihamonkey said:
Tks for the reply and also thank you very much for the kernel, it really is helping a lot!
Rather than issue, i should have worded it as G Pad having a relatively low brightness level/dim display.
Compare to my nexus 7 1st gen, G Pad at 70% brightness level still not as bright as nexus at 30%.
Actually i dont really mind it, 70-80% G Pad brightness level is my sweet spot.
However, it would be great if the number is 30% rather than 70% (i am just feeling paranoid of having big number for a display setting).
I also realized that colours (might be) a bit off, especially red that looks orange-ish.
In general display seems lean toward yellow (yellowish-white).
Wonder if this is a common thing for all unit?
Hopefully it is just a matter of colours calibration that can be solved through software update not a hardware characteristic.
I tried Screen Adjuster and added more blue and red, but i just cant seems to find the proper setting to create a whiter white or redder red...
All in all, it is nice to hear version 20d may be coming soon.
Hopefully LG will address all these screen related things.
Also, really look forward to your another great work, especially when LG get it all wrong again this time
Click to expand...
Click to collapse
You can use Faux Clock or System Tuner to adjust the color temp and gamma.
meanoc said:
You can use Faux Clock or System Tuner to adjust the color temp and gamma.
Click to expand...
Click to collapse
Really...?
In that Kernel thread it states....
Add Faux Display interface (gamma control seems broken)
so does the Faux app control the gamma, even though aicjofs had noted that it seemed to be broken...?
vimesUK said:
Really...?
In that Kernel thread it states....
Add Faux Display interface (gamma control seems broken)
so does the Faux app control the gamma, even though aicjofs had noted that it seemed to be broken...?
Click to expand...
Click to collapse
It works for me?
meanoc said:
You can use Faux Clock or System Tuner to adjust the color temp and gamma.
Click to expand...
Click to collapse
Pardon me but where can i find this Faux Clock and System Tuner?
Do you have any preferred setting for optimum screen (colour) performance?
uchihamonkey said:
Pardon me but where can i find this Faux Clock and System Tuner?
Do you have any preferred setting for optimum screen (colour) performance?
Click to expand...
Click to collapse
You can find them here https://play.google.com/store/apps/details?id=com.teamkang.fauxclock and https://play.google.com/store/apps/details?id=ccc71.pmw.pro . Your best bet is to either use a calibration tool or just adjust it to your eyes.
Credits to the developers of the modified GCam project. Please donate to them if possible to keep the development going.
After using it daily on my Pixel 2 XL it is now confirmed working on the Pixel 6.
There are alot of custom options to take that perfect shot available for this modified version, as time passes there will be more releases on the main page on the same site.
Enjoy!
Older version
https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/f/dl23/
Latest version
MWP: Gcam_8.4.300_beta5_MWP
Download Gcam_8.4.300_beta5_MWP by MWP.
www.celsoazevedo.com
Detailed info I found on Google for the app:
What is the lib patcher?
Libpatcher - is a custom setting where you can set all the settings to your liking
Radius Temporal changes the graininess of the image by affecting noise, the higher the image is more blurry and less noise, the lower the more noisy, but more detail
Tone Curve is where you can adjust dark points, white points, shadows, highlights. It is recommended to enable and leave the default values or tweak them (advanced users)
Sharpness allows you to control the sharpness of the image. Zoom in for low-light shots, and zoom out for selfies.
Luminance Noise Reduction is what controls the “graininess” in images caused by high ISO. Decrease it to get more detail at the expense of high noise, or increase it if the noise is unacceptable to you
Color Noise Reduction: Controls color spots. There is usually no need to adjust it as this will not improve the quality, but you can increase it slightly if you see colored spots in the dark. Too much chroma noise can cause a decrease in saturation. Also known as color noise. Be careful with this setting it can mess with the fine details of an image.
Contrast settings allow you to control the contrast of the image. Increase it if you want darker shadows, and decrease it to make it brighter is the general idea. This is again a personal preference
Saturation is what allows you to control the saturation of the image. Increase it if you want more saturated colors in your photos. Obviously decrease if your HDR is getting too saturated. This is again a personal preference
Now there are some advanced settings. These affect the morphological processing. Naturally thats a very basic overview. I took the course while finishing up my engineering degree. It was difficult stuff past the basic level. I wont get into what these settings do beyond a decent generalization.
Warning to all these settings can absolutely have a drastic negative effect on your images. A lot of testing would be necessary by the end user
Luminance noise reduction levels
Level 1 (Detail) changes the photo very slightly, slightly smoothing out small elements in the image.
Level 2 (Rough Surfaces) seriously alters the image by smoothing grain
Level 3 (Edges) doesn’t change much. Smooths edges slightly
Level 4 (Smooth Surfaces) radically alters the image by making it posterized by smoothing out large areas of the same color. Avoid magnification over 1.0
Color noise reduction levels
Level 1 (Detail) fine textures, but the same applies to rough details
Level 2 (Rough surfaces) fine textures, but the same applies to rough details
Level 3 (Edges) Edges are mainly defined by the contrast between one object and another
Level 4 (Smooth Surfaces) Smooth surfaces are generally uniform areas of the image. Like wallpaper with few small details
Tips:
If you notice a certain color of spots on your low light photos. Check its frequency spectrum. Look where its at in the photo and go to the specific wavelet reduction setting and tweak it. See if you can remove it. More often than not these settings are used to improve astrophotography, low light and high detail images.
My sensor has more higher frequency color noise than others. Ive seen some XDA users where they had to turn down denoise. It really all depends on a lot of stuff. Its fun to tweak and squeeze out what you can.
YMMV
I can do most, if not all, of this stuff in GIMP/Photoshop, more easily, with finer control (to include undo), and on a much larger screen
All most of us really want (I can't be the only one) in a "great" camera app is total control of:
1. Shutter speed
2. "ISO"
3. Aperture
4. Lens selection
just like my Galaxy S8's "pro mode"
Everything else can be "fixed" in post.
-But then I'm just an old guy with camera and a darkroom
biTToe said:
I can do most, if not all, of this stuff in GIMP/Photoshop, more easily, with finer control (to include undo), and on a much larger screen
All most of us really want (I can't be the only one) in a "great" camera app is total control of:
1. Shutter speed
2. "ISO"
3. Aperture
4. Lens selection
just like my Galaxy S8's "pro mode"
Everything else can be "fixed" in post.
-But then I'm just an old guy with camera and a darkroom
Click to expand...
Click to collapse
Yeah I totally get that, photo editing software is better on a computer and is more fine tuned.
This is an easy way to get more customized results. I've seen way too many complaints about the built in app being too restricted and plain.
This adds additional functionality and is my go to application when taking photos for years now.
legend221 said:
Credits to the developers of the modified GCam project. Please donate to them if possible to keep the development going.
After using it daily on my Pixel 2 XL it is now confirmed working on the Pixel 6.
There are alot of custom options to take that perfect shot available for this modified version, as time passes there will be more releases on the main page on the same site.
Enjoy!
MWP: Gcam_8.4.300.v1_beta3
Download Gcam_8.4.300.v1_beta3 by MWP.
www.celsoazevedo.com
Detailed info I found on Google for the app and recommended settings:
What is the lib patcher?
Libpatcher - is a custom setting where you can set all the settings to your liking
Radius Temporal changes the graininess of the image by affecting noise, the higher the image is more blurry and less noise, the lower the more noisy, but more detail
Tone Curve is where you can adjust dark points, white points, shadows, highlights. It is recommended to enable and leave the default values or tweak them (advanced users)
Sharpness allows you to control the sharpness of the image. Zoom in for low-light shots, and zoom out for selfies.
Luminance Noise Reduction is what controls the “graininess” in images caused by high ISO. Decrease it to get more detail at the expense of high noise, or increase it if the noise is unacceptable to you
Color Noise Reduction: Controls color spots. There is usually no need to adjust it as this will not improve the quality, but you can increase it slightly if you see colored spots in the dark. Too much chroma noise can cause a decrease in saturation. Also known as color noise. Be careful with this setting it can mess with the fine details of an image.
Contrast settings allow you to control the contrast of the image. Increase it if you want darker shadows, and decrease it to make it brighter is the general idea. This is again a personal preference
Saturation is what allows you to control the saturation of the image. Increase it if you want more saturated colors in your photos. Obviously decrease if your HDR is getting too saturated. This is again a personal preference
Now there are some advanced settings. These affect the morphological processing. Naturally thats a very basic overview. I took the course while finishing up my engineering degree. It was difficult stuff past the basic level. I wont get into what these settings do beyond a decent generalization.
Warning to all these settings can absolutely have a drastic negative effect on your images. A lot of testing would be necessary by the end user
Luminance noise reduction levels
Level 1 (Detail) changes the photo very slightly, slightly smoothing out small elements in the image.
Level 2 (Rough Surfaces) seriously alters the image by smoothing grain
Level 3 (Edges) doesn’t change much. Smooths edges slightly
Level 4 (Smooth Surfaces) radically alters the image by making it posterized by smoothing out large areas of the same color. Avoid magnification over 1.0
Color noise reduction levels
Level 1 (Detail) fine textures, but the same applies to rough details
Level 2 (Rough surfaces) fine textures, but the same applies to rough details
Level 3 (Edges) Edges are mainly defined by the contrast between one object and another
Level 4 (Smooth Surfaces) Smooth surfaces are generally uniform areas of the image. Like wallpaper with few small details
My Settings
Now I have done A LOT of testing on my phone, with my case (affects light angles coming in slightly) and just about everything I can to nail these in for my device and my tastes so please dont just copy and paste. This is more of an informative post.
Libpatcher Switches:
Force System Noise Model (I tweaked the tweaked one but I cant post that code (license issues)) ON
Disable Dehave ON
Sharpness: 1.13
Saturation: 1.21
Global Chroma Denoise: Set to wavelet
Global Luma Denoise: Set to wavelet
Wavelet Luma Denoise Settings:
Level 1 - 0.875
Level 2 - 0.875
Level 3 - 1.0
Level 4 - 1.125
Wavelet Chroma Low Frequency Denoise Settings: (556 THz - 792 THz) 89
Level 1 - 1.0
Level 2 -1.0
Level 3 - 1.1
Level 4 - 1.2
Wavelet Chroma High Frequency Denoise Settings: (403 THz - 555 THz) 89
Level 1 - 0.875
Level 2 - 1.0
Level 3 - 1.0
Level 4 - 1.3
Those work far better for me and ive noticed my pictures have less sports
Tips:
If you notice a certain color of spots on your low light photos. Check its frequency spectrum. Look where its at in the photo and go to the specific wavelet reduction setting and tweak it. See if you can remove it. More often than not these settings are used to improve astrophotography, low light and high detail images.
My sensor has more higher frequency color noise than others. Ive seen some XDA users where they had to turn down denoise. It really all depends on a lot of stuff. Its fun to tweak and squeeze out what you can.
YMMV
Will post occasional pics displaying some of the modded apps performance on occasion
Why didnt your wavelet settings work for me
Factors that affect settings
Your phone
When it was made
The chip itself
The silicon in your sensor
Ambient weather conditions
The image processing firmware on the Pixel Visual Core
Other properties of silicon unique and intrinsic to your device
FAQ
Why are your colors listed as frequencies?
Light is an electromagnetic phenomenon and as an RF engineer its easier for me to refer to spectra as a frequency but one could easily refer to it in wavelengths or color (but color wont be accurate as thats up to perception)
What are wavelets?
A wavelet is how we define a center frequency and some deviation. We use wavelets because a color is not just one frequency its a range see here : Spectral color - Wikipedia 10 Its also an entire subset of mathematics used by anyone who works with the spectrum (i.e RF engineers, optical engineers (fiber stuff), biomedical engineers). They are helpful because we can take the average of a color spectrum (say blues) and convolve it with the signal to find the center frequency of blue or the blues in a subset (image). It basically the magic behind the IM processing math.
Just tried a sample of my night time “light bleed” mode and its okay. It still need more tweaking but heres an example of what tweaking your denoise settings can do. The image is far better than a stand night photograph (even with some longer exposure)
Keep in mind you wont remove all the noise. In fact it sometimes takes noise to remove or smooth noise (dithering). Dithering is a process where we add a bit of noise to a data set in an attempt to constructively perturb the signals we want to convolve, isolate and amplify over the average.
Click to expand...
Click to collapse
See the problem with copying stuff off Google without knowing what your doing is that you have added all this and the cam doesn't have the majority of it so you are misleading users dude. You sure you have mentioned the correct cam version?
enerGy said:
See the problem with copying stuff off Google without knowing what your doing is that you have added all this and the cam doesn't have the majority of it so you are misleading users dude. You sure you have mentioned the correct cam version?
Click to expand...
Click to collapse
You can try it if you'd like or keep using the built in one. I've been using this version on my Pixel 6.
There are also other builds on the same site.
Honestly I don't even use the stock one that came with the phone. Not too many options or settings to adjust vs this Mod.
These guys have been doing this for years I've personally used it on my Pixel 2 XL since I can remember.
I'm very confident they have the knowledge and experience to release this Mod to the public.
legend221 said:
You can try it if you'd like or keep using the built in one. I've been using this version on my Pixel 6.
There are also other builds on the same site.
Honestly I don't even use the stock one that came with the phone. Not too many options or settings to adjust vs this Mod.
These guys have been doing this for years I've personally used it on my Pixel 2 XL since I can remember.
I'm very confident they have the knowledge and experience to release this Mod to the public.
Click to expand...
Click to collapse
What do you mean? I didn't say anything about the guy who builds it or him not having knowledge lol, I know him. You just replied with something totally different to what was questioned dude, doesn't make sense. Many of the options and values you gave are not in this cam as you can see below thus why I'm asking have you posted the correct version. Also I'm no noob as you might be suggesting lol I've plenty of experience with GCam on many many devices creating configs for personal use and for public.
enerGy said:
What do you mean? I didn't say anything about the guy who builds it or him not having knowledge lol, I know him. You just replied with something totally different to what was questioned dude, doesn't make sense. Many of the options and values you gave are not in this cam as you can see below thus why I'm asking have you posted the correct version. Also I'm no noob as you might be suggesting lol I've plenty of experience with GCam on many many devices creating configs for personal use and for public.
Click to expand...
Click to collapse
We are both Senior Members I know. I should edit the posting as the settings were taken from another source online.
Let the users try it and keep using it if they like it. Let him know he is an amazing guy and I hope he gets alot of well deserved donations.
Thank you for your work on the configs as well.
Hi, I strongly recomend last NOT BETA version of this great app, so Gcam_8.3.252_V2.0c_MWP (https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/) Gcam_8.3.252_V2.0c_MWP
novaq72 said:
Hi, I strongly recomend last NOT BETA version of this great app, so Gcam_8.3.252_V2.0c_MWP (https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/) Gcam_8.3.252_V2.0c_MWP
Click to expand...
Click to collapse
Thank you @novaq72
I tried out the last stable version and my P6 was not saving the pictures. I have been running without problems on 8.4.300 v1 beta3.
If anyone has any issue from the OP definitely try out the one above.
It's a pity, I don't have a problem with not saving pictures (P6P). But I use a gallery other than Google Photos, so maybe that's why. The stable version by MWP has a lot more settings options than the beta version, I think. But I use the MWP app mainly because of the names of the photos, which the built-in version has, politely speaking, 'awkward'.
legend221 said:
Thank you @novaq72
I tried out the last stable version and my P6 was not saving the pictures. I have been running without problems on 8.4.300 v1 beta3.
If anyone has any issue from the OP definitely try out the one above.
Click to expand...
Click to collapse
It's a pity, I don't have a problem with not saving pictures (P6P). But I use a gallery other than Google Photos, so maybe that's why. The stable version by MWP has a lot more settings options than the beta version, I think. But I use the MWP app mainly because of the names of the photos, which the built-in version has, politely speaking, 'awkward'.
Can you share the config file?
nchmaster said:
Can you share the config file?
Click to expand...
Click to collapse
I'm sorry unless it's on the official website I don't have it.
The app is working great without any additional files at the moment.
Google Camera Mod 8.4.300 v1 beta 5 by MWP
===============================
Changelog from previous version, plus:
1. Replacing Libpatcher with Rampatcher. Thanks Eszdman & Hasli.
2. Rearrange the settings menu.
3. Enable all fps selection in video mode.
4. Added Super res zoom / merge method.
5. Added max shutter speed limitation.
6. Added developer settings help.
7. And more
NOTE: All the previous configs (.xml) can't be use in this version.
MWP: Gcam_8.4.300_beta5_MWP
Download Gcam_8.4.300_beta5_MWP by MWP.
www.celsoazevedo.com
The download link on the site seems to be dead.
Fixed.
Google Camera Mod 8.4.300 beta 6 by MWP
==============================
Changelog from previous version, plus:
Minor changelog:
1. New libs ( xHDR & NoiC )
2. Optimized some code and added some parameters to libpatcher
NOTE: Clear app data & cache before use.
MWP: Gcam_8.4.300_beta6_MWP
Download Gcam_8.4.300_beta6_MWP by MWP.
www.celsoazevedo.com
Thanks for this. But the currently google camera in the store is 8.6?
Utini said:
Thanks for this. But the currently google camera in the store is 8.6?
Click to expand...
Click to collapse
Different developers use different Google Camera versions. Let's say it this way.. Latest is not always the greatest
Dayuser said:
Different developers use different Google Camera versions. Let's say it this way.. Latest is not always the greatest
Click to expand...
Click to collapse
Thanks! If i understand correctly the this does better pictures than the stock gcam? No .xml needed?
Utini said:
Thanks! If i understand correctly the this does better pictures than the stock gcam? No .xml needed?
Click to expand...
Click to collapse
It depends what you like. Every gcam versions with stock settings is little different but it is better use xml if somebody has created xml.