Database Info

[APP] Official LG Stock (& AOSP) Camera Update [DEODEXED][MULTI-VARIANT]

What's New:
"The app itself is more useful, time to focus is improved, low-light performance is better, etc. It's not perfect, but it's definitely an improvement. It seems like LG balanced things out. The video bit rate has been reduced, min fps increased, image quality increased, sharpness increased, audio bitrate increased, and more. Many of these changes are also in @Jishnu Sur's excellent mod, but with different values. Buy that guy a beer. He's been working on this camera for some time without even owning the device (and therefore without any of the benefit of the increased performance).
Included in the zip are a number of updated libs that deal with post-processing. If you use panorama, effects, etc. they may be improved with this. I don't use them much so I only verified they still work. Some of them (particularly some of the render script support libs), seem to be more for the stock Google gallery app and weren't even included in the VS98011A rom, but I figured it wouldn't hurt to include them in case the newer gallery app uses them." - xdabbeb
Instructions:
1) Do a backup in recovery, or backup the original files to be overwritten (check ZIP for names).
2) Flash.
AOSP
1) Flash.
NOTE: If these work on your variant and it's not on the list below, let us know so we can add it.
STOCK ROM
DOWNLOAD - Deodexed
DOWNLOAD - Deodexed (Mirror)
AOSP-based ROM (EXPERIMENTAL)
DOWNLOAD - v2
DOWNLOAD - v1
AOSP-based ROM Notes
The low-light FPS increase may not be in effect.
Burst is not working (but is available and may cause issues).
The intelligent auto does not work in low-lighting.
FC occurs when switching to front-camera, or using Panorama settings.
Confirmed Variants for Stock:
F320KE11
VS98011A (VZW)
D802A
D802B
LS980 (Sprint)
D800
Confirmed Variants for AOSP-based:
D802B
D803
D800 (AT&T)
LG Optimus 2x (P990)
Confirmed ROMs for Stock:
Stock rooted on all confirmed variants.
Malladus (VZW)
Grievous (D800)
Confirmed ROMs for AOSP-based (4.3):
AOSP
HeatshiverSX (AOKP)
OSE (VZW)
Carbon
PACman
PA
Slim ROM
CM10.2
Confirmed ROMs for AOSP-based (4.4):
PA
Gummy (VZW)
CM11
SlimKat
LucidPhusion
Create a Flashable ZIP Backup
1) If you would like to make a ZIP backup simply download the ZIP file for the update and make a copy.
2) Download a file explorer like ES Explorer or Root Explorer.
3) Open up the update ZIP and look at all the names of the folders, those will be mimicked in your phone's system folder.
4) Check the files within the folders of the update ZIP and note all the names, these will also be mimicked in your phone.
5) Use your file explorer and copy all the mimicked files in your phone to your SD card.
6) Connect your phone to your PC.
7) Move all your files to somewhere easily accessible.
8) Open (do not extract) the update ZIP copy with 7z or WinRAR.
9) Go into each folder (except META-INF) and copy over the files from your phone to the update ZIP copy.
10) Once you are done you now have a flashable ZIP to revert back to your previous state.
Camera NOT Showing in 4.3/4.4 Fix
If the AOSP camera is not appearing in the app drawer, first stop the camera that comes with the ROM, clear that camera's data, and then disable it. Reboot the phone and the AOSP camera should now be present. If it is not, then it is likely disabled. Re-enable it and that should get it to display.
Credits: xdabbeb, sefnap, Jishnu Sur

Not working on rooted international stock rom...now i lost my camera...can u pleasepost original camera so i can restore back rather than flashing all over again stock rom to have a working camera??

Tried this on the Sprint version. Didn't work. First time I installed the apks my phone did a boot loop twice and updated Android. Then I copied all the files into the other locations now my camera FC.
Sent from my LG-LS980 using xda app-developers app

edangel said:
Not working on rooted international stock rom...now i lost my camera...can u pleasepost original camera so i can restore back rather than flashing all over again stock rom to have a working camera??
Click to expand...
Click to collapse
Have you delete the .odex for two .apk?
Java

Thinking about trying this. I'll be smart and nandroid. I'll let you know in about 30 minutes. I'm att
Sent from my LG-D800 using Tapatalk 4

I was in the process of making some flashable additions for "my" ROM so here goes a flashable update and one to revert.
It removes and adds the necessary files.
Here's a flashable restore: http://www.adrive.com/public/bZgr7H/LGCamera_Restore.zip

If you guys want to hold off for a bit, there are still some other libraries I wanted to sort through for changes. I should be able to do so tomorrow and would be happy to provide the results for everyone if there is interest. My main intention was to get the principal files to Jishnu for his analysis.

This did work for me. I over wrote all the files and changed their permissions then deleted the odex files for the gallery and camera. The video focus is not fixed so not really worth the time IMO but thanks for sharing!!
Sent from my LG-D800 using Tapatalk 4

I'm playing with it and I've noticed no difference. I'm still getting watercolor photos.
Sent from my VS980 4G using Tapatalk

great work!thx

Looks like viewfinder now is less laggy. And at last i got the menu like in all reviews, before i had a strange Verizon moded camera without pics in menu and without Auto Flash in A.I. mode.
Anyway need to test it in low light conditions in the evening.

xdabbeb said:
If you guys want to hold off for a bit, there are still some other libraries I wanted to sort through for changes. I should be able to do so tomorrow and would be happy to provide the results for everyone if there is interest. My main intention was to get the principal files to Jishnu for his analysis.
Click to expand...
Click to collapse
Hey, just wanted to know if you have any comment on this particular post someone made in another thread regarding the camera:
ZigZagJoe said:
TL;DR: Use sports mode. If desperate, try forcing ISO to 800.
Did some more testing of the camera. Sports mode does indeed bias towards faster shutter speeds - usually seems to pick ISO 400 where normal/auto would have used a shutter speed two stops slower and ISO 100. If sports mode is not cutting it, set ISO 800 and hope. If you don't get it at ISO 800, you won't get it with the default camera app. Some third party apps (I tried FV-5) allow you to specify ISO 1600, but image quality will be even worse. Really, just get a real camera out or get into better lighting.
Something else I have to mention is if you are using the modified camera app, if the guy did indeed manage to modify the actual amplification levels, what he did will reduce performance in regards to capturing moving objects as it will force a slower shutter speed - not entirely sure that guy knows what he is monkeying with.
My personal theory on the slow focus in low light is its being caused by the camera dropping below 1/30th of a second shutter speeds in favor of getting a proper exposure to be able focus precisely. If this is the case, forcing it to underexpose to get a smooth preview and faster focus could result in it being unable to focus.
There is a workaround for that, though, and focusing on moving objects: use the manual focus feature LG was so kind to include and set it to infinity focus. As long as you are about 3 feet or more from the object being photographed, everything will be in focus and there will be no shutter lag.
Click to expand...
Click to collapse

Who is this ZigZagJoe Elite Recognized Dev?? If he thinks I'm a noob, please fix all the problems of the camera. Seems like He made the camera for the LG G2. If you did, man you are a bad engineer! !

Heatshiver said:
and provides a simple method to turn off the camera click sound.
Click to expand...
Click to collapse
Not working in my f320k. Camera ver. 4.3.1

javahuan said:
Have you delete the .odex for two .apk?
Java
Click to expand...
Click to collapse
Thanks...deleting the odex files made camera working..

@xdabbeb - I would definitely welcome any new libraries that would help! Feel free to tell me to add things to this thread, as it should be yours (I just got too excited when I saw it and tried it!).
 @KassaNovaKaine @Jishnu Sur @ZigZagJoe
The writer seems to be guessing, but this is my area of expertise so I can tell you that when you shoot a sports event you ALWAYS use a high shutter speed at a low aperture to capture every movement without showing blur yet having great lighting. So, obviously, Sports Mode is going to be "biased" towards high shutter speeds. Image quality never gets worse as ISO increases, noise increases as ISO increases, making the image look worse. As far as the slow lag theory, it is somewhat correct. The "lag" would refer to the drop in framerate, which looks like lag to our eyes. Test this by moving from a well-lit area to a poorly-lit area and you'll see the difference between 30/60fps and 15fps. Go back to a well-lit area and a second or two later the camera is back to 30/60fps again. 15fps always looks odd. Check out this video on YT, which compares 15fps to 30fps. I also shot video on my Galaxy Note II in a poorly-lit area, and while the lighting was horrible compared to my LG G2, the fps stayed at 30fps, explaining its smoothness. The focus issue seems to be greatly reliant on how it is setup in the software (I would say the way light is processed is a probable culprit). As noted by the commenter, setting to infinite focus gives a workaround for this but people should know that this can provide acceptable sharpness but have less items in focus. Exposure seems to have no consequences to image focus. I tested with -2.0, 0.0 & +2.0 values. I was able to focus without any issues. To that end, it seemed underexposure focused much faster, and slowed as exposure was increased (of course, at the sake of lighting). I am not sure if this what you wanted KassaNovaKaine, but I hope that helps.
NOTE: I also used "low aperture" to mean lower numbers. Normally, you would say small aperture for higher numbers and large aperture for small numbers.

Heatshiver said:
@xdabbeb - I would definitely welcome any new libraries that would help! Feel free to tell me to add things to this thread, as it should be yours (I just got too excited when I saw it and tried it!).
@KassaNovaKaine @Jishnu Sur @ZigZagJoe
The writer seems to be guessing, but this is my area of expertise so I can tell you that when you shoot a sports event you ALWAYS use a high shutter speed at a low aperture to capture every movement without showing blur yet having great lighting. So, obviously, Sports Mode is going to be "biased" towards high shutter speeds. Image quality never gets worse as ISO increases, noise increases as ISO increases, making the image look worse. As far as the slow lag theory, it is somewhat correct. The "lag" would refer to the drop in framerate, which looks like lag to our eyes. Test this by moving from a well-lit area to a poorly-lit area and you'll see the difference between 30/60fps and 15fps. Go back to a well-lit area and a second or two later the camera is back to 30/60fps again. 15fps always looks odd. Check out this video on YT, which compares 15fps to 30fps. I also shot video on my Galaxy Note II in a poorly-lit area, and while the lighting was horrible compared to my LG G2, the fps stayed at 30fps, explaining its smoothness. The focus issue seems to be greatly reliant on how it is setup in the software (I would say the way light is processed is a probable culprit). As noted by the commenter, setting to infinite focus gives a workaround for this but people should know that this can provide acceptable sharpness but have less items in focus. Exposure seems to have no consequences to image focus. I tested with -2.0, 0.0 & +2.0 values. I was able to focus without any issues. To that end, it seemed underexposure focused much faster, and slowed as exposure was increased (of course, at the sake of lighting). I am not sure if this what you wanted KassaNovaKaine, but I hope that helps.
NOTE: I also used "low aperture" to mean lower numbers. Normally, you would say small aperture for higher numbers and large aperture for small numbers.
Click to expand...
Click to collapse
Image quality definitely gets worse as ISO increases - saturation and fine detail take a dive off a cliff, to say nothing of noise. Fine detail loss is then compounded by overzealous noise reduction. Quality loss is more noticeable in these cameras due to the tiny sensor.
Yes, it makes sense that sports mode would increase shutter speed, but without documentation to that effect, who knows what it might do? For all I knew it could just be applying filters and/or changing WB like the other modes seem to do. Not sure what landscape mode does, even. Probably modifies saturation. Exposure settings increasing and decreasing framerate would make sense as it'd be changing exposure by decreasing/increasing shutter speed. Only time you'd have things out of focus is if they are closer than 3 feet, which is the approximate hyperfocal length for these sensor/lens combinations. One of the only blessings of such a small sensor....
Misc data, the phone is able to capture at 1/10000 of a second if conditions permit - ie. taking a picture of a light bulb. Might be able to go a bit faster; some images has the speed recorded as 1/INT_MAX. 1/6s seems to be the minimum shutter speed.
If autofocus was made a bit more "brave", ie. bigger focus steps, it could help, at the expense of focus precision. Could possibly be gotten away with as focus doesn't need to be hyper precise on these things anyways. Trade offs no matter how you go though - you either get slow, but accurate AF, faster but less accurate AF, or fast AF that can't focus (minimum FPS raised). A bandaid fix would be to have the flash LED turn on and be used as an AF-assist lamp for focusing in low light always instead of only when flash is enabled. Of course, wouldn't help when the object isn't in range, but still an improvement.

@ZigZagJoe
Unfortunately, that's not how ISO works. An ISO increase increases noise, it does not desaturate or deteriorate fine detail. Quality is also not saturation. A person who knows about and performs color correction does not saturate a photo as it will hinder quality in post. That isn't to say that is what quality is. If saturation is how you like your pictures, that's fine, but that lends to a personal definition (albeit common) of quality, not a technical definition of quality. I would imagine it is pretty hard to determine detail loss if noise is covering it up to begin with? It would have to be drastically different for that to be apparent. Maybe you are mistaking compression artifacts for noise? Quality is about bitrates, the higher the bitrate the less compression artifacts, which means the better the detail. In either case, the ISO is not making it worse. So it is either bitrate variation you are talking about, or the post-processing system of the camera. The sensor is tiny, but that doesn't mean much other than more ISO noise than a larger sensor. If it did, then a 5DMKII would look leaps and bounds better than a 7D, but it doesn't. It is a matter of hardware. I can name two phones from last year with near-identical sized sensors, but their quality is vastly different.
I am not going to go over the modes as they do have purposes, but they will take a long time to explain. If you have used any basic cameras of the last decade you should know what they do. Manufacturers rarely deviate from these modes other than by name. Besides, the best photographers use the manual mode.
Exposure value would not just affect shutter speeds but ISO settings as well (as evident through simple testing). It should also affect aperture, but cameras on phones have a fixed aperture. However, while shutter speeds are initially changed on this phone, they stay constant. ISO then varies depending on the lighting situation. I took 4 videos of 2 locations, all at 30fps, two at +2 EV, and two at -2 EV, and each set in a light and near-black (dark) area. The results were that the light +2 remained at 30fps, but showed a lot of compression artifacts from a bitrate of 13+MB/s. The dark +2 remained at 30fps, but showed a lot of noise. The light -2 changed to 24fps and showed much less compression artifacts at a bitrate of 17+MB/s. The dark -2 showed almost nothing at all, but the tiny emitting lights that were shown were smooth. These were all done with this mod and no focus issues were present.
I think the true issue with auto-focus primarily stems from IOS. This is the first 13MP to have it, so it's bound to have some kinks (hence the need for an update).
The more important issue is that people all want to complain about a camera phone. And when someone like @Jishnu Sur wants to help out, people insert the comments with false or half-truth information that others take as fact. Some could argue that there is no harm if just speculating, but smarter people know better. The bottom line is that the camera is great as it is. If you want a better AF, get a real camera. But those who get a real camera, and know how to use them, already know that manual focus is the way to go.
I hope this helps clear some things up, but any further comments should be left to PM or back on the thread where this actually started as I want this to be for the updated camera. Continuing this discussion is in part the fault of @KassaNovaKaine for bringing this up instead of just using a PM, and mine for wanting to correct it.
Been testing this update, and it is a vast improvement!

I had a chance so sift through the updated libs, etc., and have made a flashable zip with all the updated files.
This probably should have its own thread, but it doesn't make sense to create more clutter. @Heatshiver, if you don't mind, could you please update the title stating that this is the F320K11E Stock Camera + libs and remove the original download (as it was incomplete) to avoid any confusion. Actually, it would probably be a good idea to quote all of this as well so people don't have to read/search through the whole thread. I don't mind that you started it, as long as you field all the support questions
I have tested this on my VS98011A and it is a marked improvement over the original. All of my comments are in relation to that version of the software/camera.
What's new:
The app itself is more useful, time to focus is improved, low-light performance is better, etc. It's not perfect, but it's definitely an improvement. It seems like LG balanced things out. The video bit rate has been reduced, min fps increased, image quality increased, sharpness increased, audio bitrate increased, and more. Many of these changes are also in @Jishnu Sur's excellent mod, but with different values. Buy that guy a beer. He's been working on this camera for some time without even owning the device (and therefore without any of the benefit of the increased performance).
Included in the zip are a number of updated libs that deal with post-processing. If you use panorama, effects, etc. they may be improved with this. I don't use them much so I only verified they still work. Some of them (particularly some of the render script support libs), seem to be more for the stock Google gallery app and weren't even included in the VS98011A rom, but I figured it wouldn't hurt to include them in case the newer gallery app uses them.
Instructions:
1) Do a nandroid, or see which files are being updated and manually back them up.
2) See #1. If you mess something up you'll wish you had.
3) Flash away. I tested this with TWRP on a VS98011A and it works perfectly.
4) If you have another variant, let us know here whether or not it works.
F320K11E Camera Update
*I will also send the files along to Jishnu separately for inclusion/analysis in his mod.

So, loss of detail. For an example, have a look at this comparison. Less severe in larger sensors (IE. DSLRs) and more severe in smaller sensors, you know, what phones use. To what degree detail is lost depends on the severity of processing. Noise obscuring detail = detail loss. NR processing smoothing the image = more detail loss. Safe to say, higher ISO, more detail lost.
Saturation - essentially, color purity. I'm not referring to manipulation of saturation. A washed out image lacks saturation. Yes, it is moronic to equate saturation = quality. But, my personal preference doesn't enter into this at all. Is color information lost in an ISO 3200 image when compared an ISO 100 image? Yes. To what degree depends on the sensor and processing performed. Most dedicated cameras keep it fairly well in check, but phones tend to have serious issues with saturation at higher ISOs (also, Foveon sensors).
It does depend on the sensor pedigree, though - for instance, nikon's midrange APS-C sensors handle their noise a lot better than canon's 18mp-based offerings. So for phones to have different image quality is not unexpected.
Uh, JPG artifacting is way different than noise, and we were not even talking about compression in the first place?
Modes - don't care what the other ones are for, I was simply mentioning their presence. Don't ever use them on my real camera, but don't exactly have a choice in regards to phone. I was unable to get any sort of significant difference out of sports mode when I first tried it.... rest of the modes seem to be purely post processing related, for all I know LG made sports mode the same way. Later, checking EXIF info, I did see it changing shutter speed and ISO, favoring faster shutter speeds, which is the expected behavior, it's just not got much leeway for adjustment.
If ISO isn't already maxed (you know, like it is in low-light situations), yes, exposure control could be adjusting ISO too. But in the context of preview in low light, the exposure control directly affects the preview FPS, so it can only be adjusting shutter speed as ISO is already maxed. Would expect a similar effect on video but haven't tested it. Autofocus speed is directly linked to preview FPS, which is in turn limited by shutter speed (currently).

[APPS] Google's Cameras Ports [2 VERSIONS][HDR+][PORTRAIT MODE][DISCONTINUED]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Camera Mods​
Hi everyone. Finally i'm happy to say that i've successfully fixed/ported/changed 3 different version of Gcam that are fully working for our device! This versions are based on @miniuser123 , @Arnova8G2 and @oganyan-arthur .
First of all i'm not a developer i'm just a student of electronic engeneering that enjoys taking pics and that enjoys much more Google's Camera than Samsung's one!
I struggled a lot to make those apk working (that is == to waste time instead of studying for my courses ) beacuse i've never been into this field so don't expect anything more from me.
How to Install
Steps:
- Uninstall your current version of Gcam
- From smart manager clean up the memory (YES, sometimes it's needed beacuse after i tried a lots of different verisons of Gcams i messed up something more then the app cache itself)
- Install the app
- After the first setup close (or better force close) the app to apply all the settings
- Done!
V8.3b Base
Stability: Medium
v0 Features:
- User friendly version with remade settings menu and some stability improvements
https://drive.google.com/open?id=1KxDUQsYJkfttKlvLDU4HAC5ciHKBPGkl | Mirror
Stability: Good
v1 Features:
- Some extra setting (RAW funcitons, Lens Blur Nexus 6 HDR config)
- Completely changed settings menu with new icons
-Change descriptions and added some to have a better understanding of the menu settings (No-ZSL means that value wouldn't apply if you are on ZSL mode)
-Set to best configuration for our device (If you need to take photo with moving objects change Auto-exposure mode) to something faster
-Removed some dependencies from google for less ram consumption
-Some stability improvements
https://drive.google.com/open?id=1qBSYDJeWCmDAvcgLByy6B3t-rfVB1dSm | Mirror
Stability: Good
v2 Features:
- Merged all the v8.2b extra featuers so i removed it (Hope no more people will ask what is the best verison :angel: )
-Removed some slow shutter option that where unstable but there are new ISO options now
-Now Lens blur and portrait are usable both (not need to deactivate one or another)
-Added toggles for snapdragon users that had pink portrait problems and to fix white level
Clean install is a MUST. After the first boot of the app make sure you force close and re-open it
https://drive.google.com/open?id=13Uyifaqd4XvltCYj-H-TFVOfk5usEdp2 | Mirror
Stability: Good
v2.6 Features:
- Removed the time max exp stuff
-Added Slow shutter x2, x4 (x8 wasn't stable at all) and also the ISO are still there
-removed some unstabled option (lens blur 12mp option still cant sermove the 60 fps in video option so it wont work)
-fixed the higher exposure
-as always i set best settings to deafult based on what people report me
-disable hexagon like @cstark27 suggested the interface could be more smooth
Clean install is a MUST. After the first boot of the app make sure you force close and re-open it
https://drive.google.com/open?id=16wzZIEx3_zJ7wPxgJgksEo-iRz-AQoB8 | Mirror
Stability: Good
v2.8 Features:
-fixed slow shutter (let me know)
-added x8 again seems a bit more stable now. But still sometimes you get into blackscreen
Clean install is a MUST. After the first boot of the app make sure you force close and re-open it
https://drive.google.com/open?id=1FDdektLylUNz6azqUghTLas3M-FbmG_9 | Mirror
Stability: Good
v2.9.2 Features:
-Added 12.6 MP Lens Blur
-Changed some noise reduction code that could increase the definition of the photos
-Changed allocated mem to test if it's a little bit faster the processing
-Added italian language (and soon probably spanish and french)
-Rearranged a bit the menu the have to most used stuff on the very first settings menu
https://drive.google.com/open?id=1Qu_90fKH5_EiDM8v6nzCl2ATfEMPtFpa | Mirror
Stability: Good
3.1 Features:
- Added "wavegenerator" lib that allow higer ISO values
-Changed allocated mem again so that the app should not allocate unneeded RAM
-Added languages ES,FR, PT-Brasil,RU (thanks to @jujusito @Sergey @corentin @samoel and all who helped for translation)
-Rearranged a bit the menu the have to most used stuff on the very first settings menu
-Added bitrate settings for video(still 60 fps don't work) you can go up to 100 Mbps
-Other minor changes
I aimed to do a no config apk for exynos s8. That means that now you don't have to restart or forceclose the app after the clean install to set the settings. Everything should be ok now the only issue i found is that sometimes, after the first install only, beacuse i forced the camera selector to choose Pixel 2017 HDR, the app may crash but just after the first install and in no other situation.
https://drive.google.com/open?id=17lqzEVmhVdZllSQG56GBJBpnjV62Jw5Y | Mirror
Stability: Good
3.1.2 Features:
-enabled by default "temporal binning". Can improve processing time
-fixed the exposure of HDR+ enhaced mode on front camera for s7 users
-changed the Very High HDR config. Now will take a fixed burst of 20/24 (Pixel 2017/Nexus 6) processing time is longer but we can try to compare the result with (8/10 burst). As always you MUST restart the app to apply those settings!!
https://drive.google.com/open?id=1qGNVtTXgc1dGE-eoA9tmQAwvhTgysgVW | Mirror
Stability: Good
3.2 Features:
- Now you can select the path where to save the photos (doesn't work on sd card but probably can work with some xposed mod. I've tried to make it work with a magisk module and it works but the preview in gallery is broken).
- Removed all the snapdragon toggles. The app will know when apply that settings (if i forgot some devices just PM me with your device CODENAME and i'll add it or tell me what are the config. you use for your device)
- Removed custom denoise param and other settings
-Now the app will restart every time you go back from settings to the viewfinder. This means that you don't need anymore to restart the app to apply settings
-Now there are three gestures in the viewfinder:
1. double tap on the black area it will pop the exposure menu directly
2. long-press on gallery and it will open samsung gallery instead of google photos
3. long press on the switch camera and after the restart the viewfinder brightness will be set to maximum
- some minor changes and dark theme now as default theme
https://drive.google.com/open?id=1mblLEviff-PXvAhM5NcDSSFkwFjancb0 | Mirror
Stability: Good
3.2.7 Features:
-Fixed black level front,back camera for Samsung Galaxy A devices
-Enabled ois by default (for me works anyway) for s7 users
-Added saturation options in Advanced hdr+ settings
https://drive.google.com/open?id=168iA9cSe-UKCOIu2e2JxA_djdgPZOd7w | Mirror
Stability: Good
V8.3b Base Update
3.2.9 Features:
-Fixed black level back camera for Samsung Galaxy A8/A8+
-Fixed OIS
https://drive.google.com/open?id=1NDLxsUejxYimRyBpaDlzMA3FyKA6nbLq | Mirror
Pixe2Mod Base
Stability: Good
v6 Features:
- Fixed and working potrait mode (I may have broken it for SD variant)
https://drive.google.com/open?id=1z0cGbvZ2GoaSpPxAzPkHoxcycSfhyhEG | Mirror
Stability: Good
v 7 Features:
- Fixed black screen for some exynos devices
- Removed slowmo
- Flash is still not working for some reason. I need more time to look into this.
https://drive.google.com/open?id=1Zss2E-2r98HYzRzuaG61dzXEyXV-ip_g | Mirror
AR Stickers for Oreo
Steps:
- Install AR Core first https://play.google.com/store/apps/details?id=com.google.ar.core&hl=it
- If you can't download from playstore download from here https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-1-180312068-release/
- Then AR Stickers https://drive.google.com/open?id=1kP98vuJR9bPdecBOzVeWPLNsgQb5YwjF
- Force close Gcam and re-open it!
- Done!
FAQ - Frequently Asked Questions
Q: Why the app is not installing?
A: Make sure you uninstall first the previous version
Q: Why i'm getting "parsing error" or errors when i try to install the apk?
A: Download the apk with the browser and NOT with the Drive app or use mirror links.
Q: Why i have still pink potrait mode?
A: Follow the Install instructions.
Q: Why slow-motion/ 60fps (or whatever you want)
A: Because i don't see the point of doing videos with Google Camera Ports beacuse Samsung camera it's doing a good job on that.
This doesn't mean i wont fix them either.
Q: On the device XYZ the app is not working.
A: I only support S8/S8+. I know on other Exynos devices it works (N8,S7,S6) so maybe i can take a look for them. If you ask for everything else i will just ignore your report.
Telegram Group
https://t.me/joinchat/CaDORE32mqEN45EflrK7rA
Donations
If you are cool and you want support me for this work you can donate with the "Donate" button or https://paypal.me/IDAN1109.

A little bit of boring theory
Introduction
Everyone in this thread is asking for what are the best options? The short answer is default. The long answer is it depends. To get the best results out of this mod you need to understand what all the options are and how they work. It is more similar to a professional camera where you have all the strange options to play with and you don't know what they do. You start changing all the values and then when you take a picture you are like "wut is this i took a picture of this beautiful panorama and it looks like a Picasso painting". To avoid that situation keep reading this post so you can understand what i'm talking about.
The basics
First of all before taking any picture you need to clean the lenses you are going to use. This seems to be trivial for someone but this are the results if you don't do it.
Clean vs. Dirty
The settings
Here you can find the explaination of what the settings do and how they work. I will add more in the future. If you don't know what shutter speed is or ISO google is your friend.
-Config. HDR+ camera
Nexus 6 HDR+ Auto: more dynamic range and quality (less noise). You can set all the Auto-Exposure modes but as downside you have the shutter lag so you should be careful to find the right time to shoot a photo with moving objects.
-Pixel 2017 ZSL HDR+: (ZSL = zero shutter lag HDR+)
Less dynamic range, and more noise in low light because slow shutter mode is NOT available. However it is much better in good/medium light if you make photos of moving objects, because it processes images already taken in the background. In low light, or high contrast scenes please use Enhanced HDR+
-HDR+ parameters:
It is recommend using one of the Pixel 2017 options, because they should be more stable regarding memory leak.
"High", "Very high" and even "Default" leak memory if pixel 2017 config is used.
Description for "HDR+ parameters": for example 8/10 burst means that HDR+ operates with 8 shot bursts. Portrait mode (ZSL) operates with 10 shot bursts at most. In my personal opinion Low or Very Low HDR+ are very similiar or equal to High or Pixel values but people prefer higher values for reasons uknown.
-HDR+ Auto-Exposure mode No-ZSL:
Everything that is No-ZSL means that will not work if "Pixel 2017 ZSL HDR+" is set for the back camera!
If you want to use custom Auto-Exposure and HDR+ for front camera you have to disable "Portrait ZSL mode".
"Slow shutter" will decrease shutter speed as much as possible in bad light. The result: much lower ISO and noise. Of course fast moving objects will probably get blurry more easily.
Slow shutter x8 is not stable for front camera but you can use x4 or x2. The max exposure time is 1/3 for the slow shutter x4.Sometimes you can get in trouble with x4 if you take a picture then you look at the gallery (black screen). But you wont have any problems if you take multiple pictures and then switch to x2 and look ad the gallery.
Selecting "Stock camera2 api" will get rid of rainbow effect, but dynamic range is poor, because camera can't underexpose fast enough if auto shutter control is on.
-Antibanding modes
Anti-banding allows the camera to avoid problems caused by artificial light sources that are not constant (flicker for want of a better description) these are typically florescent tubes but also multiplexed bulbs and PWM controlled LED’s (and your TV screen for similar, if not quite the same reasons) These sources cycle (flicker) fast enough to go unnoticed to the human eye, appearing continuous, they key word here being human. The camera’s eye (its sensor) can still see this flicker.
Only select 50hz or 60hz (dependig on where you live) in case of banding problems, because it can cause suboptimal shutter speed otherwise! Works up to 1/149 sec shutter speed.
-Denoise strength for HDR+ and portrait
Self explanatory. It will increase the denoise strenght for higer values.
For front cam you need to select about 2-300% to really see the difference. Back cam is much more sensitive to this setting.
-Underexposure multiplier (HDR+ dynamic range control)
Reduce below 100% to decrease rainbow effect. Should also overexpose if set to 0 with a good light source. Higher values means lower exposure.
-Samsung specific metering modes
Touch to expose is enabled by default. So won't have the touch to focus option. With "Centered" mode it will focus what it is in the center and then you can adjust the exposure by touching the area! This is a good option beacuse if you want to get the best results from HDR+ you'll need to adjust the exposure only and not the focused object at the same time.
-Samsung Live HDR mode:
Adds some dynamic range to modes where HDR+ is not available like zero shutter Portrait mode. No Rainbow effect in HDR+ mode if this is selected, but noise is encreased if isn't used in place where you don't have a good light source!
-Custom White Balance:
You can lower greens, or whatever colour you want (This would affect HDR+ ONLY). Adjust it accordingly to your taste!
Below some good photo shared on telegram group some of them can have some post-production
https://ibb.co/bGBhW7
https://ibb.co/gQurPS
https://ibb.co/gczrPS
https://ibb.co/nneQjS

What is the difference of the version 8.3 beta published by miniuser123 with the one published here?

Pixel ZSL mode now works on s8 now in this model.
If u can eliminate the processing time in s8 oreo, it would be great. Earlier in nougart it took much much less time to process afterwards. But since oreo it takes abt 10 second to process the photo after clicking.
Also if u can get slow shutter x4 and x8 working properly in low light.
Anyway thanks for your time.

Which are you recommended for HDR and portrait?

How can i enable RAW on the mod8.3b Variant ? Thanks for your hard work!

Can u add mirror selfie also.

cogelindo said:
What is the difference of the version 8.3 beta published by miniuser123 with the one published here?
Click to expand...
Click to collapse
It's written if you look at the description in features. I remade the menu and set the standard working config for s8 so no config are needed. Also i remove some debugging code
gtrs36 said:
Which are you recommended for HDR and portrait?
Click to expand...
Click to collapse
Idk try yourself i like the pixel 2 HDR+ but HDR+ of 6p looks sharper. i would say 8.2 or 8.3b but also pixel2mod is much more stable
lucccas942 said:
How can i enable RAW on the mod8.3b Variant ? Thanks for your hard work!
Click to expand...
Click to collapse
Maybe i can add it i need to look for it

@IDan1109 Thanks man.

raj.ayush78 said:
Pixel ZSL mode now works on s8 now in this model.
If u can eliminate the processing time in s8 oreo, it would be great. Earlier in nougart it took much much less time to process afterwards. But since oreo it takes abt 10 second to process the photo after clicking.
Also if u can get slow shutter x4 and x8 working properly in low light.
Anyway thanks for your time.
Click to expand...
Click to collapse
I think slow shutter x2 forces shutter speed to 1/4 so it makes it slower when shooting it also makes the camera driver default sometimes crashes because it is not auto sensor, especially if backlight conditions are very difficult to force into a speed of 1/4 so sometimes do not want to take pictures .. btw if you want slow shutter x4 and x8 work in lowlight try to increase underexposer to 200. coz underexposer value gives the signal a dark light condition, the higher the darker the camera is to run the slow speed for the shutter to brighten the photo.

If any one dont mind then i can ask something?
What is ZSL?

Din-Ace said:
If any one dont mind then i can ask something?
What is ZSL?
Click to expand...
Click to collapse
Zero Shutter Lag
Basically it takes photos very quickly.

S4turno said:
Zero Shutter Lag
Basically it takes photos very quickly.
Click to expand...
Click to collapse
Thanks bro

What is time max and time 1/2 max comparing with slow shutter?
Other word what settings are adequate to slow shutter (2x, 4x, 8x) in @miniuser123 version?
It's v8.2 about.

Din-Ace said:
If any one dont mind then i can ask something?
What is ZSL?
Click to expand...
Click to collapse
Zero Shutter Lag
In this mode the camera app takes photos continuously, even before pressing the shutter, so when you press the shutter, it just processes and saves the pictures that were already taken.

great, will try when upgrade to O from Nou on FE ^^ thanks in advance!

I have the gcam v7...what the diference between v7 and pixel2mod??

IDan1109 said:
[
Pixe2Mod Base
Stability: Good
Features:
- Fixed and working potrait mode (I may have broken it for SD variant)
https://drive.google.com/open?id=1z0cGbvZ2GoaSpPxAzPkHoxcycSfhyhEG
​
Click to expand...
Click to collapse
Can you please stop worrying about snapdragon? They have so many apks working for them.​

Currently using Arnova8G2's Pixel3Mod v1 with great stability and image quality on a G950U. The only issue is the app crashes when switching to 4K video for either rear or front camera and no ZSL feature. Everything else works including Slow Motion and AR stickers.

Asmodean27 said:
Currently using Arnova8G2's Pixel3Mod v1 with great stability and image quality on a G950U. The only issue is the app crashes when switching to 4K video for either rear or front camera and no ZSL feature. Everything else works including Slow Motion and AR stickers.
Click to expand...
Click to collapse
This is exynos thread. Go to your chip thread.

[DISCUSSION] Google Camera dot pattern

Hi, i was wondering about the origin of "dot pattern" noticeable in orange/yellow/blue objects photographed by google camera.
I found out that this does not occur on front camera. With Camera2test i noticed that there is a Camera2 API key "android.sensor.availableTestPatternModes".
His value is "0,1,2,4" for back camera and "0,1,2,3" for front camera. Is there a way to modify this key (with a Magisk module or within the apk) to see if this could be causing this "dot pattern"?
I ask the developers if it's possible to verify this thing.
In this occasion i would like to thank @cstark27 @SerJo87 @Arnova8G2 for their great work.

@sipollo, This setting is not used on GCam, this bug is a problem with RAW mode and dual cameras.
Google has to add in its api2 a fix to solve this bug, only the manufacturer could add this code.
Source camera2 api
Code:
CAM_FORMAT_BAYER_QCOM_RAW_10BPP_GBRG, <---- Used on all API2 but with dots for dual cameras
CAM_FORMAT_BAYER_QCOM_RAW_10BPP_GRBG,
CAM_FORMAT_BAYER_QCOM_RAW_10BPP_RGGB,
CAM_FORMAT_BAYER_QCOM_RAW_10BPP_BGGR,
/* Ideal raw formats where image data has gone through black
* correction, lens rolloff, demux/channel gain, bad pixel
* correction, and ABF.
* Ideal raw formats could output any of QCOM_RAW and MIPI_RAW
* formats, plus plain8 8bbp, plain16 800, plain16 10bpp, and
* plain 16 12bpp */
CAM_FORMAT_BAYER_IDEAL_RAW_QCOM_10BPP_GBRG, <--------Works without dots
CAM_FORMAT_BAYER_IDEAL_RAW_QCOM_10BPP_GRBG, <--------Works without dots
CAM_FORMAT_BAYER_IDEAL_RAW_QCOM_10BPP_RGGB, <--------Works without dots
CAM_FORMAT_BAYER_IDEAL_RAW_QCOM_10BPP_BGGR, <--------Works without dots

@Arnova8G2 There is no way to edit camera.msm8953.so?

Arnova8G2 said:
@sipollo, This setting is not used on GCam, this bug is a problem with RAW mode and dual cameras.
Google has to add in its api2 a fix to solve this bug, only the manufacturer could add this code.
Source camera2 api
Code:
CAM_FORMAT_BAYER_QCOM_RAW_10BPP_GBRG, <---- Used on all API2 but with dots for dual cameras
CAM_FORMAT_BAYER_QCOM_RAW_10BPP_GRBG,
CAM_FORMAT_BAYER_QCOM_RAW_10BPP_RGGB,
CAM_FORMAT_BAYER_QCOM_RAW_10BPP_BGGR,
/* Ideal raw formats where image data has gone through black
* correction, lens rolloff, demux/channel gain, bad pixel
* correction, and ABF.
* Ideal raw formats could output any of QCOM_RAW and MIPI_RAW
* formats, plus plain8 8bbp, plain16 800, plain16 10bpp, and
* plain 16 12bpp */
CAM_FORMAT_BAYER_IDEAL_RAW_QCOM_10BPP_GBRG, <--------Works without dots
CAM_FORMAT_BAYER_IDEAL_RAW_QCOM_10BPP_GRBG, <--------Works without dots
CAM_FORMAT_BAYER_IDEAL_RAW_QCOM_10BPP_RGGB, <--------Works without dots
CAM_FORMAT_BAYER_IDEAL_RAW_QCOM_10BPP_BGGR, <--------Works without dots
Click to expand...
Click to collapse
Do you know if something changed in Android 9?

Hello,
This bug seems to only occur with HDR+ for me, and not for HDR+ Enchanced. Is it the case for you too?
Or is it random and I was just lucky in HDR+ Enchanced?

Kanazord said:
Hello,
This bug seems to only occur with HDR+ for me, and not for HDR+ Enchanced. Is it the case for you too?
Or is it random and I was just lucky in HDR+ Enchanced?
Click to expand...
Click to collapse
Try to take a photo of bright yellow object with uniform color, I'm quite sure that you will see dots in both HDR modes.

_mysiak_ said:
Try to take a photo of bright yellow object with uniform color, I'm quite sure that you will see dots in both HDR modes.
Click to expand...
Click to collapse
Ah yes true, I have just tested again with a very bright sky and it did it in both this time! (just had the phone since yesterday, and I noticed this dots thing only on a few shots taken in standard HDR+)

Any solution?

I noticed this and it happens only with v6 mods. v5 mods are not facing this issue.

kachimasu said:
I noticed this and it happens only with v6 mods. v5 mods are not facing this issue.
Click to expand...
Click to collapse
It happens with all Gcams with hdr+ and hdr+ enhanced.
The only way to reduce them is playing with noise reduction. In several versions there is a menu called "tuning back cam". If you set "custom chroma denoise" to higher values you won't (almost) have dots but quality will be reduced a bit.

sipollo said:
It happens with all Gcams with hdr+ and hdr+ enhanced.
The only way to reduce them is playing with noise reduction. In several versions there is a menu called "tuning back cam". If you set "custom chroma denoise" to higher values you won't (almost) have dots but quality will be reduced a bit.
Click to expand...
Click to collapse
Actually you're right.

How to fix mi A1 (code name =Tissot) front camera Colortint and grainy photos in all gcam 6.1 version

So the only fix is to turn off HDR+ before you take a picture...

sipollo said:
Hi, i was wondering about the origin of "dot pattern" noticeable in orange/yellow/blue objects photographed by google camera.
I found out that this does not occur on front camera. With Camera2test i noticed that there is a Camera2 API key "android.sensor.availableTestPatternModes".
His value is "0,1,2,4" for back camera and "0,1,2,3" for front camera. Is there a way to modify this key (with a Magisk module or within the apk) to see if this could be causing this "dot pattern"?
I ask the developers if it's possible to verify this thing.
In this occasion i would like to thank @cstark27 @SerJo87 @Arnova8G2 for their great work.
Click to expand...
Click to collapse
ive just been testing many almost all Gcam moders mods from arnova to stark etc and all those mods - on arnova less - have teh same issue white on orange or dark on blue pictures dots, ive just bought motorola g7 and ive been searching internet and this is not phone issue just a freaking mods, this ia a joke imho so many amrtphones with same isssues on all gcam mods, i understand none will fix this?
---------- Post added at 11:18 PM ---------- Previous post was at 11:15 PM ----------
sipollo said:
It happens with all Gcams with hdr+ and hdr+ enhanced.
The only way to reduce them is playing with noise reduction. In several versions there is a menu called "tuning back cam". If you set "custom chroma denoise" to higher values you won't (almost) have dots but quality will be reduced a bit.
Click to expand...
Click to collapse
i did that and no change at all

crazy4jack said:
ive just been testing many almost all Gcam moders mods from arnova to stark etc and all those mods - on arnova less - have teh same issue white on orange or dark on blue pictures dots, ive just bought motorola g7 and ive been searching internet and this is not phone issue just a freaking mods, this ia a joke imho so many amrtphones with same isssues on all gcam mods, i understand none will fix this?
Click to expand...
Click to collapse
The root cause of this dots is a bad camera 2 api implementation by the OEM. The only fix would be that someone modify the required library for your phone adding support for standard camera2 api RAW format. Playing with libpatcher settings on Gcams would only reduce them a bit.

sipollo said:
The root cause of this dots is a bad camera 2 api implementation by the OEM. The only fix would be that someone modify the required library for your phone adding support for standard camera2 api RAW format. Playing with libpatcher settings on Gcams would only reduce them a bit.
Click to expand...
Click to collapse
i m testing 3 different mods gcams and what i see for now i have dots on hdr+ mode and flash, or sometimes only on hdr+ only mode, on yellow orange white surface, i have thoise dots to on sky photos to, for now the best gcam mod is for me (has less dots or very blurry dots) GCam_5.200604.2138build-7.3.021

sipollo said:
The root cause of this dots is a bad camera 2 api implementation by the OEM. The only fix would be that someone modify the required library for your phone adding support for standard camera2 api RAW format. Playing with libpatcher settings on Gcams would only reduce them a bit.
Click to expand...
Click to collapse
so what i understand, oryginal gcam on for example pixel xl dont have this issue? only gcam mods?

Google-Camera 7.3 for Redmi Note 7 Pro

NOTICE TO ALL USERS: This thread has been discarded as it has already fulfilled its purpose and therefore is now no longer needed.
Please follow the NEW THREAD!
The saga continues

https://www.celsoazevedo.com/files/android/google-camera/f/changelog373/
Works perfect on my chinese phone, except slow motion.

Klaus69 said:
https://www.celsoazevedo.com/files/android/google-camera/f/changelog373/
Works perfect on my chinese phone, except slow motion.
Click to expand...
Click to collapse
Thanks for the help! I tried this build but it's still very unresponsive. Not sure how exactly it works for you and yet somehow it doesn't work for me. Given that we both have the same Chinese version it doesn't make any sense. However I tried the latest build available from this developer (MGC_6_1_021_xcam6_beta2.apk) and it works very very well! I would even say it's close to perfect. It's just the slow motion which doesn't work at the moment.
It seems the GCam builds maintained by xtrme are the only ones which work with the Chinese version of the RN7Pro. Although these builds are aimed at MI 9, they work for the RN7Pro as well since both of them have the exact same camera sensor.
P.S. Any particular camera settings you are using with GCam? Did you import the XML config file?

[Deleted]

vlachorumsapiens said:
Thanks for the help! I tried this build but it's still very unresponsive. Not sure how exactly it works for you and yet somehow it doesn't work for me. Given that we both have the same Chinese version it doesn't make any sense. However I tried the latest build available from this developer (MGC_6_1_021_xcam6_beta2.apk) and it works very very well! I would even say it's close to perfect. It's just the slow motion which doesn't work at the moment.
It seems the GCam builds maintained by xtrme are the only ones which work with the Chinese version of the RN7Pro. Although these builds are aimed at MI 9, they work for the RN7Pro as well since both of them have the exact same camera sensor.
P.S. Any particular camera settings you are using with GCam? Did you import the XML config file?
Click to expand...
Click to collapse
I don't use any config files.
Only enabled Pixel 2 awb, remove iso limit in dark , no enable auto exposure, and enabled dynamic black lvl.
Worked perfect on chinese rom, working perfect now on global rom.

I tested Arnova8G2 Advanced 1.4 and xtrme's xcam6_beta3. Photo, 4K video and nightshot. Both works fine.

Nope. On the Note 7 Pro, none of the versions (including this one) works perfectly. The portait mode still freezes on my Note 7 Pro from China. The Night Mode does work with this one though.

I've the Chinese note 7 pro and this one works well except for slow motion
https://f.celsoazevedo.com/file/gcamera/MGC_6.2.024_RN7_V1d_plusplus.apk
Sent from my Redmi Note 7 Pro using Tapatalk

I've been doing a lot of testing with several GCam builds on the Redmi Note 7 Pro and I finally found one which gives amazing results. Although it isn't specifically tailored for the Sony IMX586 sensor as we find with other GCam builds developed for the Mi 9 (such as the one modded by xtrme), for some reason it produces much better photos with better color accuracy, details, sharpness, exposure and dynamic range. This GCam build is modded by bulkin043 and it is tailored for a variety of different devices such as the Redmi Note 5 / Pro (whyred), Redmi Note 7 (lavender), Mi A1 (tissot), Mi A2 (jasmine), Mi 6x (wayne) and Mi 8 Lite (platina). During my extensive tests I've found this build to be exceptionally stable with smooth transitions when switching through menus and a very responsive UI.
This build is packed with a lot of great settings such as "Custom Eszdman v2.2" quality level for NightSight, Camera API2 "Metering mode", "ISO priority", and "Lens distortion correction", "Lens blur resolution" and many other unique features. Best of all it comes with a dedicated interface theme (Auto/Light/Dark) which automatically adapts to daylight or night-time conditions. Photobooth and Slow Motion aren't working unfortunately, but that's the case with many GCam builds and so it remains a work in progress.
The only bothersome issue with this build is due to the fact that it permanently crashes video mode when selecting 60fps. Please avoid this framerate for now, or else you will have to reinstall GCam to gain access to video mode again.
This Google Camera is based on the 6.2.030 version and you can download it from > HERE
I will share below the optimal settings for the Redmi Note 7 Pro (after having it thoroughly tested I've found these particular settings to give the best possible results):
[Libs]
Default from Google
[Base settings]
Back camera > Pixel 3a XL/with Pixel 3a config (perfect balance between noise control, details and sharpness with accurate exposure) or Pixel XL/with Pixel 3 config (increased noise, details and sharpness with slightly higher exposure)
Front camera > Pixel 2 XL (good colors, details and sharpness with more noise control) or Nexus 5X (greater details and sharpness with slightly more noise)
Config > Pixel 3a/with Pixel 3a XL and Pixel 3 XL AWB or Pixel 3/with Pixel XL and Pixel 2 XL AWB
[Saturation]
Front Camera > Highlight Saturation (1.9) / Shadow Saturation (2.3)
Back Camera > Highlight Saturation (1.0) / Shadow Saturation (1.6)
[Noise reduction]
Back camera > Activate
Front camera > Activate
DO NOT enable HDR+ Denoise!
[Enable these toggles]
> HDR+ Control
> Save to /DCIM/Camera
> Quick auto exposure settings
> Remove the ISO limit
> Portrait/Disable zoom
> Recompute AWB > On (mandatory!)
All other settings remain on default
NOTICE: Keep in mind that these settings have been tested only on the Redmi Note 7 Pro (China variant). For other compatible devices supported by this build you will have to experiment with the settings yourselves.

I've tested the latest xtrme GCam build and I'm very pleased to see Pixel AWB has finally been fixed. We are getting very close to a true Google Camera performance on the Mi 9 and Redmi Note 7 Pro. File size is also correct and image quality is closer to MIUI stock camera (exposure/highlight conservation is still better on stock camera though).
You can download the latest GCam build developed by xtrme from HERE
After trying various settings I've managed to find the best configuration which provides amazing image quality, with great detail, sharpness, color reproduction, noise control, exposure and dynamic range. There's one single XML config file suitable for both daytime and nighttime conditions which you can download from HERE
Here's a tutorial on how to import/export XML config files for GCam
For NightSight you need steady hands as image processing is slower, but provides maximum quality. There's also a small annoyance with my config as NightSight suggestion doesn't work with BSG Config PixelPlusNS Hdr+, but this issue will eventually be fixed.

Thanks so much @vlachorumsapiens

vlachorumsapiens said:
I've tested the latest xtrme GCam build and I'm very pleased to see Pixel AWB has finally been fixed. We are getting very close to a true Google Camera performance on the Mi 9 and Redmi Note 7 Pro. File size is also correct and image quality is closer to MIUI stock camera (exposure/highlight conservation is still better on stock camera though).
You can download the latest GCam build developed by xtrme from HERE
After trying various settings I've managed to find the best configuration which provides amazing image quality, with great detail, sharpness, color reproduction, noise control, exposure and dynamic range. There's one single XML config file suitable for both daytime and nighttime conditions which you can download from HERE
Here's a tutorial on how to import/export XML config files for GCam
After importing config file, go to Settings > Advanced > Noise Reduction > Untick & Tick again "Activate" toggles (sub-menu toggles also) in first three lenses. This procedure has to be done or else noise reduction settings won't be in effect.
For NightSight you need steady hands as image processing is slower, but provides maximum quality. There's also a small annoyance with my config as NightSight suggestion doesn't work with BSG Config PixelPlusNS Hdr+, but this issue will eventually be fixed.
Click to expand...
Click to collapse
For some reasons, the latest GCam from xtreme is not working good for me. Even after using your config files, colors are still not realistic. I am using Arnova's latest and it is working great right out of the box.

AbhiAbhiBisht said:
For some reasons, the latest GCam from xtreme is not working good for me. Even after using your config files, colors are still not realistic. I am using Arnova's latest and it is working great right out of the box.
Click to expand...
Click to collapse
Not sure why it's not working well for you. Which version are you using from Arnova? Is it the latest 2.0 version?

[Updated XML download link for xtrme GCam]
> disabled noise reduction settings completely (BSG Config PixelPlusNS Hdr+ module does enough noise reduction on its own)
> decreased HDR+ frames to 7
> set correction NightSight to "Off"
The result is faster image processing, reduced time for capturing photos with NightSight, increased details and sharpness with less chances to end up with blurry photos.

vlachorumsapiens said:
Not sure why it's not working well for you. Which version are you using from Arnova? Is it the latest 2.0 version?
Click to expand...
Click to collapse
Yes. Beta 5.

AbhiAbhiBisht said:
Yes. Beta 5.
Click to expand...
Click to collapse
Beta5 is xtrme's version. I was inquiring about Arnova's version.

vlachorumsapiens said:
Beta5 is xtrme's version. I was inquiring about Arnova's version.
Click to expand...
Click to collapse
I am sorry. This one.
https://f.celsoazevedo.com/file/gcamera/GCam_6.1.021_Advanced_V1.5.190418.1850.apk

AbhiAbhiBisht said:
I am sorry. This one.
https://f.celsoazevedo.com/file/gcamera/GCam_6.1.021_Advanced_V1.5.190418.1850.apk
Click to expand...
Click to collapse
I've tried Arnova's version and it's actually very similar with xtrme's version. Color reproduction is pretty much the same when using certain libraries like "Default from Google" or "CSeUs", in combination with BSG Config PixelPlusNS Hdr+ and Pixel 3 XL for base settings. However what Arnova's GCam lacks is a special library called Xlib v2.2s which provides far better details than any other library, with much better exposure in the shadows. I've tried many different builds with many different settings, but none can come close to this one. NightSight is absolutely amazing, but image processing is slower than on Arnova's GCam because it needs more time to capture more light and apply the adequate post-processing. But the trade-off is worth it. Slower processing and maximum quality is better than faster processing and lower quality. It should come as no surprise since xtrme's version is the only build specifically tailored for the Mi 9 which has the exact same main camera sensor as the Redmi Note 7 Pro. I just don't understand why it's not working well for you. But otherwise Arnova's version can take decent photos nonetheless. I think it's a bit better than the versions modded by bulkin043 and BSG when it comes to color reproduction and NightSight.

vlachorumsapiens said:
I've tried Arnova's version and it's actually very similar with xtrme's version. Color reproduction is pretty much the same when using certain libraries like "Default from Google" or "CSeUs", in combination with BSG Config PixelPlusNS Hdr+ and Pixel 3 XL for base settings. However what Arnova's GCam lacks is a special library called Xlib v2.2s which provides far better details than any other library, with much better exposure in the shadows. I've tried many different builds with many different settings, but none can come close to this one. NightSight is absolutely amazing, but image processing is slower than on Arnova's GCam because it needs more time to capture more light and apply the adequate post-processing. But the trade-off is worth it. Slower processing and maximum quality is better than faster processing and lower quality. It should come as no surprise since xtrme's version is the only build specifically tailored for the Mi 9 which has the exact same main camera sensor as the Redmi Note 7 Pro. I just don't understand why it's not working well for you. But otherwise Arnova's version can take decent photos nonetheless. I think it's a bit better than the versions modded by bulkin043 and BSG when it comes to color reproduction and NightSight.
Click to expand...
Click to collapse
I've again tried xtreme's version of GCam and it's working fine now. But there is one issue that the phone lags extensively after taking a photo until it processes.

AbhiAbhiBisht said:
I've again tried xtreme's version of GCam and it's working fine now. But there is one issue that the phone lags extensively after taking a photo until it processes.
Click to expand...
Click to collapse
Yes. That's the downside of this version of GCam. Image processing is slower than on other versions, but image quality is the best.

General GCAM for A52 4G/5G

Hello guys
The BSG versions of the Gcam mod works really stable on our device. But there aren't optimized configs available, so the colors do need to get a little bit tweaked. In the newest versions, it's possible to save and load configs. So it would be nice if we can test some settings out. I also tried it, so you can use it as a base if you want.
Some notes about the changes:
SlibP Custom lib
some settings in "Additional modules settings" (much more to try out there, that's the main place to play around)
activated instantaneous hdr+ enhanced (hdr+ enhanced but without loading time [ZSL], but viewfinder lags a little bit while rendering the final image because of the phone's performance)
Location to place config file: \Download\MGC.8.1.101_Configs
Used Gcam version: https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/f/dl16/
There is also a thread for the A52 5G. Because both devices use the same cameras, it would be great to have one place to tinker.

Which is the apk I have to download? Why are there so many options?
Is it OK to download the fist one?

Wierd, the Samsung cam has way more HDR.

LanguageSoez said:
Which is the apk I have to download? Why are there so many options?
Is it OK to download the fist one?
Click to expand...
Click to collapse
Some manufacturers only give access to the cameras for specific package names. With the Samsung ones, you should be on the safe side. You can also install different versions with different names to make tests
LanguageSoez said:
Wierd, the Samsung cam has way more HDR.
Click to expand...
Click to collapse
Try to disable "instantaneous hdr+ enhanced" and make sure hdr+ enhanced is activated. I think the google stock libs are a little bit brighter, so it should also look more like HDR. There's also a setting to change how many pictures are combined for a HDR+ image, try to increase the value. For me, too much of an HDR effect makes the image unnatural

Do the app always need to restart everytime changing lense ? And I got weird flashes on screen while trying to take a picture.

phoberus said:
Try to disable "instantaneous hdr+ enhanced" and make sure hdr+ enhanced is activated. I think the google stock libs are a little bit brighter, so it should also look more like HDR. There's also a setting to change how many pictures are combined for a HDR+ image, try to increase the value. For me, too much of an HDR effect makes the image unnatural
Click to expand...
Click to collapse
I actually agree that Samsung's pictures look better (as in more accurate to real life) when in bright conditions. GCam has slightly lower noise, but no matter what HDR mode I choose, Samsung still has better HDR and the picture looks brighter overall. GCam's night mode is much better, though.

First one is Samsung, second is Gcam. Samsung's colours are closer to life. Keep in mind that the houses are brightly lit, as this was taken in the morning and they're facing East. For example the flowers in the pot in the balcony of the left house look very bright and vivid IRL. (The sharpness of the shadows near the roof is likely due to clouds moving)

First one is Samsungs, second is Gcam HDR+, third is Gcam HDR+ Enhanced

Both Gcam HDR+ Enhanced (7 or 15 frames doesn't do much), but first one with Google's AWB (like the previous ones), second one without. The second one looks much better, but a little over-saturated. One thing I did notice in the configs is that the AWB is set for a Sony IMX686 sensor, which I don't know if it is correct. I've been unable to find details on the sensor used in the A52. In any case, It seems that the takeaway here is to keep Google's AWB off.

These were all taken using @phoberus 's config file.

ImGonnaTryScience said:
I actually agree that Samsung's pictures look better (as in more accurate to real life) when in bright conditions. GCam has slightly lower noise, but no matter what HDR mode I choose, Samsung still has better HDR and the picture looks brighter overall. GCam's night mode is much better, though.
Click to expand...
Click to collapse
Thanks for the testing. I can confirm that the brightness and colors are not quite good yet. But almost everything should be adjustable. So we still have to test a bit. The sensor I got from gsmarena.com, but is just a guess from them. By default, Pixel2 would be active, which is certainly not correct, but also worked.
Brightness correction: Additional modules settings > Lens x > Exposure compensation
saturation: Additional modules settings > Lens x > Ram Patcher > Saturation (off means it gets the variables from the lib, there are also other nice settings there to create our own lib)

phoberus said:
Thanks for the testing. I can confirm that the brightness and colors are not quite good yet. But almost everything should be adjustable. So we still have to test a bit. The sensor I got from gsmarena.com, but is just a guess from them. By default, Pixel2 would be active, which is certainly not correct, but also worked.
Brightness correction: Additional modules settings > Lens x > Exposure compensation
saturation: Additional modules settings > Lens x > Ram Patcher > Saturation (off means it gets the variables from the lib, there are also other nice settings there to create our own lib)
Click to expand...
Click to collapse
When can we expect a stable optimized and stable gcam for our device. Will you please try contacting gcam developers personally? And also, please drop a link of the gcam you think to be the best one till now.

mushfiqurmasum said:
When can we expect a stable optimized and stable gcam for our device. Will you please try contacting gcam developers personally? And also, please drop a link of the gcam you think to be the best one till now.
Click to expand...
Click to collapse
BSG is only in a Russian forum active. Arnova8G2 also makes good builds, but he only enables the app for the phones he has enough testers. We could ask him here: https://forum.xda-developers.com/t/app-arnova8g2s-google-camera-port.3862448/

Device name: Galaxy A52
Can we get a port for Galaxy A52 4G please?

fix choppy/stuck wide angle and front camera by going into additional settings and changing camera2API level to Level3.. scan3d works fine. but pictures are dark, something with whitebalance

> used MGC_8.1.101_A9_GVt_ruler_libs.apk
> A52 4G / LTE
phoberus' config crashes my GCam viewfinder. I can't test the actual image quality yet since it's the middle of the night here as I'm posting this message.​

So I tried Nikita's version, in terms of Color and HDR (default) it's the closest to the default camera app. I'm still playing around with the settings, so pictures to follow.

So, M51 has a similar camera setup with A52 so I thought I'd use a GCAM version from the M51 GCAM thread. Just testing Night mode and it's very clear that GCAM (right) works better. I'll edit this post to include more samples later.

Valthek said:
So, M51 has a similar camera setup with A52 so I thought I'd use a GCAM version from the M51 GCAM thread. Just testing Night mode and it's very clear that GCAM (right) works better. I'll edit this post to include more samples later.
Click to expand...
Click to collapse
Any version of GCAM I tried works better in night mode than the default camera. The problems I have is with in brightly lit scenes.

ImGonnaTryScience said:
Any version of GCAM I tried works better in night mode than the default camera. The problems I have is with in brightly lit scenes.
Click to expand...
Click to collapse
I actually tried a version of Greatness' GCAM and produced better daytime pictures, color was somewhat natural but it had better details (not noise). Unfortunately, I can't get the wide-angle lens and videos to work so I scrapped it.
I honestly don't mind the issues regarding color/hdr issues since a quick application of a vibrance filter is almost indistinguishable from the default cam. I mean it could be what the default samsung camera app is doing.
Edit: Also strange thing, low light (outdoor dusk scenario) and I get plenty of noise on GCAM compared to the default cam.