Database Info

Let's make GCam better!

Since GCam only partially supports the camera of ZF3, I've asked @Arnova8G2 to help us help him improve it. I've probably posted much less info that was asked...
Here's the log from Camera2test:
https://pastecode.xyz/view/dc2c0d0c
The phone model/name is ZE520KL and it has a bigger brother, the ZE552KL, with the same camera.
More info on the model: https://m.gsmarena.com/asus_zenfone_3_ze520kl-8197.php
The camera does record [email protected] videos, differently from what's written in the site above.

Your Api2 is GCam compatible, Test with the latest version and make a logcat
If you want help, be specific about errors and send a logcat.
Must understand that I am not your device.
Help me correct, I work without knowing what to fix.
Thank you

Excellent!
I'll use the version below and I'll send logcats as soon aa possible:
https://www.celsoazevedo.com/files/...f/GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.9.apk

Thats great!! Thanks Arnova8G2.
I think first we have to fix the max resolution:
Ze520kl/ze552kl has max resolution of 16mp (4656 X 3492)
GCAM only shows 9,4mp

pedromms86 said:
Thats great!! Thanks Arnova8G2.
I think first we have to fix the max resolution:
Ze520kl/ze552kl has max resolution of 16mp (4656 X 3492)
GCAM only shows 9,4mp
Click to expand...
Click to collapse
@Arnova8G2 here's the log of the camera starting up.
I don't know if it's useful. Thanks.

pedromms86 said:
Thats great!! Thanks Arnova8G2.
I think first we have to fix the max resolution:
Ze520kl/ze552kl has max resolution of 16mp (4656 X 3492)
GCAM only shows 9,4mp
Click to expand...
Click to collapse
on your Camera2test
Camera 0 (BACK)
[4656x3496, RAW_SENSOR(32), min_dur:33167496, stall:200000000] < ---- is the maximum resolution for image processing
[4096x2304, JPEG(256), min_dur:33333333, stall:425000000] < ---- Maximum resolution to display
[3840x2160, JPEG(256), min_dur:33333333, stall:345000000]
[3264x2448, JPEG(256), min_dur:33333333, stall:258000000]
Camera 1 (FRONT)
[3264x2448, RAW_SENSOR(32), min_dur:33300032, stall:60000000]< ---- is the maximum resolution for image processing
[3264x2448, JPEG(256), min_dur:33333333, stall:258000000] < ---- Maximum resolution to display
[3264x1836, JPEG(256), min_dur:33333333, stall:253000000]
[2560x1920, JPEG(256), min_dur:33333333, stall:243000000]
API 1 do not have the same resolution as API 2
stock camera use API 1, The only app camera used full API2 is google camera

Arnova8G2 said:
on your Camera2test
Camera 0 (BACK)
[4656x3496, RAW_SENSOR(32), min_dur:33167496, stall:200000000] < ---- is the maximum resolution for image processing
[4096x2304, JPEG(256), min_dur:33333333, stall:425000000] < ---- Maximum resolution to display
[3840x2160, JPEG(256), min_dur:33333333, stall:345000000]
[3264x2448, JPEG(256), min_dur:33333333, stall:258000000]
Camera 1 (FRONT)
[3264x2448, RAW_SENSOR(32), min_dur:33300032, stall:60000000]< ---- is the maximum resolution for image processing
[3264x2448, JPEG(256), min_dur:33333333, stall:258000000] < ---- Maximum resolution to display
[3264x1836, JPEG(256), min_dur:33333333, stall:253000000]
[2560x1920, JPEG(256), min_dur:33333333, stall:243000000]
API 1 do not have the same resolution as API 2
stock camera use API 1, The only app camera used full API2 is google camera
Click to expand...
Click to collapse
Meaning that it's not possible to get 16MP from API2?

CygnusBlack said:
Meaning that it's not possible to get 16MP from API2?
Click to expand...
Click to collapse
May be in edit the libs is replaced
[4096x2304, JPEG(256), min_dur:33333333, stall:425000000] by 4656x3496

Arnova8G2 said:
May be in edit the libs is replaced
[4096x2304, JPEG(256), min_dur:33333333, stall:425000000] by 4656x3496
Click to expand...
Click to collapse
Noob question...
Where to find the file(s) to edit?

CygnusBlack said:
Noob question...
Where to find the file(s) to edit?
Click to expand...
Click to collapse
I will do it as soon as I have the time because the file has been edited in hex.
I'll do some libs research and I'll need a tester.

Arnova8G2 said:
I will do it as soon as I have the time because the file has been edited in hex.
I'll do some libs research and I'll need a tester.
Click to expand...
Click to collapse
Count me in!

thread is dead already ?

Arnova8G2 said:
I will do it as soon as I have the time because the file has been edited in hex.
I'll do some libs research and I'll need a tester.
Click to expand...
Click to collapse
Please let me know if any support or help is required i'm in for testing and providing logs.

I can test it too. Please fix it.

ANY NEWS???
Any news about the resolution bug in gcam? I'm waiting for the problem to be solved.

eduardosubtil said:
Any news about the resolution bug in gcam? I'm waiting for the problem to be solved.
Click to expand...
Click to collapse
@Arnova8G2?

Look like he dont care this case

Maybe he's busy. Let's give him some time.

Saktis_STi said:
Maybe he's busy. Let's give him some time.
Click to expand...
Click to collapse
Yeah. It's holiday season after all.

In which question is Gcam better than AsusPixelMaster?

Video stabilization on Lenovo P2

Everything I am going to mention in this post is based on HAL3 and EIS enabled P2 on Oreo roms with the two patches from Astridxx and Highwaystar enabled.
Firstly, some of the Camera apps with manual control:
1. AZ camera
2. One plus camera
3. Footej camera
4. Freedcam
5. Manual camera
6. Open camera
7. Proshot
8. Snap camera
9. HedgeCam 2.2
10. Moment pro cam
11. DSLR camera
12. Camera FV5
13, Bacon camera
and more...
Camera apps with built-in stabilization (or otherwise build prop edit)
1. Paranoid camera (built-in stabilization - works great)
2. AZ camera
3. Footej camera
4. Snap camera
5. Freedcam
6. Update- Quality camera. Link in post 2.
Now regarding my topic:
Everyone knows that by adding a line in build prop enables video stabilization on supported ROMs and camera modules. persist.camera.eis.enable=1 (don't use EIS capital )
But in P2 most camera apps video preview will give you a green screen, yet snapit, motocam, etc, will work but we will get choppy videos with only a bit of stabilization.
NOTE: Gcam ports / Footej camera and almost all other camera apps's 1080p, 720p, 480... video recording will not work after enabling EIS. Only 4 K video works (not much stabilization).
In my research I found out that these camera apps's video preview size is the reason for the green screen.
Solution: Changing the camera "video preview size" to 960p (1280x960).
In the above-mentioned camera apps only Snapcamera has the option to change video preview size. So you can use snapcamera to record stabilized videos till 1440x1080 resolution.
After enabling eis in build.prop you will see an additional tab in snapcamera settings video tab called as "stabilization" (I feel it is auto enabled even if you select it or not).
Selected video resolutions as - 1440x1080, 1280x960, 640x480 , 320x240 - works in Freedcam / Snap camera / AZ camera / Open camera. You can record nice stabilized videos.
Recommended: Freedcam, Snap camera, AZ camera.
Note: Only those camera apps which have the above-mentioned video resolutions will work.
Miscellaneous info:
1. For dark video issue with your current cam app, you can use HTC camera app, the videos are bright enough.
2. May or may not work- for better camera picture quality
Open media_profiles.xml found in system-etc folder
<ImageEncoding quality="100" />
<ImageEncoding quality="100" />
<ImageEncoding quality="100" />
<ImageDecoding memCap="80000000" />
Thank you for reading and please hit the thanks button if I helped.

Another camera app with built-in video stabilization (EIS should be enabled in build prop).
App Name: Quality camera.
Info: No manual controls but I personally feel the picture and video quality is amazing with much reduced noise. Recorded videos are stabilized and are not that dark.
NOTE:
1. You need to disable navigation bar or use expanded desktop from your settings (put the tab in pull down menu) to select camera settings and selecting picture and video modes.
2. You need to select in camera settings photo tab (second tab), change preview size to 1.2M pixels (1280 x 960) or 1.5M pixels (1440 x 1080) otherwise, enabling EIS will give you green screen error.
3. Force close app and restart again.
You will be able to record stabilized videos at 480p, 720p, 960p, 1440 x 1080 (4:3 aspect ratio).
1080p video recording does not work (green screen).
LINK: https://apkpure.com/quality-camera/com.tafayor.qualitycamera

New Nokia camera app with pro mode. Almost all functions working. Check out the link.
https://www.xda-developers.com/nokia-camera-port-3d-personas-animojis/amp/

Hi all,
I want to bring to your attention another pro camera working fine on our P2. Asus pixelmaster.
Link:
https://www.apkmirror.com/apk/zenui...30-3_180920_2m-android-apk-download/download/

Google camera 6.1 working in oreo.
Link:
https://forum.xda-developers.com/showpost.php?p=77915456&postcount=3972

Thank you and bye-bye P2. I moved on to Realme 5 Pro.

Is the 48 mp camera real or fake?

Hi everyone. I'd like to know if anybody could get a 48 mp dng file from this phone. It is strange that raw file is only 12 mp. The quality of the 48 mp jpeg image is poor and seems rather an interpolated from 12 mp. How is possible to get a raw file smaller (12mp) than the original (48mp) ? And many camera aps won't give the jpeg 48 mp option but only the 12 mp. Comparing an original jpeg 40 mp from p20 pro with the one that this phone offers, the difference is tremendous on details and structure. Thanks for reading.

non-pro --> fake
pro --> real

TheMrBinary said:
non-pro --> fake
pro --> real
Click to expand...
Click to collapse
For what reason then, it won't give a 48 mp dng file? And also you cannot have from 48mp jpeg the option 16:9 ? If it was the stock camera limitation, why then, all other camera apps behave the same way?
Speaking always for pro model.

Kodagf said:
Hi everyone. I'd like to know if anybody could get a 48 mp dng file from this phone. It is strange that raw file is only 12 mp. The quality of the 48 mp jpeg image is poor and seems rather an interpolated from 12 mp. How is possible to get a raw file smaller (12mp) than the original (48mp) ? And many camera aps won't give the jpeg 48 mp option but only the 12 mp. Comparing an original jpeg 40 mp from p20 pro with the one that this phone offers, the difference is tremendous on details and structure. Thanks for reading.
Click to expand...
Click to collapse
I did not quite understand what you were saying. The 48MP shots are "real" as Xiaomi claims. For non-stock camera apps, just make sure you have Camera2API option available and enabled to enable 48MP mode. For instance, I enabled the same in Open Camera, and I had the capability to shoot "48MP" in RAW dng format.
And I kinda sorta get what you are trying to say, but I do not know enough about the topic to comment.
Here is one shot from RN7Pro with Open Camera app with Camera2API enabled, saved in jpeg and raw. One is the standard jpeg with resolution 8000 x 6000‬ and 6MB in size, the other is the dng of the same shot with resolution 3984 x 2984 (11.9 MP) as reported by Photoshop with a file size of 22.9 MB:
JPG: https://drive.google.com/file/d/1mKD7i2idv1YBjSFsepTCFShyTJTlPm6t/view?usp=sharing
DNG: https://drive.google.com/file/d/1Y6Xrez8sjFBP3HWI1__HchVtZ7unBTRr/view?usp=sharing
If you plan to compare the RN7 Pro, which costs as much as an early mid-range device, against the Huawei P20 Pro, which is top tier flagship from last year, then you will definitely be disappointed. One phone costs a couple of times the other. So that comparison does not make sense to me.

For a moment I was happy to hear that you were able to shoot 48 mp in raw dng format with open camera, but then I saw the dng file you posted was only 12 mp (a little less perhaps). So, unfortunately, I still am suspicious about what xiaomi claims for the camera since it is not possible to get 48 mp dng file with any app. The size of such a file should be about 45 mb. The quality of images of not 7 pro is excellent but the details are of 12 mp level. I posted an image from mi note 2 (21mp camera) where you can see the difference in details. I wonder if I get such an image from an older phone what should I expect with a newer with the double size of mp in the sensor. I'm afraid we have to do with a xiaomi's trick ......
Ps. Now I see that system made my image much smaller. 243 kb instead of 12 mb (original). you v\cannot get conclusions this way.. sorry.

I had the idea to post a crop of the original image. Take a look.

Ok, I'll explain.
It's a Quad Bayer sensor, what typically results in lack of raw output availability in case of the full res. That's due to the fact that OEMs assume no app would be able to process non-standard array, else they would have to process it on their own, through utilizing stacking (superres?) or simple remosaic. The latter would result in artifacts or loss of quality.
Because of that, all available raw streams come from binning (pixel "merging").
About the quality tho, it's just a Xiaomi thing. All you can currently do is disable the edge mode and denoising in Open Camera. Then your results might get more detailed, possibly at the cost of color fringing. At least, that's the case with Mi 9.
But about RN7 non-Pro, uhh. It has S5KGM1, which doesn't even support any kind of 48 MP mode, so the 48 MP images from RN7, Oppo F11 Pro, Vivo V15 Pro end up being a placebo.

Sorry that I saw your answer after I started a new thread with the same subject. Thanks for all your info. Still I wonder, why we cannot get a 48mp DNG file with any app, like for example on p20 pro that has the same quad bayer technology. And how is possible to get a 12 mp rawfile, from a 48 mp sensor? With p20 pro we can choose between 40 mp dng or 10 mp jpeg with binning technology. Why this is impossible with RN7pro ?

Another question that I have is that: If all available raw streams come from binning, then the 48mp jpeg from where it comes?

Kodagf said:
Another question that I have is that: If all available raw streams come from binning, then the 48mp jpeg from where it comes?
Click to expand...
Click to collapse
Sensor mode itself is a raw stream (typically 10 bit), but drivers are constructed in a way that filters out any quad bayer raw access from third party apps. The 48 MP JPEGs come from processing applied on it by the camera stack.
For further data, you can look on Camera2Test and most importantly, "dumpsys media.camera" command. "sensormode" is the keyword you're looking for in case of the latter. Then you'll get a 8000x6000 mode listed with a third number, which means the framerate, probably around 24 fps.
And anyyyway, disable edge mode and denoising in Open Camera if you want to see something about IMX586 with bare eyes.

j1505243 said:
Sensor mode itself is a raw stream (typically 10 bit), but drivers are constructed in a way that filters out any quad bayer raw access from third party apps. The 48 MP JPEGs come from processing applied on it by the camera stack.
For further data, you can look on Camera2Test and most importantly, "dumpsys media.camera" command. "sensormode" is the keyword you're looking for in case of the latter. Then you'll get a 8000x6000 mode listed with a third number, which means the framerate, probably around 24 fps.
And any way, disable edge mode and denoising in Open Camera if you want to see something about IMX586 with bare eyes.[/QU
Thanks, I can see what you mean. It's a pity thow, that there is no a 48mp dng file which, in bright light might be very interesting , offering hight level of details.... I guess that with 1,75 f and binning, xiaomi's goal is a brighter image in the shortest shooting time. This kind of images are very good for internet media use, but in a big screen they are worse than images from older phones .
Click to expand...
Click to collapse

Kodagf said:
j1505243 said:
Sensor mode itself is a raw stream (typically 10 bit), but drivers are constructed in a way that filters out any quad bayer raw access from third party apps. The 48 MP JPEGs come from processing applied on it by the camera stack.
For further data, you can look on Camera2Test and most importantly, "dumpsys media.camera" command. "sensormode" is the keyword you're looking for in case of the latter. Then you'll get a 8000x6000 mode listed with a third number, which means the framerate, probably around 24 fps.
And any way, disable edge mode and denoising in Open Camera if you want to see something about IMX586 with bare eyes.[/QU
Thanks, I can see what you mean. It's a pity thow, that there is no a 48mp dng file which, in bright light might be very interesting , offering hight level of details.... I guess that with 1,75 f and binning, xiaomi's goal is a brighter image in the shortest shooting time. This kind of images are very good for internet media use, but in a big screen they are worse than images from older phones .
Click to expand...
Click to collapse
Well, as said before, try setting edge mode off with denoising off in Open Camera, with Camera2 mode enabled and 48 MP resolution selected. You'll notice a rather good difference, but be aware of the color artifacts. BTW, the best 48 MP outputs available yet are coming from Honor View 20. Maybe Google will outperform that on Pixel 4, but it's just a guess.
Click to expand...
Click to collapse

Google Camera Port 48MP?

I have been using this Google Camera Port: https://forum.xda-developers.com/showpost.php?p=79723402&postcount=1954
It does say it supports the full 48MP (- Add ultra-resolution compatibility ( 48Mpx )) but I cant seem to get it set above 12MP. Any advice?

Sorry for the bump (is this even a bump??) but here's the answer, I believe: https://forum.xda-developers.com/oneplus-7-pro/themes/google-camera-op7-pro-t3944422
WHY THE FRONT CAMERA IS 4MP AND BACK CAMERA 12MP ?
Selfie camera uses pixel binning, same as for the main sensor. Since camera2api implementation only delivers a 4MP raw stream (16MP/4 = 4MP because of pixel binning)
GCam can only work with what raw stream the API delivers.
Same goes for back cam.

i_pk_pjers_i said:
Sorry for the bump (is this even a bump??) but here's the answer, I believe: https://forum.xda-developers.com/oneplus-7-pro/themes/google-camera-op7-pro-t3944422
WHY THE FRONT CAMERA IS 4MP AND BACK CAMERA 12MP ?
Selfie camera uses pixel binning, same as for the main sensor. Since camera2api implementation only delivers a 4MP raw stream (16MP/4 = 4MP because of pixel binning)
GCam can only work with what raw stream the API delivers.
Same goes for back cam.
Click to expand...
Click to collapse
The answer that OP provides is pretty half-assed. The selfie camera doesn't use pixel binning by default at all, nor does camera2api make it suddenly 4mp. Also, all the Aux cams are subject to the same pixel binning from the gcam app, reducing their quality by a lot. The "Real" answer seems to be that gcam (only OP CAMERA CAN) simply cannot, at the moment, use the full 48mp resolution, and with some probably faulty coding, applies the pixel binning to all other cameras.
---------- Post added at 11:24 PM ---------- Previous post was at 11:16 PM ----------
Mutterz said:
I have been using this Google Camera Port: https://forum.xda-developers.com/showpost.php?p=79723402&postcount=1954
It does say it supports the full 48MP (- Add ultra-resolution compatibility ( 48Mpx )) but I cant seem to get it set above 12MP. Any advice?
Click to expand...
Click to collapse
Main camera captures only at 12 mpx? - yes, gcam is capable of 48 mpx but libs need to be modified. Arnova is working on that. (He hasn't stated if this is impossible or not just yet, he is working on the proyect). Those 12 mpx will be the 48 mpx quad bayered photo. The purpose of this mod will be a full 48 mpx HDR gcam photo working. Fingers crossed.
From first post of this thread: https://forum.xda-developers.com/oneplus-7-pro/themes/gcam-enabling-aux-camera-t3935086

12mp (9-to-1 binning) available on main cam?

As the title asks, can you set the main cam on this to 12mp mode? Should offer smaller file size and better low light performance)

yes with open camera you can set it to 12Mpx don't tested the quality

TF1920 said:
yes with open camera you can set it to 12Mpx don't tested the quality
Click to expand...
Click to collapse
Thanks for that. Would you be able to test and post 27MP (main and open cam) and 12MP (open cam)? Would be fascinating to see the differences.