Related
Hi,
I'm the developer of Open Camera, and looking at the OnePlus 3 as a potential new phone and test device, but I'm curious as to its support for Camera 2 API. I was wondering if people could share their experiences of using third party camera apps with Camera2 API enabled - either in Open Camera, or others like Snap Camera and A Better Camera (all these have options to enable Camera2 API)? In particular:
* It seems a lot of devices have problems with flash and Camera2 (either flash doesn't fire, or misfires so pictures come out under or overexposed). I finally managed to get Open Camera flash working on my Nexus 6, but no luck on a Samsung S7 (precapture doesn't seem to trigger). How does the OnePlus Three do with Camera2 and third party apps?
* I see some reports that manual exposure times don't work (e.g., http://forum.xda-developers.com/oneplus-3/help/camera2-api-broken-oxygenos-3-1-2-t3400886 ), though they mostly refer to the "more than one second" times (which most Android devices don't even offer). I'm less bothered about that, but does manual exposure time (and ISO) work at all (even for less than one second) in Camera2 API on the OnePlus Three?
* Around a year ago I see lots of reports that RAW didn't work on the One Plus devices (either not at all, or pictures were wrong). Supposedly this was fixed, but can anyone confirm that this is working properly on the OnePlus Three?
Thanks in advance!
mark
I use CM 13. So the following observation will most probably differ from Oxygen OS. I hope someone else using the stock ROM provides their input too.
1. Flash is unusable with Open Camera. I tried with Camera2 enabled and disabled. When its enabled, the overexposure is less but overall the picture is still horrible. CM's Snap camera that comes with the ROM works fine however.
2. I have not tested manual exposure yet. Will report back later if no one else does it.
3. There doesn't seem to be any problem while saving RAW files using Camera2 API. Opened it in Ubuntu's image viewer and the image is the same as it's JPEG counterpart (without the flash)
Manual exposure settings work fine. I increased the ISO and exposure time gradually using Open Camera. It let in more light and captured the image without any issues
mdwh said:
* It seems a lot of devices have problems with flash and Camera2 (either flash doesn't fire, or misfires so pictures come out under or overexposed). I finally managed to get Open Camera flash working on my Nexus 6, but no luck on a Samsung S7 (precapture doesn't seem to trigger). How does the OnePlus Three do with Camera2 and third party apps?
* I see some reports that manual exposure times don't work (e.g., http://forum.xda-developers.com/oneplus-3/help/camera2-api-broken-oxygenos-3-1-2-t3400886 ), though they mostly refer to the "more than one second" times (which most Android devices don't even offer). I'm less bothered about that, but does manual exposure time (and ISO) work at all (even for less than one second) in Camera2 API on the OnePlus Three?
* Around a year ago I see lots of reports that RAW didn't work on the One Plus devices (either not at all, or pictures were wrong). Supposedly this was fixed, but can anyone confirm that this is working properly on the OnePlus Three?
Click to expand...
Click to collapse
I've got a OP3 and a bunch of camera apps. The flash is overexposing with Open Camera, but in e.g. Footej (which I believe also uses Camera API v2) the image is exposed similarly to the built-in camera app.
Changing ISO manually seems to work as expected.
RAW files that I've tested from the stock app in Lightroom appear fine.
Let me know if you want me to test something else (PM or email works too).
The biggest challenges I have with Open Camera is that the manual focus (at least in video mode) is somewhat jumpy and not as smooth as e.g. Cinema 4K when you drag the slider, so it is only useable when you're not recording, and then it lacks focus assist (zooming in 2x or 4x automatically when you adjust focus). And then, of course touch focus is also broken (it always focuses at the center) when using APIv2.
Oh, and I'm on the mainly release (3.2.6 atm).
Thanks for both your replies!
Regarding flash and Camera2 API, the newly released Open Camera v1.34 has an option under Settings/Photo settings/"Use alternative flash method". Does that work any better? (Interesting that you mention Footej, that's also the only other 3rd party camera app that gets flash working with Camera2 API on my Nexus 6 - I think it's also using the "torch method" that my new option enables as a workaround.)
Another question I have please - does HDR in Open Camera work okay? (Note it won't be the same as the stock camera's HDR, as these will be different algorithms - but does it at least seem to work? In theory it should if manual exposure is working, but there may be additional issues with burst mode.)
A shame that touch to focus isn't working (this seems to be a known issue with Camera2 on the OnePlus 3?) I note from http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68764646 , comment 329, someone says that touch to focus is fixed in the community build 3.5.2 (they tested Open Camera and Snap Camera HDR), so hopefully this fix will soon be rolled out.
I'll take a look at the jerky manual focus, and focus assist.
Wrt flash: Compared to the built-in camera app and to Footej and with/without the new flash setting enabled, then yes: It works with the work-around enabled. Before enabling it, it overexposes (and has an incorrect color balance), but after enabling it, the photo looks almost identical to the Footej one.
As for HDR, then yes, it also works As you say, it's not identical to the built-in camera app, but there is a difference between a single-capture shot and an HDR one: Shadows are lifted and highlights become somewhat subdued. Comparing an OpenCamera HDR shot to the same scene taken with the built-in camera, I'd say the shadows are similar, but the highlights are less compressed with the default app (i.e. OpenCamera makes the highlights darker, and maybe also darker than need to be).
As for touch focus, then we can hope it will be fixed -- I guess it's a problem with the Camera2 API implementation/driver in OP3.
Thanks for your efforts!
Just to say that I got the OnePlus 3T in the end. It's an excellent device - but I've made a new thread at https://forum.xda-developers.com/oneplus-3t/how-to/camera2-bugs-t3569283 which details the outstanding problems that I seem unable to fix (and seem to affect other camera2 apps too).
Interestingly, touch-to-focus works fine to me (even when I first got it when it was on Android 6), possibly this was something that'd already been fixed.
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
I was thinking if the new portrait mode could be ported to the pixel xl since google is basing it off software and machine learning and not hardware. On a side note do you think the launcher from the xl 2 could also be ported?
i think it uses extra info from the new dual pixel camera
but you never know
there are some talented guys on here who might port it
flex360 said:
i think it uses extra info from the new dual pixel camera
but you never know
there are some talented guys on here who might port it
Click to expand...
Click to collapse
From what i can tell:
Back Camera: obviously uses the dual sensor (NOT dual camera but two sensors). The phone then does some processing with information from second sensor to give you that "portrait mode" effect. Some say it's better than with dual cameras...idk about that
Front Camera: now this is one of the reasons a lot of people, myself included, think that porting might work. Front camera only has one sensor and one lens, just like OG pixel camera. Google uses a software processing and AI similar to what is used in back camera, to do the portrait mode; except this time there's more processing involved to "figure out" the BG vs FG etc (which in the back camera would be assisted by the extra information given by the extra sensor or another camera), which is the main thing with portrait mode effect. However, what I've been told is that there is an extra processor hardware called "gouda" in the pixel 2's that assist in this intensive extra processing.
I'm not sure if the same (use of the "gouda" processor) applies to the obviously less amount of processing required with the two sensors at the back, definitely with only one sensor that is apparently the case.
All in all, it SEEMS that this is impossible as the OG Pixel lacks the extra processor to do the calculations required to mimic portrait mode without a second sensor or lens. This is not even getting into the fact that, a LOT of people say that even with all the calculations nothing beats the portrait mode on the back camera that has all that extra information from the second sensor.
However, my hope is that this new "portrait mode" is at least made available eventually in the app on playstore, perhaps hooking into any extra information available from a second camera or sensor at the back (meaning, for example, other phones that *do* have dual sensors or dual cameras can make use of google's obviously excellent rendering for portrait mode).
I just downloaded the APK for the new camera app and it works fine, you have to do the "keep object centered and move phone up" thing but it works fine, both front and back camera.
EDIT: Also in Android 8.1 the new launcher is coming to the original Pixel, iirc. I just downloaded that APK as well
I also downloaded the new camera apk and have it on my XL as well. It works really well too.
mrlugo88 said:
I also downloaded the new camera apk and have it on my XL as well. It works really well too.
Click to expand...
Click to collapse
Lens blur is similar to portrait mode but it's not exactly the same. Lens blur target focus area is smaller while portrait mode automatically find the object in the foreground and blurs the background.
Sent from my Pixel 2 XL using Tapatalk
biggiestuff said:
Lens blur is similar to portrait mode but it's not exactly the same. Lens blur target focus area is smaller while portrait mode automatically find the object in the foreground and blurs the background.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Hmm interesting. My wife has the smaller 2 and I never even looked in the camera to notice haha. I just assumed it was the same. Well learned something new.
gamemastr said:
I just downloaded the APK for the new camera app and it works fine, you have to do the "keep object centered and move phone up" thing but it works fine, both front and back camera.
EDIT: Also in Android 8.1 the new launcher is coming to the original Pixel, iirc. I just downloaded that APK as well
Click to expand...
Click to collapse
Hi, please share!
https://www.xda-developers.com/pixel-2-portrait-mode-port-non-google-android-oreo/
this seems to work quite nicely without magisk permissions etc if on stock
http://www.androidpolice.com/2018/01/01/get-pixel-2s-portrait-mode-first-gen-pixel-phones-nexus-6p-nexus-5x-mod-apk-download/
this new portrait mode works great but how to you change its default storage location?
I'd like to store the pics in the same location as the stock pixel location.
Thanks
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.
Hey there,
is there any change to get the Stock Samsung Android App as a APK to install on a Samsung A40?
Unfortunately they reduced the Camera App on this device.
how they reduced it ? what are the differences ?
For example on the A40 you can only use the bokeh (live focus) - effect, when the camera detects a face. for no reason.
on the a50 you can use this effect on anything you focused on.
Guess it's just another little way to artificially reduce the functions. Same as the missing always on display.
r0ckster05 said:
For example on the A40 you can only use the bokeh (live focus) - effect, when the camera detects a face. for no reason.
on the a50 you can use this effect on anything you focused on.
Guess it's just another little way to artificially reduce the functions. Same as the missing always on display.
Click to expand...
Click to collapse
I understand your concern mate but there's currently no way to use camera app from other samsung devices. Samsung releases it's own version of apk for specific devices or else blocks the function if the device is different. I wanted to use Night mode present on S10 on my A50, though the build numbers are same, the app doesn't get installed & when it does, it crashes.
You might need root or someone needs to make an universal port of Samsung's apk.
Cheers
I wonder if the reason is the lack of depth camera (A50 has it, A40 does not). The algorithm can detect a face and blur stuff around it. But it has no way of knowing the limits of other objects without depth data.