Are you sure it would even work? Maybe it needs Sony’s framework to work properly, and I don’t think that Android Support relies on it because it’s built on top of AOSP.
Then again, maybe I’m wrong…
Are you sure it would even work? Maybe it needs Sony’s framework to work properly, and I don’t think that Android Support relies on it because it’s built on top of AOSP.
Then again, maybe I’m wrong…
Nope.
But it’s worth a try, eh?
Absolutely! 20 chars and stuff
What is so special about this camera app?
It may offer a slightly better experience when taking photos (that’s a big maybe, because camera2 api is not supported on 10 III running SFOS).
I’m keeping my fingers crossed (for camera2 api and some other missing features on 10 III)
Actually today I checked Open Camera. You can switch camera API within settings. Switching to camera2 didn’t show any error on my XA2+. However, from quick test pictures I haven’t found any difference.
Are you sure that the improvements will be due to the apk rather than the driver itself?
If I’m not mistaken, the drivers are not those optimized by Sony, it’s the brightness control under sailfish of the LED that reminds me of that, I have the impression that the problem is quite similar. …
I think Xperia camera will never work the same way as on native Android. As far as I understand it, you have the Android driver, and it doesn’t go straight to an Android app, but instead first gets adapted to SFOS way of doing things (droidcamera that right now only supports Camera1API), and then back to the Android AppSupport. So Android camera app doesn’t simply talk to the driver, but instead goes through 2 adaptation layers. So even if droidcamera will start supporting all the features, it will still not be the same as on Android phone. And there shouldn’t be any features that Android apps can access but native SFOS app can’t.
I think that is because the layer that talks between the Android driver and SFOS only supports Camera1API. But then translation from SFOS interfaces to AppSupport interfaces does support Camera2API, that is why OpenCamera and API prober do show all features are supported, but from my testing they do nothing.
I can confirm this, tested with Android Open Camera on Volla / Waydroid. Switching to the API2 leads to much better images, it works!
Better sensitivity, better colours.
edit: I’ll try tomorrow with Xperia 10 & AlienDalvik…
Then there’s sony proprietary camera algo blobs that get erased when unlocking bootloader (at least that’s my understanding of Has anyone an exploit for backing up TA (Trim Area) partition on Xperia 10 iii), but probably not worth it as, from my brief excursion to android side everyone is complaining about sony camera performance/quality anyway
Is this even true, or just an urban myth? Personally I can’t really see any reason Sony would want to nuke the camera software when you unlock the bootloader.
Just checked, but i think camera2api needs to be interpreted by the sony somehow, cause i’ve got the same exact result on my xa2 with the default app
This has been made with opencamera and camera2api
This has been made with the stock camera app
Or viceversa, but still they are pratically the same…
Edit: the only difference seems to be that photo with opencamera are thrice the size, like the jolla one is 4.5 mb versus the opencamera 12 mb, quite a difference…
What’s the urban myth? You need a jailbreak to unlock bootloader nasty way, the good way erases keys to closed blobs
To add to the confusion, I believe, this is true for older Xperias, but not for the 10 series and friends.
Before i flash my xz2 Compact with the Community-Port i tested the Camera with Stock Android and after flash. The Picture-Quality remains the same. Only the Focus seems to be affected (often fails to find the right spot) with the Jolla-Photo-App and also with Advanced-Cam-App. But this behaviour seems to be a known issue and will hopefully fixed when switching to camera2api.
I repeated tests with Volla and Xperia 10, Stock Camera and Android Open Camera.
Android Open Camera:
There is no noticeable difference in quality between Original Camera-API and Camera2-API, There is a little difference in file size, this may be coincidence because the test photos are not absolutely identical.
Camera2-API shows ISO 1920 and shutter time on the screen depending on the light conditions while operating the camera. Original Camera-API doesn’t.
Same situation on both phones.
Stock Camera:
Picture quality is the same as above, Camera2-API not available.
Open Camera 1.51.1 on 4.5.0.19: all Settings sub-pages fail to render for some reason. Android back button still works, so app doesn’t completely hang.
Tried restarting everything but problem persists.
Anyone else experiencing this?
(Fortunately Camera2 API toggle is on main page.)
sometimes when you rotate the screen, it updates the opencamera settings display. if you rotate it a few times, you can see where to click, even if you have to visually remember it when you rotate back.
OR you can edit the prefs and uri grants in the terminal.
i edit opencamera prefs to use camera2 and set save location to sdcard with a script that works something like this:
content://com.android.externalstorage.documents/tree/3a40d44e-582e-11ee-b39d-6fe95b3c53ab%3ADCIM%2FOpenCamera
/home/.android/data/data/net.sourceforge.opencamera/shared_prefs/net.sourceforge.opencamera_preferences.xml
preference_save_location_saf
<string name="preference_save_location_saf">content://com.android.externalstorage.documents/tree/3a40d44e-582e-11ee-b39d-6fe95b3c53ab%3ADCIM%2FOpenCamera</string>
preference_using_saf
<boolean name="preference_using_saf" value="true" />
preference_camera_api
<string name="preference_camera_api">preference_camera_api_camera2</string>
/home/.android/data/system/urigrants.xml
<uri-grants/>
to <uri-grants> </uri-grants>
<uri-grant sourceUserId="0" targetUserId="0" sourcePkg="com.android.externalstorage" targetPkg="net.sourceforge.opencamera" uri="content://com.android.externalstorage.documents/tree/3a40d44e-582e-11ee-b39d-6fe95b3c53ab%3ADCIM%2FOpenCamera" prefix="true" modeFlags="3" createdTime="1695268606158" />