Skip to content
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

[tone] [kagura] Camera flashlight not in sync with shutter #406

Closed
ix5 opened this issue May 21, 2019 · 5 comments
Closed

[tone] [kagura] Camera flashlight not in sync with shutter #406

ix5 opened this issue May 21, 2019 · 5 comments

Comments

@ix5
Copy link
Contributor

ix5 commented May 21, 2019

Platform: tone
Device: kagura
Kernel version: 4.9
Android version: 9.0 Pie

Description
In the AOSP camera app, with flash turned on, the flash fires fine, but the shutter is delayed too much so that the picture is still dark.

How to reproduce
Build with r37 and current kernel HEAD and v8 binaries, open AOSP camera, turn on flashlight, take a picture.

@MarijnS95
Copy link
Contributor

I assumed this was specific to Tama with the new camera framework; seems other phones are affected as well.

@xarinatan
Copy link

Seems likely, I have issues with the flash (and camera in general) as well but I have a tama apollo (xz2c). Seems like if I turn off autofocus in some applications the flash does manage to sync up, so perhaps the autofocus timing isn't correctly added to the flash delay or something along those lines..

@rinigus
Copy link

rinigus commented Jul 24, 2020

Probably known by others, mainly for pinging. Same goes on AOSP10, v9 binaries. On Tama/Apollo with the flash fired at the wrong time while acquiring image. Flash is used during focusing, switched off and triggered with the delay to ensure that it is not there when it is needed.

@MarijnS95
Copy link
Contributor

@rinigus Same on Akatsuki. The snapshot is either too late or goes completely crazy, flickering for multiple seconds (likely trying to compensate for the sudden increase in brightness) before finally taking the picture.

and triggered with the delay to ensure that it is not there when it is needed.

Unless I'm reading this wrong, "ensure" is an odd choice of words here 🤔 . Are you seeing something in the logs that is intentionally and explicitly (but wrongly) compensating for something?

@rinigus
Copy link

rinigus commented Jul 25, 2020

Unless I'm reading this wrong, "ensure" is an odd choice of words here thinking . Are you seeing something in the logs that is intentionally and explicitly (but wrongly) compensating for something?

That was supposed to be enclosed with /ironic/, sorry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants