tl;dr
I opened the blobs in a hex editor and changed two numbers
Magic!
Preface
This is my attempt at an explanation of what I think is wrong with the Mi Note 2 camera. My overall knowledge of all subjects involved is pretty limited and i may be downright wrong.
But, as wrong as I may be, what I found seems to actually fix something.
This development was motivated by the lack of working Google Camera mods on the Mi Note 2.
And I was, fortunately, somewhat successful!
If this is what you are looking for, go ahead and visit the Google Camera thread here https://forum.xda-developers.com/mi-note-2/how-to/fix-camera-sensor-gcam-mod-t3782495
My goal with this thread is to share what I did, not only the files, but also the thought process behind the changes. You are free to do with them as you wish.
I am also opening discussion on the topic, if anyone more knowledgeable then me wants to chime in and help, I'd be extremely thankful.
I'll keep updating and editing this post with new information and any developments.
Intro
Let's start with what we know about our phone.
The Xiaomi Mi Note 2 has a 22,5MP Sony IMX318 CMOS image sensor.
This sensor has:
an Active Resolution of 5488 x 4112.
an Unit Cell Size of 1µm
a 6,31x Crop Factor.
What's wrong
With this information in mind, let's take a look at the libmmcamera_imx318.so file:
Snippet of file opened in Hex Workshop:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is wrong.
Why it is wrong
Although I have no definitive answer as to why, I can make a few conjectures.
Only one Sony sensor has a 5344 x 4016 active resolution, a 1,12µm unit cell size and a 5,78x crop factor.
That's the Sony IMX230. Released in April 2015. Found inside a dozen phones and predecessor to the IMX318.
Maybe Xiaomi was planning to use this sensor inside the Mi Note 2 and on a last minute decision chose to go with the IMX318.
This change was hastily implemented and some leftover crumbs remained in the code.
The Fix
The only thing I changed was the active array size. I changed it from 5344 x 4016 to 5488 x 4112.
I'm currently testing the consequences of fixing the other incorrect values and further exploring the file for more inaccuracies.
Why it works
For this we need to take a look at the code for our Camera HAL3:
C++:
[B]Snippet from file: /QCamera2/HAL3/QCamera3CropRegionMapper.cpp[/B]
/*===========================================================================
* FUNCTION : update
*
* DESCRIPTION: update sensor active array size and sensor output size
*
* PARAMETERS :
* [user=285871]@active[/user]_array_w : active array width
* [user=285871]@active[/user]_array_h : active array height
* [user=8139033]@sensor_[/user]w : sensor output width
* [user=8139033]@sensor_[/user]h : sensor output height
*
* RETURN : none
*==========================================================================*/
void QCamera3CropRegionMapper::update(uint32_t active_array_w,
uint32_t active_array_h, uint32_t sensor_w,
uint32_t sensor_h)
{
// Sanity check
if (active_array_w == 0 || active_array_h == 0 ||
sensor_w == 0 || sensor_h == 0) {
ALOGE("%s: active_array size and sensor output size must be non zero",
__func__);
return;
}
if (active_array_w < sensor_w || active_array_h < sensor_h) {
ALOGE("%s: invalid input: active_array [%d, %d], sensor size [%d, %d]",
__func__, active_array_w, active_array_h, sensor_w, sensor_h);
return;
}
mSensorW = sensor_w;
mSensorH = sensor_h;
mActiveArrayW = active_array_w;
mActiveArrayH = active_array_h;
// Derive mapping from active array to sensor output size
// Assume the sensor first crops top/bottom, or left/right, (not both),
// before doing downscaling.
// sensor_w = (active_array_w - 2 * crop_w) / scale;
// sensor_h = (active_array_h - 2 * crop_y) / scale;
float scale_w = 1.0 * active_array_w / sensor_w;
float scale_h = 1.0 * active_array_h / sensor_h;
float scale = MIN(scale_w, scale_h);
uint32_t crop_w = 0, crop_h = 0;
if (scale_w > scale_h) {
crop_w = (active_array_w - sensor_w * active_array_h / sensor_h)/2;
} else {
crop_h = (active_array_h - sensor_h * active_array_w / sensor_w)/2;
}
mSensorCropW = crop_w;
mSensorCropH = crop_h;
mSensorScale = scale;
ALOGI("%s: active_array: %d x %d, sensor size %d x %d", __func__,
mActiveArrayW, mActiveArrayH, mSensorW, mSensorH);
ALOGI("%s: mSensorCrop is [%d, %d], and scale is %f", __func__,
mSensorCropW, mSensorCropH, mSensorScale);
}
This sanity check in particular
C++:
if (active_array_w < sensor_w || active_array_h < sensor_h) {
ALOGE("%s: invalid input: active_array [%d, %d], sensor size [%d, %d]", __func__, active_array_w, active_array_h, sensor_w, sensor_h);
return;
}
The active array size can never be smaller than the sensor output size.
The sensor output size is our desired output resolution. The resolution in which we want to take photos or capture videos.
The camera HAL then takes our active array size and crops it to the desired output size. It can't do the opposite. The active array size is the highest possible image size the CMOS is capable of outputting.
So what happens when the driver file is telling the camera HAL the active array size is 5344 x 4016 and the sensor output size is 5488 x 4112? It returns an exception.
Some software don't catch this exception and crash. The google camera for example.
Other software catch the exception and assume the 5488 x 4112 sensor output resolution isn't supported. That is what the Camera Hal is telling it. So they try capturing the photo with a lower resolution. This is why we get cropped photos in apps like WhatsApp.
And although I have only looked at the Camera HAL3 code. We can assume the Camera HAL1 code is affected by the same issue.
The other files
On my device the libmmcamera_imx318_primax.so file is the only I need to edit.
I can safely delete both libmmcamera_imx318.so and libmmcamera_imx318_semco.so files from my Mi Note 2 with no consequence.
But not every smartphone is built the same. For example, the Redmi Note 4 can have a Sony, Samsung or Omnivision camera sensor.
The Mi Note 2 isn't as drastic, every Mi Note 2 has a Sony IMX318. But it can come from a few different camera model vendors.
So, I'm assuming the different blobs are for camera models built and sold by Sony, Semco and Primax, all using the Sony IMX318 CMOS.
All these files have the incorrect active array size. The change was the same.
What about the front camera?
I'll edit this bit with info about the change to the front camera blobs. The change was similar but the reasoning was different.
Latest blobs
All these files are located inside /vendor/lib/
Original blobs were taken from MIUI 8.4.12. Edited on 03-05-2018.
https://mega.nz/#!JWoVBCTR!VrThENYfBBO4GMs31obnn4Z8QkBhEASEdNP3FBSOOjw
Hex Workshop Bookmark Files
libmmcamera_imx318_primax.so https://mega.nz/#!sfh2jSRK!pZJQ0dJIyJxv_yXeFMrkt3OkGyD7I0vPrxRobCQjBlw
Some sources
gmsarena page for the Mi Note 2 https://www.gsmarena.com/xiaomi_mi_note_2-8014.php
Sony IMX318 product brief https://www.sony-semicon.co.jp/products_en/IS/sensor1/img/products/ProductBrief_IMX318_20161122.pdf
Sony IMX230 product brief https://www.sony-semicon.co.jp/products_en/IS/sensor1/img/products/ProductBrief_IMX230_20150427.pdf
QCamera3 Crop Region Mapper source code https://source.codeaurora.org/quic/...ee/QCamera2/HAL3/QCamera3CropRegionMapper.cpp
Thanks
Thank you to everyone who participated on the Google Camera thread and helped get it to work.
Thank you @Psy_Man for the chat about this issue.
Thank you @defcomg. Your work on the OP3 sent me in the right direction. https://www.celsoazevedo.com/files/android/google-camera/op3fix/
Amazing!!!
You've done a really great job!!! I changed all the file in /vendor/lib. Suddenly the external apps like whatsapp or instagram stopped to crop the photo taken!
In addiction HDR+ works in a lot of google camera! Thank you a lot!
Official lineage os
Doesn't appear to work in stock based ROMs.
Globe ROM latest weekly based on xiaomi.eu
After reboot fail to connect to camera in any app.
Just a heads up to others wanting to try this.
*Edit* flash able zip in other thread works perfectly though.
What the hell, what I'm supposed to do with this?
Can u make some more clear Tutorial or something?
Or maybe I'm just sleepy and I can't understand XD
Nvm, great job, maybe I'll be somehow able to do that tomorrow and check it
Yeah,great job but could you make it simple for the noobies like me? Thanks ?
all I can say is this is such a great work.
now gcam works even with portrait mode
only problem is the camera lags at rare times, don't know why
For me the camera in other apps such as WhatsApp, Instagram, etc keeps autocropping while in camera mode, instead when you make the photo it's correctly saved. I just applied the mod cam and followed all the steps in raccomandation notes, but I haven't solved. My phone is a Mi Note 2, I'm on Aosp extended. In GCam app it's working correctly
TWRP package, tested on miuiPOLSKA rom.
Reuplad, sorry.
V2 really copies files.
I tested, both photo, some random old ones and made after modification. Both have a size of 5488 x 4112. So nothing changed about the resolution.
@Mimi Mix
I did copy the provided files into /Vendor/lib folder, but for now, I can't open any camera apps.
Can you provide a simple step by step procedure in order to achieve your post please ?
Edit : did work back by manually copying @mstdzw uncompressed files to my /vendor/lib
Thanks
Maybe we need some transplants from other device?
Not so much devices https://www.kimovil.com/pl/lista-telefony-za-model-soczewki/sony-imx318-exmor-rs
@everyone
The point of this thread was mostly to share what I did and get more knowledgeable people to help.
If all you want is to copy the files and see what or if it fixes anything for you, just go grab the installer from my other thread: https://forum.xda-developers.com/mi-note-2/how-to/fix-camera-sensor-gcam-mod-t3782495
or use the one provided by @mstdzw
mstdzw said:
Maybe we need some transplants from other device?
Not so much devices https://www.kimovil.com/pl/lista-telefony-za-model-soczewki/sony-imx318-exmor-rs
Click to expand...
Click to collapse
This is what I'm gonna start looking into today! I've managed to get my hands on another device's blobs and I'm going to start hacking around.
macho_man said:
For me the camera in other apps such as WhatsApp, Instagram, etc keeps autocropping while in camera mode, instead when you make the photo it's correctly saved. I just applied the mod cam and followed all the steps in raccomandation notes, but I haven't solved. My phone is a Mi Note 2, I'm on Aosp extended. In GCam app it's working correctly
Click to expand...
Click to collapse
The viewfinder is bugged. I haven't found out why yet. Maybe something wrong inside the libchromatix files?
The good thing is, it's just that, the viewfinder, now photos get taken correctly!
I believe this is the same issue that's causing the smaller viewfinder in google camera's 4K video recording and the recently released Google Lens inside the Google App.
Related
(I'm only two days into WP7, so don't smack me too hard.)
While attempting to debug some Windows Phone 7 behavior via RustyGrom's unlocked images, I stumbled across the whole "/h/ttps issue". This forced me to re-look at how the original mod was performed.
The original method, as outlined in this blog post, involves manipulating the read-only portion of the system registry -- default.hv. Doing so invalidates its baked in signature, wrecking havoc (manifesting itself as broken /h/ttps and other assorted crappiness).
To work around this, I instead made a change to an internal function within AppMetadata.dll, causing all requests to blacklist to return empty handed. (A one byte change at 0xAC8A, 75->EB.) That unlocks the applications on the splash screen.
To unlock the "settings", however, is a trickier matter and involves those irritating "SecureItem" values and the parsing code within SplashSettingsDll.dll. (If you're wondering what the GUIDs mean, there's a translation to canonical names in 8C9C0C34-B77D-45FB-9E4E-D53AC5900244.rgu).
Code:
Themes = {165705CD-200B-4b23-961D-E3F66F844514}
Sounds = {92F34415-4D78-4430-9933-D2DEEA0C9D3D}
FlightMode = {1DEF9B7D-2322-40eb-A007-16A75D5CDA62}
Accessibility = {C5A90F1C-112F-43d3-8C80-C5D1746F3B68}
WiFi = {291A7CF3-48C4-4319-A6F6-E4BABFCCB8E8}
Bluetooth = {BFBBBF37-35E3-447b-BE65-DFC149EF614F}
Location = {41954AAF-E1C4-4b81-A5EC-A5C8961FE34C}
CellularConn = {FD427838-F373-40a3-9FEC-76C6CFFAFC04}
Accounts = {87F5E764-4AB3-4664-B2A3-BE00A2E8AF4A}
Brightness = {B7AFEE4D-7738-48df-8CA4-588D14AE256B}
TouchKeyboard = {071692BE-EC17-463e-94C7-64FB874A6180}
Regional = {E37398A2-CEAD-423c-9EC2-F43251C0B2CE}
DateTime = {9CB05CAE-D2CF-4409-8E64-352DD8F6FDE2}
PhoneLock = {37966764-79C8-4090-A8CF-FB65D638E529}
Updates = {C956380A-087F-4548-A5F6-CEF3616A55DA}
About = {9DAD8821-3F8C-474f-AB2B-D120BA03AFDC}
Speech = {7D878951-E418-46a3-AF6B-DCB45CD375B9}
Contacts = {2D267C1E-C53A-4718-8032-FAC545DDDF8C}
Photos = {864AAEB9-9419-40f9-BA88-03E986859450}
Messaging = {D651D70D-B141-4d71-8FFB-1004C24FB12B}
Phone = {83171528-D3B9-49b6-BC05-BBB3B4B25460}
IE = {A7DD1D7D-C7CA-4566-A5E7-015C7940276E}
Maps = {21EF1D0A-5EBE-4056-9622-2D9615C967E1}
Search = {90A593C1-F945-4bf7-AB56-A999E425F16F}
OfficeMobile = {5962CFCF-8008-4d55-B048-BDCDD7A90EAB}
Games = {B193A538-115B-4789-93D1-F3981B9D7B11}
Radio = {18916419-df98-4042-bb27-6ae39dbc3310}
FindMyPhone = {1691B767-686D-4934-A844-C0057C6024A0}
Feedback = {BF0D001A-1988-4cf3-81E1-16A1CCAB5DA3}
Marketplace = {1D36BBB8-9EEE-4e30-A72B-77ED9CFF11D1}
Unfortunately, Microsoft decided to put required data in these SecureItem values. It appears this data drives what order the application shows in the Settings list and/or the "type" of task. (Unsure about that last bit.) If this data is empty -- for example, I skip over all the SecureItem parsing -- the item vanishes.
I wrote some assembly to simulate returning order data, in an incrementing fashion (10, 20, 30, ...) -- which was fun -- but utterly useless. I'm obviously not putting this data where it wants it to be. I believe the second parameter to an internal function that handles enumerating all the SecureItems (va 41415066/offset 0x4266) is some sort of structure (with two members?) that's key here.
Without a debugger, probing this structure is nearly impossible -- I'm open to ideas here... The only idea I have is making the application crash on "executing" those members, then using the output window to get the values... but this'll be super difficult to pull off.
(If you could convince a mod to lift the restrictions on my account, that'd be wonderful. I can't post links or do anything useful.)
Thanks for the work.
mod speaking: about the link as you are a new member you need 5 posts before you can post link so only one post left until you can edit and post comment
Great work! One thing I thought about, what about just editing the RGU files to get to the same goal of writing to the registry? It seems like those are applied at boot time and presumably wouldn't be under the 'read only'.
RustyGrom said:
Great work! One thing I thought about, what about just editing the RGU files to get to the same goal of writing to the registry? It seems like those are applied at boot time and presumably wouldn't be under the 'read only'.
Click to expand...
Click to collapse
I don't know much about those files, but each RGU file has a corresponding DSM which appears to have certificate information. I'll see what happens tho. (I'm guessing these files were designed for OEM use.)
Update: Yeah, as I thought. The (signed) default.hv references the RGUs, so you can't just rip one out. And you can't tinker inside because they're signed. You can't replace the DSM either because its root certificate is checked against the baked in few (similar to desktop Windows). Ahhhh. We might be forced to patch up the boot/kernel binaries... that sucks tho.
Update 2: ... and no, you can't replace the RGU/DSM pair with a "valid" one. The files are SHA160 hashed, with the first 16 bytes put into default.hv -- HKEY_LOCAL_MACHINE\System\ObjectStore\RegistryUpdate. I suppose since the hash is truncated, you could -- in theory -- edit a RGU until it generated a similar hash... but that's crazy talk.
Keep up the good work Rafael, I'm sure you will figure out a way around it. You always find the craziest ways around Microsoft's lock-downs. Good Luck and I can't wait to see the results .
Just an update: I was able to build an SDK that works pretty damn well for native WP7 binary creation. After some fiddling with the buggy XIPPort tool and VS2010, I was able to produce a binary that runs just fine in WP7. (Currently, I just replaced Settings3.exe and used the menu's Settings link as an entrypoint.)
Now I can fiddle with more fun things, like accessing the registry and inserting those elusive SecureItems Not sure if those values are checked all the time tho -- if it's a one-time deal, I'll need to "reboot" the home screen.
Code:
INT start(
__in HINSTANCE hInstance,
__in HINSTANCE hPrevInstance,
__in LPWSTR lpCmdLine,
__in int nCmdShow
)
{
NKDbgPrintfW(L"[Hello, WP7. I haz you.]\r\n");
return 0;
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome stuff man. This should be extremely valuable once we figure out how to mod the ROM.
Settings3.exe is an application that runs in a normal user context, i.e. isn't very useful. Preload.exe, however -- which is used to insert dummy address book data at boot -- runs at a higher level. I replaced that with my code and was able to edit the registry (blacklist, secureitems) just fine... but it's too late during boot (damn!). The splash screen starts before my code is executed.
CAMERA MOD FOR S6 EDGE G925F & G925I LOLLIPOP 5.1.1
YOUR DEVICE NEED ROOT ACCESS
THIS MOD IS ONLY FOR SAMSUNG TOUCHWIZ BASED ROM (STOCK/CUSTOM)
*****************************************
Many user reported that this Mod is not working, I don't have the device now, I have modded the camera from stock Rom, I am not sure if this Mod will work with any custom ROM.
Anyway, I will update the Mod again Once the Marshmallow is out.
*****************************************
PLEASE READ COMPLETE POST BEFORE POSTING ANY QUESTION
CHANGE LIST:
IMAGE QUALITY:
• Increased to 100% for Normal Mode (Now you will get 100% quality, Uncompressed).
• Increased to 100% for Burst Mode.
VIDEO QUALITY:
Video Bitrate:
• UHD 4K (3840x2160) : Increased to 70Mbits from 48Mbits.
• FHD (1920x1080) [FRONT, BACK & DUAL-MODE CAMERA; FAST MOTION : 1/2, 1/4, 1/8] : Increased to 25Mbits from 17Mbits.
• FHD (1920x1080)@60FPS : Increased to 50Mbits from 28Mbits.
• WQHD (2560x1440) [FRONT & BACK CAMERA] : Increased to 40Mbits from 25Mbits.
• HD (1280x720) [FRONT, BACK & DUAL-MODE CAMERA] : Increased to 17Mbits from 12Mbits.
• SLOW MOTION (1/2): Increased to 17Mbits from 12Mbits.
• SLOW MOTION (1/4): Increased to 17Mbits from 12Mbits.
• SLOW MOTION (1/8): Increased to 8.5Mbits from 6Mbits.
VIDEO RECORDING TIME:
• Increased to 30:00 Minutes from 5:00 Minutes for WQHD and UHD. (Maximum upto 4GB = 8 Minutes : 09 Seconds)
• Increased to 30:00 Minutes from 10:00 Minutes for FHD_60FPS and DUAL_FHD.
• File Size Increased to 4 GB from 2GB for Slow motion and Fast Motion video recording.
SNAPSHOT RESTRICTION REMOVED:
• Now you can Take a Snapshot while recording UHD, WQHD and FHD_60FPS videos.
• While recording UHD & WQHD video, 15.9 MegaPixel (5312x2988) stills will be captured.
• While recording FHD_60FPS video, 2.0 MegaPixel (1920x1080) stills will be captured.
FLASH RESTRICTION REMOVED:
• Now you can use Flash even when the Battery is lower than 15%.
NOTE: If the battery is below 15%, then everytime you open Camera app, a Warning pop-up will appear "Flash is turned off to save battery (Below 15%). However you can turn on the flash manually." and the Flash will be Off every time you open the camera when battery below 15%, you have to manually change the Flash.
BATTERY LOW RESTRICTION REDUCED TO 1% FROM 5%:
• Now you can use Camera even if the battery is lower than 5%. (and Greater than 0%).
*********************************************
*** TAKE BACK UP OF EXISTING CAMERA APK AND XML FILE ***
Steps for replacing Manually.
• Delete all the .odex [If Exist] files (SamsungCamera4.odex and SamsungCamera4.odex.art) present in "arm " folder (system/app/SamsungCamera4/arm).
• Replace SamsungCamera4.apk (system/app/SamsungCamera4) with the one provided in below attached .zip file, based on your device model.
• Replace media_profiles.xml (system/etc) with the one provided in below attached .zip file, based on your device model.
• Set Correct permissions:
• Folder Permission: 0755 [rwxr-xr-x]
• File permission: 0644 [rw-r--r--] for SamsungCamera4.apk and media_profiles.xml
• After replacing the files and setting correct permissions. Wipe Camera data from App Manager; Please go to recovery and wipe the cache then Reboot.*********************************************
If you like this Mod; consider Hitting Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Button.
hey, any idea if this will work with the G925I model?
I did this and everything appears to b working so far. Fhd 60fps is now 60Mbits. I still need to test the rest. On a side note I did not clear cache
Cant wait to test it!
Btw AUT is Austria
ITS ONLY FOR 480 DPI/Density!
A little Density mod... my first modded APK!
I used the APK from this thread, and edit quick and dirty the XML files. Layout not perfect, but more fullscreen than the standart version.
So use the Manuel in the Startthread and have fun with it =)
ITS ONLY FOR 480 DPI/Density!
no warrenty from my side. i use it, on G925F with last update and it works.
The default density in build.prop ist 640! you can use dies APK only with density 480!
UPDATE:
the Multi-DPI is not so easy, in old versions from samsung camera its enouth to change some layout values.
but in this version, the "normal" camera works fine, but all effects, camcorder function and so on are broken.
when i open the "back-camera" in VGA the camcorder works, when i changed the back-cam to Full HD the app stops working.
but, with the front camera every thing is working fine, also full-hd recording.
i dont know, whats the problem is, i checkt the files and the values and all is looking fine.
maybe a real app dev could fix it.
Amazing! Trying now on Tmobile s6 edge
Worked great!
i see, there is a problem with the camcorder function. i could only record in VGA modus. The other modus give me a black screen, when i change to camcorder.
failure with media_profiles or dpi changes?
all working great on 925F using files from 1st post
unbelievable quality .... file size is big but SO worth it, THANKS
has anyone tried this on the SM-G925i ?
Can i use in my rom? Credits Will be given
2nd confirmation, working great on SM-G925T.
the Multi-DPI is not so easy, in old versions from samsung camera its enouth to change some layout values.
but in this version, the "normal" camera works fine, but all effects, camcorder function and so on are broken.
when i open the "back-camera" in VGA the camcorder works, when i changed the back-cam to Full HD the app stops working.
but, with the front camera every thing is working fine, also full-hd recording.
i dont know, whats the problem is, i checkt the files and the values and all is looking fine.
maybe a real app dev could fix it.
Hello, where are files:
• Delete all the odex files [arm64 folder]
Thanks!
Will this work on SM-G925W8?
jazenf said:
Will this work on SM-G925W8?
Click to expand...
Click to collapse
It should. It works on the T
ktetreault14 said:
It should. It works on the T
Click to expand...
Click to collapse
It does work, great job ?
Thanks for sharing but battery don't works less than 5% why....?:good:
Hello!
I've tried this on my S6 and my S6 Edge and works great on both (920F and 925F)
By the way, i want to come back and restore the default configurations....i've placed again the backup files and also the files in arm64 folder...all permission are OK anda i've done the wipe cache....but it still working with the MOD....can you please tell me how to go back?
Thanks in advance!!
tjuanma said:
Hello!
I've tried this on my S6 and my S6 Edge and works great on both (920F and 925F)
By the way, i want to come back and restore the default configurations....i've placed again the backup files and also the files in arm64 folder...all permission are OK anda i've done the wipe cache....but it still working with the MOD....can you please tell me how to go back?
Thanks in advance!!
Click to expand...
Click to collapse
This worked for me:
1. Replace your backufiles (arm64 files, SamsungCamera4.apk, and the .xlm), set the right permission as listet in the first post.
2. navigate to "/data/dalvic-cache/arm64", search and delete the two files with "... @samsungc[email protected]" in the name. Its a .dex and a .art file.
3. Power off, wipe cache, reboot.
now the Camera should work with the default settings.
I have been flashing ROMS since it was cool to do so (no, not before).
But I am a complete n00b when it comes to dev stuff and this whole post is written at that point of view; this post MAY contain incorrent information and n00bish mistakes.
Why change to 720px1280?
Frame rate doubles when using games or other graphics intensive applications.
Increased batter life due to lower resolution.
Even more snappier!
Since it's a 5.5" screen, not much difference between 1080x1920 and 720x1280. Of course, it's a compromise but barely noticable.
(Don't actually do anything, just read!)
How to change the resolution?
Make sure you enable "USB Debugging"
Make sure you installed adb and fastboot in your computer.
Connect your phone to your computer (usb cable... etc).
In the terminal type : adb shell wm size 720x1280
Wait, everything is so big! We need to change the DPI.
The original DPI is 480, but at 720x1280, 350 seems to restore the previous size and feel. Feel free to experiment with the DPI
How to change the DPI?
Make sure you enable "USB Debugging"
Make sure you installed adb and fastboot in your computer.
Connect your phone to your computer (usb cable... etc).
In the terminal type : adb shell wm density 350
OK, now you notice the (Virtual) Navigation Keys at the bottom don't work anymore.
Well that is because the Virtual Keys Mapping is out of range.
To understand why, consider this question : How will the system know which button you are pressing?
System uses the "display coordinate system" to identify where the buttons are located on the screen.
This info in located in this file: /sys/board_properties/virtualkeys.ftxxxx_ts
virtualkeys.ftxxxx_ts:
Code:
0x01:158:215:2045:260:250
0x01:102:540:2045:260:250
0x01:139:865:2045:260:250
Syntax:
Code:
0x01: A version code. Must always be 0x01. (ok google)
<Linux key code>: The Linux key code of the virtual key.
<centerX>: The X pixel coordinate of the center of the virtual key.
<centerY>: The Y pixel coordinate of the center of the virtual key.
<width>: The width of the virtual key in pixels.
<height>: The height of the virtual key in pixels.
Linux key code says what the button is: return, home, recent...
The last four parameters (centerX, centerY, width_of_virtual_key, height_of_virtual_key) are our concern, because they say where the buttons are located on the screen using "display coordinate system".
In "virtualkeys.ftxxxx_ts", the location of buttons is defined for 1080x1920.
So when we changed the resolution to 720x1280, the mapping for the virtual buttons became out of range and thus unusable.
So what should those parameters be for 720x1280?
Code:
0x01:158:143:1363:173:166
0x01:102:360:1363:173:166
0x01:139:576:1363:173:166
Stop lying!
Well I don't know for sure.
Method 1:
The original resolution is 1080x1920 and we changed it to 720x1280.
a -> 1080x1920
b -> 720x1280
w -> width
h -> height
wb/wa = 1280/1920 = hb/ha = 1280/1920 = 0.666666667
Both the resolutions have same aspect ratio. So we need not bother about width and height seperately, because they are both changed at the same proportion.
So, multiply the last four parameter values (centerX, centerY, width_of_virtual_key, height_of_virtual_key) by 0.666666667 and you should get the location of the buttons when resolution is changed to to 720p.
Method 2:
Enable "Show pointer location" in "Developer Settings".
The co-ordinates of where you touched the screen are displayed at the top.
Change the resolution to 720x1280.
The Navigation Buttons don't work but drag your fingers onto them.
You will see X and Y are near to the values we calculated in METHOD 1.
So lets modify the file already! (/sys/board_properties/virtualkeys.ftxxxx_ts)
Well you see, the file (virtualkeys.ftxxxx_ts) is located in the directory "/sys".
It turns out, it is not an actually directory. It is a "view" of the KERNEL as a filesystem.
So, every time the system boots, the kernel creates (magics?) those files in "/sys" which the system uses.
We do not have permission to change that directory's contents, not even with a slip from our parents.
Unless we have a way of overriding the kernel created file (virtualkeys.ftxxxx_ts), we have to patch the kernel itself.
I don't know how to patch kernels and stuff, this escalated quickly for me. So if you are interested check it out!
Please check the validity of anything said in this post. Positive criticism is welcome!
Sources : https://source.android.com/devices/input/touch-devices.html#virtual-key-map-files, @aziz07 (started all this after reading their posts in : http://forum.xda-developers.com/zenfone2/general/downgrade-resolution-ze551ml-t3163797)
This is the file on ze550ml. Your results appears to correct.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Im using second monitor from play store to change resolution and density on the fly.
Sky on demand not work if detect 1080 device. So i change to 720p to connect tv.
Facing with virtual Keys not working, hwvr i use iswipe to manage it.
Solution can be virtual nav bar, exposed mondule, anyway resulution is not 1080 or 720 but is scaled so open zenui.apk to see how it work, what now? You need mod zenui or just flash custom rom, 'cuz will afect call screan, setting screen, app drawer and so on.
Some aps will not work changing density and zenui sometime crash, so need reboot.
Forget to say that: changing resolution will impact batery life in whorste way (you will run ever biggest res then the normal use). Only wallpaper, immersive mode (photo and video) and of course user apps are the only run in full resolution, set black screen wallpaper and use appsetting module to change per app resolution if you tink will save batery life.
Ah, the much easier method. Thank you for posting.
I think, 540x960 will be better for lowres because it will use whole 2x2 pixels and won't create blur.
I've just got idea to mix such tweak with second user. So, when you switch the user, resolution will be switched as well.
UP, it work with Cyanogenmod 13, much better battery life, but we need kernel patch for modify virtualkeys.ftxxxx_ts
tikilou said:
UP, it work with Cyanogenmod 13, much better battery life, but we need kernel patch for modify virtualkeys.ftxxxx_ts
Click to expand...
Click to collapse
why?
@blazzer12 I would like to correct something :
the correct parameters for 720x1280 are
0x01:158:140:1341:180:100
0x01:102:360:1341:170:100
0x01:139:580:1341:180:100
these values are the one metioned in our kernel source.
blazzer12 said:
Well you see, the file (virtualkeys.ftxxxx_ts) is located in the directory "/sys".
It turns out, it is not an actually directory. It is a "view" of the KERNEL as a filesystem.
So, every time the system boots, the kernel creates (magics?) those files in "/sys" which the system uses.
We do not have permission to change that directory's contents, not even with a slip from our parents.
Unless we have a way of overriding the kernel created file (virtualkeys.ftxxxx_ts), we have to patch the kernel itself.
Click to expand...
Click to collapse
Better you can try a ROM from Z008/720p Model. Because I've flashed a full ROM of Z008 to my Z00A for recovering it from HardBrick (In that case I had only 720p model RAW Firmware file). That ROM was working very fine but the icons was smaller due to DPI of the ROM. My Idea is, if I flash 720p ROM and change resolution to 720p using your methid, everything will be normal. right? (Or, you can use a kernel alone from Z008 instead of searching for a kernel patch).... Am I right?
say99 said:
@blazzer12 I would like to correct something :
the correct parameters for 720x1280 are
0x01:158:140:1341:180:100
0x01:102:360:1341:170:100
0x01:139:580:1341:180:100
these values are the one metioned in our kernel source.
Click to expand...
Click to collapse
would be nice if you can add this patch in your kernel
xCalibur15 said:
would be nice if you can add this patch in your kernel
Click to expand...
Click to collapse
ok, I did this today in the morning, but I must tell you this method didn't work
https://github.com/Zenfone2-Dev/kernel-FlareM/commit/ba444d0616457c283cd257a363d427c915efbf7b
I was able to change the content of the file, but as soon as that happened, I was only able to access 3/4th of my screen, touch didn't work. I must also tell you guys that, even though we change the DPI to 720P, sweep2sleep still works that just means that the location of the hardware keys is still the same. I am trying to figure out the correct coordinate that we should use. Cause according to our boot animation, we get a increase of about 1.45x in X coordinate.
help me with the codes if you want to
Sent from my ASUS_Z00A using Tapatalk
i calculated the values for 540x960px (easier to calculate):
0x01:158:107:1023:130:125
0x01:102:270:1023:130:125
0x01:139:433:1023:130:125
dpi 240
if i got it right, I can make the values for 720p also
i found this very cool, and wish to change the button positions... but sorry i dont get it, there is a way to do it?
Asus Zenfone 2 Laser ZE500KL
Asus Zenfone 2 Laser ZE500KL
Resolution 720 x 1280 pixels (~294 ppi pixel density)
android marsmallow
0x01:158:140:1328:160:80
0x01:102:360:1328:180:80
0x01:139:580:1328:160:80
---------- Post added at 07:02 AM ---------- Previous post was at 06:51 AM ----------
Asus Zenfone 2 ZE551ML
1080 x 1920 pixels (480 ppi pixel density)
android marsmallow
0x01:158:140:1328:160:80
0x01:102:360:1328:180:80
0x01:139:580:1328:160:80
https://goo.gl/UKaif3 here's how to change resolution with root
say99 said:
ok, I did this today in the morning, but I must tell you this method didn't work
Click to expand...
Click to collapse
And if you include the next code but with correct touch screen coordinates for 720p?
https://github.com/BORETS24/Kernel-...0c/drivers/input/touchscreen/ftxxxx_ts.c#L926
https://github.com/BORETS24/Kernel-...0c/drivers/input/touchscreen/ftxxxx_ts.c#L986
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samples
Original Camera x Camera M x GCam HDR+ : Sample 1, Sample 2
GCam HDR+ x Camera M : Sample 1
Original Camera x Camera M : Sample 1
Old:
https://i.cubeupload.com/BxqGVT.jpg
https://i.cubeupload.com/slXZ8t.jpg
https://i.cubeupload.com/4o9jFT.jpg (by @vagkoun83)
Don't hesitate to post your settings, samples and comparisons !
Features
JPEG quality increased to 100
Denoise responsible of the watercolor picture disabled
Sharpness adapted before picture been processing to prevent watercolor picture
IntelligentHQ : prevent higher ISO than needed in good light situation
Possibility of choosing front camera sharpness in Settings
Before installing
If you have installed an update of Oneplus Camera before, you have to understand that the update is "above" the original system application. Because my mod replace the original system application, you will never see a difference because the current app will be the updated app and not the system app.
To remove the update, go into the App Info of Oneplus Camera, press the tree dots in the top right and press "Uninstall Updates". (thanks to @Im_Mattgame for this easier way)
Current settings I use
Sharpness for front camera => 3
Bugs known
Panorama and watermark doesn't work
Changelog
Code:
[B]2018.07.22 [/B]
- Based on new version 2.8.11.
- Code base cleaned to prevent some errors.
- Not adapted to OP6 yet !
[B]2018.02.22 [/B]
- Quick fix concerning the new feature "IntelligentHQ". It should work more consistently now.
[B]2018.02.21 [/B]
- New feature "IntelligentHQ" : In good light situation, Oneplus Camera app tends to use a higher ISO than needed. In order to prevent this, when it's possible, I use automatically the HQ mode to lower the ISO rate. The picture will be more detailed and with less noise thanks to low ISO. Only works in "No-HDR mode", which is the default mode.
- Sharpness decreased in really low-light situations to prevent oil-painted pictures
- Panorama mode should work now (thanks to [user=2185114]@DorianX[/user])
[B]2018.02.12 [/B]
- Sharpness increased in really low-light situations
- Sharpness decreased in good and mid light situations to avoid too much noise / oversharpening effect
- Noise reduction is applied a bit earlier than before to avoid too much noise. Don't worry for the oil-painting effect I have adapted the sharpness for it
- Remove of the switch for disabling noise reduction in Parameters : It causes too much confusion. I have seen many people asking if they need to enable it or not, so I remove it. When it was enabled, the picture quality was really bad compared to when it was disabled anyway.
- Auto-HDR and HDR is now working like the original Oneplus Camera app
- No-HDR is now by default. It gives better results than Auto-HDR, even when Auto-HDR doesn't not kick the HDR mode
- Code base cleaned and prepared for the next "big" feature :)
[B]2018.01.31 [/B]
- Sharpness increased in some bright-light situations
- Sharpness decreased in mid-light and low-light situations to mitigate "oil-painting" effect and others weirderies caused by Oneplus noise reduction. Pictures should be now more "natural", even with Oneplus noise reduction on.
- Renaming of the switch in Settings because it caused confusion concerning the light situation. I added a subtitle which explains how and when it works. I STRONGLY ADVISE YOU TO NOT ENABLE THIS SWITCH.
[B]2018.01.28 [/B]
- Noise reduction enabled by default in pictures with ISO between 800 and 3000 (was already by default when ISO was upper than 3000)
- Added a switch to disable noise reduction in low light (ISO between 800 and 3000). Not possible to disable when ISO is upper than 3000 because is really ugly without noise reduction.
- Name of the version is included now in Settings to avoid confusion
[IMG]https://i.cubeupload.com/eLSM9v.jpg[/IMG]
[B]2018.01.26 [/B]
- Based on original version 2.5.22
- Fix for selfie pictures at 4MP (thanks for the report !)
[B]2018.01.24 [/B]
- Remove chroma noise and increase sharpness in bright light
- Overall tune-in depends on the current light situation
[B]2018.01.22 [/B]
- Sharpness according to the current light situation has been tuned
- Oneplus noise reduction was not enabled in extremely low-light picture, it should work now.
[B]2018.01.21 [/B]
- Luminance denoise is disabled now in Photo Mode. Was responsable of the "watercolor" effect. In counterpart, luminance noise is increased.
- To prevent luminance noise, I decrease sharpness according to the current light situation but 100% of the time, it's better than picture taken by original camera app. Pictures are now on par with GCam HDR+.
- Luminance denoise is enabled only in extremely low-light picture.
- Auto-HDR mode will now never enable HDR mode. Is now like a no-HDR mode.
[B]2018.01.13 [/B]
- Portait Mode works
- Modded process affects currently only the Photo Mode (not Portrait Mode, Pro Mode, etc ...)
- Modded process is now customizable with 3 modes : Sharpness level in good light, in low light and for front camera. 1 is the default level use by Oneplus. So if you want to disable the modded process, you should put level 1 in the three modes.
[B]2018.01.10 [/B]
- Panorama works now
- Settings menu revamped
[B]2018.01.09 [/B]
- Revert back to the original Oneplus process : better noise reduction
- Sharpness increased to counter-balance the "over-blurring" effect made by original Oneplus process
[B]2018.01.05 [/B]
- Based on version 2.5.21
- Use of the alternative Oneplus process
- Sharpness increased
- Switch added in Settings for use of original Oneplus process
[B]2017.12.15 [/B]
Based on version 2.5.20 coming from new OxygenOS Oreo update
[B]2017.12.15 [/B]
Based on version 2.5.15
[B]2017.12.11 [/B]
Based on version 2.5.12
[B]2017.12.07 [/B]
Based on version 2.5.11
[B]2017.12.04[/B]
First release
Downloads
Magisk Module
Big credits for
@jerkwad
@Youtube_Ll0r3nt3
Previous downloads views
Downloading!!
Thanks bro
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
@xXx will you add it to the rom ?
Anyone got it to work on Oreo beta?
Can't flash. Says zip is corrupt
Xcal15 said:
Can't flash. Says zip is corrupt
Click to expand...
Click to collapse
New zip uploaded, can you try again and tell me if it works ? If not, tell me what the recovery shows you and you try to flash it.
Magisk version?
cesar_9046 said:
Magisk version?
Click to expand...
Click to collapse
In bird culture it's considered a bad move.
Why it is so natural to have a magsik version of everything?
You didn't even say a thanks for this mod.
txx1219 said:
New zip uploaded, can you try again and tell me if it works ? If not, tell me what the recovery shows you and you try to flash it.
Click to expand...
Click to collapse
I have extracted the apk from the Zip and I have copied it into system / priv / camera, I have given it the permissions, and I have restarted. Works. Thank you
jordirpz said:
I have extracted the apk from the Zip and I have copied it into system / priv / camera, I have given it the permissions, and I have restarted. Works. Thank you
Click to expand...
Click to collapse
Which permissions have you given ?
txx1219 said:
Which permissions have you given ?
Click to expand...
Click to collapse
644
jordirpz said:
644
Click to expand...
Click to collapse
Thanks
_MartyMan_ said:
In bird culture it's considered a bad move.
Why it is so natural to have a magsik version of everything?
You didn't even say a thanks for this mod.
Click to expand...
Click to collapse
What the hell is bird culture?
Also heres a magisk version for this.
https://drive.google.com/open?id=1X-OxOhVFPSsA3R5TnTG4tLTgFAlVMjVo
-DarkKnight- said:
What the hell is bird culture?
Also heres a magisk version for this.
https://drive.google.com/open?id=1X-OxOhVFPSsA3R5TnTG4tLTgFAlVMjVo
Click to expand...
Click to collapse
He is from future.
Xcal15 said:
Can't flash. Says zip is corrupt
Click to expand...
Click to collapse
Me2.
gre0ge said:
Me2.
Click to expand...
Click to collapse
Can you try again with the new zip I uploaded ? (see first post)
Thank you, Magisk's one works fine and smooth But, as all the others apk releases after the official update (OOS 4.5.14), this camera hasn't electronic image stabilization in videos, sadly. Can you make a modded version of the camera from 4.5.14 update? Would appreciate a lot, thanks man!
txx1219 said:
Can you try again with the new zip I uploaded ? (see first post)
Click to expand...
Click to collapse
I tried with magisk version and works!
Firstly, thank you for the mod
I'd like to see some sample shots. Does 5% really make a huge difference, even on a 100% zoom level? If it's anything like Photoshop's Quality Setting, 5% has just resulted in higher file size but minimal to no increase in quality.
how to flash without TWRP
Thank you so much
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
User Manual For Gcam
Gcam may come with some bugs and xml or apk related problems.
If you can find any bugs in apk,xml,image,post processings etc...many more ; reply me with the specific screeen shots and log file located at the same folder with XMLs.
I will surely try to fix the problem overtime...
So,Always try to keep your XML file updated from thread
⊕⊕For support⊕⊕
Join☞YAS Gcam support group
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Camera version wise user Classification
➤ Perfect for normal use with any ROM (custom/stock).
✔Update (01.09.21) [Gcam 7.3] {Normal + Averaged} Arnova's GCam stable version <<RUI☞1/2>>
This thread is for GCam 7.3➤ Stable Edition that enables all facilities and mods over any other Gcam Changelog v1.2 -Stable version -lib patched with true tone -Front and back saturation increased to maximum -HDR enhanced supports true black...
forum.xda-developers.com
➤ Perfect for saturation lovers and landscape photographers.
✔Update (29.08.21) [GCam 7.4] { Saturation + Landscapes } Tr camera ***Spring Release*** <<RUI☞ 1/2>>
GCam 7.4 Tr Camera ***Spring Release*** [] Changelog➤➤ -Lib patched -Sashta Factor Enabled -Sabre Enabled -Astro Improved -Auxiliary Lens Control -Social share on -Front illuminating -ISO and AWB override -Frames rate increased -Device Model...
forum.xda-developers.com
➤ Perfect for Macro photographers and selfie lovers.
[Gcam 7.4] { Macro + Selfie } Tr Camera ***X-mas Release*** <<RUI☞1/2>>
Gcam 7.4 Tr Camera max with enhanced features [] Changelog➤➤➤ -Lib patched -Sashta Factor Enabled -Sabre Enabled -Astro Improved -Auxiliary Lens Control -Social share on -Front illuminating -ISO and AWB override -Frames rate...
forum.xda-developers.com
➤ Perfect for Realme UI 1 and it’s final version for Realme UI .
✔Update (22.07.21) [GCam 8.2] { RUI ~1 FINAL } P-Z-D Extreme Customised version <<RUI☞1>>
Gcam 8.2 changelogs of xml ⇨Astro time shifting mode ⇨Astro time lapse mode ⇨Starry Night mode ⇨45 x superzoom ⇨Noise model IMX 682 ⇨All sensor specific AWB & Noise model (IMX 686, Hynix HI 846, Galaxy core GC02K0, OV 02B10) ⇨EIS forced with...
forum.xda-developers.com
➤ Perfect For almost all situations; specially for Astro photography.
☆✔Update (20.02.22) [Gcam 8.2] { Raw Color Tone Enhanced Edition } NGcam for stable photography <<RUI☞1/2>>
◑◑ Gcam 8.2 latest version ◑◑ ➤➤➤Changelog for 8.2.300➤➤➤ ======================================= 👇Download link👇 ♥APK♥ NGCAM 8.2 Final ♦XML♦ RAW COLORS by YaSiR ======================================= ~~~~☞XML apply method☞~~~~ 1.Make a...
forum.xda-developers.com
➤Perfect for True Tone Colors;Specially For Leica™ effects
✔ Update (16.01.22) [GCam 8.2] { True Colors } Helena Leica cam 8.2 <<RUI ☞ 2>>
◑ GCAM 8.2 ◑ HELENA 🎆LEICA TRUE COLORS🎇 Changelog>> -TRUE colors -HDR day images -LDR mode -Leica mode -CT fix -Color blended with HMX sensor models -IMX 682 noise model -Macro mode -Automatic &fixed white balance control -Focus tracking -Focus...
forum.xda-developers.com
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
✔
And If you want to share my xml anywhere please let me know that you are sharing that.
✔
☞ Now I am describing some common problems with solutions...
#1
Crashing while taking photo
✪Fix> Clear RAM before taking photo and you can also change the HDR+ enhanced to HDR+
#2
Night mode taking a lots of time
✪Fix>Turn off astrophotography mode
#3
Slow Motion / Stabilization video mode Crash
◑Fix>Reduce the slow motion frames and stabilize videos after shooting with google photos
#4
XML is not applicable
◑Fix>Reply me with the XML version and file attached
#5
Auxiliary cameras not working
◑Fix>Realme UI 2 has blocked use of Aux cameras
#6
Long shutter time,Slow pic capturing
◑Fix>Use HDR+ instead of HDR+enhanced
#7
Too much time needed for post processing
◑Fix>Turn off HDR+ enhanced and Use normal HDR
#8
Camera crashed after taking pic
◑Fix> Turn off Raw+JPEG and Use JPEG only
#9
Leica Camera giving Over smooth effects
◑Fix> Turn off Leica mode
Reserved
User based Version Updated
So which GCam is the best for daily use with RUI 2 stock ROM? It is quite hard to choose by descriptions like "Perfect for normal use", "Perfect for saturation lovers", "Perfect For almost all situations"...all of that sounds good :-D
A
lapist said:
So which GCam is the best for daily use with RUI 2 stock ROM? It is quite hard to choose by descriptions like "Perfect for normal use", "Perfect for saturation lovers", "Perfect For almost all situations"...all of that sounds good :-D
Click to expand...
Click to collapse
Actually all cams are made for user based situations...
As we are not using basic or RAW GCam released by Google,
We are using modded GCams.
So different cams have different functionality and special qualties..
It depends which one you wanna choose for your work.
Someone only takes selfies while other takes macro,somebody takes landscape at day somebody is astrography lover.
As a result, I am giving all options to the user, so they can enjoy shooting and get better picture based on their needs and needs.
Hope you have understood.