# Use all camera functions, especially wide angle

**URL:** <https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826>\
**Category:** System and Apps\
**Tags:** Fairphone3, Fairphone4\
**Created:** [21 October 2022 20:35 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826 "2022-10-21T20:35:11Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Barry](https://community.iode.tech/letter_avatar_proxy/v4/letter/b/958977/32.png) [@Barry](https://community.iode.tech/u/Barry)\
**Post date:** [21 October 2022 20:35 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/1 "2022-10-21T20:35:11Z")

</div>

Since Android 11, it seems to be extremely difficult to use all cameras and all functions with 3rd-party apps. Is this the case everywhere or does only Fairphone have such a big and almost insurmountable problem with this? They have been working on it since at least March and put it on hold around the end of September!!!  
There is the topic “Camera & Camera2 API - missing features & bugs” in the Fairphone forum where the [problems](https://forum.fairphone.com/t/camera-camera2-api-missing-features-bugs/83196) with the cameras are summarized:

> **summarized problems**
>
> > [@](#):
> >
> > # Missing features
> > 
> > - The **wide angle camera** is accessible only through the stock camera app, not through the API. This prevents its usage in alternative camera apps such as GCam or Open Camera.
> > - The full **48MP quality** (8000×6000) of the main camera and **24MP quality** (5760×4312) of the selfie camera are completely unavailable.
> > - For some reason, even the basic **12MP resolution** (4000×3000) is inaccessible in the **Camera2 mode** , though it’s probably fine when using the old camera API. This is problematic for example when taking HDR photos using Open Camera. You simply cannot achieve the full 12MP quality.
> > - The same applies to the basic **6MP resolution** (2880×2156) of the selfie camera. But funnily enough, this resolution is accessible in preview and video modes. Only the photo mode is missing.
> > - There also seems to be no access to **FPS values higher than 30** , which complicates, for example, slow motion video shooting.
> > - Also there is no direct access to the **ToF sensor**.
> > 
> > # Bugs
> > 
> > - When accessing the **selfie camera in video mode using the Camera2 API** , it sometimes freezes or straight up crashes apps. The workaround seems to be to set zoom to at least 1.07x, then it is stable. This is [reproducible](https://forum.fairphone.com/t/fp4-gcam-port/79450/45), but [not by all users](https://forum.fairphone.com/t/fp4-gcam-port/79450/47).
> > - Trying to access **1/8x slow motion** in GCam crashes the app. It works in Open Camera (0.125x speed), but the resulting video is choppy.

The solution of the problems could be partly with the proprietary blobs. And a large part seems to be related to the [SYSTEM\_CAMERA](https://forum.fairphone.com/t/camera-camera2-api-missing-features-bugs/83196/10) issue. Because the wide angle camera and the TOF sensor are not system cameras, you can’t use them:

> Also adding that Info here: Apps need SYSTEM\_CAMERA permissions to access the full feature set. This is only possible for apps on the system partition with correct permissions. Therefore app like Camera2 API Probe cannot see all features.  
> [https://source.android.com/devices/camera/system-cameras](https://source.android.com/devices/camera/system-cameras)
> 
> Not sure why it was done that way. Most user friendly way would probably be to drop the SYSTEM\_CAMERA requirement.
> 
> For custom Roms it should still be possible to grant that permission and access all features.

At the end of September Fairphone gave a [feedback](https://forum.fairphone.com/t/camera-camera2-api-missing-features-bugs/83196/58) (with the conclusion that the difficult topic is on hold):

> There’s no standard way in Android to work with those high resolutions, wide angle camera etc. Regular Android apps (installed via Play etc) can only access standard feature sets of Android (Android SDK etc). Anything that’s not covered by the SDK is just not accessible for regular apps. Preinstalled system apps (like our own camera app) can have access to everything we give them access to, including device-specific custom camera features.
> 
> Just to clarify: wide-angle support, high-resolution and other such features are not “exotic” or unique to Fairphone. But Android just doesn’t provide a standard way to implement them. There are ways to make some such features accessible to 3rd-party apps (AndroidX, camera extensions), but that’s not done on FP3 and FP4, and is not a trivial topic at all.

I really have no idea about these things. I would just like to know if this is really such a big and time-consuming problem for professional Android developers? If so, I really wonder what Google was thinking making such a bullshit. This is all extremely unsatisfying!

I know that these are all not problems that iodéOS has to deal with directly. I was just hoping to get a professional view from another direction.

---

<div class="post-metadata">

**Author:** ![AlphaElwedritsch](https://community.iode.tech/user_avatar/community.iode.tech/alphaelwedritsch/32/496_2.png) [@AlphaElwedritsch](https://community.iode.tech/u/AlphaElwedritsch)\
**Post date:** [22 October 2022 21:00 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/2 "2022-10-22T21:00:13Z")

</div>

No chance until fairphone open their propritary code

---

<div class="post-metadata">

**Author:** ![Barry](https://community.iode.tech/letter_avatar_proxy/v4/letter/b/958977/32.png) [@Barry](https://community.iode.tech/u/Barry)\
**Post date:** [23 October 2022 10:57 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/3 "2022-10-23T10:57:24Z")

</div>

You mean the iodé team could solve the problem if Fairphone would publish the code? Would be nice of course, but I guess that iodé would not have time for that?

But my question remains: Is it also a very difficult and extremely time consuming task for all other manufacturers? Do the additional cameras and some camera functions of the smartphones of all other manufacturers also not work with 3rd-party apps? Or have they solved the problems long ago? 🤔

---

<div class="post-metadata">

**Author:** ![AlphaElwedritsch](https://community.iode.tech/user_avatar/community.iode.tech/alphaelwedritsch/32/496_2.png) [@AlphaElwedritsch](https://community.iode.tech/u/AlphaElwedritsch)\
**Post date:** [23 October 2022 13:53 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/4 "2022-10-23T13:53:01Z")

</div>

> [@Barry](#):
>
> You mean the iodé team could solve the problem if Fairphone would publish the code?

I think so

---

<div class="post-metadata">

**Author:** ![Barry](https://community.iode.tech/letter_avatar_proxy/v4/letter/b/958977/32.png) [@Barry](https://community.iode.tech/u/Barry)\
**Post date:** [4 November 2022 19:39 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/5 "2022-11-04T19:39:13Z")

</div>

Sad but true: The FP4 has been out for over a year and there is no solution in sight. 😥 I don’t think anything can be expected from Fairphone in the short or medium term. They are working hard on various other software issues and are **completely** busy with that. The question is rather if in the long run or if ever the camera problems will be solved by them.

@vince31fr Could perhaps the iodé team imagine to solve the camera issues from the FP4 if Fairphone would open the propritary code? Or at least make the TOF sensor and the wide-angle camera usable for 3rd-party apps? I don’t know if this is an appropriate question. This is pure desperation talking. ☹  
Just some thoughts on this: Maybe this would also bring iodé to Fairphone’s attention and create an official partnership??? Which would give iodé a higher visibility…

---

<div class="post-metadata">

**Author:** ![AlphaElwedritsch](https://community.iode.tech/user_avatar/community.iode.tech/alphaelwedritsch/32/496_2.png) [@AlphaElwedritsch](https://community.iode.tech/u/AlphaElwedritsch)\
**Post date:** [4 November 2022 20:57 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/6 "2022-11-04T20:57:05Z")

</div>

As long as FP is doing nothing, all questions are hypothetical, sorry.  
I can imagine your frustration, but it doesnt help.  
Was one of the reasons why i sold my fp4…

---

<div class="post-metadata">

**Author:** ![Barry](https://community.iode.tech/letter_avatar_proxy/v4/letter/b/958977/32.png) [@Barry](https://community.iode.tech/u/Barry)\
**Post date:** [4 November 2022 22:07 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/7 "2022-11-04T22:07:30Z")

</div>

> [@AlphaElwedritsch](#):
>
> Was one of the reasons why i sold my fp4…

I’m sorry to hear that. I know that Fairphone is not getting behind with the software problems and that their support is suboptimal. If iodé would agree to help with the cameras, it wouldn’t hurt to ask Fairphone for the code. They can only win with that, as it would soften the dissatisfaction of many a bit. I don’t think there’s anything wrong with letting others help you. Actually, it makes much more sense to get to the goal in a community, where perhaps even both sides get something out of it. I have the impression that the atmosphere among the fairphoners is tilting a bit in some cases. The intransparency and very difficult reachability makes people more and more dissatisfied. I would be willing to ask Fairphone for the code. But of course I would only do this if iodé could really help.

---

<div class="post-metadata">

**Author:** ![vince31fr](https://community.iode.tech/user_avatar/community.iode.tech/vince31fr/32/13_2.png) [@vince31fr](https://community.iode.tech/u/vince31fr)\
**Post date:** [16 November 2022 00:55 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/8 "2022-11-16T00:55:10Z")

</div>

Good news, wide-angle will work in next release for FP4. A beta build is available (go to [beta · master · iode / ota · GitLab](https://gitlab.com/iode/ota/-/tree/master/beta) to join the program).

---

<div class="post-metadata">

**Author:** ![Barry](https://community.iode.tech/letter_avatar_proxy/v4/letter/b/958977/32.png) [@Barry](https://community.iode.tech/u/Barry)\
**Post date:** [16 November 2022 17:23 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/9 "2022-11-16T17:23:04Z")

</div>

@vince31fr This is really very good news! 🎉 That is so great, thank you so much for that!!! 😃 👍

How exactly did you do that? Is Open Camera a system app now? Did you change anything else? Or have you solved it some other way?

---

<div class="post-metadata">

**Author:** ![AlphaElwedritsch](https://community.iode.tech/user_avatar/community.iode.tech/alphaelwedritsch/32/496_2.png) [@AlphaElwedritsch](https://community.iode.tech/u/AlphaElwedritsch)\
**Post date:** [16 November 2022 19:05 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/10 "2022-11-16T19:05:12Z")

</div>

OC is a system app  
Solved with SYSTEM\_CAMERA permissions

---

<div class="post-metadata">

**Author:** ![Barry](https://community.iode.tech/letter_avatar_proxy/v4/letter/b/958977/32.png) [@Barry](https://community.iode.tech/u/Barry)\
**Post date:** [16 December 2022 18:28 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/11 "2022-12-16T18:28:24Z")

</div>

> **[Camera & Camera2 API - missing features & bugs](https://forum.fairphone.com/t/camera-camera2-api-missing-features-bugs/83196/74)**
>
> The next CalyxOS update will include unlocked aux camera for all 3rd party apps. No need to mess with SYSTEM\_CAMERA or anything 😃

> **[Camera & Camera2 API - missing features & bugs](https://forum.fairphone.com/t/camera-camera2-api-missing-features-bugs/83196/76)**
>
> It is in proprietary blobs but with a little creativity you can bypass the check: https://review.lineageos.org/c/LineageOS/android\_hardware\_lineage\_compat/+/344852 https://review.lineageos.org/c/LineageOS/android\_device\_fairphone\_FP4/+/344881

> **[4.3.2 - Bugfixes and improvements](https://calyxos.org/news/2022/12/03/update-fixes-improvements/)**
>
> 4.3.2 - Bugfixes and improvements

### FP4:

- Make wide-angle camera available to third party apps (OpenCamera, Google Camera, amongst others)

> <https://github.com/LineageOS/android_device_fairphone_FP4/commit/39fbb665f2bf172699e056d31af94b62cf32e697>
>
> This basically NOPs update\_camera\_metadata\_entry() call that sets
> ANDROID\_REQUES…T\_AVAILABLE\_CAPABILITIES\_SYSTEM\_CAMERA to 1 for aux cam.
> 
> Change-Id: Ie869b3eb0ea85af99904e2e23e86c4cd0acc3596

🎉 CalyxOS has solved the problem of being able to use the wide-angle camera with all third party apps. The Camera2 API Probe [report](https://forum.fairphone.com/t/camera-camera2-api-missing-features-bugs/83196/87) contains 4 Camera ID’s. From Camera ID 0 to 3. Maybe even the TOF sensor will work. 🙂

@vince31fr Can this solution also be integrated in iodéOS?

---

<div class="post-metadata">

**Author:** ![Barry](https://community.iode.tech/letter_avatar_proxy/v4/letter/b/958977/32.png) [@Barry](https://community.iode.tech/u/Barry)\
**Post date:** [28 January 2023 19:56 UTC](https://community.iode.tech/t/use-all-camera-functions-especially-wide-angle/826/12 "2023-01-28T19:56:48Z")

</div>

Topic solved:

> [@Camera patch, monthly security updates (Android, kernel, firmware), A13 via OTA with closed bootloader?](https://community.iode.tech/t/camera-patch-monthly-security-updates-android-kernel-firmware-a13-via-ota-with-closed-bootloader/1126/1):
>
> 1. LOS has adopted the camera patch (bypassing the SYSTEM\_CAMERA permission check) from CalyxOS. Will it also be adopted in iodéOS?

> [@Camera patch, monthly security updates (Android, kernel, firmware), A13 via OTA with closed bootloader?](https://community.iode.tech/t/camera-patch-monthly-security-updates-android-kernel-firmware-a13-via-ota-with-closed-bootloader/1126/2):
>
> 1. Yes
