Tag captured photos and videos with device location

[temcguir]

Summary

Wires the location stack into capture. Photos and videos are tagged with the device location when the user has enabled location saving and granted location permission.

This is Part 3 of the location series, stacked on #587.

How it works

While the preview is visible, PreviewViewModel runs the location provider from #587, which keeps an in-memory cached location (see the diagram in #587 for how location is acquired). On shutter press, the capture is tagged with the cached location without waiting on location hardware.

Key Changes

• :core:camera:
  • Adds an optional location: Location? parameter to CameraSystem.takePicture and CameraSystem.startVideoRecording (default null).
  • Image capture sets the location on ImageCapture.Metadata. Out-of-range coordinates are dropped instead of failing the capture.
  • Video recording sets the location on the CameraX output options (FileOutputOptions, FileDescriptorOutputOptions, MediaStoreOutputOptions).
• :ui:controller:impl:
  • CaptureControllerImpl accepts an optional LocationProvider and reads getCurrentLocation() at capture time for both images and videos.
• :feature:preview:
  • PreviewViewModel injects Optional<LocationProvider>.
  • Runs LocationProvider.runLocationUpdates() while the preview is visible (startLocationUpdates() / stopLocationUpdates() from PreviewScreen's LifecycleStartEffect).
  • Gates both location updates and capture-time location on the locationEnabled setting.
  • Pauses location updates while video recording is starting or active, and resumes them when recording stops if the preview is still visible.
• :core:location:location-manager-di (new):
  • Binds LocationManagerLocationProvider as the concrete LocationProvider. The optional contract stays in :core:location:location-di, following the low-light-playservices-di pattern, so host applications opt in explicitly and can substitute their own implementation.
• :app:
  • Depends on :core:location:location-manager-di.
  • Declares ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION, and the location hardware features as required="false".
  • Adds location to the startup permission list, which enables the onboarding location page and the Settings "Save Location" row added in Add location permission UX to onboarding and settings #586.
• Testing:
  • PreviewViewModelTest: 9 tests covering location update start/stop, setting toggles, absent provider, video recording pause/resume, and capture with the setting disabled.
  • CaptureControllerImplTest: 4 tests covering location passed to image and video capture, and omitted when disabled.
  • PermissionsTest (instrumented): location permission page granted and denied paths.
  • FakeCameraSystem records the last location passed to capture calls.

[gemini-code-assist]

Code Review

This pull request implements geographic location tagging (geotagging) for both image and video captures. It introduces location permissions, a new Hilt module for location provider dependency injection, location hardware warmup logic in the preview lifecycle, and updates to the camera session to attach location metadata to output files. The review feedback focuses on improving robustness by sanitizing coordinates to prevent out-of-bounds crashes, adopting idiomatic Kotlin patterns (such as using apply instead of complex .let blocks and smart-casting Optional values), and restricting dependency injection provider visibility to internal.