Visual Core switch missing - Google Pixel 2 XL Questions & Answers

So before I updated to the February build I had the visual core switch in developer options. I think it said CAL HDR+ or something like that. After updating yesterday, I factory reset my phone, and then enabled developer options again...only this time the option to turn on the visual core is missing. Is it now just on by default with the February update?
Sent from my [device_name] using XDA-Developers Legacy app

Yes, it's on by default...

The February update enables the visual core for 3rd party services. For example snapchat on android phones because there are so many devices and setups what snapchat does is uses the camera view finder to get the pictures and then captures what's on the screen to take the pictures or video. That's why iPhones always have better snapchat photos and videos.
Now since Google has released the visual core to 3rd parties. What snapchat can do no is actually take full advantage of the camera on our phones

clapper66 said:
The February update enables the visual core for 3rd party services. For example snapchat on android phones because there are so many devices and setups what snapchat does is uses the camera view finder to get the pictures and then captures what's on the screen to take the pictures or video. That's why iPhones always have better snapchat photos and videos.
Now since Google has released the visual core to 3rd parties. What snapchat can do no is actually take full advantage of the camera on our phones
Click to expand...
Click to collapse
Yeah but I just meant there used to be a switch for it in developer options. The switch is no longer there after the February update. Just making sure it was turned on officially and there was no need for the switch any more.

v2.2v said:
Yeah but I just meant there used to be a switch for it in developer options. The switch is no longer there after the February update. Just making sure it was turned on officially and there was no need for the switch any more.
Click to expand...
Click to collapse
that is exactly the case.

Related

Camera app with HDR+ enabled

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.

Camera2-API fixed for 3rd-party camera apps or not?

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.

How to imporve App Camera?

Default Camera App of Xiaomi Redmi Note 5/Pro is not bad!
But when another apps using camera (such as facebook, google Duo...), the picture quality is realy bad? i khow it doen't/isn't because of sensor'quality!
So How to imporve App Camera?
Tks
I always try to take photos with the camera app and then share to other apps, rather than take from within Facebook, hangouts, Viber, WhatsApp, etc. Most of those apps will still compress the image a bit also, so better starting with the best quality image, ie straight from the actual camera app itself.
Sent from my Redmi Note 5 using Tapatalk
gsmyth said:
I always try to take photos with the camera app and then share to other apps, rather than take from within Facebook, hangouts, Viber, WhatsApp, etc. Most of those apps will still compress the image a bit also, so better starting with the best quality image, ie straight from the actual camera app itself.
Sent from my Redmi Note 5 using Tapatalk
Click to expand...
Click to collapse
But it takes many time and inconvenience. Can any one replace default csmera API for app with better one?
dynamic503 said:
But it takes many time and inconvenience. Can any one replace default csmera API for app with better one?
Click to expand...
Click to collapse
You can't change what API an application uses, some apps take advantage of camera2 api. If any of the ones your using do and you haven't enabled camera2 api with magisk or either i think it's a build.prop edit, then there likely to be defaulting to camera1 api that's my guess at least.
This assumes your using a custom rom, i'm not sure if camera2 api is enabled by default with MIUI or if it requires root.Your primary camera app can take advantage of binary, blobs drivers that the third party apps may not necessarily benefit from, no perfect solution try it and see.
gsmyth said:
I always try to take photos with the camera app and then share to other apps, rather than take from within Facebook, hangouts, Viber, WhatsApp, etc. Most of those apps will still compress the image a bit also, so better starting with the best quality image, ie straight from the actual camera app itself.
Sent from my Redmi Note 5 using Tapatalk
Click to expand...
Click to collapse
Alister. said:
You can't change what API an application uses, some apps take advantage of camera2 api. If any of the ones your using do and you haven't enabled camera2 api with magisk or either i think it's a build.prop edit, then there likely to be defaulting to camera1 api that's my guess at least.
This assumes your using a custom rom, i'm not sure if camera2 api is enabled by default with MIUI or if it requires root.Your primary camera app can take advantage of binary, blobs drivers that the third party apps may not necessarily benefit from, no perfect solution try it and see.
Click to expand...
Click to collapse
I have enabled camera api2 already. For google camera. The pic quality is very good. But how can another camera app can use that camera driver?
dynamic503 said:
I have enabled camera api2 already. For google camera. The pic quality is very good. But how can another camera app can use that camera driver?
Click to expand...
Click to collapse
I've asked this type of thing before, and had a few developers try to answer it it's messy. The idea is Samsung, LG, Xiaomi every manufacturer has there own default rom.
They call theirs stock, that's their version of stock, it's customised only AOSP is truly stock, but the manufacturers versions of their "own" stock roms include a binary also referred to as binary, blobs, it's pretty much a closed source driver each manufacturer makes so their default camera looks amazing.
A general idea is replacing stock rom from any manufacturer with any that isn't based of their "own" stock rom isn't going to include their camera driver as it's closed source, so developers can't use it, they can get the cameras working but they don't look great compared to stock with binary. Lots of people avoid custom roms lineage os aosp ect for this reason video calls, all apps using the camera look terrible.
Two exceptions google open sources there camera drivers and oneplus might be some rare others, in these cases camera quality is expected to be the same while using lineage os or aosp.
I'm not 100% sure if all apps use camera1 and camera2 api if you try look for whatsapp or google duo i couldn't confirm it for them, snapchat uses camera1 api instagram uses camera2 api, but maybe some apps don't benefit from camera2 api at all i'm unsure.
I also tried asking if google camera ports, look better on stock roms that have the binary driver from companies, compared to lineage os ect that don't have it, but that's unclear as even tho i'm 100% sure the binary from manufacturers benefit there own made camera apps, i'm not 100% if the binary benefits all third party apps, but i guess it does, as that's likely the reason all apps look worse moving away from stock roms.
Google camera ports may look great on roms without, the binary as they simply make use of camera2 api which doesn't really require anything from the closed source driver, which would explain why everyone raves about google camera ports on lineage os ect been great, before camera 2 api never saw people been overly impressed about camera apps with missing binary drivers.
Are you on MIUI or something else? you did say the stock camera app not google camera looks good and everything else looks worse, if your still on MIUI then maybe they don't have a binary or simply one that only effects there own camera app, you mentioned the camera lens quality also it's mostly software driver optimisations per individual app ect influencing it's quality.
You asked how to make other apps use google cameras driver, well google camera is benefiting from camera2 api that isn't a driver at all, however it is a requirement similar aspect to a driver it's up to each app developer if there going to make there, application benefit from camera1 api or camera2 api or not at all, so you cant force apps to use it when the developer of that app never implemented camera2 api to begin with, you enable camera2 api for google camera because custom roms and lots of phones don't have it enabled at all. Some phones sold from stores have camera2 api enabled out of the box.
I do actually wish there was a way to fix this, as i've thought about this myself, i did ask a question here about the same type of thing you can read it if you like.
https://android.stackexchange.com/questions/200073/stock-os-vs-custom-proprietary-camera
also this the different levels of camera2 api supported depending on your phone
https://www.androidexplained.com/camera2-api-support/
the only other idea, i have is if the rom you use lets you choose the stock camera app to use and you change that to google camera and whatever, but i'm sure that's wishful thinking as when you do a video call an app will likely default to it's own camera even if you do that, but couldn't hurt to try it i guess!
Alister. said:
I've asked this type of thing before, and had a few developers try to answer it it's messy. The idea is Samsung, LG, Xiaomi every manufacturer has there own default rom.
They call theirs stock, that's their version of stock, it's customised only AOSP is truly stock, but the manufacturers versions of their "own" stock roms include a binary also referred to as binary, blobs, it's pretty much a closed source driver each manufacturer makes so their default camera looks amazing.
A general idea is replacing stock rom from any manufacturer with any that isn't based of their "own" stock rom isn't going to include their camera driver as it's closed source, so developers can't use it, they can get the cameras working but they don't look great compared to stock with binary. Lots of people avoid custom roms lineage os aosp ect for this reason video calls, all apps using the camera look terrible.
Two exceptions google open sources there camera drivers and oneplus might be some rare others, in these cases camera quality is expected to be the same while using lineage os or aosp.
I'm not 100% sure if all apps use camera1 and camera2 api if you try look for whatsapp or google duo i couldn't confirm it for them, snapchat uses camera1 api instagram uses camera2 api, but maybe some apps don't benefit from camera2 api at all i'm unsure.
I also tried asking if google camera ports, look better on stock roms that have the binary driver from companies, compared to lineage os ect that don't have it, but that's unclear as even tho i'm 100% sure the binary from manufacturers benefit there own made camera apps, i'm not 100% if the binary benefits all third party apps, but i guess it does, as that's likely the reason all apps look worse moving away from stock roms.
Google camera ports may look great on roms without, the binary as they simply make use of camera2 api which doesn't really require anything from the closed source driver, which would explain why everyone raves about google camera ports on lineage os ect been great, before camera 2 api never saw people been overly impressed about camera apps with missing binary drivers.
Are you on MIUI or something else? you did say the stock camera app not google camera looks good and everything else looks worse, if your still on MIUI then maybe they don't have a binary or simply one that only effects there own camera app, you mentioned the camera lens quality also it's mostly software driver optimisations per individual app ect influencing it's quality.
You asked how to make other apps use google cameras driver, well google camera is benefiting from camera2 api that isn't a driver at all, however it is a requirement similar aspect to a driver it's up to each app developer if there going to make there, application benefit from camera1 api or camera2 api or not at all, so you cant force apps to use it when the developer of that app never implemented camera2 api to begin with, you enable camera2 api for google camera because custom roms and lots of phones don't have it enabled at all. Some phones sold from stores have camera2 api enabled out of the box.
I do actually wish there was a way to fix this, as i've thought about this myself, i did ask a question here about the same type of thing you can read it if you like.
https://android.stackexchange.com/questions/200073/stock-os-vs-custom-proprietary-camera
also this the different levels of camera2 api supported depending on your phone
https://www.androidexplained.com/camera2-api-support/
the only other idea, i have is if the rom you use lets you choose the stock camera app to use and you change that to google camera and whatever, but i'm sure that's wishful thinking as when you do a video call an app will likely default to it's own camera even if you do that, but couldn't hurt to try it i guess!
Click to expand...
Click to collapse
Thankyou very much. But sad. Because many cheaper phone have better facebook messenger video call quality.
dynamic503 said:
Thankyou very much. But sad. Because many cheaper phone have better facebook messenger video call quality.
Click to expand...
Click to collapse
Your welcome, hmm what phones have you seen with better video call quality on facebook messenger? i assume you have compared to more expensive phones.
That just becomes confusing, since for example just because a bunch of apps use camera2 api doesn't mean they will all be the same, software optimisations determine if it looks better or worse.
I would have assumed facebook's software was exactly the same for each phone it has been put on, unless it's simply the case these cheaper phones your speaking of are benefiting from a closed source driver, and for some crazy reason xiaomi phones don't have a binary for it, guess i'll look into that at some point.
Now that i've got this phone, yes xiaomi's camera app in particular is very good photo quality, better then any camera app i've seen on any custom rom very adjustable.
Worth noting i installed lineage os that had the xiaomi's default camera included in the rom i compared the quality to when i was using stock camera on miui itself, i couldn't see any differences in picture quality, which suggests to me perhaps xiaomi's camera isn't using any closed source driver, binary at all and it's quality is simply optimisations and the fact there's no binary driver is why there other apps look worse.
Just guessing at this point, but that's about the only scenario i think makes sense.
Just remembered there's a new thing called Project Treble the note 5 pro can upgrade to be treble compatible i have the note 5 ai so i got treble out of the box the crux is, if you flash a rom well a treble rom is called a GSI, generic system image a benefit of this, if it allows you to keep the vendor partition untouched while using custom roms, the vendor partition is where the closed source driver is and does mean a custom rom can use those drivers as they haven't been removed.
So it would mean custom roms with good camera/videos of course Treble is so new, so who noes if that's working properly yet! and it would assume xiaomis phones had closed drivers, if your not using miui and camera is bad then no surprise try go back to miui you never said what you use.
anyways you can read about that here.
https://www.androidpolice.com/2018/05/13/project-treble-impact-android-custom-rom-community/
it points out the stuff about cameras and roms.
Alister. said:
Your welcome, hmm what phones have you seen with better video call quality on facebook messenger? i assume you have compared to more expensive phones.
That just becomes confusing, since for example just because a bunch of apps use camera2 api doesn't mean they will all be the same, software optimisations determine if it looks better or worse.
I would have assumed facebook's software was exactly the same for each phone it has been put on, unless it's simply the case these cheaper phones your speaking of are benefiting from a closed source driver, and for some crazy reason xiaomi phones don't have a binary for it, guess i'll look into that at some point.
Now that i've got this phone, yes xiaomi's camera app in particular is very good photo quality, better then any camera app i've seen on any custom rom very adjustable.
Worth noting i installed lineage os that had the xiaomi's default camera included in the rom i compared the quality to when i was using stock camera on miui itself, i couldn't see any differences in picture quality, which suggests to me perhaps xiaomi's camera isn't using any closed source driver, binary at all and it's quality is simply optimisations and the fact there's no binary driver is why there other apps look worse.
Just guessing at this point, but that's about the only scenario i think makes sense.
Just remembered there's a new thing called Project Treble the note 5 pro can upgrade to be treble compatible i have the note 5 ai so i got treble out of the box the crux is, if you flash a rom well a treble rom is called a GSI, generic system image a benefit of this, if it allows you to keep the vendor partition untouched while using custom roms, the vendor partition is where the closed source driver is and does mean a custom rom can use those drivers as they haven't been removed.
So it would mean custom roms with good camera/videos of course Treble is so new, so who noes if that's working properly yet! and it would assume xiaomis phones had closed drivers, if your not using miui and camera is bad then no surprise try go back to miui you never said what you use.
anyways you can read about that here.
https://www.androidpolice.com/2018/05/13/project-treble-impact-android-custom-rom-community/
it points out the stuff about cameras and roms.
Click to expand...
Click to collapse
Vivo V9 ... have better facebook video call quality...
Thankyou for your information
Camera performance in WhatsApp is very poor for rn5 pro selfie camera. How it could be improved ?
mjnabi said:
Camera performance in WhatsApp is very poor for rn5 pro selfie camera. How it could be improved ?
Click to expand...
Click to collapse
No way now. Plz all of us report to Xiaomi
Yes plz report to Xiaomi

Camera Configuration Problems

Since update to Android 11 / UI 3.1 I am not able to set photo or video sizes. There is no such option in the configuration menu.
Mu phone is Note 10+ Exynos version
Any hint, please?
Those settings were removed much earlier. I don't recall exactly when, videos about this emerged on YouTube already in sep 2019...
You can only aspect ratio in camera app, but not resolution/quality. Resolution can be changed in Galery or other app afterwards only.
OnnoJ said:
Those settings were removed much earlier. I don't recall exactly when, videos about this emerged on YouTube already in sep 2019...
You can only aspect ratio in camera app, but not resolution/quality. Resolution can be changed in Galery or other app afterwards only.
Click to expand...
Click to collapse
Many Thanks
You're probably wright. I was using a third party camera app, and only now I noticed that.

Question Camera question from other users

Hello everyone!
I have the phone for over 10 months, and I as many of you can see, Vivo's main selling point is their camera.
I love the photos which comes out of the device, but after the Beta update to A13 which I did back in the beginning of December 2022, I noticed while I was out and shooting some pics and taking video footage with the device that when you switch to Video mode (no matter if it's in the Stock camera or 3rd party apps like FilmicPro), I am unable to change the lenses which I would like to shoot with? I am left only with the 1x Wide camera lens, and at the Stock app camera app, when I select 2x in the video mode, it just crops-in.
I was chit-chatting with Vevo's support a couple of times, over their live chat, sending emails, countless messages over their official Instagram page (where I was left on "seen" only).
The only "true" answer which I got from their support while I was chatting live with their support a few months back regarding this issue was that it will be put in Priority to be fixed in their future updates.
Now, since December (almost 6 months), I am left with this 1000+ euro expensive device, where I cannot use the other lenses in video mode, in the stock app and in 3rd party apps?
Like, excuse me, but as I mentioned at the beginning, they are mentioning "Professional Photography", but the other lenses are also good for shooting "Professional Videography" as far as I can say. LOL
They also suggested me to send my device to their official repair shop in the nearby countries where I live, so they can downgrade it to A12 -- Are you kidding me? I just want the ****ing update, not wiping my device. Principle.
I would like to ask you all, if you could check on your phone when you open your stock Camera app, or any 3rd app pro camera app, if you have the ability to change the lenses for shooting the video?
My build version: PD2185BF_EX_A_13.1.11.15.W30
aleksandar069 said:
Hello everyone!
I have the phone for over 10 months, and I as many of you can see, Vivo's main selling point is their camera.
I love the photos which comes out of the device, but after the Beta update to A13 which I did back in the beginning of December 2022, I noticed while I was out and shooting some pics and taking video footage with the device that when you switch to Video mode (no matter if it's in the Stock camera or 3rd party apps like FilmicPro), I am unable to change the lenses which I would like to shoot with? I am left only with the 1x Wide camera lens, and at the Stock app camera app, when I select 2x in the video mode, it just crops-in.
I was chit-chatting with Vevo's support a couple of times, over their live chat, sending emails, countless messages over their official Instagram page (where I was left on "seen" only).
The only "true" answer which I got from their support while I was chatting live with their support a few months back regarding this issue was that it will be put in Priority to be fixed in their future updates.
Now, since December (almost 6 months), I am left with this 1000+ euro expensive device, where I cannot use the other lenses in video mode, in the stock app and in 3rd party apps?
Like, excuse me, but as I mentioned at the beginning, they are mentioning "Professional Photography", but the other lenses are also good for shooting "Professional Videography" as far as I can say. LOL
They also suggested me to send my device to their official repair shop in the nearby countries where I live, so they can downgrade it to A12 -- Are you kidding me? I just want the ****ing update, not wiping my device. Principle.
I would like to ask you all, if you could check on your phone when you open your stock Camera app, or any 3rd app pro camera app, if you have the ability to change the lenses for shooting the video?
My build version: PD2185BF_EX_A_13.1.11.15.W30
Click to expand...
Click to collapse
I think you should do a factory reset.
Mine same version work great.
zaeb hole said:
I think you should do a factory reset.
Mine same version work great.
Click to expand...
Click to collapse
On the A13 beta?
You are able to change the lenses in 3rd party apps when shooting video?

Categories

Resources