Some high res photos (200MP) displaying as very low res (2MP)

[yushiyangk]

Describe the bug

Here are two photos, both of size 12288 × 16320. In Aves Libre, the first one is displayed at its nominal size, whereas the second one is displayed in very low resolution, with reported size of 1080 × 1440.

Edit: removed the externally hosted images, since it's been determined that they themselves were not the cause of the problem

(Apologies for the external link, the images are too large to be uploaded here.)

All of the other image viewers I tried have been able to display the second image correctly.

To Reproduce

Steps to reproduce the behavior:

1. Add the photos to a folder indexed by Aves Libre
2. Open the photos in Aves Libre's Viewer; the resolution in the top right of the Viewer says 1080 × 1440
3. Pinch to zoom into the image: it is of very low resolution, seemingly matching the reported 1080 × 1440
4. Swipe up to show the image Info: the resolution is reported as 1080 × 1440 · 2 MP, while its size is reported as 618.53 KB, much smaller than the actual size of the file

Expected behavior

The image should be much higher resolution, and have a reported resolution of 12288 × 16320, and a size of about 36 MB.

Screenshots

First image, expected behaviour

Second image, incorrect behaviour

System information and logs

vivo X300 (V2509A), 6.12.23-android16-5-gb9f62917cfba-abogki444319749-4k
aves-logs-20251107_035826.txt

Additional context

The 200MP photos were created using the stock camera app for vivo X300. I believe that these high resolution photos are made by stacking multiple images, although I could not find concrete documentation to that effect.

I could semi-reliably generate the incorrectly-behaving images by swinging the phone around rapidly while the image was being captured/processed, which seems to suggest that this might be related to situations where the stock camera fails to stack the entire set of images that it was expecting to.

Nonetheless, all the other image viewers I tried were still able to render such images at its full expected size, and with reasonably high detail.

I'm not really familiar with the jpeg file format, so that's just my guess which could be completely wrong.

Thank you!

[deckerst]

Thanks for the samples. On my devices, both files render correctly.

What I notice from your screenshots is that the size of the second file (618kB) is matching the dimensions (2MP), as if the file was incomplete or temporary. In other words it's not that it's opening the full size and misinterpreting it.

If the file on storage is indeed the full one, could you try in Aves to select the item in the Collection page (with a long press), then select Rescan in the top right menu? Please let me know whether it gets the proper file information (size/dimensions) this time.

[yushiyangk]

Hi, thank you for the suggestion. Rescan did not fix the problem. However, that made me try and move it to a different file path, whereupon it did start rendering correctly.

[deckerst]

Then I think it's a problem that Aves has with cameras that register temporary media before registering the full one. It can happen more often with large images (or the ones with some complex post-processing). Aves should catch the media info update as the image gets finalized.

[yushiyangk]

After moving the image back to the original path, it is now rendering correctly.

[deckerst]

Related:

• Preview from GCam fails for transient images #1688

[yushiyangk]

Then I think it's a problem that Aves has with cameras that register temporary media before registering the full one. It can happen more often with large images (or the ones with some complex post-processing). Aves should catch the media info update as the image gets finalized.

Yeah that definitely makes sense.

Do you mean that the current software should already be updating the file details after the image gets finalised, but is not doing that on this phone for some reason? Is the rescan not working part of the same problem as well?

[deckerst]

Normally, apps that create or modify a media item register it with the Android Media Store (a media database at the OS level), and Aves gets notified whenever there are changes in the Media Store.

So Aves should be updating when the image gets finalized if the item in the Media Store is updated as expected (which is likely), and Aves receives and processes the update events correctly (which seems to fail).

Is the rescan not working part of the same problem as well?

Rescan is actually designed to parse metadata (tags, location, motion photos and panorama details, etc), not for basic info like the dimensions and size. I suggested a rescan as a shot in the dark.