[LG G6 Guides, News, & Discussion] ArtZ:
Face recognition does not fix focus on the face. You have to touch the face on the screen to set focus point. It's really an useless gimmick.

---------- Post added at 09:15 AM ---------- Previous post was at 08:52 AM ----------

You're talking here about the Wide-angle camera with 'HDR+ enhanced' ON. I'm aware of the problems with the wide-angle (strong vignetting and underexposure issues). Google Camera must correct vignetting by software but something is not working properly (algorithm not good). However, I don't get the blue cast anymore, even in very low-light conditions.

Now, concerning both cameras, the problem comes from AWB and light metering. As I explained to you in a previous post, even when you touch the screen for spot metering, depending on the room situation you can get different results for the same view under exactly the same conditions. IMHO, I'm convinced that only a manual WB could solve these issue.

Another finding: Using 'HDR+enhanced' with a setting for HDR+ higher than 'Medium', you won't get better results. I don't have a Pixel 2 to check but I think Google sets HDR+ to 'Default' (lowest) when 'HDR+enhanced' is ON. I do believe if many options in official Goggle camera are not available to users, it's because these hidden fonctions found by BSG cannot be used in all possible combinations.

Good luck for your modifications.

Best regards,

---------- Post added at 09:52 AM ---------- Previous post was at 09:15 AM ----------

Essential Phone is not included in the detection list. It's recognized as 'other' and then 'Taimen' configuration is used. 'Shamu' is used ONLY for LG G5, G6, V20. 'Taimen' for all other devices.

Regards,

---------- Post added at 10:25 AM ---------- Previous post was at 09:52 AM ----------

Guys,

This are the exact values used for the LG G6 (and probably for Sony IMX258 sensor) with 'Shamu' configuration:

Release (default is 64.0 for all)

0x427F70A4 # 63.86f

0x427FB852 # 63.93f

0x427FB852 # 63.93f

0x428047AE # 64.14f

(Decimals are very important. There's visible differences using for instance 63.85 instead of 63.86!!!)

However, for Google devices sensors, sensor calibration is included in camera configuration module. These values apply a correction to defaults on camera configuration module. Now, cstark version uses 'Shamu' for the LG G5, G6, V20 and 'Taimen' for the V30 and others. As camera configuration module is different for the V30 and G6 (Taimen instead of Shamu), sensor calibration values are also different. If you use values above on a mod Google Camera for the G6 that doesn't use 'Shamu', my own values will be probably not good.

In other words, the manual values to calibrate a third party (not Google device) sensor are different depending the camera model we use. This is why with Google default values you get better results when you use Nexus 6 configuration instead of Pixel 2 XL. The default values for Nexus 6 sensor configuration are closer to correct values for Sony IMX258.

It will be possible to find calibration values for LG G6 using 'Taimen' configuration but that means hundreds of tests (the same I did to find the proper values for 'Shamu'). Each sensor needs its own calibration for each configuration model.

Regards,