Add camera torch (flashlight) support

[paradoxsyn]

this is just a quick fix to add the flashlight. im using this personally figured I'd stick it here. I won't have time to check other submissions but this was quick so.

Best

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Adds cross-platform torch (flashlight) controls to the Flutter YOLO camera view via new MethodChannel APIs. 🔦

📊 Key Changes

• Exposes new platform channel methods: toggleTorch, setTorchMode(enabled), isTorchAvailable, and isTorchEnabled (Android + iOS).
• Implements torch control in Android YOLOView using CameraX (enableTorch, torchState, hasFlashUnit).
• Implements torch control in iOS YOLOView via AVCaptureDevice torch configuration (lock/unlock + max torch level).
• Adds matching Dart controller APIs in lib/widgets/yolo_controller.dart with basic error handling and null-safe query methods.

🎯 Purpose & Impact

• Enables end-users to turn the flashlight on/off during live camera inference, improving low-light usability. 🌙
• Provides feature parity across Android and iOS with a consistent Flutter API surface.
• Helps apps gracefully adapt UI by checking torch availability/state before displaying a torch button.

[github-actions]

All Contributors have signed the CLA. ✅
_{Posted by the CLA Assistant Lite bot.}

[UltralyticsAssistant]

👋 Hello @paradoxsyn, thank you for submitting a ultralytics/yolo-flutter-app 🚀 PR! This is an automated message—an Ultralytics engineer will review and assist soon. 🔦

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/yolo-flutter-app main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Looks clean overall. The new MethodChannel surface is wired consistently across Dart, Android (CameraX), and iOS (AVCaptureDevice), with reasonable null-safety and graceful fallbacks (e.g., returning false/null when unavailable). No clear bugs or failure cases introduced in the shown diff.

[codecov]

Codecov Report

❌ Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
lib/widgets/yolo_controller.dart	75.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[asabri97]

@paradoxsyn please sign the CLA

[asabri97]

Can we double check this method?

This approach isn't locking and the single path in setAutoFocusMode call cancelFocusAndMeterinng(), which resets metering back to default auto behavior. The method claims to lock but likely return to auto so the feature behaves opposite of its contract.

[damaradiprabowo]

Any update on this @paradoxsyn ?

[paradoxsyn]

Sorry all, I can take a look at this over the weekend. I haven't tested the focus mode yet, that was a "nice to have" and currently the reason I developed these is on hold - but I'll get it in a good spot for the PR here.

[paradoxsyn]

8DUJ1

@paradoxsyn please sign the CLA

Also I don't know what CLA? Am I missing something?

[pderrenger]

Yes, the CLA is the Contributor License Agreement required before we can merge the PR; your 8DUJ1 comment won’t trigger it, so please add the standalone signature comment referenced above and the bot should take it from there, and you can review the terms in the CLA docs.

[glenn-jocher]

Thanks for the contribution here. Camera-related work tends to have a wide surface area, so it takes more review than the smaller fixes, but the effort is appreciated and it does help show where users want the project to go.

[glenn-jocher]

Rescoped this onto current main and force-pushed a much smaller version of the PR.

What remains:

• one Dart controller method: setTorchMode(bool enabled)
• Android/iOS native handling for that method
• a small controller test and matching API doc update

What was intentionally removed:

• tracking
• trackId model changes
• focus/exposure/white-balance controls
• all other camera-control API expansion

Local verification on this cleaned branch:

• flutter analyze
• flutter test
• flutter build ios --simulator --no-codesign in example/

flutter build apk --debug in example/ still fails on the existing unrelated top5Indices classification regression already present on current main; I kept that out of scope so this PR stays minimal.

The remaining merge blocker is CLA. @paradoxsyn please add this exact standalone PR comment so the bot can pass:

I have read the CLA Document and I sign the CLA

[glenn-jocher]

Reviewed after rescoping onto current main. This is now the minimal useful version of the feature: a single controller API wired through the native Android and iOS camera views, with the unrelated focus/exposure/tracking work removed.

[glenn-jocher]

Reviewed after rescoping onto current main. This is now the minimal useful version of the feature: a single setTorchMode(bool enabled) controller API wired through the native Android and iOS camera views, with the unrelated focus/exposure/tracking work removed.

[paradoxsyn]

Thanks for the help here, im sorry I wasn't able to update this still, some things have happened. I agree to the CLA Best, Derek

…

On Wed, Apr 15, 2026, 8:59 AM Glenn Jocher ***@***.***> wrote: ***@***.**** approved this pull request. Reviewed after rescoping onto current main. This is now the minimal useful version of the feature: a single setTorchMode(bool enabled) controller API wired through the native Android and iOS camera views, with the unrelated focus/exposure/tracking work removed. — Reply to this email directly, view it on GitHub <#435 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC3EXNRZ4VO4F75HG5PCTPL4V6WWRAVCNFSM6AAAAACR34VXCOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHM2DCMJVGAZDCMBVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[pderrenger]

Thanks Derek, and sorry to hear that; this email-style reply usually won’t satisfy the CLA check, so please add the exact standalone PR comment requested above directly in GitHub so the bot can detect it and we can move this forward.

[paradoxsyn]

I have read the CLA Document and I sign the CLA