惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
Cyberwarzone
Cyberwarzone
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG
P
Proofpoint News Feed
小众软件
小众软件
Recent Announcements
Recent Announcements
博客园 - 三生石上(FineUI控件)
Security Archives - TechRepublic
Security Archives - TechRepublic
W
WeLiveSecurity
Cloudbric
Cloudbric
博客园 - 司徒正美
美团技术团队
N
News and Events Feed by Topic
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
PCI Perspectives
PCI Perspectives
宝玉的分享
宝玉的分享
H
Help Net Security
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Google DeepMind News
Google DeepMind News
Help Net Security
Help Net Security
Last Week in AI
Last Week in AI
S
Schneier on Security
N
News | PayPal Newsroom
B
Blog RSS Feed
L
LINUX DO - 最新话题
T
Troy Hunt's Blog
S
Secure Thoughts
雷峰网
雷峰网
aimingoo的专栏
aimingoo的专栏
L
Lohrmann on Cybersecurity
G
Google Developers Blog
Microsoft Azure Blog
Microsoft Azure Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
T
Tenable Blog
S
Securelist
L
LangChain Blog
Recent Commits to openclaw:main
Recent Commits to openclaw:main
I
InfoQ
H
Heimdal Security Blog
Cisco Talos Blog
Cisco Talos Blog
F
Full Disclosure
Y
Y Combinator Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
K
Kaspersky official blog
T
Tailwind CSS Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
阮一峰的网络日志
阮一峰的网络日志
C
Cisco Blogs

freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

Learn Command Line Interface (CLI) Development with Dart: From Zero to a Fully Published Developer Tool How to Build a Live Options Database in Python – A Complete Guide How to Migrate to S3 Native State Locking in Terraform How to Use SCons to Build Software Projects [Full Handbook] How to Run Open Source LLMs Locally and in the Cloud QuRT: The Real-Time OS Inside Your Phone's Processor [Full Handbook] The Real Infrastructure Behind Remote Work (It’s Not Just Wi-Fi) The Lithography Handbook: Machines, Markets, and the Next Wave of Semiconductor Startups ITCM vs DTCM vs DDR: Embedded Memory Types Explained [Full Handbook] AI Paper Review: Improving Language Understanding by Generative Pre-Training (GPT-1) How to Build a Market Research Copilot with MCP and Python [Full Handbook] How to Build a Scoped Note-Taking API with Django Rest Framework and SimpleJWT The Complete SOC 2 Type II Implementation Handbook for Engineers: A Month-by-Month Roadmap with Real Commands Mastering the JavaScript Event Loop Data Science Insights: Why the Mean Lies When Handling Messy Retail Data How to Build High-Ranking SEO Landing Page How to Query Data in DynamoDB Using .Net How to Unblock Your AI PR Review Bottleneck: A Tech Lead’s Guide to Building a Codebase-Aware Reviewer How to Navigate Microservices as a Frontend Engineer How to Compress PDF Files in the Browser Using JavaScript (Step-by-Step) Stanford's youngest instructor talks InfoSec, AI, and catching cheaters - Rachel Fernandez interview [Podcast #217] Product Experimentation with Propensity Scores: Causal Inference for LLM-Based Features in Python How to Build a Multi-Agent AI System with LangGraph, MCP, and A2A [Full Book] How to Land Your First Cloud or DevOps Role: What Hiring Managers Actually Look For How to Deploy a Serverless Spam Classifier Using Scikit-Learn, AWS Lambda, & API Gateway How to Dockerize a Go Application – Full Step-by-Step Walkthrough Learn Hardware, Cloud, DevOps, Networking, Security, Databases, DNS, Git, and Linux Inside TreeHacks 2026, Stanford’s Elite Student Hakc Inside Stanford’s Elite Student Hackathon [Full Documentary] How to Measure Your AI Citation Rate Across ChatGPT, Perplexity, and Claude How to Deploy a Full-Stack Next.js App on Cloudflare Workers with GitHub Actions CI/CD How to Build a Multi-Tenant SaaS Platform with Next.js, Express, and Prisma How I Completed 15 freeCodeCamp Certifications in 4 Months: A Structured Learning Journey How to Build an Agentic Terminal Workflow with GitHub Copilot CLI and MCP Servers How AI Changed the Economics of Writing Clean Code How to Apply STRIDE Threat Modeling and SonarQube Analysis for Secure Software Development How to Set Up OpenID Connect (OIDC) in GitHub Actions for AWS How to Split PDF Files in the Browser Using JavaScript (Step-by-Step) How to Build Your Own Language-Specific LLM [Full Handbook] How to Build a Self-Learning RAG System with Knowledge Reflection How to Trace Multi-Agent AI Swarms with Jaeger v2 How I Tested Malaysia's Open Data Portals with Plain English How I Built a Production-Ready CI/CD Pipeline for a Monorepo-Based Microservices System with Jenkins, Docker Compose, and Traefik The Hidden Tax of Infrastructure: Why Your Team Shouldn’t Be Running It Anymore From Metrics to Meaning: How PaaS Helps Developers Understand Production From Symptoms to Root Cause: How to Use the 5 Whys Technique Product Experimentation for AI Rollouts: Why A/B Testing Breaks and How Difference-in-Differences in Python Fixes It How to Create a GPU-Optimized Machine Image with HashiCorp Packer on GCP 3D Web Development with Blender and Three.js How to Fix a Failing GitHub PR: Debugging CI, Lint Errors, and Build Errors Step by Step How to Merge PDF Files in the Browser Using JavaScript (Step-by-Step) How to Handle Stripe Webhooks Reliably with Background Jobs How to Build an Automatic Knowledge Graph for Your Blog with PHP and JSON-LD Understanding Proxies and Reverse Proxies: Your Gateway to Secure Networking The Evolution of Nvidia Blackwell GPU Memory Architecture How to Use PostgreSQL as a Cache, Queue, and Search Engine The New Definition of Software Engineering in the Age of AI Reclaim Your Time – Master Automation with Zapier How to Create Dynamic Emails in Go with React Email Why Many Beginner Self-Taught Developers Struggle (And What to Do About It) How to Build a Headless WordPress Frontend with Astro SSR on Cloudflare Pages How to Make Your GitHub Profile Stand Out How to Use Context Hub (chub) to Build a Companion Relevance Engine Why Chrome OS Is the Operating System the AI Era Was Built For How to Build Microservices-Based REST APIs for Healthcare Portals How to friction-max your learning with software engineer Jessica Rose [Podcast #216] Shadow AI Explained: Why Employees Are Using AI Behind Your Back Traditional Scraping vs AI Scraping: A Practical Guide for Developers and Data Teams How Database Indexes Work – A Practical Guide with PostgreSQL Examples How to Streamline Search in Web Applications with Elasticsearch How to Build an Open Source Data Lake for Batch Ingestion OpenAI Codex Essentials – AI Assisted Agentic Development Course Learn Software System Design How to Generate PDF Files in the Browser Using JavaScript (With a Real Invoice Example) How to Get Started with Terraform Service-to-Service Communication: When to Use REST, gRPC, and Event-Driven Messaging A Developer’s Guide to Lazy Loading in React and Next.js The Data Quality Handbook: Data Errors, the Developer's Role, and Validation Layers Explained. United States Residential Proxy: Why Local IP Accuracy Matters for SERP, Ads, and Pricing How to Build a Fashion App That Helps You Organize Your Wardrobe How to Build an Admin Dashboard Sidebar with shadcn/ui and Base UI The AI Governance Handbook: How to Build Responsible AI Systems That Actually Ship How to Build a Local DevOps HomeLab with Docker, Kubernetes, and Ansible How to Use Mixins in Flutter [Full Handbook] How to Prep for Technical Interviews – A Guide for Web Developers GPT-5.4 vs GLM-5: Is Open Source Finally Matching Proprietary AI? Data Visualization Tools for Svelte Developers How to Keep Human Experts Visible in Your AI-Assisted Codebase Efficient Data Processing in Python: Batch vs Streaming Pipelines Explained How to Build and Deploy Multi-Architecture Docker Apps on Google Cloud Using ARM Nodes (Without QEMU) How to Build a Secure AI PR Reviewer with Claude, GitHub Actions, and JavaScript How to Build a Positioning-Based Crude Oil Strategy in Python [Full Handbook] How to learn programming and CS in the AI hype era – interview with dev and prof Mark Mahoney [Podcast #215] CUDA Programming for NVIDIA H100s How to Build Reliable AI Systems. How to Build an Online Marketplace with Next.js, Express, and Stripe Connect How to Build a Cost-Efficient AI Agent with Tiered Model Routing The WebCodecs Handbook: Native Video Processing in the Browser The Bluetooth LE Audio Handbook: From "Why Does My Call Sound Like a Tin Can?" to AOSP Implementation How to Set Up OpenClaw and Design an A2A Plugin Bridge
How Step Counters Work in Wearables and Why Different Devices Give Different Results
Shradha Puri · 2026-05-30 · via freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
How Step Counters Work in Wearables and Why Different Devices Give Different Results

It’s been three years since I started using my wearables to count my steps. Three years of trying to hit the daily 10K target, closing rings, and going to sleep knowing that I accomplished something productive.

But then I put another smartwatch on my wrist in an attempt to see how different those results were. Both watches were on the same wrist, at the same time, counting the same walk. One said 8,400 steps, while the other said 6,900.

Same wrist, 1,500 steps apart.

So naturally, I had a small crisis about everything I thought I knew.

The strange thing is that nobody really tells you this when you buy a fitness tracker. The packaging doesn’t read “lab accurate, not life accurate” or anything remotely close to this idea. The app never mentions the fact that two people who own wearables from the same company might actually have their steps counted differently.

But when you start looking into how wearables calculate your steps, things make more sense than you think.

Table of Contents

  • Inside the MEMS Accelerometer

  • How a Step Becomes a Number

  • Why Wrist-Based Tracking Is Hard

  • Why Slow Walking Confuses Wearables

  • False Steps Are Real

  • Why Lab Accuracy Doesn’t Match Real Life

  • Do Some Brands Perform Better?

  • How the Person Wearing the Device Affects Accuracy and What You Can Actually Do to Improve It

  • Final Thoughts

Inside the MEMS Accelerometer

Each modern fitness tracker and smartwatch includes a MEMS accelerometer (Micro-Electro-Mechanical System). The MEMS consists of a tiny silicon chip with microscopic moving parts inside.

Body movements cause these microscopic components to move by an extremely small margin, which is captured by the sensor as a change in the electric signal. Most wearable devices have 3-axis or triaxial accelerometers. This means that they measure motions in three directions at once:

  • up/down

  • left/right

  • forward/backward

These signals are captured continuously at about 50 times per second.

When you walk, your body produces a recognizable motion pattern, such as hip movement downward, movement of torso up and down and arm swinging rhythmically. What's most important is that your body bounces up and down with each step taken.

This vertical bounce is considered one of the clearest indications when someone walks and that is why step counters are so dependent upon it.

The accelerometer sends out three streams of information regarding movement. Many algorithms combine them into a single magnitude signal using the Euclidean norm:

‖a‖ = √(x² + y² + z²)

This gives the device a rotation-independent way to measure total acceleration.

The Role of Gyroscopes

Higher-end wearables also have a gyroscope that detects any rotations. The accelerometer and gyroscope together make up the Inertial Measurement Unit (IMU). This makes sure that the device can differentiate between you walking or just moving your wrist around.

How a Step Becomes a Number

The sensor itself can't calculate anything. All it does is produce raw motion data. The real work happens when that signal is interpreted through an algorithm, which is where things begin to differ dramatically.

All companies have their own proprietary algorithms. The algorithm used by Garmin is not the same algorithm used by Apple. And Apple’s is not the same as Samsung’s. Some of the most common approaches include:

  • Peak detection: The algorithm detects repeating peaks in the acceleration signal that correspond to walking activity in humans. Since most people walk at a step rate in the range of 100 to 130 steps per minute, the device is designed to detect periodic activity in this range.

  • Zero-crossing detection: Instead of looking for peaks, this approach involves determining how often the signal crosses a midpoint value.

  • Autocorrelation: This method involves searching for repeating patterns in the motion signal over time.

  • Frequency-domain analysis: Some algorithms search for the dominant frequency of walking.

  • Machine learning models: Modern wearable devices have adopted machine learning approaches for walking pattern recognition based on training on large datasets of labeled walking behavior. These systems can differentiate between walking, running, typing, driving and random arm motion most of the time.

But every algorithm carries its own trade-offs. If the sensitivity of the algorithm is set too high, then the smartwatch may overlook slow or subtle motions. On the other hand, if the sensitivity is set too low, the watch would generate false steps when washing dishes or riding on bumpy roads.

There's no perfect setting, but every company has chosen to adopt its preferred compromise.

Why Wrist-Based Tracking Is Hard

The primary problem with modern wearable devices is their position on the body.

The waist-mounted pedometer is located close to the center of mass, which allows for the detection of very clear and strong signals. This is why traditional clip-on pedometers often perform better than you might expect.

On the contrary, smartwatches operate with signals detected from arm movements, and your wrist is noisy. The natural walk accompanied by a natural swinging of the arms provides a very strong correlation between leg movements and arm movements, but any real-life scenario may disturb this reading. If you’re pushing a stroller, holding shopping bags, a mobile phone, or walking with hands deep in your pockets, the correlation weakens and it becomes impossible to detect a specific signal related to leg movement.

Beyond this, even the side of the body where you wear the smartwatch plays a role in data interpretation. For example, the dominant arm tends to produce a stronger acceleration signal, but it also produces additional signals due to its active work in performing different routine actions.

This is one of the reasons why you would’ve noticed that most wearable devices require specifying which wrist you are strapping the device to during setup.

Why Slow Walking Confuses Wearables

One of the most surprising things about this research is that it’s far easier to accurately detect regular walking than it is to detect slow walking.

Wearables do well enough in detecting walking speed at normal paces. But as your speed drops, the acceleration and rhythm of the motion signals start to become smaller. This makes it difficult for algorithms trained primarily on healthy adults walking at normal treadmill speeds to identify slow walking correctly. The same studies may also show that wrist-worn trackers underestimate the number of steps in slow walking.

But why does this matter? The older we get, the slower and more restricted our gait becomes, which means that the motion signals detected by our wearable devices will be weaker. Then there are patients with neurological conditions like Parkinson’s disease or stroke, which can produce gait patterns that consumer algorithms simply weren’t trained to recognize.

So the next time you think your watch is broken, its likely that the detection system is simply working from assumptions that don’t match your movement pattern.

False Steps Are Real

Wearables not only overlook steps, but they can actually create non-existent ones. Because accelerometers measure all kinds of acceleration, quite a lot of actions completely unrelated to walking may trick the algorithm.

Activities that can cause phantom steps include:

  • Driving on bumpy roads

  • Typing aggressively on the keyboard

  • Washing dishes

  • Folding the laundry

  • Drumming

  • Taking a train or bus

There's an engineering dilemma here: the more sensitive your algorithm is to slow walking, the more prone to errors. The less sensitive it is, the better it works, but undercounts certain activities.

This is the reason for very different results from different brands despite having the same data entered.

Why Lab Accuracy Doesn’t Match Real Life

Fitness trackers tend to be surprisingly accurate within laboratory testing. In tests under controlled conditions, such as on treadmills, a number of wearables manage to reach step counting errors below 10%. But the real world tends to be messier.

Researchers call this “free-living” data because it involves movements made outside of the laboratory in normal life situations. The real-world walking pattern is characterized by irregularities such as rough surfaces, stops, carrying things, changes in speed, unpredictable arm movements and walking intervals. All these factors contribute to making step detection more difficult.

A smartwatch may prove to be exceptionally accurate in a controlled environment, yet still behave inconsistently in daily use.

Do Some Brands Perform Better?

Yes, but it’s rarely that significant. Studies indicate that Apple Watch, Garmin, Fitbit, and Samsung are all decent pedometers during normal walking conditions. Garmins are especially valued for their consistency and reliable tracking when outdoors. The Apple Watch reportedly works very well for altered gait and slower walking. Fitbits use a more sensitive algorithm and that may result in increased step counts.

But there are other elements at play. The speed at which you walk, natural movement of your arms, location of the device on the body, what activity you’re doing, and how the algorithm interprets your movement. The difference between two people using the same watch is often larger than the difference between two brands.

How the Person Wearing the Device Affects Accuracy and What You Can Actually Do to Improve It

A few things can noticeably improve step-count accuracy:

  • Walk at a natural pace when possible: Wearables work best at moderate walking speeds. Walking slowly, shuffling and stop-and-go actions are significantly harder to detect with algorithms.

  • Wear the device properly: Try putting on your wearable device snugly above your wrist bone to ensure consistent movement along with your arm.

  • Set your dominant wrist correctly: Most smartwatches will adjust sensitivity settings based on which hand you use as the dominant one.

  • Keep your arms moving naturally: Holding bags, pushing a stroller, or keeping your hands in your pockets might affect the accuracy because most wearable sensors depend greatly on the motion of your arms.

  • Keep firmware updated: Most manufacturers continue to refine their algorithms through firmware updates.

  • Use trends, not exact numbers: Step counts are better at tracking your habits and long-term patterns on the same device, but are less accurate compared to the number of steps registered by other brands.

  • Be cautious with slow or altered gait: Older adults, rehabilitation patients, or those with brain injuries are likely to see undercounting of steps because most algorithms are trained on standard walking patterns.

Final Thoughts

The technology in today’s wearables is truly amazing. A small sensor the size of a grain of rice measures your movement multiple times each second, filters out noise and tries to make sense of the data generated by it. That’s an incredibly difficult engineering problem. But step counting is ultimately an estimation problem.

There are different step counts generated by various brands because they all have different filtering, motion classification, signal interpretation and sensor placement. None of them count your actual steps perfectly. They estimate the probabilities based on your movement patterns. And in reality, human movements aren't always neat and monitored.

So if you have two watches that generate different step counts, don’t panic. They do their best to understand messy movement data.



Learn to code for free. freeCodeCamp's open source curriculum has helped more than 40,000 people get jobs as developers. Get started