Aperture (camera) app cuts off margin of pictures

[deesnook]

Device

FP6

LineageOS Version

23.2

Build Date

20260322

Kernel Version

6.1.163

Baseband Version

Milos.LA.2.0-00125-STD.PROD-2.

System Modifications

microG

Expected Behavior

When taking a picture with Aperture, the full content of what you see on the screen should be included in the picture.

Current Behavior

When taking a picture in portrait position, the actual picture is narrower than the screen content because parts of the left and right margin are cut off. This is quite annoying as you cannot really be sure that everything you want to have in the picture will actually be in it. The problem occurs when using a 16:9 screen ratio. As far as I can tell, it doesn't occur with a 4:3 ratio. Furthermore, I noticed that it happens when you take a picture in landscape format, too. In that case, it is the top and bottom that are cut off. So it seems to be a problem with the long sides of the picture.

The same behavior was present in LineageOS 20 and 21, but I never submitted a bug report. For LineageOS 21, I submitted a bug report on Gitlab for OnePlus 8T: https://gitlab.com/LineageOS/issues/android/-/work_items/6957

There, another user confirmed the bug on Google Pixel 4XL. My current description of the system build in this bug report refers to an unofficial build for Fairphone 6 and not to OnePlus8T (kebab), which I don't have anymore. However, given the circumstances it is probably safe to assume the issue is not related to the system build, but rather to Aperture.

Possible Solution

No response

Steps to Reproduce

1. Open Aperture
2. Take picture in portrait or landscape position with a screen ratio of 16:9
3. Compare what you saw on the screen with the actual picture, which will be narrower. See pictures at https://gitlab.com/LineageOS/issues/android/-/work_items/6957

Confirmation

• I have read the directions at https://wiki.lineageos.org/how-to/bugreport

[github-actions]

Hi! It appears you didn't read or follow the provided issue template.
Please edit your issue to include the requested fields and follow the provided template, then reopen it by commenting /reopen.
For more information please see https://wiki.lineageos.org/how-to/bugreport.

Problems:

• Device "FP6 / kebab / coral" is not a valid device codename. Supported values are: a21s, a52q, a52sxq, a71, a72q, a73xq, akita, alioth, apollon, aston, astonc, avatrn, audi, avalon, bale, bangkk, barbet, bathena, benz, berlin, berlna, beyond0lte, beyond1lte, beyond2lte, beyondx, bluejay, borneo, bramble, caihong, caiman, capri, caprip, cebu, cheetah, cmi, comet, coral, corvette, cupid, d1, d1x, d2s, d2x, davinci, denver, devon, discovery, diting, dm1q, dodge, dre, dubai, earth, erhai, f62, felix, flame, fogo, fogos, FP4, FP5, fuxi, garnet, gauguin, ginkgo, giulia, giuliac, gta4l, gta4lwifi, gta4xl, gta4xlswifi, gta4xlwifi, gts7l, gts7lwifi, guacamole, guacamoleb, guam, guamp, gunnar, hawao, heart, hotdog, hotdogb, husky, ingot, instantnoodle, instantnoodlep, kane, kebab, kiev, kirin, komodo, larry, lemonade, lemonadep, lemonades, lexus, lisa, lmi, luigi, lynx, m52xq, marble, martini, mayfly, mermaid, Mi439, Mi8917, Mi8937, miami, milanf, mondrian, munch, nairo, nicole, nio, nuwa, oriole, oscar, oscaro, panther, pdx203, pdx206, pdx214, pdx215, pdx223, pdx224, pdx225, pdx234, pdx235, pdx237, pdx245, pdx257, peridot, pioneer, Pong, pro1x, pstar, pyrite, Q25, r8q, r8s, racer, raven, redfin, renoir, rhode, rhodep, rosemary, rtwo, sake, salami, shiba, socrates, Spacewar, sunfish, sweet, tangorpro, tegu, thor, thyme, timelm, tokay, TP1803, troika, tucana, tundra, umi, unicorn, venus, vermeer, violet, voyager, waffle, x1s, xpeng, y2s, z3s, zeus, zippo, zizhan, akari, akatsuki, akershus, aura, aurora, axolotl, B2N, baracus, baracus_tab, beckham, beryllium, blueline, bonito, bronco, casuarina, caymanslm, channel, cheeseburger, cheryl, chiron, crosshatch, deadpool, dipper, dopinder, DRG, dumpling, enchilada, eqs, equuleus, evert, fajita, foster, foster_tab, FP3, g710n, g710ulm, gemini, grus, gtowifi, gts4lv, gts4lvwifi, haydn, joan, judyln, judyp, judypn, l01k, lake, m5, m5_tab, marlin, mata, messi, miatoll, nash, natrium, NB1, nx, nx_tab, nx563j, nx606j, nx616j, nx619j, nx659j, ocean, odroidc4, odroidc4_tab, payton, perseus, PL2, polaris, porg, porg_tab, pro1, pyxis, quill, quill_tab, radxa0, radxa02, radxa0_tab, radxa02_tab, river, sabrina, sagit, sailfish, sargo, scorpio, shark, sif, style3lm, surya, taimen, trident, ursa, vayu, vela, wade, walleye, xz2c, Z01R

(this action was performed by a bot)

[deesnook]

/reopen

[github-actions]

Hi! It appears you didn't read or follow the provided issue template.
Please edit your issue to include the requested fields and follow the provided template, then reopen it by commenting /reopen.
For more information please see https://wiki.lineageos.org/how-to/bugreport.

Problems:

• Device "kebab coral" is not a valid device codename. Supported values are: a21s, a52q, a52sxq, a71, a72q, a73xq, akita, alioth, apollon, aston, astonc, avatrn, audi, avalon, bale, bangkk, barbet, bathena, benz, berlin, berlna, beyond0lte, beyond1lte, beyond2lte, beyondx, bluejay, borneo, bramble, caihong, caiman, capri, caprip, cebu, cheetah, cmi, comet, coral, corvette, cupid, d1, d1x, d2s, d2x, davinci, denver, devon, discovery, diting, dm1q, dodge, dre, dubai, earth, erhai, f62, felix, flame, fogo, fogos, FP4, FP5, fuxi, garnet, gauguin, ginkgo, giulia, giuliac, gta4l, gta4lwifi, gta4xl, gta4xlswifi, gta4xlwifi, gts7l, gts7lwifi, guacamole, guacamoleb, guam, guamp, gunnar, hawao, heart, hotdog, hotdogb, husky, ingot, instantnoodle, instantnoodlep, kane, kebab, kiev, kirin, komodo, larry, lemonade, lemonadep, lemonades, lexus, lisa, lmi, luigi, lynx, m52xq, marble, martini, mayfly, mermaid, Mi439, Mi8917, Mi8937, miami, milanf, mondrian, munch, nairo, nicole, nio, nuwa, oriole, oscar, oscaro, panther, pdx203, pdx206, pdx214, pdx215, pdx223, pdx224, pdx225, pdx234, pdx235, pdx237, pdx245, pdx257, peridot, pioneer, Pong, pro1x, pstar, pyrite, Q25, r8q, r8s, racer, raven, redfin, renoir, rhode, rhodep, rosemary, rtwo, sake, salami, shiba, socrates, Spacewar, sunfish, sweet, tangorpro, tegu, thor, thyme, timelm, tokay, TP1803, troika, tucana, tundra, umi, unicorn, venus, vermeer, violet, voyager, waffle, x1s, xpeng, y2s, z3s, zeus, zippo, zizhan, akari, akatsuki, akershus, aura, aurora, axolotl, B2N, baracus, baracus_tab, beckham, beryllium, blueline, bonito, bronco, casuarina, caymanslm, channel, cheeseburger, cheryl, chiron, crosshatch, deadpool, dipper, dopinder, DRG, dumpling, enchilada, eqs, equuleus, evert, fajita, foster, foster_tab, FP3, g710n, g710ulm, gemini, grus, gtowifi, gts4lv, gts4lvwifi, haydn, joan, judyln, judyp, judypn, l01k, lake, m5, m5_tab, marlin, mata, messi, miatoll, nash, natrium, NB1, nx, nx_tab, nx563j, nx606j, nx616j, nx619j, nx659j, ocean, odroidc4, odroidc4_tab, payton, perseus, PL2, polaris, porg, porg_tab, pro1, pyxis, quill, quill_tab, radxa0, radxa02, radxa0_tab, radxa02_tab, river, sabrina, sagit, sailfish, sargo, scorpio, shark, sif, style3lm, surya, taimen, trident, ursa, vayu, vela, wade, walleye, xz2c, Z01R

(this action was performed by a bot)

[deesnook]

/reopen

[luk1337]

i'll let it slide this time but don't lie in your bug report next time...

[luk1337]

i'll let it slide this time but don't lie in your bug report next time...

for reference you were trying to report FP6 bug as kebab one:

[deesnook]

My problem is that I don't have a kebab device anymore, so at first I wanted to report for the devices we know the bug occured on (which are kebab, coral and FP6). I didn't know the bot wouldn't accept the denomination of the three devices.

[luk1337]

My problem is that I don't have a kebab device anymore, so at first I wanted to report for the devices we know the bug occured on (which are kebab, coral and FP6). I didn't know the bot wouldn't accept the denomination of the three devices.

we accept one device per bug report and it's up to maintainers to transform it into platform one or one affecting multiple related devices.

[deesnook]

My problem is that I don't have a kebab device anymore, so at first I wanted to report for the devices we know the bug occured on (which are kebab, coral and FP6). I didn't know the bot wouldn't accept the denomination of the three devices.

we accept one device per bug report and it's up to maintainers to transform it into platform one or one affecting multiple related devices.

OK, didn't know that. Then someone else needs to provide info for kebab and coral, I can only help with FP6 at the moment

[luk1337]

My problem is that I don't have a kebab device anymore, so at first I wanted to report for the devices we know the bug occured on (which are kebab, coral and FP6). I didn't know the bot wouldn't accept the denomination of the three devices.

we accept one device per bug report and it's up to maintainers to transform it into platform one or one affecting multiple related devices.

OK, didn't know that. Then someone else needs to provide info for kebab and coral, I can only help with FP6 at the moment

this one has been relabeled as platform+apps, since i think this is a generic Aperture thing.

[deesnook]

since i think this is a generic Aperture thing

That was my suspicion as well. Thanks!