Too much delay between flashes taken during image capture (on Pixel 3a) [211474332]

Fixed

Bug

Status Update

No update yet.

Description

sh...@gmail.com

created issue #1

Dec 21, 2021 01:42PM

We had previously filed an issue regarding the flash (https://issuetracker.google.com/issues/205373142) which has now been fixed with the latest release. However, our Pixel 3A users are facing another issue with the flash after the latest changes.

While clicking a photo there are two flashes (one to light the scene and another for the actual photo). Generally (for other devices), this delay between these two flashes is minimal (a few milliseconds).. however for Pixel 3a (specifically in the dark) this delay has been tested to be more than 1 second which indirectly causes the focus to get deviated while taking a photo. (The focus getting changed due to this was the main issue being faced by the user.

Thanks a lot for all the help and support!

Regards, Mohit

Comments

sh...@gmail.com <sh...@gmail.com> #2Dec 21, 2021 01:48PM

Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.

wu...@google.com <wu...@google.com> Dec 22, 2021 08:09AM

Reassigned to sc...@google.com.

ap...@google.com <ap...@google.com> #3Dec 27, 2021 08:37AM

Great! Thanks a lot, I'll look for the live updates soon!

sc...@google.com <sc...@google.com> #4Dec 27, 2021 09:16AM

Marked as fixed.

Hi Mohit,
Thanks for filing the issue. After investigation, yes it is slow when capturing with flash in dark. So we changed it to use torch as the flash instead. The results shows using torch not just can be quicker but also the quality is better than using flash. The Jan release will contain the fix.

Scott

sh...@gmail.com <sh...@gmail.com> #5Jan 11, 2022 01:51AM

Hi Scott,

Thanks a lot for fixing this issue! Hope this issue gets resolved in the next release (by the final confirmation from the Pixel 3a user).

Regards, Mohit

fr...@gmail.com <fr...@gmail.com> #6Jun 7, 2023 09:18AM

Is it possible to extend the list of devices that implement this workaround to include the Samsung A3 2017 (a3y17lte) please? There is an open issue reporting the same original issue as with the Pixel 3a (

https://issuetracker.google.com/issues/235172945) but it doesn't seem to have received any traction as of yet.

fr...@gmail.com <fr...@gmail.com> #7Jun 7, 2023 10:08AM

Comment has been deleted.

Message last modified on Jun 7, 2023 10:09AM

sc...@google.com <sc...@google.com> #8Jun 8, 2023 06:10AM

Hi Tahsin

can you help on this one. Enabling the quirk on Samsung A3 seems reasonable.

ta...@google.com <ta...@google.com> #9Jun 8, 2023 06:25AM

Hi! Thanks for mentioning Samsung A3 2017 may be facing the same problem.

It seems b/235172945 wasn't noticed by us due to not being in the CameraX tracker component, but b/286190938 has been filed regarding the issue. Let's continue tracking this problem in b/286190938

Message last modified on Jun 8, 2023 07:55AM

bm...@gmail.com <bm...@gmail.com> #10Jun 8, 2023 07:53AM

Comment has been deleted.

Message last modified on Jun 8, 2023 07:55AM

fr...@gmail.com <fr...@gmail.com> #11Jun 8, 2023 07:55AM

Sure thing, I was just trying to connect some dots for the original issue poster of

b/235172945

as it had been a year without a response, although I'd only noticed the issue myself more recently.

Can I please ask that you remove the full email from the text of your previous comment though?

Message last modified on Jun 8, 2023 07:57AM