Related
Is it possible to copy the algorithm of Google pixel camera and install it in Xiaomi mi 5s? Because both have exactly same sensors. As I have seen the reviews of Xiaomi mi 5s, there is a room for improvement in the software. Specially night shots need improvement. So is there any way to copy pixel's algorithm and software into mi 5s?
At this point? Probably not.
In the future? Who knows, I hope so too...
We might (or might not) need to copy some libraries from pixel's system image, and probably must use the included google camera (which requires android 7.0 for now...)
awaaas said:
At this point? Probably not.
In the future? Who knows, I hope so too...
We might (or might not) need to copy some libraries from pixel's system image, and probably must use the included google camera (which requires android 7.0 for now...)
Click to expand...
Click to collapse
Why not replace the crappy dual camera of 5s plus with dual imx378? Is it possible? I am really curious to do something with these phones.
Ahm_Shoaib said:
Why not replace the crappy dual camera of 5s plus with dual imx378? Is it possible? I am really curious to do something with these phones.
Click to expand...
Click to collapse
If you want to break your phone then go ahead
Ahm_Shoaib said:
Why not replace the crappy dual camera of 5s plus with dual imx378? Is it possible? I am really curious to do something with these phones.
Click to expand...
Click to collapse
Not possible because of so many things...
- There's likely no drivers for IMX378 included in the kernel/system by xiaomi for Mi5s Plus
- You must have to somehow find dual IMX378 module with the same pin configuration as the original one for it to even turn on (won't work if there's no driver for it though...)
Ahm_Shoaib said:
Why not replace the crappy dual camera of 5s plus with dual imx378? Is it possible? I am really curious to do something with these phones.
Click to expand...
Click to collapse
It would be redundant, the 5s plus uses a normal sensor with a monochrome sensor, similar to P9, and this allows (should) better lowlight, and higher dynamic range, however from samples I've seen, Xiaomi has not implemented it very well. They would have been better off with one 378 sensor, as that is currently one of the best mobile sensors
Man I think the original idea is ask about how we can get the eis and quality photos video from pixel to the mi5s small who carrier the same sensor.
How get software from pixel to mi5s (pixel too expensive), I want use the Xiaomi mi5s small with cm14 and Google pixel software/library features camera
Regards
roghax said:
Man I think the original idea is ask about how we can get the eis and quality photos video from pixel to the mi5s small who carrier the same sensor.
How get software from pixel to mi5s (pixel too expensive), I want use the Xiaomi mi5s small with cm14 and Google pixel software/library features camera
Regards
Click to expand...
Click to collapse
Yes, and I think I've already answered that. Pixel runs android 7.1, Mi5s runs 6.0, you can't get the camera app that comes with pixel to run on mi5s, and if you manage to backport that to android 6.0, what if it needs some library, can you make sure that it is can run on android 6.0, while it is built for android 7.1?
Moreover, I found out the hard way that Mi5s did not specify it's HFR modes, so the latest Google Camera that is compatible with android 6.0 won't run at all. Except if you turn the HFR functionality off, by adding this line to your build.prop:
Code:
persist.camera.hal3hfr.enable=0
I don't know if this bug comes from xiaomi, or xiaomi.eu (as I am running xiaomi.eu's ROM right now), and I don't know if it's gonna be fixed in the future.
You're welcome to pursue this idea, but keep that things in mind
Since Google's HDR+ is so good in low light, has anyone tried alternative 3rd party apps that use image stacking to improve low light IQ ( Better Camera and Snap HDR Cam low light modes come to mind)
I am interested in this phone because of the price and sensor and would like an HDR+ alternative.
Has anyone tried those apps? Thanks
Try cortex camera, it basically is the best app at stacking images.
awaaas said:
Yes, and I think I've already answered that. Pixel runs android 7.1, Mi5s runs 6.0, you can't get the camera app that comes with pixel to run on mi5s, and if you manage to backport that to android 6.0, what if it needs some library, can you make sure that it is can run on android 6.0, while it is built for android 7.1?
Moreover, I found out the hard way that Mi5s did not specify it's HFR modes, so the latest Google Camera that is compatible with android 6.0 won't run at all. Except if you turn the HFR functionality off, by adding this line to your build.prop:
Code:
persist.camera.hal3hfr.enable=0
I don't know if this bug comes from xiaomi, or xiaomi.eu (as I am running xiaomi.eu's ROM right now), and I don't know if it's gonna be fixed in the future.
You're welcome to pursue this idea, but keep that things in mind
Click to expand...
Click to collapse
Hi, thanks for the information about google camera. Any possibility that we can have settings like manual iso, or hdr (just normal hdr) ? Is it exclude to nexus devices, I mean after hacking still? How about the snapdragon camera, it seems that we need caf kernel, but maybe it's working after adding this line?
forgivemypoorEN said:
Hi, thanks for the information about google camera. Any possibility that we can have settings like manual iso, or hdr (just normal hdr) ? Is it exclude to nexus devices, I mean after hacking still? How about the snapdragon camera, it seems that we need caf kernel, but maybe it's working after adding this line?
Click to expand...
Click to collapse
We already have manual controls, just use snap cam and enable cam 2 api in it's settings, or use FreeDcam and you get full manual
shaneel1491 said:
We already have manual controls, just use snap cam and enable cam 2 api in it's settings, or use FreeDcam and you get full manual
Click to expand...
Click to collapse
That's true, I'm just curious if google has better post processing (now I think an app won't change much) If apps can't change, is it possible to copy the drivers from pixel, if the sensors are the same? Meanwhile, we don't have iso 50 (although maybe the native iso is 100, so 100 might be better than 50). Freedcam seems to be able to enable eis on camera api 1, but it crashed a lot, and it's api 1. Now I'm confused which is the best choice. I'm using snap camera, but there's no long exposure like the stock camera (up to 32s, I think it's a stack of photos). Sorry I asked a lot, but it seems that you are an expert . Last question, the stock camera in manual mode, the preview never changes while changing iso/shutter speed. In other apps, it got very slow when the shutter is long (1/3 s). I wonder if this is because imx 378 is very powerful and generating large data, or it's MIUI‘s bug?
forgivemypoorEN said:
That's true, I'm just curious if google has better post processing (now I think an app won't change much) If apps can't change, is it possible to copy the drivers from pixel, if the sensors are the same? Meanwhile, we don't have iso 50 (although maybe the native iso is 100, so 100 might be better than 50). Freedcam seems to be able to enable eis on camera api 1, but it crashed a lot, and it's api 1. Now I'm confused which is the best choice. I'm using snap camera, but there's no long exposure like the stock camera (up to 32s, I think it's a stack of photos). Sorry I asked a lot, but it seems that you are an expert . Last question, the stock camera in manual mode, the preview never changes while changing iso/shutter speed. In other apps, it got very slow when the shutter is long (1/3 s). I wonder if this is because imx 378 is very powerful and generating large data, or it's MIUI‘s bug?
Click to expand...
Click to collapse
I guess Google's HDR+ algorithm is the only great thing the Pixel has we don't besides that fact they don't have long exposure so they can't take as good night pics as us.
In camera 1 Api we can go all the way to 60 sec, although stock libs limited at 32 sec which is fine. Also we do have ISO 50 on FreeDcam API 2, I think I have a specially built FreeDcam by @defcomg who sorted it out. I'll ask him if I he or I can post it here.
Also Quallcomm seemed to mess up the camera libs recently and max exposure on cam 2 api is only around 5 sec.
But I suggest you to experiment with Snap and FreeDcam, I use FreeDcam for long exposures and low light shots. And I use snap camera in the day time. I have denoise and ZSL forced off for both of them.
The preview should get slow and laggy on cam 2 api but stay the same on Cam 1 api
shaneel1491 said:
I guess Google's HDR+ algorithm is the only great thing the Pixel has we don't besides that fact they don't have long exposure so they can't take as good night pics as us.
In camera 1 Api we can go all the way to 60 sec, although stock libs limited at 32 sec which is fine. Also we do have ISO 50 on FreeDcam API 2, I think I have a specially built FreeDcam by @defcomg who sorted it out. I'll ask him if I he or I can post it here.
Also Quallcomm seemed to mess up the camera libs recently and max exposure on cam 2 api is only around 5 sec.
But I suggest you to experiment with Snap and FreeDcam, I use FreeDcam for long exposures and low light shots. And I use snap camera in the day time. I have denoise and ZSL forced off for both of them.
The preview should get slow and laggy on cam 2 api but stay the same on Cam 1 api
Click to expand...
Click to collapse
I tried freedcam with 50 iso, but the photo actually got iso 100 still. You can also set iso 50 in snap camera, which still outputs 100.
Turn ZSL (0 lag?) is better for HDR? I heard a saying that ZSL is not as good as longer hdr, which is software implementation.
forgivemypoorEN said:
I tried freedcam with 50 iso, but the photo actually got iso 100 still. You can also set iso 50 in snap camera, which still outputs 100.
Turn ZSL (0 lag?) is better for HDR? I heard a saying that ZSL is not as good as longer hdr, which is software implementation.
Click to expand...
Click to collapse
When zsl is enabled you can't have manual controls, so that's why I disable it. But also try in FreeDcam (cam 1) to set shutter speed and leave ISO on auto and see, it's possible to get up to 0 ISO.
shaneel1491 said:
When zsl is enabled you can't have manual controls, so that's why I disable it. But also try in FreeDcam (cam 1) to set shutter speed and leave ISO on auto and see, it's possible to get up to 0 ISO.
Click to expand...
Click to collapse
cam 1 you mean Camera api 1? It crash a lot (every time I touch to focus, or use exposure longer than 1/3s ). I couldn't got iso lower than 100. Do I need to use hdr mode to get this or any mode as long as I set iso to auto and a long shutter?
hdr+ is out for mi5s
It's funny since people thought it was impossible 1+ year ago but now thanks to awesome devs more devices can taste the magic of Google Camera HDR+
How to Copy Google Pixel Camera algorithm into Xiaomi Redmi 6A?
Hello everybody Is it possible to copy the algorithm of Google pixel camera and install it in Xiaomi mi Redmi 6A? Because both have exactly same sensors. So is there any way to copy pixel's algorithm and software into my Redmi 6A ?Thanks to all
Hi all -- When I purchased a Moto Z late last month, I was excited about the device's performance but blind to the fact that I was going to lose the HDR+ camera mode that I had become so accustomed to with my Nexus 6.
This got me working on some potential solutions -- and after decompiling the Camera NX app posted on chromloop.com, I was able to change some settings that enable full HDR+ photography on the Moto Z. So if any of you are craving being able to take photos with Google's HDR+ mode, here is a modified APK that will allow you to do so: http://www.mediafire.com/file/l8num4lyw05vybt/Camera4-hdrplus.apk
I have been using it for several weeks on my Moto Z, and I can confirm that the HDR+ images come out looking much better than those taken with the stock camera app or even the same modified Camera NX app with HDR+ disabled. It's slightly buggy (low-light images are only occasionally not saved) but a great solution for any Moto Z users afflicted with the Nexus blues. This should also work on other devices with equivalent Camera2 API support; if you are wondering whether it will work, just try it -- if HDR+ images are successfully captured, your device supports the needed API calls.
Can you enable RAW capture and manual control?
Hello, I installed the camera application, but when I go to slow motion mode, App crashes. Any solution?
Will this be continually developed?
Because this is a wonderful addition. Just needs some bug fixes and it'll be seriously golden.
D13H4RD2L1V3 said:
Will this be continually developed?
Because this is a wonderful addition. Just needs some bug fixes and it'll be seriously golden.
Click to expand...
Click to collapse
I'm afraid that ongoing development of this app might be challenging, as I'm no expert in modifying decompiled apps, which this is (as the official Nexus/Pixel camera app is closed source). The extent of my modifications, believe it or not, was to return a constant boolean value of "true" for a function that checks whether a device is a Nexus 6P -- so the app enables HDR+ as the app is hard-coded to enable all functions available on Nexus 6P devices. It just happened to be very lucky that HDR+ is supported! -- I'm not so optimistic about being able to enable slow motion video, RAW capture, or manual control, but I will keep those in mind next time I have more time to work on this.
need root? or standard apk install
taphius said:
need root? or standard apk install
Click to expand...
Click to collapse
Just a standard APK install.
elosito said:
Hi all -- When I purchased a Moto Z late last month, I was excited about the device's performance but blind to the fact that I was going to lose the HDR+ camera mode that I had become so accustomed to with my Nexus 6.
This got me working on some potential solutions -- and after decompiling the Camera NX app posted on chromloop.com, I was able to change some settings that enable full HDR+ photography on the Moto Z. So if any of you are craving being able to take photos with Google's HDR+ mode, here is a modified APK that will allow you to do so: http://www.mediafire.com/file/l8num4lyw05vybt/Camera4-hdrplus.apk
I have been using it for several weeks on my Moto Z, and I can confirm that the HDR+ images come out looking much better than those taken with the stock camera app or even the same modified Camera NX app with HDR+ disabled. It's slightly buggy (low-light images are only occasionally not saved) but a great solution for any Moto Z users afflicted with the Nexus blues. This should also work on other devices with equivalent Camera2 API support; if you are wondering whether it will work, just try it -- if HDR+ images are successfully captured, your device supports the needed API calls.
Click to expand...
Click to collapse
Thank you so much for this. I see a big difference with HDR+. I've had the Nexus 6P and Pixel, I know how great HDR+ is. It's sad that Google closed source their app.
Let us know if you can enable RAW, because HDR+ takes 3 RAW photos for the composition, so theoretically RAW is supported by the app.
This is awesome! So far with just a little experimenting today with a Force, I can see the difference. I look forward to testing it further.
elosito said:
Hi all -- When I purchased a Moto Z late last month, I was excited about the device's performance but blind to the fact that I was going to lose the HDR+ camera mode that I had become so accustomed to with my Nexus 6.
This got me working on some potential solutions -- and after decompiling the Camera NX app posted on chromloop.com, I was able to change some settings that enable full HDR+ photography on the Moto Z. So if any of you are craving being able to take photos with Google's HDR+ mode, here is a modified APK that will allow you to do so: http://www.mediafire.com/file/l8num4lyw05vybt/Camera4-hdrplus.apk
I have been using it for several weeks on my Moto Z, and I can confirm that the HDR+ images come out looking much better than those taken with the stock camera app or even the same modified Camera NX app with HDR+ disabled. It's slightly buggy (low-light images are only occasionally not saved) but a great solution for any Moto Z users afflicted with the Nexus blues. This should also work on other devices with equivalent Camera2 API support; if you are wondering whether it will work, just try it -- if HDR+ images are successfully captured, your device supports the needed API calls.
Click to expand...
Click to collapse
This is incredible! How did you figure out how to bypass the checks and actually enabled the hdr+? Google never open sourced this so how were you able to get it to work? Many have tried to get hdr+ but failed.
Today's testing was outside and yielded mixed results. I'll continue to experiment.
Sent from my XT1575 using XDA-Developers Legacy app
Wen trying to install the apk it says there was a problem parsing the apk
I created a little album on Google Photos demonstrating the difference between regular shots, the stock app's HDR mode and HDR+. They are shot in that order but I have put them in the description in order to aid identification. Differences can be subtle but often, they are very dramatic.
If you need to know, my variant is an unlocked standard Moto Z running Android 7.0 that's also rooted. It also has a 1/3" 13MP Sony IMX214 with 1.12-micron pixels and an f/1.8 aperture. Pretty sure the Force will do better since it has a larger sensor at 1/2.4". Regardless, HDR+ makes a significant enough difference that it has become my main camera app. If I still had my Note 7, I'd be drooling right now.
https://goo.gl/photos/bQ1NQzCCMmviGtCs6
Thanks for sharing this. I've done something similar with the Force camera.. It's a mixed bag to me. Often HDR+ did a better job with the sky, but often its shots were too dark to me. I've seen a bigger difference with indoor shots.
Thanks for the sharing. Hope moto can implement HDR+ to its own camera app.
benjamminh said:
Thanks for sharing this. I've done something similar with the Force camera.. It's a mixed bag to me. Often HDR+ did a better job with the sky, but often its shots were too dark to me. I've seen a bigger difference with indoor shots.
Click to expand...
Click to collapse
Yeah, the 6p and pixel both exhibit the same thing, most of the the time their shots are going to look darker (if you compare them side by side to other phones)
D13H4RD2L1V3 said:
I created a little album on Google Photos demonstrating the difference between regular shots, the stock app's HDR mode and HDR+. They are shot in that order but I have put them in the description in order to aid identification. Differences can be subtle but often, they are very dramatic.
If you need to know, my variant is an unlocked standard Moto Z running Android 7.0 that's also rooted. It also has a 1/3" 13MP Sony IMX214 with 1.12-micron pixels and an f/1.8 aperture. Pretty sure the Force will do better since it has a larger sensor at 1/2.4". Regardless, HDR+ makes a significant enough difference that it has become my main camera app. If I still had my Note 7, I'd be drooling right now.
https://goo.gl/photos/bQ1NQzCCMmviGtCs6
Click to expand...
Click to collapse
I like five of the shots with HDR+ more (two are very significant) 7 with the Moto HDR, and three with the normal mode fwiw.
skullman_247 said:
Wen trying to install the apk it says there was a problem parsing the apk
Click to expand...
Click to collapse
Has to be on Nougat
You know, I wonder if this works with the Hasselblad mod.
I've always thought that the issues with the Hasselblad camera are software-related since the sensor is likely the same one from the 6P. If HDR+ and better processing can save it, color me impressed.
Dear owners of an OnePlus 5T and maybe 5 too,
please grant me an answer to a really important question: Is the Camera2-API bug fixed for the OP5T or is it still valid and OnePlus didn't do anything against it?
Please do following:
Download Open Camera > Go to settings > Scroll down > Switch on Camera2-API > Cover the rear camera with your hand > Read the values at the very top of your screen:
• If ISO 799 and 1/16,7 is still here: Nothing was fixed. Please leave a reply.
• If values differ from those values (ISO 799 1/16,7) OnePlus finally fixed the Camera2 API. Please also leave a reply.
Thanks in advance.
MickyFoley said:
Dear owners of an OnePlus 5T and maybe 5 too,
please grant me an answer to a really important question: Is the Camera2-API bug fixed for the OP5T or is it still valid and OnePlus didn't do anything against it?
Please do following:
Download Open Camera > Go to settings > Scroll down > Switch on Camera2-API > Cover the rear camera with your hand > Read the values at the very top of your screen:
• If ISO 799 and 1/16,7 is still here: Nothing was fixed. Please leave a reply.
• If values differ from those values (ISO 799 1/16,7) OnePlus finally fixed the Camera2 API. Please also leave a reply.
Thanks in advance.
Click to expand...
Click to collapse
Glad I could help.
ISO 9600 and 1/16,7s
so what does this mean now exactly?!
what are the advantages, what can be accomplished? the Google Cam HDR still doesn't seem to work correctly on the 5t.
@vercetti: The reason why I'm asking it: There are several good, real camera apps out, taking advantage of the Camera2 API. I still have the 3T and OnePlus didn't fix the Camera2 API implementation for us. Neither with Oreo. With the correct implementation (thanks for the confirmation @Wilux), Open Camera, Footej Camera, A Better Camera, etc. will work correctly and a Google Camera port is more likely than with a bugged implementation of the API - like for the 3 and 3T.
OnePlus 5 also shows ISO 9600 and 1/16,7s (latest stock rom)
MickyFoley said:
@vercetti: The reason why I'm asking it: There are several good, real camera apps out, taking advantage of the Camera2 API. I still have the 3T and OnePlus didn't fix the Camera2 API implementation for us. Neither with Oreo. With the correct implementation (thanks for the confirmation @Wilux), Open Camera, Footej Camera, A Better Camera, etc. will work correctly and a Google Camera port is more likely than with a bugged implementation of the API - like for the 3 and 3T.
Click to expand...
Click to collapse
This means pictures will be lot better then on original camera app?
Would like to see some comparison from OP5t camera and OpenCamera. I still thinking to buy this great piece of tech, but its all about camera what I am focused about. Google phones not available in my country (officialy), Im getting sick over Samsungs (got them for 3 years now, too much!) as all what is good on Sammies is camera. Want to move from my s7e as there was no good flagship, but OP5t is perfect, if at least have same quality of pictures/videos as its on s7e, even if that means using 3rd party app.
@droidhd: This means, the device is theoretically able to do better images via the correct working Camera2 API. Mostly, images will be bad because of post-processing. And if you shoot RAW, mostly the hardware and the correct implemented API is significant for good photos. Maybe you'll see more grain. Maybe the colors aren't the same like you do with the standard camera app. But I'd say: Yes, they get better with more advanced camera apps.
My list of professional camera apps (No need for social media crap like filters, effects, etc.):
Open Camera: https://play.google.com/store/apps/details?id=net.sourceforge.opencamera (Simply a great piece of software!)
Snap Camera HDR (Beta): https://play.google.com/store/apps/details?id=com.marginz.snap (Looks like abandoned. Last update 1 year ago)
Manual Camera: https://play.google.com/store/apps/details?id=pl.vipek.camera2
A Better Camera Unlocked: https://play.google.com/store/apps/details?id=com.almalence.opencam_plus (Looks abandoned, but will get updates from time to time. Unsteady, but alive)
Camera FV-5 (Beta): https://play.google.com/store/apps/details?id=com.flavionet.android.camera.pro
ProShot: https://play.google.com/store/apps/details?id=com.riseupgames.proshot2
Footej Camera: https://play.google.com/store/apps/details?id=com.footej.camera
Sadly, only one for video left:
FiLMiC Pro: https://play.google.com/store/apps/developer?id=FiLMiC+Inc. (Please try Evaluator first!)
Cinema FV-5: https://play.google.com/store/apps/details?id=com.flavionet.android.cinema.pro (Seems abandoned. Last update 2 years ago)
The list isn't very long, I know. Feel free to extend it. But please: No filters, no effects, no social media like things. Those are around in thousands and nothing professional in it!
Micky, could you explain to me why it is common knowledge that picture quality is usually best when the stock rom with the stock cam is used compared to any photography app running on custom roms?
I've read in so many threads, posts... that people went back to the stock rom just because pic quality is higher than on custom rom.
is this history when camera2 API works correctly? meaning that images are identical when using open camera on stock vs opencam on custom rom? or would opencam (or any other photo app) still produce images of lesser quality when used on a custom rom?
People went back, because of the abstraction layer and because drivers are still closed source. I'd like to compare it a bit:
If you setup a new computer, you only have standard drivers for each and everything. You can use it, but only if you install the correct drivers, things get to start working like they should. Like your graphics card: Working, but you'll notice some kind of stuttering/tearing when scrolling in your browser on certain websites. If you install the driver for your card: All is smooth, like it should.
So we can say: Drivers in AOSP are more like standard. Not all functions, more workarounds, but working OK. And drivers directly from stock (OEM) will get all functions to work good and smooth (if they're implemented correctly).
But you can see, that it's possible to get great photos out of your device with mods for Google Camera even on AOSP-ROMs. Because this mod brings itself some "magic". So you see: Closed source vs. open source. If we'd have the full code of the drivers: Photos, produced by the standard camera app of every OEM would probably look like crap.
OnePlus once promised to get us at least the camera blobs, but they didn't. They say: "Too hard!". Lie, because they know, that their already scratched images would suffer more than now, because Devs like sultanxda would have kicked their butts out of the universe by producing better photos than the stock camera app.
Thx for the answer Micky, i like the comparison with the computer and missing drivers, you made it much clearer now!
But 2 questions still remain:
1.) Does a 3rd party photo app (like Open Camera or any other one) lead to the exact the same picture quality if installed on a stock rom as compared to being used on a custom rom? Or will a 3rd party app still be better on the stock rom than on a custom rom because of the drivers you explained before?
And 2.) does this whole camera2 API aspect change what you explained about the driver situation? Meaning, that there is no need anymore for the drivers that can only be found in a stock rom because camera2 API gets to use the whole potential of the camera hardware?
Just trying to figure out where the best image quality can be found. The whole thing is too confusing to me, sorry
@vercetti: Sorry for the late reply. Was kinda busy. To answer your questions:
1: Yes and no. Depends. But pictures will probably visualize it a bit better:
HAL1 (LEGACY):
HAL3 (CAMERA2):
A bit more complex explained: https://source.android.com/devices/camera/camera3
2: HAL and driver are bond together. Without a driver, you can't even get HAL1 to work . But yes: A correct working HAL3 implementation will get you to the point of using your full potential of your camera. Again depends on the driver too . Hard to explain, but the more advanced explanation at Google should answer your questions very well.
UPDATE: Used hide tags to organize this post better and make information easier to find.
Alright, so you've got a shiny new Moto G5 plus, which supposedly has a similar Sony imx sensor as the one found on flagships like the Galaxy S7 and Pixel2. Yet, you are somehow disappointed by the camera's quality.
YOU ARE NOT ALONE!
Turns out the camera sensor on this thing is actually pretty darned good, and the f/1.7 lens is no slouch, however it is being held back by poorly designed software from Moto/Lenovo.
Before I got into the solutions, let me specifically point out the problems I found with the camera so we're on the same page (click to reveal content, or just skip the fixes below):
1) Overzealous Sharpening and aggressive Noise Reduction are the biggest culprits. It almost looks like a bad filter is being applied to your images, turning fine details into mush and contrasty lines like text into something bizarre and artificial looking. The camera is doing this as part of the internal capture process, so this happens no matter what application it is taken in.
2) Highlights clipping earlier than it should. I'd say this might be a function of the camera's sensor more than the hardware, but analyzing RAW data from the sensor (more on that later) in my admittedly unscientific half-hazard naked eye, I'd go out on a limb and say it seems like we're not being shown all the DR the camera is able to see. To the layman: this means brights turn completely white effectively overexposing parts of the image that should otherwise still look OK.
3) The preview/viewfinder mode is even worse at #1 than the captured image is. That is, the preview mode (the video feed you see before you capture the full resolution image) is still applying the sharpening and NR at the same level as the captured image, however since the resolution is lower for the preview, it looks more exaggerated and ugly. This means two things: A) Its hard to tell what the image you take will look like, as the preview is ugly (and you have to hope the final will look better), and B) some apps use the preview feed as their capture method. For example, snapchat and augmented reality apps like Pokemon Go. It just looks terrible.
The good news is that there is a lot that can be done to improve and fix the camera.
The bad news is that almost all of it requires modifying system files. That means those with locked bootloaders (Amazon ad users or those who are afraid of voiding their warranties) might be out of luck.
You don't necessarily need root access, although some of this can be more easily performed with root. I needed to unlock my bootloader and performed most of this within TWRP, but chose to keep my phone otherwise unrooted. I'm going to split this into sections, fixing and improving.
A) FIXING THE IMAGE PROCESSING ISSUES
If you want to remove/circumvent the aggressive sharpening and NR issues (so that apps like snapchat or other camera applications don't look over-processed, including the stock Moto cam), try the following:
1) Chromatix mod. Shout out to @defcomg for finding and adjusting the values that control sharpening and NR in the system libs. See thread here:
https://forum.xda-developers.com/g5-plus/themes/modcamera-aggressive-sharpening-noise-t3604458
There are two sets of files to replace in your system. Chromatix and LIBMM. NOTE: I don't recommend the LIBMM / binning part. Binning is combining pixels together into an averaged single pixel value, effectively reducing resolution to combat noise on the sensor. In other words, instead of having a large possibly noisy image, you get a smaller less noisy picture. But you can always choose to resize the image in post after you take it with the same resulting effect, so I don't see why this would be desirable to do. I recommend just applying the chromatix mod to remove the sharpening and NR. If you're comfortable using TWRP, there's actually a flashable zip in post #9, which is what I personally did (again, remember I'm not rooted, so I needed to flash/overwrite/etc within TWRP).
After applying this mod, even the stock camera app looks better, and apps that use the live preview (Snapchat, Pokemons AR view, etc) don't have the shadow ghosting from excessive sharpening anymore either. You might want to apply some sharpening and NR in post yourself if the image requires it, but thats always something you can choose but at least you have control over it and even without doing that it looks far better and more natural than stock to me.
2) Enable camera2 API. This doesn't have a direct effect on quality, but will allow other apps to have more direct access to the camera. If you want to improve beyond the results of #1 above, you'll need this.
The stock rom, surprisingly, has Camera2 API included, however it is disabled by the build.prop file. Again, no idea why Moto/Lenovo chose to do this, but the good news is you can enable it again easily. To do this, you need to add the following line to the build.prop
persist.camera.HAL3.enabled=1
Or if rooted, via terminal / shell:
su persist.camera.HAL3.enabled 1
Once this is enabled, you can use apps such as the modified freedcam to shoot RAW, as found here: https://forum.xda-developers.com/g5-plus/how-to/how-to-enable-camera2-shoot-raw-root-t3582392
I found RAW from this app particularly difficult to work with, so I'm keeping it for experimentation purposes but for practical real-world usage, I'd recommend the next item below.
B) IMPROVING YOUR PHOTOS (or, how to install Google Camera!)
Section A was all about how to avoid the crummy filters that get automatically applied to the camera. But your device is capable of even BETTER photos by using Google's magic HDR+ algorithm (the special sauce that makes the Pixel phones so awesome). Here's how to do that:
1) If you haven't already enabled the Camera2 API, you need to do that first (info in section A above).
2) Get a working version of Google Camera with HDR+ for your phone. The last available 32-bit version with HDR+ is Gcam 4.2, so if you're on the stock ROM like I am, you're stuck with only the 32-bit versions (all the new versions with the bells and whistles are 64-bit only). The image quality is remarkably better, both in sharpness and dynamic range in almost any light. I have to admit, I'm in love with the images from this, and have even printed some for my wall.
You can get the APK ported from the Nexus 5x version here:
https://forum.xda-developers.com/showpost.php?p=74081041&postcount=3
UPDATE: New version from Savitar on post #44!
https://forum.xda-developers.com/showpost.php?p=75483974&postcount=44
Problem is, our cameras use a different focus system than phones like the Nexus and Pixel. So, in photo mode, it doesn't really work correctly. Switching over to video mode, however, DOES work (likely using contrast detection focus, which is slower but more universal, especially for video focus). So the workaround is to swipe over to video mode, focus, swipe back to photos and press-and-hold to lock focus. It's annoying, but HDR+ is that good that I still try to work with it much of the time.
For times that it would be frustrating or not necessary, I'll just resort to the stock camera app or Footej camera, since the chromatix mod makes them mostly usable now. Just not ZOMG AMAZING like the Google HDR+ does.
OPTIONAL #3) Install a 64-bit custom Rom and use the latest Google Camera HDR+ app floating around (v4.4). The recent versions B-S-G released based on the Pixel camera has options to change camera modes in settings, some combination of which supposedly focus properly. You will likely get a more stable camera app experience with this as it requires less modification to work, but you'll have to be committed enough to go off stock.
Check out the app and suggested settings to try here:
https://forum.xda-developers.com/showpost.php?p=74999182&postcount=19
Thanks @shanks125 for the info!
Update 1/3/18: I just heard there is a port of the new portrait mode feature from the Pixel2 that is sort of working on 64-bit roms, but I think some modifications will need to be made to avoid focus drift like previous modded gcam versions.
There is also a 32-bit version of the new v4.4 that @Aby lad came up with in this thread:
https://forum.xda-developers.com/android/apps-games/google-camera-4-4-arm-device-t3666090
In order to make it more compatible with other devices, it looks like he has disabled the Hexagon DSP, which I think is what makes HDR+ work, so while we can now change settings and focus, HDR+ isn't working. The app still has some Google goodies like Sphere and Blur mode, but without HDR+ the real benefit of Google camera is lost anyway. Might as well use stock with chromatix mod at that point.
Hope some of you find this helpful/useful!
UPDATE 12/28/17: New GCam with 6P features on post #14.
There actually may be some alternate versions of the gcam apk with benefits the one originally linked above doesn't have. I will try to update when if/when I find them.
Dishe said:
There actually may be some alternate versions of the gcam apk with benefits the one originally linked above doesn't have. I will try to update when if/when I find them.
Click to expand...
Click to collapse
That would be useful!
So if I apply the chromatic mode, do I still have to enable the Camera2 API?
It's my bad. I would like to know if there is a way to disable Camera2 api. I am on Linage 14.1 and I edited my prop.build (yeah, I know). I switched back to the original line of code, but camera app still crashing. How to revert without reflashing the rom? Thanks.
edit. reflashed.
iBART said:
It's my bad. I would like to know if there is a way to disable Camera2 api. I am on Linage 14.1 and I edited my prop.build (yeah, I know). I switched back to the original line of code, but camera app still crashing. How to revert without reflashing the rom? Thanks.
edit. reflashed.
Click to expand...
Click to collapse
Did you try clearing data+cache for the camera app?
iamsonal said:
So if I apply the chromatic mode, do I still have to enable the Camera2 API?
Click to expand...
Click to collapse
Nope, but it doesn't hurt to so why not? Some apps will have more options in camera2 if enabled.
iBART said:
It's my bad. I would like to know if there is a way to disable Camera2 api. I am on Linage 14.1 and I edited my prop.build (yeah, I know). I switched back to the original line of code, but camera app still crashing. How to revert without reflashing the rom? Thanks.
edit. reflashed.
Click to expand...
Click to collapse
There is another way to enable camera2 api if you're using a custom ROM. You need to flash a magisk module.
https://forum.xda-developers.com/showpost.php?p=74081041&postcount=3
Which Google camera works in a complete stock g5? I keep getting a praising error with every one I try.
eemgee said:
Which Google camera works in a complete stock g5? I keep getting a praising error with every one I try.
Click to expand...
Click to collapse
Parsing error means you are probably trying to use a 64-bit or one made for a different version of Android (7.1 instead of 7.0). The one linked above will work.
However, all recent versions of Google's Camera require the camera2 api to work. That's one of the primary reasons to enable the Camera2 api in my opinion. It comes in the stock rom, but it is disabled for some inexplicable reason (G5S model has it enabled, so some people are hoping that we'll get it enabled with an update or at least when Oreo rolls around). The good news is that it only takes one line of text in the build.prop file to enable it on the G5+. However, the bad news is that build.prop is part of the protected system partition, so editing it requires root-level file access. Doesn't seem to be any way to do that without unlocking the bootloader, so either way you won't be able to do it on a 100% stock g5+ as things are right now.
Thanks i managed to get 2.7 working.
I will unlock the bootloader at some point in the next few weeks....
There is also a Magisk module in post #54 on that Chromatix thread. Really helpful!
Hi, so in search for better images from my g5+ camera I stumbled upon this place and rooted my phone to add the chromatix mods and edit the build.prop file .
I downloaded the google camera port v4.2 for the hdr+ but have been unable to install it as I get the error that package may be corrupted.
So could someone please link me to one which is good or upload it.
And BIG thanks to this community.
New gcam from savitar
UPDATE: Better gcam version from Savitar/Defcomg
http://s000.tinyupload.com/?file_id=00826724446841525700
Features:
Burst Mode (hold shutter button)
Focus doesn't drift when switching from video mode (this is a huge fix IMO- old app would drift after setting focus in video mode).
Selfie cam now has HDR as well (with caveats)
RAW image capture with each photo!
Instructions for use are largely the same as the old app, but it works better / more reliably now:
WHEN USING APP FOR THE FIRST TIME, GO INTO SETTINGS AND CHANGE VIDEO TO 4K. This will prevent FCs.
To take a picture:
1) Swipe left to switch to video mode, tap to focus
2) Once focus is achieved, swipe right to return to photo mode. (Focus should not drift in this version)
3) Tap the area again in photo mode, and hit the shutter button.
NOTES:
It appears that you no longer need to press-and-hold to lock focus in photo mode before shooting. I believe this is because the focus system doesn't adjust anymore in photo mode (I'm guessing Savitar/Defcomg removed it to combat that focus drifting problem). It is already locked at wherever you put it in video mode. You DO however need to still tap the screen as if you are focusing. I think this is because the camera needs to think it is focusing, but it is anyway helpful to tap somewhere for metering / exposure reading purposes. Skipping the press-and-hold to lock focus makes it a lot more manageable.
This version of the app is setup to shoot RAW+Jpeg, so you will find your camera roll will have both a jpeg and DNG file of the shot. Be aware that the RAW DNG files are multiple times larger than the jpeg, so you may want to keep an eye on storage if you shoot a lot of them. They're really useful if you want to adjust WB and exposure afterwards, quality is astoundingly good.
Selfie Mode was broken in HDR+ on earlier builds because for some reason the front camera on our phone doesn't return an ISO value to the app (says iso is zero). The HDR+ algorithm would fail. Savitar/defcomg fixed it by setting it always return a value (he picked 100, otherwise it would overexpose in daylight). The catch is that in lower lighting, the selfie HDR+ comes out darker than expected. Thankfully you can take the RAW file and adjust the exposure in post if needed (snapseed, Lightroom mobile, etc). But there might be times it is just too dark to be useful. The difference when it works is big enough that I recommend it trying it at least once to compare.
ENJOY!
Big shout out to @defcomg for this and all his awesome mods!
Landscape gcam 6p
A modified version of the APK above is available which starts the camera off focused at infinity.
http://s000.tinyupload.com/?file_id=31694573387513766779
This was made for people who want to shoot landscapes and/or things far enough away that they don't want to deal with focusing (swipe to video mode, etc). See a beautiful sunset for example, open this app, tap the sky and hit the shutter. Its already focused in the right position.
Otherwise identical to previous post's apk. Can be installed side-by-side, as each app has its own ID.
can't use gcam because it crashes at first run
marcol87 said:
can't use gcam because it crashes at first run
Click to expand...
Click to collapse
Do u have camera2 API enabled?
Dishe said:
UPDATE: Better gcam version from Savitar/Defcomg
Click to expand...
Click to collapse
Thank you for sharing this.
Add this, BSG GCam MOD with working HDR+ and Touch to Focus for 64bit roms. Settings as per attachment! https://androidfilehost.com/?fid=889964283620770378
Dishe said:
Do u have camera2 API enabled?
Click to expand...
Click to collapse
yes, I added persist.camera.HAL3.enabled=1 to build.prop and rebooted
Dishe said:
persist.camera.HAL3.enabled=1or
Click to expand...
Click to collapse
ps: the string persist.camera.HAL3.enabled=1 is wrong in the OP
Project Status
2021-12-20: This project is no longer being worked on. Please look towards MWP mods https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/
As you may have noticed or seen in my sporadic posts here, Camera PX development has been non-existent for quite some months now. This is mainly due to a lack of substantial updates within Google Camera, but also due to lack of interest in the project as other things in our lives have become more important. As each new Google Camera version is released, the modifications have to be re-done from scratch so this would take quite some time as we only get to do this in our "free" time after work and spending time with our families. We do hope the Pixel 5 release brings some new/interesting things to the table but that is yet to be seen, and the passion to restart the project is also yet to be seen. For now, we are releasing a minor update to "support" Pixel 4a's but since Google Camera 7.2 was not built with Pixel 4a's in mind, you may notice a quality difference than your stock camera.
Click to expand...
Click to collapse
Disclaimer
This has turned into a collaboration between @back.rider555, @johngalt1 and myself. We do this in our free time, when able, to bring newer Pixel features and mods to your older device.
Click to expand...
Click to collapse
Introduction
This is a Google Camera mod for the Pixel phones. The main goal is to bring newer features to older Pixels, where possible.
What is Google Camera (AKA GCam)?
Google Camera is the camera app for the Google Nexus and Google Pixel phones. It is not designed or intended to be run on other phones.
What is HDR+?
Basic: HDR+ is Google's proprietary image processing routine, and is more than just traditional "HDR' modes. HDR+ employs image stacking to control exposure, and also to preserve details, reduce noise, increase sharpness, etc. It is an all-in-one package.
Advanced: https://ai.googleblog.com/2014/10/hdr-low-light-and-high-dynamic-range.html
Google Camera Features
Pixel 1
Zero Shutter Lag (ZSL) HDR+ - The Pixel 1 introduced ZSL HDR+ which means when you open the camera, the system utilizes the Hexagon DSP to constantly buffer frames and marks the time slot of when you pressed the shutter button.
* -- Quote from Marc Levoy via The Verge:
"The moment you press the shutter it's not actually taking a shot — it already took the shot," says Levoy. "It took lots of shots! What happens when you press the shutter button is it just marks the time when you pressed it, uses the images it's already captured, and combines them together."
It's a major usability improvement on the HDR+ mode in last year's Nexus 6P and 5X. "What used to happen last year is you'd press the shutter button and you'd get this little circle going around while it captured the images you need for the burst; now it's already captured those," says Levoy. "And that's big, because that means that you can capture the moment you want."
* -- https://www.theverge.com/2016/10/18/13315168/google-pixel-camera-software-marc-levoy
Pixel 2
Portrait Mode - Simulates bokeh for improved subject separation from the background. The front camera of the Pixel 2 only provides Portrait Mode when a human face is detected, and the rear camera can work on an object, an animal, a human, etc because it uses information from the Dual Pixel PDAF sensor to detect depth. Google Camera ports for non-Pixel phones can NOT do this so all ports for non-Pixel phones utilize the front camera technique for both front & rear (which means all ports for non-Pixel phones can only properly apply bokeh when a human face is detected).
* -- Advanced read: https://ai.googleblog.com/2017/10/portrait-mode-on-pixel-2-and-pixel-2-xl.html
Motion Photos - Provides short clips of moments before and after you take the photo.
* -- Advanced read: https://ai.googleblog.com/2018/03/behind-motion-photos-technology-in.html
Pixel 3
Top Shot - When Motion is set to Auto or On, Pixel will recommend a better photo to you if it detects one. Like if you captured a photo when someone blinked.
* -- Demo:
Photobooth - Automatically capture a photo when Pixel detects a silly face or a smile.
Super Res Zoom - Enhances zoomed picture quality by purposely shifting the camera module using OIS (Pixel 3 only) to gather more data.
* -- Advanced read: https://ai.googleblog.com/2018/10/see-better-and-further-with-super-res.html
Motion Metering - On the Pixel 3 Motion Metering is used in the "default photo mode" to detect subject motion and if it detects enough motion, Pixel will shoot with a faster shutter speed to reduce subject blur. The Pixel 1 and 2 get to use this in Night Sight only.
* -- Further reading (about 1/3 down the article): https://ai.googleblog.com/2018/11/night-sight-seeing-in-dark-on-pixel.html
Synthetic Fill Flash - Pixel 3 will brighten faces in selfies.
Tracking Autofocus - Tap on a subject or area to keep focus when the subject or phone moves.
Learning Based White Balance - Google's attempt to fix white balance for low light photos. Used in Night Sight and HDR Enhanced on the Pixel 3.
* -- Further read (about 1/2 down the article): https://ai.googleblog.com/2018/11/night-sight-seeing-in-dark-on-pixel.html
Portrait Mode Learned Depth - Pixel 3 improves the rear camera Portrait Mode depth detection for more consistent and more pleasing bokeh.
* -- Advanced read: https://ai.googleblog.com/2018/11/learning-to-predict-depth-on-pixel-3.html
Click to expand...
Click to collapse
Installation instructions
Root is NOT needed.
* -- Download APK to your Phone (or PC then transfer to your phone)
* -- Locate APK with File Manager and Install
* -- You will be prompted to Allow Unknown Sources. This is normal for APK's not downloaded from the Play Store.
Click to expand...
Click to collapse
Download
PXv8.1_GCam-v1.2.apk
See optional Magisk modules in Post 2 below.
Alternative download location (thanks to @s4turno):
https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
Previous Versions:
PXv4.5_GoogleCamera_7.2.014.apk
PXv4.3_GoogleCamera_7.2.014.apk
PXv4.2_GoogleCamera_7.2.014.apk
PXv4.1_GoogleCamera_7.2.014.apk
PXv4.0_GoogleCamera_7.2.014.apk
PXv3.3.1_GoogleCamera_7.2.010.apk
PXv3.3_GoogleCamera_7.2.010.apk
PXv3.2_GoogleCamera_7.2.010.apk
PXv3.1_GoogleCamera_7.2.010.apk
PXv3.0_GoogleCamera_7.2.010.apk
PXv1.1_GoogleCamera_6.3.020.apk
PXv1.0_GoogleCamera_6.3.020.apk
P3v12.6_GoogleCamera_6.2.030.apk
P3v12.4_GoogleCamera_6.2.030.apk
P3v12.3_GoogleCamera_6.2.030.apk
P3v12.2_GoogleCamera_6.2.030.apk
P3v12.1_GoogleCamera_6.2.030.apk
P3v12_GoogleCamera_6.2.030.apk
P3v11.4.31_GoogleCamera_6.2.024.apk
P3v11.4.2_GoogleCamera_6.2.024.apk
P3v11_GoogleCamera_6.2.024.apk
P3v10.1_GoogleCamera_6.1.021.apk
-Add Xlib2 (another reduced contrast option) and modify to support Pixel 3 Portrait bokeh on Pixel 2
-Add Portrait and Night Sight App Shortcuts from back.rider555
Known Issues on Android 8.1:
-Tapping to focus breaks autofocus. Exiting camera or switching modes/cameras fixes this.
-Night Sight will crash the very first time you use it after installation. It appears to run just fine after that until you Clear Data of the app.
P3v9.1_GoogleCamera_6.1.021.apk
-Disable HDR+ mode resetting for Pixel 1 when opening Camera
-Add "reduce contrast" option which loads a custom lib by Savitar to reduce black crush a little bit. I have not tested in all conditions. Feel free to test at your own discretion and provide your thoughts with comparison pics.
Known Issues on Android 8.1:
-Tapping to focus breaks autofocus. Exiting camera or switching modes/cameras fixes this.
-Night Sight will crash the very first time you use it after installation. It appears to run just fine after that until you Clear Data of the app.
P3v9_GoogleCamera_6.1.021.apk
-Revert default color accent to Google Blue by popular request
-Fix HDR+ mode resetting for Pixel 1
-Exif fix (big thanks to @Arnova8G2 for helping)
-Fix Night Sight for Android 8.1 (big thanks to BSG)
Known Issues on Android 8.1:
-Tapping to focus breaks autofocus. Exiting camera or switching modes/cameras fixes this.
-Night Sight will crash the very first time you use it after installation. It appears to run just fine after that until you Clear Data of the app.
P3v8.6_GoogleCamera_6.1.021.apk
-Change default color accent to Google Green
-Add P3 Mod Settings>Permanent Night Sight Suggestion
--Provides an always on button to enter Night Sight
-If P3 Mod Settings toggles are changed, the camera will restart automatically to apply the changes (be careful if HDR+ is Processing) (thanks @fu24 / namok)
Known Issues on Android 8.1:
-Tapping to focus breaks autofocus. Exiting camera or switching modes/cameras fixes this.
-Night Sight will crash the very first time you use it after installation. It appears to run just fine after that until you Clear Data of the app.
-Night Sight viewer is black. There is a fix for this but then it requires Flash to be set to Auto/On for it to work properly. I don't use Flash ever so this is not a good option to me at the moment. I opted for the black screen until a fix can be found. Thanks for understanding. Wait until the focus ring is gone, or choose your focus in the Focus Option on the top right, then click the photo.
P3v8.5_GoogleCamera_6.1.021.apk
-Cleaned up P3 Mod Settings. Settings not relevant for Android 8.1 are removed, and PVC toggle is removed for non-Pixel 2/3.
-Add P3 Mod Settings>HDR+ Enhanced for Portrait toggle. This increases dynamic range, at the cost of shutter delay. Force close the app is required for the setting to change. (Credit to BSG for the method)
-Tried to adjust some stuff for Wear remote shutter support but I need a proper log if there's issues still.
P3v8_GoogleCamera_6.1.021.apk
Must uninstall old version due to signature change.
-Support for Android 8.1 (referenced BSG's latest versions)
-Settings>P3 Mod Settings
--Toggles to switch Photo viewers (Classic or Google Photos), Enable Pixel Visual Core for ZSL HDR+, Disable Learning Based AWB in HDR Enhanced, & Disable Tracking Autofocus. The last 2 options only work on Android 9, so the toggles don't do anything for Android 8.1
Known Issues on Android 8.1:
-Tapping to focus breaks autofocus. Exiting camera or switching modes/cameras fixes this.
-Night Sight will crash the very first time you use it after installation. It appears to run just fine after that until you Clear Data of the app.
-Night Sight viewer is black. There is a fix for this but then it requires Flash to be set to Auto/On for it to work properly. I don't use Flash ever so this is not a good option to me at the moment. I opted for the black screen until a fix can be found. Thanks for understanding. Wait until the focus ring is gone, or choose your focus in the Focus Option on the top right, then click the photo.
P3v7_GoogleCamera_6.1.021.apk
P3v6_GoogleCamera_6.1.013.apk
Uninstall old version. This has a different package name (to fix Lens). The new app is in your app drawer labeled CameraP3.
-Lens option in More
-Pixel 3 Portrait mode (which seems to only improve the rear lens Portraits, so no improvement on Pixel 1 probably)
-Removed HDR+ Options for now due to bugs/instability/confusion
Only tested on Pixel 2. I don't have a Pixel 1 to test with to offer fixes for.
P3v5_GoogleCamera_6.1.013.apk
-Add workaround for Pixel 1 rear Portrait (only works on human faces)
Previous changelog:
For all Pixel:
-Enable Night Sight
-Enable manual focus button in Night
-Add HDR+ Config selection
Tested only on Pixel 2:
-Enable focus tracking
-Enable Photobooth
-Video FPS options (Auto/30/60)
-Google Lens Suggestions in Viewfinder
-H265/HEVC toggle
-Super Zoom (maybe??)
-"New" HDR+ Enhanced (colors may differ in extreme tinted light conditions, test it out; this is how the Pixel 3 behaves see https://www.teknofilo.com/analisis-pixel-3-xl/4/)
P3v4_GoogleCamera_6.1.013.apk
For all Pixel:
-Enable Night Sight
-Enable manual focus button in Night
-Add HDR+ Config selection
Tested only on Pixel 2:
-Enable focus tracking
-Enable Photobooth
-Video FPS options (Auto/30/60)
-Google Lens Suggestions in Viewfinder
-H265/HEVC toggle
-Super Zoom (maybe??)
-"New" HDR+ Enhanced (colors may differ in extreme tinted light conditions, test it out; this is how the Pixel 3 behaves see https://www.teknofilo.com/analisis-pixel-3-xl/4/)
Click to expand...
Click to collapse
FAQ
Q: "I already have a Pixel, why do I need to use a GCam mod?"
A: Here are the added benefits of Camera PX:
All Pixels:
Ability to choose Camera, Portrait, or Night Sight as the default mode
Custom Lib options to reduce black crush, improve details, and/or increase clarity
Ability to choose 4K Time Lapse quality
Ability to choose zoom level in Portrait Mode of 1.2x or 2.0x (for the rear camera)
Ability to choose to enable HDR+ Enhanced for Portrait Mode
Option to have quicker access to Night Sight by "permanently" adding the little message at the bottom regardless of measured light (admittedly it disappears if you capture a photo in regular mode)
Option to increase shutter speed and frames in Night Sight for potentially "better" Night Sight photos
Option to disable the "Learning AWB" in HDR+ Enhanced/Night Sight
Option for manual shutter speed & ISO
Face warping is completely disabled
In addition to the above, these are the added features for specific devices (when compared to the stock app):
Pixel 1:
Portrait Mode (only when a "human face" is detected, does not work on objects/animals like Pixel 2, 3, 3a)
Removes the HDR+ mode reset on launch or when leaving settings
Synthetic Fill Flash (brightens faces when there is a strong backlight)
Motion Photos & Top Shot (if you have the correct Google Photos APK installed)
HEVC option
Photobooth
Adds focus button in Night Sight (Auto/Near/Far)
Tracking Autofocus in Photo mode
Super Res Zoom sharpening algorithm
Pixel 2:
"Learned Depth" for Portrait Mode which provides, usually, a more accurate depth detection and more pleasing bokeh
Synthetic Fill Flash (brightens faces when there is a strong backlight)
Top Shot (if you have the correct Google Photos APK installed)
HEVC option
Photobooth
Adds focus button in Night Sight (Auto/Near/Far)
Tracking Autofocus in Photo mode
Super Res Zoom sharpening algorithm
Pixel 3:
-Adds 60ps option to top bar in Video mode
Pixel 3a:
Synthetic Fill Flash (brightens faces when there is a strong backlight)
Q: Do I need to change any settings?
A: This mod is optimized for the Pixels to run without changing any settings. There are some advanced settings in P3 Mod Settings. Experiment at your own will.
How to get Top Shot working?
A: https://forum.xda-developers.com/showpost.php?p=78186764&postcount=726
Click to expand...
Click to collapse
Thanks To/Credits
B-S-G for fixes for Android 8.1
Arnova8G2 for general help and other fixes as he comes up with them
Click to expand...
Click to collapse
XDA:DevDB Information
[GCam] Camera PX for Google Pixel 1 / 2 / 3 / 3a / 4, App for all devices (see above for details)
Contributors
cstark27, back.rider555, johngalt1
Version Information
Status: Beta
Created 2018-12-05
Last Updated 2020-09-03
Magisk Modules
Magisk Modules
These optional modules may provide more functionality and/or improve processing speed or efficiency. Warning: I have been informed that having Viper or JamesDSP modules installed will cause problems with the long exposure libs (GCam crashes).
All Pixels:
SELinux Permissive for Camera P3
---This reduces the processing time a small amount and may be more battery efficient. The modded apps appear to be blocked from using the DSP/PVC for Processing, by default.
Pixel 1:
Pixel 1 modified system libs for long(er) exposure times during Astrophotography Mode
Pixel 2:
Pixel 2 modified system libs for long(er) exposure times during Astrophotography Mode
Pixel 3:
Pixel 3 modified system libs for long(er) exposure times during Astrophotography Mode
Pixel 3a:
Pixel 3a modified system libs for long(er) exposure times during Astrophotography Mode
Pixel 4:
Prop editor to allow Telephoto Lens to be used past 8x zoom when using a modified APK that supports longer zoom levels.
Click to expand...
Click to collapse
Outdated modules:
Magisk Modules
These optional modules may provide more functionality and/or improve processing speed or efficiency.
All Pixels:
SELinux Permissive for Camera P3
---This reduces the processing time a small amount and may be more battery efficient. The modded apps appear to be blocked from using the DSP/PVC for Processing, by default.
Pixel 1:
Pixel 1 modified system libs for long(er) exposure times
Pixel 2:
Pixel 2 modified system libs for long(er) exposure times
Pixel 3:
Pixel 3 modified system libs for long(er) exposure times
Pixel 3a:
Nothing to see here
Pixel 4:
Prop editor to allow Telephoto Lens to be used past 8x zoom when using a modified APK that supports longer zoom levels.
Warning: I have been informed that having Viper or JamesDSP modules installed will cause problems with the long exposure libs (GCam crashes).
Click to expand...
Click to collapse
Bug Report Template
Please copy and fill in the info when reporting issues. Failure to do so may result in no response.
Unfortunately, it's hard to fix "the app doesn't work" without any more information.
---BEGIN COPY---
Which Google Pixel?
Android version:
What is the issue?
How are you able to reproduce it?
Have you cleared the app data and left the settings alone?
Does the issue still happen?
Does the issue happen with a certain setting enabled or disabled?
What Magisk Modules are installed?
Do any of them promise to enable certain features of newer Pixels or other phones?
Have you disabled all extra Magisk Modules, temporarily, and rebooted to see if your problem is solved?
---END COPY---
Please attach a logcat (instructions below).
Not Rooted/Rooted (using phone):
If you are not rooted, download Matlog from Play Store and follow prompts to set it up, then see the instructions below.
Open Matlog, clear the log, open CameraPX, reproduce the crash. Go back to MatLog and save the log.
Not Rooted (using PC, with USB debugging enabled):
command window:
Code:
adb logcat -c
This clears all previous logs (private info and irrelevant stuff).
command window:
Code:
adb logcat > C:\file.txt
Open, CameraPX, get it to produce App Not Responding message, close out of command window, send file.
Thanks for your great work as always, greatly appreciated.
The best Gcam mods.. thanks @cstark27
Gives me 410 gone Error when trying to Download
Amazing work ? However, there seems to be a problem if the PVC is used. After rapidly taking multiple photos in normal mode or portrait mode, there is a delay to take the next shot. In Pv7 without the PVC, this wasn't the issue.
True, PVC does help process faster though.
What's the problem with pixel 3 AWB in HDR Enhanced? Just wonder should I switch it off or not
@cstark27
Thanks a lot for this new mod. Works great!
One request:
If it is not too much trouble, could you allow the "Enable camera sounds" toggle to always appear in "Settings", irrespective of region?
This is the best app Ive ever used. Thanks a bunch for the work.
This is truly the best mode thus far. Kudos for the work, man.
Same here
PsychOlli said:
Gives me 410 gone Error when trying to Download
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
@cstark27 topshot/recommended shots stopped working with photos shot with p3v8. also tried clearing data and cache many times with no luck. i also have the motio photo on. rest is working sooper fine. thanks for the update
Can't get to the download I don't know if there's an issue with it just letting you know thank you for your hard work
Sent from my [device_name] using XDA-Developers Legacy app
davidstjohn1 said:
Can't get to the download I don't know if there's an issue with it just letting you know thank you for your hard work
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
open it in a browser with open link a new tab option.
I am running "PieX BETA ROM"(Android Pie) on my Nexus 5x, and I tried installing the P3v8 App on it.
Every time I use "night mode", the "Quick Step" launcher crashes when I try to quit the app.
I tried this many times, each time, after using the night mode, the launcher crashes.
Then I have to (most of the time) restart the phone to get everything working again.
Is there any trick to get this to work?
Thanks.
note3exynosbd said:
Amazing work ? However, there seems to be a problem if the PVC is used. After rapidly taking multiple photos in normal mode or portrait mode, there is a delay to take the next shot. In Pv7 without the PVC, this wasn't the issue.
True, PVC does help process faster though.
Click to expand...
Click to collapse
Yes there are still limitations to the config. I hope Google is working on improving it to match or exceed the great work they have done to utilize the Hexagon DSP, and then hopefully they make it the default method in the future. But who knows.
noname729 said:
What's the problem with pixel 3 AWB in HDR Enhanced? Just wonder should I switch it off or not
Click to expand...
Click to collapse
See "Google Camera Features" under Introduction in the OP to see what it does. Then know that the Pixel 3 applies this learning based AWB to HDR+ Enhanced, as well as night mode. Some may not prefer to have this behavior on their older Pixel phones where it may not be as accurate, and/or doesn't capture the scene as your eyes see it. This setting does not disable it for Night Sight.
surya1078 said:
@cstark27 topshot/recommended shots stopped working with photos shot with p3v8. also tried clearing data and cache many times with no luck. i also have the motio photo on. rest is working sooper fine. thanks for the update
Click to expand...
Click to collapse
I still see the strip of photos ("Shots in this Photo") when swiping up in Google Photos. Do you have that still? Recommended and Best Shot has always been random for me, and I don't use Motion Photos by default so my experience is limited. I have a link in the FAQ in the first post on how to get Top Shot working. Basically you just need the listed Google Photos installed.
PsychOlli said:
Gives me 410 gone Error when trying to Download
Click to expand...
Click to collapse
Nichie said:
Same here
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
davidstjohn1 said:
Can't get to the download I don't know if there's an issue with it just letting you know thank you for your hard work
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I am told this happens if there are too many requests at once. Try again later or when @S4turno gets a chance to upload to his mirror website https://www.celsoazevedo.com/files/android/google-camera/
surya1078 said:
@cstark27 topshot/recommended shots stopped working with photos shot with p3v8. also tried clearing data and cache many times with no luck. i also have the motio photo on. rest is working sooper fine. thanks for the update
Click to expand...
Click to collapse
Make sure you have the 4.6 Daydream 500+ DPI Photos app. Just google it.
It is working fine here with v8. I am really digging the new options in the cam
Hi @cstark27 thank you for update everything working great portrait working now.....
But night sight saturation too much Greenish now in P8 version....
Can we have stock saturation.,..?
And more request can you please add this Mod from BSG....View attachment 4658878
Sent from my Nexus 6P using Tapatalk
@cstark27 i too get the photo strip but not the recomended shot. have tried taking different photo poses which previously suggested recommended shot in p3v7 but not in p3v8.