Activity for Mark
-
Mark modified ticket #1328
Gallery does not open, because of wrong Intent string
-
As noted in my earlier comment, it's not possible to add this by default, but the next version will have the debug option Settings/More camera control/Gallery to support different methods of launching a third party gallery application.
-
viewing last photo opens Image Toolbox
-
As noted in my earlier comment, it's not possible to resolve this by default, but the next version will have the debug option Settings/More camera control/Gallery to support different methods of launching a third party gallery application.
-
Note that Dolby have reportedly sued Snap over AV1 (e.g. https://www.techspot.com/news/111865-dolby-sues-snap-over-video-compression-patent-claims.html ). It's possible that applies more to applications including that code specifically rather than using on-device codecs (AV1 at least has Android support directly now as far as I can tell). But then, more generally, that does highlight a risk of including third party libraries to do image/video encoding (in theory the risk applies to any code I write...
-
I'm not quite sure what methods that the GCam ports use, but I note they have the advantage that there are many versions of these often tailored made/supported for specific devices, In theory there are hacky backdoor methods that work on some devices, but will break or give buggy behaviour on other devices - the link above is indeed useful, so yes that explains why they need different versions. Renaming the package name requires some kind of development tools (either rebuilding from the source, or...
-
See also https://sourceforge.net/p/opencamera/tickets/1328/ .
-
I've added support for MediaStore.ACTION_REVIEW for the next version, but I'd had to add it as a second priority to "com.android.camera.action.REVIEW" - a problem is that some older gallery apps only support "com.android.camera.action.REVIEW" (even though in theory they're the ones that should be updated, users will complain to me if Open Camera no longer works with it...) I wasn't sure what your symptoms were - if you weren't seeing any options at all for viewing photos/videos, then the new version...
-
Hi, what device and gallery application is this? The reason is due to the various different ways of calling applications on Android: Originally, the only official way was to call an application to open an image/video ("Intent.ACTION_VIEW"). This was very broad, and meant it would also include image editors, media players and so on. Google camera and Google photos used an undocumented method ("com.android.camera.action.REVIEW") which meant (a) it restricted it to gallery apps, and (b) meant videos...
-
Thanks, I'll take a look. com.android.camera.action.REVIEW is an unofficial intent as it was used by the stock Android camera years ago and because a kind of unofficial standard. I hadn't noticed MediaStore.ACTION_REVIEW, so I'll see if thican replace it. Which gallery app are you using - or if it's the stock gallery, what device is this?
-
add resolution 50Mpxl and macro
-
As far as I can tell, most devices aren't allowing third party applications to access the very high resolutions. (Note that you'll still get the benefit of the camera's sensor - I don't know if you have a particular need for a 50MP image, or are just assuming higher MP is better.)
-
Hi, yes it depends on the manufacturer. Open Camera supports all the relevant APIs (accessing multiple cameras, automatically switching via zooming in and out; accessing specific "lenses") but some manufacturers still don't expose to third party applications via the Android API. I did look at CameraX a few years ago, but I don't think it would help here (CameraX still uses the Android API).
-
Can't set it as a Default Camera App
-
Unfortunately Android doesn't have a concept of default camera app - it's no longer possible for apps to call third party camera apps, and behaviour such as launching from a gesture is device/company specific.
-
The next version will support Exif interface for PNG and WebP. Note it's not possible to capture directly as PNG - the JPEG data comes direct from the camera driver (although possibly this could be done by requesting data in YUV_420_888 format). Thanks for the info on PNG and HDR. I think UltraHDR is only currently supported via JPEG and HEIC formats, so there's a gap here (if I use YUV_420_888 format to get a lossless result, there wouldn't be any HDR info to add to the PNG result).
-
For non-RAW mode I get the data from a JPEG stream - Android does support returning in other formats (e.g. Camera2 supports YUV_420_888), I have thought about trying to convert from that instead but not yet implement this.
-
This is fixed for the next version.
-
Please keep things friendly :)
-
Indeed I need to add support for this, since Android restricted this. Note though that the standard Android backup when moving to a new phone should transfer application settings anyway - unless you're preferring to not use this or aren't using Google services(?)
-
Indeed there is a double save/compression. MyApplicationInterface.getImageQualityPref() will set the first request to 100% for when non-JPEG formats (WebP, PNG) (which I know is still lossy, but tries to minimise the first generation loss). Although JPEG XL could be supported similarly to WebP/PNG, I'm a bit wary of adding it at the moment, firstly due to the issue that it won't be direct from the camera, and due to losing support for UltraHDR.
-
Thanks for the comments and suggestions! Yes it's true, some sort of intro guide could be useful. I don't have immediately plans for a built-in gallery I'm afraid.
-
It still feels unlikely that this is due to build issues (it wasn't clear which differences you were seeing between Google Play, Sourceforge and F-Droid?) If there was a change due to a phone's update, again that could just be a change in the update and not spyware. "Can you point me to your best documentation and the source code for these settings?" It's set in VideoProfile.copyToMediaRecorder(), specifically the call to media_recorder.setVideoEncodingBitRate(this.videoBitRate); "Is there any way...
-
Hi, sorry for the delay - I get a lot of posts/emails. There should be no difference in the different versions. Sourceforge receives the exact same APK as Google Play (and will be signed the same). F-Droid builds from the source (so has a F-Droid's signature, but is built from identical source). I wasn't sure what you mean by maximum bitrate or framerate? The framerate option is only a recommendation to the device so may vary depend on the scene, similarly for the bitrate, so it could be coincidence...
-
Good point, I've added this to my TODO.
-
Hi, Open Camera does have support for UltraHDR - see Settings/Photo settings/Image format/"Ultra HDR JPEG". But it requires the device to support this for third party camera applications, I'm not sure if Pixels have enabled it yet (it it supported on my Galaxy S24+, but not on my older Pixel 6 Pro). The double-tap-power-button is something that's device specific (again Samsung does better here, although one still has to unlock as they don't allow third party applications to launch when locked). (Don't...
-
Hi, can you clarify - as in the flash comes on but is not as bright in manual mode compared to auto? What device is this?
-
Thanks for the report. I don't have a Pixel Fold to test this, although looks like this is now being tracked as a device issue ( https://issuetracker.google.com/issues/471257330 ).
-
Does this happen with any other camera apps?
-
save gps altitude in exif as float not integer
-
This is part of Android as far as I can tell - as in the device saves the GPS exif information. Even if I wrote my own code to save the exif information, the same issue applies to Android's location API: I confirmed that this is also being rounded to an integer (as can be seen with Open Camera's photo stamp option). Although Location.getAltitude() returns a "double", I see it rounded to an integer on my device.
-
Can you post an example photo please, where Settings/Photo settings/"Remove device EXIF data" is set to "Remove device Exif data". Also which version of Open Camera is this (see Settings/About)?
-
Changing Settings/On screen GUI/"Immersive mode" to "Hide everything" would remove the on-screen icons. A possible workaround to make completely black might be Settings/Camera preview/"Ghost image" if you have a completely black image to supply, although currently the max opacity you can set to is 80%
-
Hi, make sure Settings/"Camera API" is set to "Camera2 API", then this can be set via Settings/More camera controls/"Shutter sound".
-
Storage Access Framework
-
Fixed for the next version - force quitting whilst the SAF dialog is open will mean SAF is turned back off.
-
Hi, thanks for the suggestions. Which metadata isn't getting removed when using Settings/Photo settings/"Remove device EXIF data"?
-
The reply is correct - whilst in theory I could use a library to support this, it's likely a large amount of work, and would be difficult to support a range of USB cameras.
-
What happens if you click on the thumbnail (bottom right when phone held in portrait) after taking a photo? As in they don't show in the gallery? Maybe try a file explorer app to see if that shows files in the relevant DCIM folder?
-
Usually a restart fixes this. If not, are other camera apps able to access the camera?
-
I've fixed this for the next version (to measure time from when each photo was started, rather than only restarting the timer after taking a photo).
-
Zoom issues on Galaxy S24 Ultra
-
Thanks for the update. As far as I can tell this is a device limitation, and I see similar in the Samsung stock camera: RAW is only available in Pro mode as far as I can tell(?), and in Pro mode you can't switch to different cameras by zooming, and only by selecting the cameras manually. Admittedly it's more confusing in Open Camera as it's not obvious that turning on RAW turns off this ability, although I'm not sure there's any way to get this information easily (Samsung have the advantage they...
-
If it's supported by the device (and the device allows third party applications to use the ultra-wide camera). Make sure Open Camera's Settings/"Camera API" is set to "Camera2 API", then see if you can either zoom out (to below 1x), or if there's a camera icon with a "+" to choose different cameras.
-
Open Camera no longer cycles through all cameras, but separates switching front/back as a separate icon, so you should be able to ignore additional cameras if you don't want them.
-
Failed to start camera preview during lens selection
-
Open Camera now supports multiple cameras via a menu, rather than cycling through, so at least it's a bit easier to skip it. Is the problem camera still occurring, in which case please post a screenshot of the camera menu in Open Camera?
-
Thanks for the update. Open Camera only exposes cameras that are made available to third party applications. In Open Camera with the OnePlus Nord, does zooming in and out switch between different cameras? If not, it should be raised with OnePlus as a request to support multiple cameras for third party camera applications.
-
Thanks for the info. I'm not aware of anything I'm doing differently to support flicker I'm afraid. The only possible related setting is Settings/Processing settings/"Anti-banding", but that just sets an option to the camera driver, rather than it being part of Open Camera's algorithms. It's on my todo to support zoom for RAW images.
-
Sure, have reopened for the feature of having manual shutter with auto ISO (or vice versa).
-
Shutter speed cap
-
Hi, yes having one of these set manually and the other set to auto is a new feature available in Android 16, it's on my todo to add support for this.
-
Please see reply at https://sourceforge.net/p/opencamera/tickets/1285/ .
-
Please see reply at https://sourceforge.net/p/opencamera/tickets/1285/ .
-
Shutter speed cap
-
Thanks for the info. I'm afraid that the decisions on shutter speed and ISO in auto mode is controlled by the device rather than the application, and there isn't a way as far as I know to set a maximum value. Android 16 does introduce a way to have manual shutter speed with auto ISO (on my TODO to support), although that still doesn't seem quite what you're after.
-
"The FP5 has a 50MP Camera (8192x6144 (50,33MP) and this is usable with other camera apps" Which non-stock camera apps have 50MP resolution on the Fairphone 5? Thanks for the links to the e/OS fork, that's interesting - ideally I'd stick with the standard Android API rather than using device specific routes (the device specific strings for the keys), there's the risk that even if it works now, it could change in future. Ideally FairPhone would expose this either directly, or via https://developer.android.com/reference/android/hardware/camera2/CameraMetadata.html#REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR...
-
I have issues on Xiaomi Redmi 12 with MIUI Global 14.0.6 and Android 13.
-
Thanks for the info - indeed, this often seems to be the case, but often hard to be sure if I don't have that particular make of device, so thanks for the confirmation.
-
Thanks for the update!
-
Although it lists 3 back cameras, it looks like ID0 is for the logical camera (that should automatically switch between the cameras based on zoom), with ID2 and ID3 being the physical cameras for main and ultrawide. So I don't think the telephoto lens is exposed as a camera to be able to explicitly switch to. It may be that the default camera (ID0) switches to telephoto when zooming in(?) - although if not, it's not something that Open Camera can access I'm afraid.
-
Hi, please see reply at https://sourceforge.net/p/opencamera/discussion/photography/thread/6b223428b3/?limit=25#4930/fd33 . Note that what a device allows for third party camera applications doesn't have to match what they expose for the built-in camera.
-
I don't have plans to add scanner-specific features I'm afraid.
-
Hi, as far as I can tell (at least testing on my Galaxy S24+), the high MP resolutions aren't made available to third party applications, instead they pixel bin it down to the more regular resolutions.
-
Thanks for the info - I've identified an issue that seems to match this description, affecting a small number of devices (including Nokia G42 5G), I'll try to fix for the next version. If in Open Camera you go to Settings/About, can you let me know please what it lists for "Device model"? (I wasn't sure if this is "Nokia G42 5G", or some other device model/code.) Camera2 API offers extra features like manual controls (and on some devices at least may be faster at taking photos), but original API...
-
jerk from zoom on videos
-
That's great to hear! Yes no need for donations, thanks anyway.
-
I believe that's Google Photos - Open Camera doesn't have a built-in gallery, when you click on the thumbnail it just links to the gallery app on your phone (which looks like Google Photos in your case). I imagine it's something they changed in an update to Google Photos.
-
Interestingly the "Display size:" in the About info suggests the display is in portrait orientation, so I'm not sure why pulling down the notification/settings is operating in landscape. But yes, I agree with trying latest version - for non-Google devices, I'd recommend installing from F-Droid - https://f-droid.org/ ). Whilst I'm not aware of anything that would have affected/fixed this, it seems best to try the version that's updated with latest libraries and targetting a more recent Android ve...
-
Android now has QR code scanning as standard, via the pull down widgets, "Scan QR code". Or even from within Open Camera, holding the home button, then doing Google's "circle to search" should work on QR codes.
-
Unfortunately these controls are now deprecated on Android (and they did look rather old fashioned). Potentially in future I could add more modern buttons to do something similar.
-
Thanks for the update. I have identified an ANR in my Google Play stats showing a Camera2 startup issue affecting a small number of devices, including the Pixel 5a. I should be able to put a workaround in for the next version (unfortunately that will be 1.56, not the 1.55 that just went out), so hopefully that will be what you're seeing.
-
I'm not sure what you mean by Google lens button? Open Camera doesn't have a built-in button for Google lens. Maybe post a screenshot?
-
I'll put a fix in hopefully for next version. In the meantime note you can disable haptic feedback under Settings/More camera controls/"Allow vibration feedback".
-
I don't have a device to reproduce/investigate the issue I'm afraid, which makes this hard. Note that immersive mode is optional - I mean, I appreciate reporting the bug, but if it's causing problems for you using Open Camera it's better to just disable it (long pressing to go to Settings). I realise I missed the separate point about stuck in landscape orientation - these days Open Camera shouldn't be locked to an orientation. If the phone is held in portrait, then go to Settings/About and paste...
-
Version 1.55
-
It's not in my plans I'm afraid (and arguably there are some privacy-related benefits in Open Camera not having Internet permission, so I've been trying to keep with that).
-
Galaxy S20+: 3/4 cameras selectable, does not include primary 64MP camera
-
It'll likely automatically switch to telephoto when you zoom in. Older Galaxy S devices don't expose choosing a specific lens for third party applications I'm afraid. It does seem to be supported for the S24 at least (works on my Galaxy S24+).
-
Fairphone Gen 6.: Main Camera with 50 MPixels not recognized?
-
Normally the camera should automatically switch to the telephoto lens when zooming in. Open Camera now supports choosing a physical lens, but this requires the device to support it for third party applications.
-
Thanks for the info, I can reproduce on my Galaxy S24+. I can also reproduce with other third party camera applications, so seems to be a device behaviour. I'll see if I can report as a Samsung bug.
-
Unfortunately there was an anonymous commenter posting several repeated comments, in some cases copying from existing comments, across various threads including this one. So I suspect the notifications are genuine - someone else was posting these anonymously. I've deleted the comments, so they no longer show here. Sorry for the confusion!
-
Indeed, Open Camera uses Java with the Android APIs, rather than any cross-platform toolkits. The Camera API specific code is self-contained inside the CameraController/CameraControllerManager classes (indeed that's how it supports both the original and Camera2 APIs). Although I imagine the issue would be the large number of other Android specific APIs in use too (not just GUI, but things like image processing, launching background threads, and sadly even now file access, can be different to using...
-
Thanks for the info, it's on my TODO for a future version to have option to disable optical stabilization.
-
Please see Settings/Photo settings/"Enable fast HDR/expo burst" (under debugging options) - what value is that set to, and does changing it help? Also please make sure you're on the latest version v1.54.1.
-
Catalan translation
-
GPS Longitude show 0.0 in Exif (v1.54.1)
-
This suggests the device is not storing the GPS data in the JPEG information correctly, but I've applied a workaround to force writing the data (for Camera2 API) if longitude or latitude is 0 (similar to existing workarounds when the data isn't present at all).
-
Hi, it adds vibration/haptic feedback for various "seekbars" (e.g., the sliders for changing zoom or exposure).
-
[feature] please allow entire "lockscreen session" to be browsable without unlock, not just one photo
-
Open Camera doesn't have its own built-in gallery - so it's not possible to only show photos from the current session I'm afraid, instead unlocking is required to go to the installed gallery application.
-
Also see https://sourceforge.net/p/opencamera/tickets/1253/ .
-
Also see https://sourceforge.net/p/opencamera/tickets/1253/ .
-
Thanks - can you post screenshots of the bit above that screenshot please? Also make sure in Open Camera Settings/"Camera API" is set to "Camera 2 API"?
-
Bug
-
Open Camera doesn't have the ability to crop photos?
-
imx 686 capture 12MB only
-
Corrupted Front Camera Images on FP5
-
Thanks for the update - it seems worth reporting to Fairphone 5. I don't know if I changed something that either fixed a bug, or just worked around it.
1 >
