Skip to content

CHANGELOG.md

Latest commit

 

History

History
30 lines (22 loc) · 1.98 KB

CHANGELOG.md

File metadata and controls

30 lines (22 loc) · 1.98 KB

0.3.0

  • Removed SCHEDULE_EXACT_ALARM and USE_EXACT_ALARM permissions from the Android manifest. Google Play restricts these to calendar/alarm-clock apps and was rejecting uploads of consuming apps.
  • Replaced the AlarmManager-based heartbeat with an in-process Handler.postDelayed loop inside LocationService. Heartbeats now fire while the foreground service is alive (which is the normal case — the ongoing notification + battery-optimization exemption keep it running). Heartbeats may pause during deep Doze, which is a behaviour change from 0.2.x.
  • Removed WatchdogAlarmReceiver (the 15-minute OEM-kill recovery alarm). OEM-kill resilience now relies solely on the foreground service notification + REQUEST_IGNORE_BATTERY_OPTIMIZATIONS.
  • Removed HeartbeatAlarmReceiver; its headless-callback dispatch logic moved into LocationService.emitHeartbeat().
  • Removed LocationService.ACTION_HEARTBEAT_ALARM (no longer dispatched).

Migration notes for consumers: No API changes. If you were relying on heartbeats firing during deep Doze, you'll see them pause until the next Doze maintenance window or until the user interacts with the device. For most use cases this is acceptable — the foreground service's location updates continue independently of the heartbeat tick.

0.2.1

  • Bump package version to trigger a fresh tag-based pub.dev publish
  • Keep 0.2.0 fixes and release automation improvements intact

0.2.0

  • Preserve motion state when updating config with setConfig
  • Enforce a 50m distance filter to reduce noisy updates
  • Add a passive listener to improve motion/state handling
  • Improve release automation and pub.dev trusted publishing workflow

0.1.0

  • Initial release
  • Background location tracking via AOSP LocationManager (Android) and CoreLocation (iOS)
  • Motion detection for adaptive GPS polling
  • Geofencing support (ProximityAlert on Android, CLCircularRegion on iOS)
  • Three tracking modes: Active, Balanced, Passive
  • Zero Google Play Services dependencies