signalapp / signalapp/Signal-Android
Size discrepancy between camera preview and actual photo
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.4k
- Forks
- 6.9k
- PR merge metrics
- No merged PRs in 30d
Description
Guidelines
- I have searched searched open and closed issues for duplicates
- I am submitting a bug report for existing functionality that does not work as intended
- This isn't a feature request or a discussion topic
Bug description
When taking a photo in the Signal Android app, the preview will show a certain way, and I'll frame the photo based on that.
After taking the photo, the result I'm presented with shows a lot more content than the preview would suggest, making it very difficult to properly frame stuff without having to crop in post and lose resolution.
Screenshots
Screenshot while taking/framing a shot in the Signal app:
(Note also how the camera UI/buttons are abnormally high up on the screen compared to other similar apps.)
After taking the photo:
Compare this to e.g. Telegram:
Before:
After:
There's some difference, but not as massive as in Signal.
Also compare with the stock camera app:
Before:
After:
Note how the stock app uses the correct aspect ratio for the sensor (4:3) and it correctly matches in both preview and actual taken photo.
Device
Google Pixel 8
Android version
16
Signal version
7.67.1
Link to debug log
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the mismatch on the stated Google Pixel 8, Android 16, using Signal 7.67.1, and review the linked debug log for camera-related context. Trace the camera preview and photo-capture entry points, comparing their aspect ratios. Done means the framing shown in the preview matches the captured photo closely enough for reliable composition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100