Both options make no difference for me. Sabre_Allowed was already enabled. Disabling and again enabling leads to no change...The HDR+Enhanced thing was an error on my part. That option and Sabre enabled still gets me no lag.
Both options make no difference for me. Sabre_Allowed was already enabled. Disabling and again enabling leads to no change...The HDR+Enhanced thing was an error on my part. That option and Sabre enabled still gets me no lag.
I've got little to no experience in the developer options of the app, but I noticed that resetting the developer options to their default values does solve the delay problem.Both options make no difference for me. Sabre_Allowed was already enabled. Disabling and again enabling leads to no change...
I'll try to have a look, later, and see what could possibly cause the issues to some of you. Being not affected myself, I will then share a series of test files that some of you will need to test, one by one, until we find what caused those delays when switching modes.I've got little to no experience in the developer options of the app, but I noticed that resetting the developer options to their default values does solve the delay problem.
Does anyone know if there's an easier way to compare to .XML files than to manually look in the app?
Unfortunately none of them makes any difference for me.Could those who have the lag issue when switching between modes possibly test those custom xml files and let me know if any of them solves the problem? Thanks.
I'm sorry, but for me neither...
Still the same results :/
Thanks for trying. I might look into the dev options more later.Well then, I really have no idea how to solve it, I'm sorry. I'd suggest you stick to the xml file provided by another user which seems to solve your issue, or simply reset all the Dev settings back to "default" when using mine, if it helps. Wish I could help more, but without having the issue on my device, it's kinda hard to fix it...
Great news and well done! I would have never expected this setting to cause any trouble... And it's quite weird that this dev setting could have different consequences on similar devices equipped with the same ROM.Found the problem! Manually toggled every developer setting until the problem was fixed. Camera.cutout_display was the thing that was moving the camera viewfinder and making the delay.
The latest day and night configs with the cutout developer option disabled is attached.
You're running Oxygen 12, right? I'm on Pixel experience 12 plus, rooted with magisk, mainly for some of the pixel features and having unlimited original quality upload for Google photos for free.Great news and well done! I would have never expected this setting to cause any trouble... And it's quite weird that this dev setting could have different consequences on similar devices equipped with the same ROM.
Yup, but I remember another user said he was using OOS12 and had this lag issue as well. I'm rooted too, with a few magisk modules on.You're running Oxygen 12, right? I'm on Pixel experience 12 plus, rooted with magisk, mainly for some of the pixel features and having unlimited original quality upload for Google photos for free.
GREAT and well done!!! My issues with LMC 8.4 and stock, plain vanilla OOS 12 without root are solved! No more lags when switching from mode to the other... With the camera.cutout_display_day.xml i have no more lags. Thanks a lot!Found the problem! Manually toggled every developer setting until the problem was fixed. Camera.cutout_display was the thing that was moving the camera viewfinder and making the delay.
The latest day and night configs with the cutout developer option disabled is attached.
Yes the XML files l attached are based on the latest XML files posted on this thread before.GREAT and well done!!! My issues with LMC 8.4 and stock, plain vanilla OOS 12 without root are solved! No more lags when switching from mode to the other... With the camera.cutout_display_day.xml i have no more lags. Thanks a lot!
And the camera.cutout_display_day.xml bases on the NICKAMPRO 2.4?
Cheers!
Yes, for me too. When i switch to wide and take a shot, the app closes near end of processing. When i restart the app, it closes again. Only when I start the app a second time, it runs again. No image was saved. Thanks a lot for your support![ Edit: I noticed a force-close of the app when processing a shot from the Ultra-Wide angle from V2.5 'standard' version. Is anyone else affected as well? If so, I will update this post with a fix. ]
It actually has nothing to do with the wife camera, but more so it being the 3rd camera. In my case, the zoom camera in the .XML config is the wide camera (I don't bother so didn't change it). Thus for me, the zoom camera is crashing, not the wide.Yes, for me too. When i switch to wide and take a shot, the app closes near end of processing. When i restart the app, it closes again. Only when I start the app a second time, it runs again. No image was saved. Thanks a lot for your support!
Cheers!
In my case the wide camera is the 3rd camera. Thus for me the wide camera crashes...It actually has nothing to do with the wife camera, but more so it being the 3rd camera. In my case, the zoom camera in the .XML config is the wide camera (I don't bother so didn't change it). Thus for me, the zoom camera is crashing, not the wide.
Edit: Clearing strorage in the camera app did solve the crash for me. Maybe the same for you.
And it has been such a luck for us to have such a competent modder !** LMC R11 LITE Google Cam Mod (V8.4.300 Base) **
This is a very similar version to the original LMC mod, with the exception of the RamPatcher area being much reduced, which makes it simpler to configure your prefered photo settings.
Changelog:
- Minimal patcher, special tweaks.
Custom XML NiCkAM8PRO V1.0 for R11 Lite (APK + XML): https://ufile.io/3k0ldcba
[PW: NiCkAM8PRO-for-XDA ]
As I am upgrading to a different device soon, this will be my last contribution for the OnePlus 8 Pro. It has been a great pleasure to serve this amazing community!
Cheers![]()
I hope they will come. Maybe they comes with different names or something. Like Xiaomi 12TMaybe, but I doubt it, as they've actually broadcasted and translated the Live event in different (european) languages from their different YT branches. Given how much it has cost them to co-develop that IMX989 with Sony, I don't see why they'd keep it exclusive to China only. My guess: September worldwide.