Rear Camera not using right resolution

[Ahtlon]

The Unihertz website advertises a rear camera resolution of 48 MP but the Lineage Camera app only reports 11.8 MP.

[ADeadTrousers]

I cannot confirm this.
Lineage Camera and Open Camera (for both Original and Camera2 API) report a max. resolution of 48 MP (8000x6000 P)
Can you elaborate this issue a little bit further? Like which model/variant you use and also which of the releases?

[Ahtlon]

I use the Atom L EEA
The system was built from source by myself with test-keys and the signature-spoofing patch.
Build date was 18.03.2022
I have pasted the Camera section of Deviceinfo here.

[Ahtlon]

I just "updated" to your latest Release "v20220216-alpha", so that signature spoofing and Magisk got disabled but the problem persists.
Full Deviceinfo output

[ADeadTrousers]

You've got me worried for a bit ;)
OK. So you've built your own ROM and also while testing mine you encountered that the resolution is not what it's used to be.
May I ask how you got the Deviceinfo? I just want to compare it with mine. Currently I can only rely on what Camera and Open Camera tell me.

Here is a screenshot from the Camera pp which shows the full resolution:

Here is a screenshot from the Open Camera app which shows the full resolution: (8000x6000 = 48.000.000)

Did you check if the stock rom reports the correct resolution? Just to rule out any hardware problem.

[Ahtlon]

Camera

Open Camera app

I have not checked the stock rom yet. Will try in the next few days or so.
Edit because i forgot: I used this app for the Deviceinfo.

[ADeadTrousers]

Just in case you did everything else on building your ROM correctly and there is no hardware issue:
Did you "upgrade" the bootloader and all the other other bits from the stock rom 20210520 or did you do the switch to LOS right after unboxing your device?

[Ahtlon]

So, after overwriting everything with Stock (20210518) using SP-Flash (is that what you meant with upgrading?), the Camera and system did report 48MP capability, [deviceinfo].
(relevant section: "#CAMERA2API=": { "0=back<LIMITED>8000x6000([100, 3200])": {)

After that I rebooted to bootloader and flashed your vbmeta and recovery (v20210810-beta).
Restart to recovery worked but TWRP did not accept any input. (a known problem apparently?)
Using SP-Flash I flashed the Lineage Recovery I build as part of the OS.
Since lineage recovery can be controlled using the hardware keys I used that to sideload your lineage-17.1-20220216-UNOFFICIAL-Atom_L_EEA-signed.zip.
There was a "signature verification failed" error but I chose to ignore that and install anyway. (I checked the MD5 of the file on SD and that wasn't the problem)
Reboot to Lineage
The Camera app still only shows 11.8MP max, [deviceinfo]
(relevant section: "#CAMERA2API=": { "0=back<LIMITED>4000x3000([100, 3200])": {

[ADeadTrousers]

I just switched my development phone from L TEE to L EEA to make sure the ROM is indeed working correctly. Previously I had some mixup with L TEE and XL TEE so I wanted to be sure that this isn't also the case here.

Besides the decryption not working in TWRP (Could be a side effect from fast switching between TEE and EAA, I'll have to look into this) everything else is working as expected. In TWRP the touchscreen is responding (binary hack) and Camera in LOS is correctly reporting 48 MP.

So I'm at a loss here. As long as I cannot reproduce the error I don't have anything to analyze.
As we both seem to be from europe (and even german speaking as from the screenshots) may I ask from where you are exactly? I'm from Austria by the way.
It would be interesting to get this sorted out as I had various other claims that my ROM isn't behaving as it should. So it would really help to have such a misbehaving device in my own hand to test it. Maybe, if we are not too far away from each other we could figure something out.

[ADeadTrousers]

A little heads up:
Now on A11 / LOS 18.1 I also have the camera defaulting back to 12MP.