-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Camera error message #501
Comments
Hi @0l1e, When exactly do you encounter this issue? Thanks for using our camera app and reporting this issue! |
Hi.
Well it happens after taking several photos, this error message pops up. I close the app and restart it and it works again.
Didn't have this issue with the original camera app.
Regards Olle
Skickat från Outlook för Android<https://aka.ms/AAb9ysg>
…________________________________
From: Mohit Shetty ***@***.***>
Sent: Sunday, February 2, 2025 10:54:35 PM
To: GrapheneOS/Camera ***@***.***>
Cc: 0l1e ***@***.***>; Mention ***@***.***>
Subject: Re: [GrapheneOS/Camera] Camera error message (Issue #501)
Hi @0l1e<https://github.com/0l1e>,
When exactly do you encounter this issue?
Thanks for using our camera app and reporting this issue!
—
Reply to this email directly, view it on GitHub<#501 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOLLSBS577P2QR7QIJZLK5T2N2HZXAVCNFSM6AAAAABU46IY26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRZGU3TGMZYGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @0l1e, Sorry to hear that you are facing this issue. The source of this issue still seems to be a bit uncertain. Do you repeatedly have to tap the capture button for this issue to occur or does the error show up even if the capture requests are not so continuous/frequently repeated in nature? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello. I often get this error when using the camera. Hope its possible to fix. It works to close the app and restart it.

The text was updated successfully, but these errors were encountered: