Related
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).
I just recently bought Xperia XZ and I'm very disappointed to see that the "Full Manual Controls" in the camera UI and Camera2 API are actually pretty limited. Manual settings, such as "Saturation", "Contrast", "Sharpness", available since a long long time in Samsung and HTC devices, are absolutely unavailable and inaccessible here, neither in the default camera UI, nor in third-party applications, such as FreeDCam, Camera FV-5 and so on. For example, if you check this video, showing the capabilities of the FreeDCam application - youtube.com/watch?v =PWg0KaXbv5I (I can not post links yet, so you have to remove the spaces) , you can see how many settings at the bottom of the screen can be manually adjusted. But when I installed this application on my Xperia XZ, I got only "Manual focus", "ISO", "Manual exposure time", "Exposure compensation" and "Zoom". All other settings are missing. I read some time ago that Sony finally enabled the full manual settings, but from what I see quite a lot of settings are missing... Is there any way to enable them, maybe by rooting the device or I don't know, but I need them, otherwise I'll have to sell the phone and look for other options...
mediar said:
I just recently bought Xperia XZ and I'm very disappointed to see that the "Full Manual Controls" in the camera UI and Camera2 API are actually pretty limited. Manual settings, such as "Saturation", "Contrast", "Sharpness", available since a long long time in Samsung and HTC devices, are absolutely unavailable and inaccessible here, neither in the default camera UI, nor in third-party applications, such as FreeDCam, Camera FV-5 and so on. For example, if you check this video, showing the capabilities of the FreeDCam application - youtube.com/watch?v =PWg0KaXbv5I (I can not post links yet, so you have to remove the spaces) , you can see how many settings at the bottom of the screen can be manually adjusted. But when I installed this application on my Xperia XZ, I got only "Manual focus", "ISO", "Manual exposure time", "Exposure compensation" and "Zoom". All other settings are missing. I read some time ago that Sony finally enabled the full manual settings, but from what I see quite a lot of settings are missing... Is there any way to enable them, maybe by rooting the device or I don't know, but I need them, otherwise I'll have to sell the phone and look for other options...
Click to expand...
Click to collapse
Most likely it's an app limitation. Just like when I tried to install Camera FV-5 and Manual Camera apps for lower shutter speed but unfortunately they only provide 1/10 SS while the stock camera has 1 second.
ermond012 said:
Most likely it's an app limitation. Just like when I tried to install Camera FV-5 and Manual Camera apps for lower shutter speed but unfortunately they only provide 1/10 SS while the stock camera has 1 second.
Click to expand...
Click to collapse
That one as well, I forgot about that one, as well as the ISO limited only up to 800, and many others, all these limitations are set by Sony to their Camera2 API so that no third-party apps can use the full potential of that sensor, which is a shame. Clear evidence is that when you install the same application, even from the same apk file, on other phones, such as Samsung or HTC, these additional manual contrrol options are present, they are missing only on Xperia phones...
The reason why I need these settings is because of the camera's very poor performance with the default camera app, mostly because of the dull and poor colors, and I want to compensate that by boosting the saturation and the contrast. Even my trustworthy 5 years old Xperia Pro takes much better photos - with less noise and better colors... I'm very disappointed with Xperia XZ's camera...
mediar said:
I just recently bought Xperia XZ and I'm very disappointed to see that the "Full Manual Controls" in the camera UI and Camera2 API are actually pretty limited. Manual settings, such as "Saturation", "Contrast", "Sharpness", available since a long long time in Samsung and HTC devices, are absolutely unavailable and inaccessible here, neither in the default camera UI, nor in third-party applications, such as FreeDCam, Camera FV-5 and so on. For example, if you check this video, showing the capabilities of the FreeDCam application - youtube.com/watch?v =PWg0KaXbv5I (I can not post links yet, so you have to remove the spaces) , you can see how many settings at the bottom of the screen can be manually adjusted. But when I installed this application on my Xperia XZ, I got only "Manual focus", "ISO", "Manual exposure time", "Exposure compensation" and "Zoom". All other settings are missing. I read some time ago that Sony finally enabled the full manual settings, but from what I see quite a lot of settings are missing... Is there any way to enable them, maybe by rooting the device or I don't know, but I need them, otherwise I'll have to sell the phone and look for other options...
Click to expand...
Click to collapse
Try switching to camera 1 api in freedcam
Sent from my NX503A using XDA Free mobile app
defcomg said:
Try switching to camera 1 api in freedcam
Click to expand...
Click to collapse
I made two screenshots with my Xperia XZ, the first one with Camera1 API, the second one with Camera2 API, and the third screenshot, which I took from this site - en.miui.com/thread-269521-1-1.html , shows the UI of the application as seen on Samsung, HTC, MIUI and other brands or ROMs (basically the default manual controls, provided by stock Camera2 API in stock Android). Clearly the ones from the Xperia miss quite a lot of manual options...
mediar said:
I made two screenshots with my Xperia XZ, the first one with Camera1 API, the second one with Camera2 API, and the third screenshot, which I took from this site - en.miui.com/thread-269521-1-1.html , shows the UI of the application as seen on Samsung, HTC, MIUI and other brands or ROMs (basically the default manual controls, provided by stock Camera2 API in stock Android). Clearly the ones from the Xperia miss quite a lot of manual options...
Click to expand...
Click to collapse
try save camera parameters from camera 1 Settings > Save camera parameters you should find txt file in dcim/freedcam
defcomg said:
try save camera parameters from camera 1 Settings > Save camera parameters you should find txt file in dcim/freedcam
Click to expand...
Click to collapse
F8331_CameraParameters.txt is created with camera1 -> Settings > Save camera parameters (for some reasons I can't find "Save camera parameters" when using camera2);
log1.txt is created with Camera FV-5 with camera2 set;
log2.txt is created with Manual Camera Compatibility application.
Maybe someone should provide such logs from other phones so that we can compare them.
mediar said:
F8331_CameraParameters.txt is created with camera1 -> Settings > Save camera parameters (for some reasons I can't find "Save camera parameters" when using camera2);
log1.txt is created with Camera FV-5 with camera2 set;
log2.txt is created with Manual Camera Compatibility application.
Maybe someone should provide such logs from other phones so that we can compare them.
Click to expand...
Click to collapse
i see the params its because the device is using sony camera hal and not qualcomms thats why the parameters in camera 2 you maybe able to control sharpness via edge mode and contrast via tone curve .
dunno if you have raw option in camera2 if you tap on jpeg to the left of ui there should be raw10 or raw_sensor if there is neither the best you can hope for is for an aosp rom with qualcomm framework on know the z5c had full qualcomm hal so it had all the options available including raw
defcomg said:
i see the params its because the device is using sony camera hal and not qualcomms thats why the parameters in camera 2 you maybe able to control sharpness via edge mode and contrast via tone curve .
dunno if you have raw option in camera2 if you tap on jpeg to the left of ui there should be raw10 or raw_sensor if there is neither the best you can hope for is for an aosp rom with qualcomm framework on know the z5c had full qualcomm hal so it had all the options available including raw
Click to expand...
Click to collapse
It is known issue that the Xperia XZ (as well as all Xperias so far, not sure whether Z5 makes exception) have no RAW capture, so the jpeg option on the left of the UI has only option at all - jpeg and that's it But I'm very disappointed to hear that previous generations Xperias had more manual controls than the latest ones, that's really a shame
Google Camera Port by BSG and @sannn111ty for the Poco f1
If you don't really know why you are here, You can download Gcam here. Gcam is short for Google's camera app that ships with the pixels. Google has been making incredible advances in camera software that they put on their Pixel devices. Most of the magic of the camera quality of pixel's reside in the High Dynamic Range google algorithms. However, this software is not officially available for other devices. BSG is the first developer to have adapted Gcam for other devices. He now has a MI 8, which is very siùilar to the Pocophone, so his ports actually work pretty well on this phone.
Here is a list of the features that make google's software stand apart from all the other stock and 3rd party camera apps. (Not all of them are available in the ports, but more appear with time).
HDR + and HDR+ Enhanced: That's what most people want Gcam for. The app takes multiple pictures at different exposure levels and combines them to get even lighting. This photography technique is available on many stock cams, but Google's custom implementation of it is generally regarded as highly superior.
Super Res Zoom: That is a "usebug" feature. When you're taking a picture, unless you have a tripod, you can't hold the phone perfectly still. Google uses this slight movement to take multiple shots, which are then combined to make out more detail for the final image. Where other OEMs add a second camera, Google gives better results with just one.
Night Sight: where HDR combines multiple under-exposed shots, Night Sight does the same thing with over-exposed and longer exposed images. This produces impossible-before shots with way less noise and blur in very low-light conditions. In Daylight, Night Sight Mode also applies Super res Zoom to the image, giving a lot more detail to your pictures.
ZSL HDR+: ZSL stands for Zero Shutter Lag. As HDR uses multiple pictures, you need to wait for the phone to snap those multiple shots. ZSL essentially means your phone is always taking pictures and has a couple already buffered when you hit the shutter, so you don't need to wait.
Portrait Mode: That's blurring that background of an image behind a face. this is a trend on smartphones, and most OEMs implement it by adding a second camera on the back. the two sensors produce a slightly different image and you can calculate from the difference where to blur the image. But Google has decided not to add a second sensor to their phones. The way they pull it off is by local Artificial intelligence to detect faces and blur the rest.
Photosphere: This is essentially a 360° Panorama. You point around you and the phone takes, then stitches together, multiple images in a sphere around you. You can then view the pictures by moving them around with your fingers, or moving around your phone like a window around you.
Panorama: That is self-explanatory. like everything else, Gcam takes excellent panoramas.
Video Recording: Gcam Records video at up to [email protected]
Slow-Motion: this port can take slow-motion videos at up to [email protected]
Top Shot: Google's AI is now so good it know what a good image is like. If you hit the shutter too Soon or too late, Google will suggest another shot. It will actually take a dozen out of which you can choose, but will also suggest the best one.
Photobooth: As the camera is continually shooting and waiting for you to tap the shutter, why couldn't it do this for you too? Once Photobooth is on, you just leave your phone and it will take the picture on its own when it "sees something interesting", like a smile. Essentially, it's an AI photograph for group shots where everyone can fit in and lets you use the back sensor instead of the selfie cam.
Tracking Autofocus : As the name implies, once you click on an object while filming, it will keep the focus on it however it moves.
I am not a developer, but the subforum is for gcam ports, so here is the one for the Pocophone, with instructions and
Go to this thread, wich always has the last version up.
You are welcome to post your amazing pictures here :
These ports are specifically made for the Pocophone F1. They might or might not work on your phone.
If you find that our APK's work well on your other model, you can open a thread for your phone to help others find a working APK faster and discuss model-specific issues.
If you have bugs, something isn't working correctly, please don't just post "Not Working !!!!" That doesn't help. Give details :
- The model of your Phone, your ROM if you're using one, any fixes installed;
- The name of the apk you're using;
- Screenshots or video recordings of the bug if you're able to;
- A logcat if there's a crash;
- Steps to reproduce the bug/crash;
It's really lag when opening any camera mod (except Panaroma and Video) and I could NOT take photos when pressing the button.
I'm Using Pocophone F1 with Global MIUI 10.1.3.0
File using: MGC_6.1.021_MI8_Vc.apk
the same issues.
Same issues for me, impossible to take photos, 1 frame per second refresh rate....
not working with several versions
When opening any camera mod (except Panaroma and Video) NOT possible take photos when pressing the button.
I'm Using Pocophone F1 , Android 9, with Global MIUI 10.1.3.0
Files used:
MGC_6.1.021_MI8_V2_plus3.apk
and
MGC_6.1.021_MI8_V2_plus.apk
and
MGC_6.1.021_MI8_V2a_plus.apk ; MGC_6.1.021_MI8_V2a+_plus.apk
cr0wdelex said:
It's really lag when opening any camera mod (except Panaroma and Video) and I could NOT take photos when pressing the button.
I'm Using Pocophone F1 with Global MIUI 10.1.3.0
File using: MGC_6.1.021_MI8_Vc.apk
Click to expand...
Click to collapse
Try flashing twrp fix bro. It fixed my issue.
Try installing MIUI 10 v10.2.2.0 or higher , it should fix most of problems with gcam
Love this camera ...
I installed gcam and flashed twrp fix. I was using 10.1.3.0
After 10.2 I updated it and flashed twrp fix again for the lag issue.
Now I noticed that portrait mode is not working in stock camera. ?
i downloaded and it seems fine ...
Confused a bit, what is the difference between this and the one here :
https://forum.xda-developers.com/poco-f1/themes/b-s-g-google-camera-port-developed-mi-8-t3843130
Update to miui 10.2.2.0 i installed the same version of gcam on miui 10.1.3.0 and it didnt work i manually updated to miui 10.2.2.0 and it worked to install it just use android studs guide
Maybe a dumb question.? How is "Motion" in GCam working? Is it working at all? I have never found any of these short videos. Where are they stored? I'm using a Pocophone F1.
Thank you
Working fine with poco rom stock mui 10.3.6
Credits goes to the guys of this topic:
https://forum.xda-developers.com/on...ide-enable-960fps-slow-motion-7t-pro-t4101389
The mod adds to the stock camera the option to record 10 seconds of the video in 720p 960 fps.
Just wanted to let you know that in the normal one plus 7 this mod works as well. I am using the latest stable Android 10 firmware with arter97 kernel. I did not tested the macro mode.
The only one difference is that we need to add the values described in the topic above to camera 0 and 3, because the camera 5 does not exist for us. Please check carefully the screenshots.
Don't forget to install the newest apk of the camera from the link below, as well as after applying the mod don't forget to restart your phone.
https://www.apkmirror.com/apk/oneplus-ltd/oneplus-camera/oneplus-camera-3-10-19-release/
Have fun!
Not working with my OP7, with camera ver: OnePlus Camera 3.10.17 and OOS 10.3.2.GM57AA.
After editing the .xml files when I open the camera app it shows nothing just a black screen.
How about enabling Macro mode, Did it work for any?
Dipesh17 said:
Not working with my OP7, with camera ver: OnePlus Camera 3.10.17 and OOS 10.3.2.GM57AA.
After editing the .xml files when I open the camera app it shows nothing just a black screen.
Click to expand...
Click to collapse
3.10.19 is the newest version. Download this version, edit the XML 0 and 3 by adding the values, and then restart the phone. It has to work because for me is working.
Not working
misiek735 said:
3.10.19 is the newest version. Download this version, edit the XML 0 and 3 by adding the values, and then restart the phone. It has to work because for me is working.
Click to expand...
Click to collapse
I tried the same but not working.
Check screenshot.
The only difference is I am using pref edit to edit xml because preferences manager is always crashes on my mobile.
And pref edit is working.
Would you please share your screenshot or suggest something.
Dipesh17 said:
I tried the same but not working.
Check screenshot.
The only difference is I am using pref edit to edit xml because preferences manager is always crashes on my mobile.
And pref edit is working.
Would you please share your screenshot or suggest something.
Click to expand...
Click to collapse
You wrote 920, instead of 960. Change the name in both to the correct number.
Dipesh17 said:
I tried the same but not working.
Check screenshot.
The only difference is I am using pref edit to edit xml because preferences manager is always crashes on my mobile.
And pref edit is working.
Would you please share your screenshot or suggest something.
Click to expand...
Click to collapse
Had the same problem using Pref Edit, i edit them manually afterwards it works great, here are my xml files
https://drive.google.com/file/d/1bb-oFqq4wXxOk4wKR_OCIs_88uh3zpnr/view?usp=sharing
Just put them in /data/data/com.oneplus.camera/shared_prefs.
Hi! I am the author of the original thread. First. Camera 5 id exist on our phone. Is for multi camera. As camera 0 is for dual. And camera 3 is for wide angle. Totally not used here. The stringset needs to be added on 0 and 5 for stability reasons. I would appreciate the OP to not create duplicated of the threads please. (Thanks for the credits though, but this mod is not only mine, other people deserve credits too) and not spread wrong info please.
Hi @elmarian756
With all respect, the purpose of writing it here was to inform the users of standard one plus 7 about the possibility of using this mod. I decided to write about it here because it was important to mention that the settings in the preferences manager apk has to be different. If you think that this topic doesn't make sense, please edit your topic and include the information that the standard op7 can also use this mod with the proper settings. In that way I don't mind in deleting this topic. The idea was just to share the info, not to change/share/steal the credits from the original author.
I believe that for the op7 pro there is CameraInfo_5.xml file, but for op7 there is not. Please take a look at the screenshot below how does it look in my op7. The CameraInfo_3.xml is the "highest" available number. There is also CameraInfo_2, and 1 and 0, but there is no file which has number 5 in the title. I guess that the difference is caused by the reason that the op7pro has one camera lens more (the wide angle what you wrote about) compared to op7 which does not have that lens.
For the users of standard op7 (me including) editing the camerainfo_3 and 0 brings the possibility of using 960fps slow motion mod. If you wish, I can record and share the video showing the settings as well as the sample of the 960fps slow motion.
By the way, thanks for sharing the info about this mod!
All the best,
Misiek735
misiek735 said:
Hi @elmarian756
With all respect, the purpose of writing it here was to inform the users of standard one plus 7 about the possibility of using this mod. I decided to write about it here because it was important to mention that the settings in the preferences manager apk has to be different. If you think that this topic doesn't make sense, please edit your topic and include the information that the standard op7 can also use this mod with the proper settings. In that way I don't mind in deleting this topic. The idea was just to share the info, not to change/share/steal the credits from the original author.
I believe that for the op7 pro there is CameraInfo_5.xml file, but for op7 there is not. Please take a look at the screenshot below how does it look in my op7. The CameraInfo_3.xml is the "highest" available number. There is also CameraInfo_2, and 1 and 0, but there is no file which has number 5 in the title. I guess that the difference is caused by the reason that the op7pro has one camera lens more (the wide angle what you wrote about) compared to op7 which does not have that lens.
For the users of standard op7 (me including) editing the camerainfo_3 and 0 brings the possibility of using 960fps slow motion mod. If you wish, I can record and share the video showing the settings as well as the sample of the 960fps slow motion.
By the way, thanks for sharing the info about this mod!
All the best,
Misiek735
Click to expand...
Click to collapse
I am sorry i dont want to be rude but you are just misinformed. The information you are providing is just incorrect.
You can check this yourself typing *#*#1597#*#* and check the cameras IDs.
IDs are: 0 for dual
5 multilens
4 telephoto related (not sure which mode uses this)
3 wide angle
2 telephoto
1 front camera.
Oneplus can set many IDs as they need according to use.
There is no higher or lower. Dial the code and switch between modes and you will find out yourself.
Changing only 0 id works. But crashes camera sometimes. It needs 5 too. 3, is wide angle. Totally unrelated.
That is why you enable macro support on cameraid 3. Because macro uses that wide angle lens.
Again, i dont mean to be rude. But you are calling my info wrong. Just posting wrong information. It will confuse users. And you are duplicating a thread. It will only create confusion. Please do check your info. Is wrong. I dont want to report the thread as duplicate. But kinda is. Users dont need this clarification or my info doesn't need correction. With all respect. Yours is wrong.
Cheers and all the best! :highfive:
Duplicate topic. Please consolidate discussion in one thread:
[GUIDE]enable 960Fps slow motion like 7t pro!
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.