• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

please help! "open camera" app removed the resolution of 176x144 in the newer devices, please help me bring it back

please help! "open camera" app removed the resolution of 176x144 in the newer devices, please help me bring it back



the "open camera" open source app uses the camera2 api for listing the avaliable photo resolutions, on older devices such as S8,S9 users had low resolutions such as 176x144 bit on the s20 and s22 that resolution isn't available.



if anyone could add that resolution to the newer devices would help everyone so much.
 

Attachments

  • Screenshot_20230710_051049_Open Camera.jpg
    Screenshot_20230710_051049_Open Camera.jpg
    191.5 KB · Views: 108
Are you talking about videos? or photo resolution?
photo resolution of 176x144 has been removed either by open camera or by camera2 api so the "open camera" app gets the avaliable photo resolutions from camera2 api, how can i add that resolution back to camera2 api
 
That's such a low resolution I never bother to even use it as a test shot but after reading your query I found an oddity conversely the opposite to your situation -- on a relatively newer OnePlus phone the Open Camera app does show resolutions as low as 176 x 144 but on an older Moto phone the Open Camera app only goes down to 320 x 240.
That's an indication there's just a minimum resolution issue with the camera module, a hardware aspect, difference in your collection of Galaxy S phones. The Open Camera app does not have the ability to '...remove the resolution of 176x144...' as you stated, it's just software. The camera app includes the support for various resolutions, but it can only use the available capabilities of the hardware that's available to it. Apparently Samsung has opted to no longer include support for such low resolutions in the camera modules it puts into its phones now.

That said, I'd suggest you should be using the stock Samsung Camera app. I myself really like the Open Camera app, it's very capable and with a large number of options to customize and optimize its usage but Samsung's camera modules include a lot of proprietary functions that being proprietary only work with Samsung's software. So apps like Open Camera cannot access all of those whiz-bang features, there are licensing restrictions in place. Open Camera is a debatably better option for the lackluster Moto Camera app but because of those patent issues the Samsung Camera app has a lot of advantages.
Of course if you're hesitant to adopt to different interfaces and prefer Open Camera, and don't care about all the Samsung bling, never mind. Best to use the camera app you're most comfortable using.
 
And just to add, it doesn't have that option on my s21.

But I agree with @svim, this isn't the Open Camera app, and there's nothing you can do apart from resize later if you want. Even if it were the api rather than the hardware you'd need to go into the actual Android source code and rebuild the ROM from scratch to do that, which would have other consequences you'd have to weigh against this need. But that's probably irrelevant anyway, because I'm guessing from the time you posted that you are in North America, and recent Samsungs from that region are usually not rootable in the first place and hence that option simply doesn't exist.
 
And just to add, it doesn't have that option on my s21.

But I agree with @svim, this isn't the Open Camera app, and there's nothing you can do apart from resize later if you want. Even if it were the api rather than the hardware you'd need to go into the actual Android source code and rebuild the ROM from scratch to do that, which would have other consequences you'd have to weigh against this need. But that's probably irrelevant anyway, because I'm guessing from the time you posted that you are in North America, and recent Samsungs from that region are usually not rootable in the first place and hence that option simply doesn't exist.
one of the devices has root access, can that be used to manually include the desired resolution of 176x144 into the camera2 api? if anyone has an idea that would be much appreciated by a lot of people.
 
That's such a low resolution I never bother to even use it as a test shot but after reading your query I found an oddity conversely the opposite to your situation -- on a relatively newer OnePlus phone the Open Camera app does show resolutions as low as 176 x 144 but on an older Moto phone the Open Camera app only goes down to 320 x 240.
That's an indication there's just a minimum resolution issue with the camera module, a hardware aspect, difference in your collection of Galaxy S phones. The Open Camera app does not have the ability to '...remove the resolution of 176x144...' as you stated, it's just software. The camera app includes the support for various resolutions, but it can only use the available capabilities of the hardware that's available to it. Apparently Samsung has opted to no longer include support for such low resolutions in the camera modules it puts into its phones now.

That said, I'd suggest you should be using the stock Samsung Camera app. I myself really like the Open Camera app, it's very capable and with a large number of options to customize and optimize its usage but Samsung's camera modules include a lot of proprietary functions that being proprietary only work with Samsung's software. So apps like Open Camera cannot access all of those whiz-bang features, there are licensing restrictions in place. Open Camera is a debatably better option for the lackluster Moto Camera app but because of those patent issues the Samsung Camera app has a lot of advantages.
Of course if you're hesitant to adopt to different interfaces and prefer Open Camera, and don't care about all the Samsung bling, never mind. Best to use the camera app you're most comfortable using.
i agree with but here's the thing, on other apps such as "Fast burst camera" the resolution of 176x144 shows up on list but the "fast burst camera" app doesnt provide options such as timestamp or hdr
 

Attachments

  • Screenshot_20230710_153855_Fast Burst Camera.jpg
    Screenshot_20230710_153855_Fast Burst Camera.jpg
    146 KB · Views: 40
one of the devices has root access, can that be used to manually include the desired resolution of 176x144 into the camera2 api? if anyone has an idea that would be much appreciated by a lot of people.
"A lot of people"? How many people use this resolution?

What API does "Fast Burst Camera" use? Presumably not the original, long-deprecated Camera API, but might it be using CameraX? Because if it is using Camera2 as well that would prove that the restriction isn't the API - though it wouldn't tell you why Open Camera thinks the device doesn't support it. But Open Camera is, as the name says, "open": if another Camera2-based app gave you the resolution you want you can find the Open Camera source on Sourceforge and see whether you can work out the cause and make your own version (the code is available under the GPL V3 license). Or ask the developer if they have any ideas.

Of course if Fast Burst Camera uses CameraX then it could be a difference between the APIs, or how those APIs interact with elements lower in the stack (of which there are several layers). Getting into that will require a lot more effort, and most likely rebuilding the operating system on your phone from source (assuming you can identify where in the source the confusion arises). I think it unlikely that there's some config file sitting in some system directory that you can just add a line to and reboot the phone and it will work (though as my s21 isn't rooted I can't prove that).

(For what it's worth I don't think it is that Camera2 itself simply doesn't support this resolution: we've already established that it's available on other devices that use Camera2, which is actually pretty old. But it's conceivable that different APIs see the device slightly differently, so if the other app uses the more recent CameraX then that might be the answer).

Before we get ahead of ourselves, I suppose you have tested that 176x144 works in Fast Burst Camera? I just like to cover all of the bases.

There are a lot of assumptions here, but if Fast Burst Camera does work at that resolution and does use Camera2 then probably the simplest way forward would be to contact the Open Camera developer and ask them whether they have any idea why Open Camera does not offer this same resolution on the same device?
 
"A lot of people"? How many people use this resolution?

What API does "Fast Burst Camera" use? Presumably not the original, long-deprecated Camera API, but might it be using CameraX? Because if it is using Camera2 as well that would prove that the restriction isn't the API - though it wouldn't tell you why Open Camera thinks the device doesn't support it. But Open Camera is, as the name says, "open": if another Camera2-based app gave you the resolution you want you can find the Open Camera source on Sourceforge and see whether you can work out the cause and make your own version (the code is available under the GPL V3 license). Or ask the developer if they have any ideas.

Of course if Fast Burst Camera uses CameraX then it could be a difference between the APIs, or how those APIs interact with elements lower in the stack (of which there are several layers). Getting into that will require a lot more effort, and most likely rebuilding the operating system on your phone from source (assuming you can identify where in the source the confusion arises). I think it unlikely that there's some config file sitting in some system directory that you can just add a line to and reboot the phone and it will work (though as my s21 isn't rooted I can't prove that).

(For what it's worth I don't think it is that Camera2 itself simply doesn't support this resolution: we've already established that it's available on other devices that use Camera2, which is actually pretty old. But it's conceivable that different APIs see the device slightly differently, so if the other app uses the more recent CameraX then that might be the answer).

Before we get ahead of ourselves, I suppose you have tested that 176x144 works in Fast Burst Camera? I just like to cover all of the bases.

There are a lot of assumptions here, but if Fast Burst Camera does work at that resolution and does use Camera2 then probably the simplest way forward would be to contact the Open Camera developer and ask them whether they have any idea why Open Camera does not offer this same resolution on the same device?
in "fast burst camera" the resolution of 176x144 works but the app doesn't support timestamp so i tried adding the resolution of 176x144 by manually editing the source code of "open camera" and what happened was is that photos were being taken in 176x144 but the images were distorted.

it would be highly appreciated if an expert showed us how to:
1) successfully add the resolution of 176x144 to the source code of "open camera"

or

2) instruct us on how to add the resolution of 176x144 to camera2 api if root access is granted on the device
 

Attachments

  • Screenshot_20230710_051049_Open Camera.jpg
    Screenshot_20230710_051049_Open Camera.jpg
    191.5 KB · Views: 40
You'll probably find it easier to contact Mark Harmon, the developer of Open Camera. It's an Open Source project and he has its own web site, blog, etc.
But if you insist on doing it yourself, he also has its source code on Github:
Be sure to read through the documentation notes -- i.e. in Open Camera / Code / [31a38f] /_docs/devices.html

<p>If you're interested in enabling Camera2 support for advanced features (manual focus, manual exposure, expo bracketing, HDR),
be aware that some devices have poor support for Camera2 (even if they support the API, the
implementations seem to have problems). Thankfully things seem to be improving on that front with newer
devices. Please read the details below on what I know about different devices.</p>

<p>Also note that just because a manufacturer advertises a particular camera feature, it doesn't mean that Open Camera can use
it. Unfortunately some manufacturers limit some features to the "stock" camera application, and don't make it available
through to third party cameras.
 
yes i did precisely that, i added the resolution of 176x144 to the photo resolutions in the source code in the following java classes in "open camera" source code :
CameraController2.java
ImageSaver.java

the images come out in 176x144 resolution but they are distorted, what am i missing here?
 
Back
Top Bottom