While the seventh iteration of One UI currently seems like a distant dream as even the beta phase is yet to start, we were recently blessed with the 6.1.1 incremental updates. The update brought in a handful of goodies and the usual performance enhancements and security improvements. However, it seems an infuriating bug has also managed to creep in alongside that update as well. This is because numerous users have voiced their concern that the 3x lens is not working on their Galaxy S24 Ultra after installing the latest One UI 6.1.1 update.
Table of Contents
Why is 3x Lens Not Working on Galaxy S24 Ultra after One UI 6.1.1 Update
Whenever users try to take an image via that lens, the output comes out as pink-striped images. This is because the camera app is unable to access that lens because it has been blocked at the OS level. And how did that happen? Well, the latest update has made some changes regarding how Camera2 API handles RAW format data for the impacted 3x lens. For the unaware, numerous third-party camera apps, including the popular GCam or Google Camera, use this API to access the 3x lens of the device, the inability of which is resulting in this issue.
Impacted Apps
Apart from GCam, the likes of MotionCam Pro and ProShot are also impacted by this issue because they too use the same aforementioned API. On the other hand, apps that don’t use this RAW photo data, such as most video-centric apps, are not affected by this update. All in all, this is a dire situation for many users who are more inclined towards a third-party camera app instead of the built-in one, which encompasses a large user base.
Bug or Intentional Change?
So this begs the all-important question- has this been done intentionally or it’s due to the rollout of a buggy update? Well, as of now, there is no official statement from the OEM and everything is merely speculation. But a similar issue has occurred in the past as well [at that time, the 1x lens was impacted] and a buggy update was the culprit which was ultimately patched with a subsequent OTA update. So let’s just hope that this is the case this time around as well and the issue gets ironed out at the earliest. As and when that happens, we will update this guide accordingly. So stay tuned.
