Camera2 API

(Topic created on:  

22/07/2026 03:22 PM

)

414 Views

Labels:  

 
K

Kinemonfx

Student

last edited

 

22/07/2026 03:22 PM

To the Samsung Camera Engineering Team,

​While the sensor hardware on @galaxy devices is world-class, the current Camera2 API software restrictions severely bottleneck what third-party applications like#MotionCam can achieve

​Currently, key sensor capabilities are artificially locked out of the Camera2 API for developers. I am requesting that Samsung open up the following features via API opcodes or vendor extensions:
1.​Dual Conversion Gain (DCG): The hardware supports it, but third-party RAW video apps are blocked from accessing it.
2.Unrestricted RAW Framerates: We need full 60fps RAW sensor readout across all lenses.
3.Unfiltered Sensor Access: Please allow third-party developers direct access to raw sensor data without forced OEM processing limiters.
Opening up these vendor tags and opcodes would instantly make Galaxy devices the undisputed top choice for mobile filmmakers.

Thank you for your time and for passing this up to the camera development team.

​Best regards,

    • R

      riecodes

      Student

      last edited

       

      10/08/2026 05:59 PM

      same problem here. hit a brick wall on cannot use 60 fps for a third party camera i am building

    • B

      Bugn0

      Student

      last edited

       

      12/09/2026 07:33 PM

      And I’ll add this... These 'locks' are preventing third-party apps like Camo Studio, Instagram, and TikTok from fully utilizing the camera's capabilities... Samsung simply doesn't do what Apple does with ARKit and the like... 3D mapping and stabilization features in other apps are completely blocked because of this lousy API that restricts everything the camera has to offer... It was bad enough that they removed LiDAR from the devices... Now they want to limit these features for third-party apps too?

    • K

      Kinemonfx

      Student

      last edited

       

      18/10/2026 03:05 PM

      Yes, exactly, thank you!!!!

      I really don't get why samsung doesn't whitelist some OPmodes or atleast give us some proprietary stuff so we could code with those things that could make samsung phones better, no reason to try to catch up to Apple if you are gonna close down the tools to do so!

      So once again I think this should be addressed by Samsung and why it locks us out of OUR own phones this way!

    • L

      LYHT

      First Poster

      20/11/2026 02:25 AM

      I've never been more disappointed with a smartphone. Today, I bought the Samsung Galaxy S26 Ultra specifically for its high-resolution camera because I'm developing a book-scanning application.

      Only to discover that Samsung apparently limits the Camera2 API to around 4K, preventing third-party developers from using the camera's full capabilities.

      Even worse, the 50 MP and 200 MP modes seem to introduce noticeable artifacts and excessive image processing, sometimes making the results look worse than lower-resolution photos. What's the point of advertising such high resolutions if the actual image quality doesn't consistently reflect them?

      What makes this even more frustrating is that Samsung doesn't publicly document which camera resolutions and features are accessible through the API for each phone. How are developers supposed to make informed purchasing decisions without this information?

      I think this raises serious concerns about misleading advertising. Samsung promotes its impressive camera hardware without clearly explaining that some features may be restricted to its own apps.

      Now I'm stuck with an expensive phone that's practically useless for my project, and I'll probably have to return or resell it. Samsung should be transparent about these limitations before customers spend their money.

      0 likes