Text overlaps the front camera in the Android app
-
- device: google pixel10 pro fold
- OS: Android 16
- Simplenote App: 2.3.7(184)
When I run the Simplenote app on the Google Pixel 10 Pro Fold’s secondary display and hold the device sideways with the front camera on the left, the note’s output overlaps with the front camera, making it difficult to read or write in that area.
Please let me know if there are any good solutions.
The Google Pixel 10 Pro Fold is a special device with a foldable function, but the secondary display looks the same as a regular smartphone with an in-display front camera like other Pixel 10s, so I would like to see a good solution.
(This is a machine translation. Sorry if there are any suspicious points.)
-
Thank you for reaching out. Your message is very clear!
Would you be able to share a screenshot showing the overlap? That would help our team better understand how the text is being cut off on your device.
In the meantime, we’ve passed this along as feedback to our development team.
Thanks again for letting us know!
-
@tamiratb Thank you for your response.
As instructed, I have prepared images showing the problem. These are two images simulating the work in progress, with the approximate location of the front camera added using paint software.
Please review them.
- Images A show scenes of editing text using the on-screen keyboard. Google’s keyboard app GBoard avoids the front camera, while Simplenote does not.
- Images B simulate scenes of viewing text and editing text using a hardware keyboard. It’s clear that the front camera is being interfered with, hindering the work.
- Images C and D have red circles drawn on them to indicate the approximate location of the front camera, which is not visible in the screenshots.
A: Screenshot_20260424-092019.png
B: Screenshot_20260424-092031.png
C: Screenshot_20260424-092019_.png
D: Screenshot_20260424-092031_.png -
Thank you for the detailed screenshots @joyousfcb1cd7548!
I can confirm this is a known issue with how the app handles display cutout areas on newer devices. I’ve added your report and screenshots to the existing bug ticket with our development team so they have this additional context.
Unfortunately, there’s no timeline available on a fix for this.
We appreciate you taking the time to document this so thoroughly!