-
Notifications
You must be signed in to change notification settings - Fork 3.4k
[camera_android_camerax] Fix the rotation of captured videos and streamed images #9637
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request refactors the orientation handling for video capture and image streaming by removing the stateful shouldSetDefaultRotation
flag. The new logic is simpler and more robust, setting the target rotation on use cases whenever the orientation is not locked. This should fix the reported rotation issues. I've identified a couple of areas where performance could be improved by caching the last set rotation value to avoid redundant platform channel calls. These are not critical but would make the implementation more efficient.
@@ -390,17 +379,18 @@ class AndroidCameraCameraX extends CameraPlatform { | |||
); | |||
|
|||
// Configure ImageCapture instance. | |||
final int defaultDisplayRotation = | |||
await deviceOrientationManager.getDefaultDisplayRotation(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider extracting deviceOrientationManager.getDefaultDisplayRotation()
to a local variable before calling proxy.newImageCapture
. This avoids calling the platform multiple times, which could be inefficient.
final int defaultDisplayRotation = await deviceOrientationManager.getDefaultDisplayRotation();
if (!captureOrientationLocked) { | ||
await videoCapture!.setTargetRotation( | ||
await deviceOrientationManager.getDefaultDisplayRotation(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of calling deviceOrientationManager.getDefaultDisplayRotation()
directly within setTargetRotation
, consider storing the value in a variable and reusing it. This avoids redundant calls to the platform, improving efficiency.
final rotation = await deviceOrientationManager.getDefaultDisplayRotation();
await videoCapture!.setTargetRotation(
rotation,
);
if (!captureOrientationLocked) { | ||
await imageAnalysis!.setTargetRotation( | ||
await deviceOrientationManager.getDefaultDisplayRotation(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of calling deviceOrientationManager.getDefaultDisplayRotation()
directly within setTargetRotation
, consider storing the value in a variable and reusing it. This avoids redundant calls to the platform, improving efficiency.
final rotation = await deviceOrientationManager.getDefaultDisplayRotation();
await imageAnalysis!.setTargetRotation(
rotation,
);
wip :) todo:
Fixes flutter/flutter#163859.
Pre-Review Checklist
[shared_preferences]
pubspec.yaml
with an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.md
to add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of
Gemini Code Assist for GitHub.
Comments from the
gemini-code-assist
bot should not be taken as authoritativefeedback from the Flutter team. If you find its comments useful you can
update your code accordingly, but if you are unsure or disagree with the
feedback, please feel free to wait for a Flutter team member's review for
guidance on which automated comments should be addressed.
Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3