accurate_step_counter

Releases

1. ▸▾3.1.028 Jul 20262 sources agree

   iOS support via HealthKit (health package) with filtered step reads and HC smoothing semantics aligned with meltdown.

   Added

   • iOS support via HealthKit (health package) with filtered step reads and HC smoothing semantics aligned with meltdown.
   • New internal IosHealthStepDetector service that emits realtime step events from Health app totals.
   • Cross-platform example flow now handles iOS initialization cleanly.

   Changed

   • watchTodaySteps() remains immediate and floor-protected while now supporting iOS live step source.
   • Package positioning updated from Android-only to Android + iOS HealthKit.

   Fixed

   • Native event merge now always applies floor protection before emitting (prevents downward jitter on transient resets).
   • Rotation drain persists previous day totals into SQLite with date anchoring.

   Open source →
2. ▸▾3.0.026 Jul 20262 sources agree

   Primary detection is now TYPE_STEP_COUNTER FGS on all Android API 24+ (including Samsung). Previous API≤29 / non-Samsung gate removed.

   Breaking

   • Primary detection is now TYPE_STEP_COUNTER FGS on all Android API 24+ (including Samsung). Previous API≤29 / non-Samsung gate removed.
   • SmartMergeHelper.mergeStepCounts semantics changed — no longer naive max(). Uses StepLogic (HC duplication band, sensor overcount at 1.10×, HC can correct downward, server floor). Prefer SmartMergeHelper.merge() for full MergeDecision flags.
   • Legacy auto-start of StepCounterForegroundService on app termination is off by default to prevent dual-FGS fights.
   • StepDetectorConfig.useForegroundServiceOnOldDevices defaults to false (legacy sensors_plus fallback only).

   Added

   • Production-hardened StepCounterService: prefs persist, reboot detect, burst/minute/hour caps with baseline fold-in, vehicle/bicycle Activity Recognition filter, TYPE_STEP_DETECTOR cross-check, exact midnight alarm, BootReceiver, TimeChangeReceiver, rotation stamps
   • ActivityClassifier + soft-fail without Play Services (play-services-location)
   • Dart policies: StepLogic, MergePolicy, smoothHcReading, RotationGuard, StepRateLimiter
   • Platform APIs: setNotificationDisplay, forceUpdateTodaySteps, consumeLastRotation, resetNativeStepState
   • startTracking() — one-call setup (DB + FGS + aggregated logging)
   • Short aliases: isBatteryOptimized(), requestBatteryOptimization()
   • Safe calibration from SQLite today (sensor=0, seed ≤40k) on start
   • Native↔SQLite reconcile on aggregated start (fixes undercount after process death)
   • Rotation drain on start / resume / step stream
   • Ported production policy unit tests under test/policy/
   • Soft uses-feature for stepcounter/stepdetector (required=false)
   • Consumer ProGuard keep rules for services/receivers

   Fixed (production DX / hardening)

   • Skip legacy terminated-prefs sync when the native FGS is available (no dual recovery)
   • Example + verification check TYPE_STEP_COUNTER FGS, not fallback detector
   • Removed 500ms artificial delay from initSteps (now aliases startTracking)
   • Collapsed duplicate getTodaySteps / getYesterdaySteps definitions
   • Cold-start day-gap restore stamps KEY_LAST_ROTATION_* and persists rotated prefs
   • Activity Recognition PendingIntent uses explicit component + unique request code; receiver in manifest
   • Removed Play-risk permissions USE_EXACT_ALARM, BODY_SENSORS, BODY_SENSORS_BACKGROUND, HIGH_SAMPLING_RATE_SENSORS
   • Plugin no longer permanently registers a second TYPE_STEP_COUNTER listener (battery)
   • Kotlin unit test matches real MethodChannel API
   • NotificationChannel creation guarded for API 24–25 (StepCounterService)
   • dispose() / stopLogging() flush write buffer and cancel flush timer

   Migration

   1. Bump to ^3.0.0 and request ACTIVITY_RECOGNITION + notifications before startTracking().
   2. Prefer await steps.startTracking() over the old three-call sequence.
   3. If you relied on naive max merge, switch to SmartMergeHelper.merge(...) and handle MergeDecision.
   4. Keep notification synced with setNativeNotificationDisplay(merged) — do not force-write merged HC into sensor baseline.
   5. Supply HC/server yourself (BYO); package does not embed Health Connect SDK.