I have a problem
On Galaxy A5 2017 Marchmallow, the jpeg generated file has 30 Mbytes (for 12 Mpx) whatever is the jpeg compression parameter
It is not a blocking problem since I prefer storing in best quality then adjust it on computer and sdcards are large.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In fact, compression parameter works if I disable camera 2 api mode
in this case at 100% size is 10 Mbytes, 80% 1,6 Mbyte
after inspection with binary editor, it seems that under camera 2 api, file is paded with 00 bytes until 30 Mb
If I compare used space between camera 2 and without camera 2 api I have on an example about the same size 11,5 Mbyte quality 100% 1 Mbytes quality 50%
padding is done by every camera application using camera 2 api, google, open camera, etc
not with the basic application may be not using camera 2 or removing padding
Last edit: danielfr40 2017-03-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the update - if it's happening with other 3rd party apps using camera2, this seems to be a problem with the device's camera2 implementation (unfortunately camera2 seems to be a lot more buggy on many devices, than the old api...). I confirmed that the quality setting works as expected on the OnePlus 3T with Camera2 enabled.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, quality setting works, as observed under jpeg scanning tool, datas with information decrease in size with the compression ratio, but compensated by zero byte
may be corrected by future firmware update.
minor trouble
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Noticed exactly the same issue, I also have the same phone.It would be great if the image file could be saved without the padding as it would save having to run the images through another application later. I like the extra manual features Camera2 API offers so will continue to use the feature as I have plenty of storage but obviously the extra bytes slow down save times which slows bursts etc.
Great app though, love it!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I wrote an Android utility which scan the galaxy A5 DCIM folder and subfolder and other and which remove the padding
to be dataloaded on http://psylon.free.fr/freeware/CleanJpgA5/CleanJpgA5en.htm
I just use it on my phone so test it carefully on yours before to really use it
best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Replying to an old thread, but I have noticed similar problem on OnePlus2.
I have custom ROM (Delight ROM 1.2 beta which is 8.0.0 Oreo). I took photos with Open Camera with quality settings 50% and 100%. I noticed that the file sizes were almost same. I also checked those photos on my laptop with image viewer and both photos were saved as 98% quality!
This is same with other camera apps which have quality setting, for example A Better Camera, Camera FV-5 and a port of Snapdragon Camera.
Then I flashed stock ROM OxygenOS 3.6.0 (Android Marshmallow) back and made same test. Photos were saved properly with different quality.
So I'm wondering do different custom ROMs have different implementation of Camera2 API or is it because of Oreo? If you have phone with stock Oreo do you see difference in quality setting?
What can I tell to the ROM developers to fix Camera2 API implementation if they insist that there is nothing wrong with their ROMs?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It sounds reasonable to report to the ROM developers, if it can be reproduced with different camera applications, and doesn't happen with the stock OS.
I note that the JPEG quality is ignored on my Samsung Galaxy S10e, whether using the old or Camera2 API. I confirmed this still works with Open Camera on another device (Nokia 8). Meanwhile, I also noted that Footej's JPEG quality option has no effect on my S10e (but it does have an effect on my Nokia 8). So I think Samsung have not implemented this API.
ETA: the JPEG quality will have an effect if any post-processing effects are applied by Open Camera (i.e., it Open Camera decodes the JPEG to apply edits, and then resaves), because then I use the JPEG quality setting when saving the bitmap, which works. I suppose a workaround might be to force resaving the JPEG always, but I haven't bothered doing this (and it would make saving slower) - also this would only be useful for using a decreased quality than whatever Samsung are using, it couldn't be use to increase the JPEG quality.
Last edit: Mark 2020-01-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-07-24
IamamIamamamamIamamIIamamIamamamamIamamIIamamIamamamamIamamIIamamIamamamamIamamI amamamamamamamamamamamamamamamamamamamamamamamamamamamamamamamamI am using Samsung A5 (A520F) with API 2.0 and with the same problem. It was very annoying to have internal storage full of 30 MB photos. Open Camera FAQ led me to am idea that solved the problem:
Go to photo settings and enable Stamping photos. Then disable all stamp texts (date, time, gps).
Until now all photos has reasonable file size around 1-2 MB.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-12-06
You are really a genius!
Solved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-12-17
thanks! finally no more forever uploads to dropbox for just a few photos...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2021-04-11
Samsung A5 (A520F) API 2.0 on LineageOS 17.1 (25-03-2021) same problem. Solved thanks to your idea! Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-07-24
BTW, there is something rotten in this submission form... Using Chrome from Android
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First thanks for this open source product very powerfull, for me the best on my smartphone
comparative review on
http://www.phonandroid.com/forum/l-appareil-photo-du-galaxy-a5-2017-t168418.html
sorry, in french
I have a problem
On Galaxy A5 2017 Marchmallow, the jpeg generated file has 30 Mbytes (for 12 Mpx) whatever is the jpeg compression parameter
It is not a blocking problem since I prefer storing in best quality then adjust it on computer and sdcards are large.
In fact, compression parameter works if I disable camera 2 api mode
in this case at 100% size is 10 Mbytes, 80% 1,6 Mbyte
after inspection with binary editor, it seems that under camera 2 api, file is paded with 00 bytes until 30 Mb
If I compare used space between camera 2 and without camera 2 api I have on an example about the same size 11,5 Mbyte quality 100% 1 Mbytes quality 50%
padding is done by every camera application using camera 2 api, google, open camera, etc
not with the basic application may be not using camera 2 or removing padding
Last edit: danielfr40 2017-03-05
Thanks for the update - if it's happening with other 3rd party apps using camera2, this seems to be a problem with the device's camera2 implementation (unfortunately camera2 seems to be a lot more buggy on many devices, than the old api...). I confirmed that the quality setting works as expected on the OnePlus 3T with Camera2 enabled.
Yes, quality setting works, as observed under jpeg scanning tool, datas with information decrease in size with the compression ratio, but compensated by zero byte
may be corrected by future firmware update.
minor trouble
Noticed exactly the same issue, I also have the same phone.It would be great if the image file could be saved without the padding as it would save having to run the images through another application later. I like the extra manual features Camera2 API offers so will continue to use the feature as I have plenty of storage but obviously the extra bytes slow down save times which slows bursts etc.
Great app though, love it!
Hi
I wrote an Android utility which scan the galaxy A5 DCIM folder and subfolder and other and which remove the padding
to be dataloaded on http://psylon.free.fr/freeware/CleanJpgA5/CleanJpgA5en.htm
I just use it on my phone so test it carefully on yours before to really use it
best regards
Replying to an old thread, but I have noticed similar problem on OnePlus2.
I have custom ROM (Delight ROM 1.2 beta which is 8.0.0 Oreo). I took photos with Open Camera with quality settings 50% and 100%. I noticed that the file sizes were almost same. I also checked those photos on my laptop with image viewer and both photos were saved as 98% quality!
This is same with other camera apps which have quality setting, for example A Better Camera, Camera FV-5 and a port of Snapdragon Camera.
Then I flashed stock ROM OxygenOS 3.6.0 (Android Marshmallow) back and made same test. Photos were saved properly with different quality.
So I'm wondering do different custom ROMs have different implementation of Camera2 API or is it because of Oreo? If you have phone with stock Oreo do you see difference in quality setting?
What can I tell to the ROM developers to fix Camera2 API implementation if they insist that there is nothing wrong with their ROMs?
It sounds reasonable to report to the ROM developers, if it can be reproduced with different camera applications, and doesn't happen with the stock OS.
The relevant parameter is CaptureRequest.JPEG_QUALITY ( https://developer.android.com/reference/android/hardware/camera2/CaptureRequest.html ). (Open Camera sets this in CameraController2.CameraSettings.setupBuilder().
The same thing is happening with me. The images are of 30mb size even after setting the JPEG_Quality.
I note that the JPEG quality is ignored on my Samsung Galaxy S10e, whether using the old or Camera2 API. I confirmed this still works with Open Camera on another device (Nokia 8). Meanwhile, I also noted that Footej's JPEG quality option has no effect on my S10e (but it does have an effect on my Nokia 8). So I think Samsung have not implemented this API.
https://stackoverflow.com/questions/20420682/android-camera-parameters-setjpegquality-deprecated-custom-camera-application has someone reporting this being ignored for old API on the Galaxy S4.
ETA: the JPEG quality will have an effect if any post-processing effects are applied by Open Camera (i.e., it Open Camera decodes the JPEG to apply edits, and then resaves), because then I use the JPEG quality setting when saving the bitmap, which works. I suppose a workaround might be to force resaving the JPEG always, but I haven't bothered doing this (and it would make saving slower) - also this would only be useful for using a decreased quality than whatever Samsung are using, it couldn't be use to increase the JPEG quality.
Last edit: Mark 2020-01-19
IamamIamamamamIamamIIamamIamamamamIamamIIamamIamamamamIamamIIamamIamamamamIamamI amamamamamamamamamamamamamamamamamamamamamamamamamamamamamamamamI am using Samsung A5 (A520F) with API 2.0 and with the same problem. It was very annoying to have internal storage full of 30 MB photos. Open Camera FAQ led me to am idea that solved the problem:
Go to photo settings and enable Stamping photos. Then disable all stamp texts (date, time, gps).
Until now all photos has reasonable file size around 1-2 MB.
You are really a genius!
Solved.
thanks! finally no more forever uploads to dropbox for just a few photos...
Samsung A5 (A520F) API 2.0 on LineageOS 17.1 (25-03-2021) same problem. Solved thanks to your idea! Thanks!
BTW, there is something rotten in this submission form... Using Chrome from Android
At long last, seems to be fixed on my Galaxy S24+, I confirmed the image quality setting takes effect, for old and camera2 API.