Your first 30 days with the Amazfit Cheetah Pro
The box tells you what the Cheetah Pro measures. This is the part it leaves out: which of those numbers you can believe in the first week, which need a month, and what to set before the first run so the month is not wasted.

Before the first run
Twenty minutes on the first evening. Everything the Cheetah Pro will tell you for the next month is built on a heart-rate trace, a satellite mode and a screen setting, and all three are decided here.
Put it where the sensor works
A finger’s width above the wrist bone, one notch tighter than feels natural for the first week, sensor window clean. The Cheetah Pro has a 47 mm case and wants a wrist of about 160 mm or more to sit flat; on a smaller wrist it rocks, and a rocking sensor is the source of half the strange numbers in month one. See wrist and case size .
Set your maximum heart rate, or clear it
Every zone, every training-effect score and most of the load figures hang off this one number. If you know it from a recent hard effort, enter it. If you do not, delete the age-based default rather than leaving it: a wrong maximum quietly miscounts every run.
Decide about multiband now
The Cheetah Pro has multiband GPS. Under trees, between buildings and in steep valleys it is the accuracy that matters; on an open road it changes nothing and costs battery — 26 h of GPS becomes 26 h with it on. Pick one mode and leave it: switching between runs makes the pace history uncomparable. See multiband GPS: when it matters .
Choose gesture or always-on, and mean it
The Cheetah Pro has an AMOLED screen. Always-on is the single biggest drain after the GPS chip — the site’s battery guide takes a fifth off for it — and gesture mode is what the quoted 26 h assumes. Try gesture for a week before deciding it annoys you.
Build one data screen you will actually read
Pace, heart rate, distance, time. Four fields, one screen, big digits. Everything else can be a second screen you swipe to when you want it. The stock screens show too much and you will read none of it at speed.
Download maps before you need them
The Cheetah Pro shows full topographic maps, and the tiles for your region are a download over Wi-Fi or the app, not something in the box. Do it on the first evening; it is slow, and the first time you want a map is not the time to discover it is missing.
Load music now, decide about it later
Music from the watch to earphones is convenient and expensive: on the one maker that publishes a figure, GPS with music is about a third of GPS alone. Load a playlist while the watch is on the charger, then treat it as a short-run feature until you have checked the battery planner for anything long.
Calibrate the altimeter once
The barometric altimeter is what makes the elevation on a hilly run honest. Calibrate it once from a known height or from GPS on a clear day, and let it auto-calibrate after that.
Week one: the numbers that appear first
Zepp’s training tools on the Cheetah Pro starts producing figures after the first run and the first night. These are the ones that arrive first, with what each one needs before it means anything.
- PAI — from the first day, a rolling seven-day score built from heart-rate response to everything you do, with 100 as the target. It is a health-habit figure rather than a training one.
- Training Effect and Training Load — after each session, an aerobic and anaerobic effect and a load figure, plus a recovery time. Generic until the watch has your fitness level.
- A VO2max estimate — after the first outdoor run with heart rate.
- Readiness — after a few nights, a score from overnight HRV, resting heart rate, skin temperature and sleep. Like every readiness score, it needs its ranges first.
Weeks two and three: the numbers that need data
The second layer of figures is where the Cheetah Pro earns its price, and where a new owner is most often misled — because each of them shows a value before it has the data to justify one. What follows is what each needs, on this maker’s system: the baseline takes about a week for Readiness, a few weeks for load.
- Readiness as a trend — about a week of nights for the score to be about you rather than a default.
- Training load over time — the acute-versus-chronic view needs a few weeks of sessions before a normal week stops looking like a spike.
- Sleep — from the first night; the trends want a fortnight, and Readiness wants the watch on your wrist for all of them.
Weeks three and four: what to trust
Zepp’s system is the closest to Garmin’s in shape — a load figure, a training effect, a readiness score — and the least documented, so it deserves the most scepticism in the first month. After four weeks the Readiness has ranges and the load history has depth; before that, PAI and the sleep score are the two numbers worth looking at.
- PAI at 100 is a health target, not a training plan. A runner in training will sit well above it; that is fine.
- Wear it to bed or ignore Readiness. It is built entirely on overnight data.
- Recovery time is a floor, not a ceiling.
- The model cannot see illness or life stress — see training load and readiness, and how much to believe .
Two figures on the Cheetah Pro are worth writing down at the end of the month, because they are the ones you will compare against later: the fitness estimate and, if the watch shows one, the morning recovery figure. Everything else is a snapshot.
Battery on the Cheetah Pro
These are the Cheetah Pro’s own figures, and the arithmetic the site’s battery guide applies to them. The quoted number is the best case; the settings you chose above decide which line you actually live on.
| Mode | Hours | What it assumes |
|---|---|---|
| GPS, quoted | 26 h | The manufacturer’s figure, cheapest satellite mode, screen in gesture mode, no music |
| Multiband | 26 h | The figure to use if you turned multiband on above |
| … with the screen always on | ≈ 20.8 h | A fifth off, per the battery guide |
| … with music | ≈ 8.3 h | About a third of the figure above it — the only maker that publishes this ratio is Garmin, and it is applied to every watch as an estimate |
| Everyday | 14 days | Watch mode with the sensors on; decides how often it lives on a charger |
For a race, take a further fifth off for a cold day and then add your margin — or let the battery planner do the sum for the Cheetah Pro with your settings and your finish time. Everyday battery of 14 days means the charger is a weekly appointment at most.
What the catalogue says about it
The finder ranks the Cheetah Pro on the same figures this page uses. Its one-line verdict: Titanium, maps and multiband for the price of an entry Forerunner.
Where it is strong
- 43 g with a titanium bezel and offline maps.
- Multiband GPS that tests surprisingly well.
- Two weeks of everyday battery.
What it gives up
- Training analysis is the shallowest of the dedicated watches.
- Smaller and less mature software ecosystem.
If any of that is news after buying it, the finder will show you what the trade-off bought you — and what sat next to it in the ranking.
Questions readers ask
- What is PAI supposed to be?
- Personal Activity Intelligence: a seven-day rolling score of how much your heart rate has been raised, with 100 as the level associated in the underlying study with lower cardiovascular risk. It is about health, not about running faster.
- Do I need a chest strap?
- Only if the wrist trace misbehaves for you. See [wrist or chest: which heart rate to trust](/guides/wrist-or-chest-heart-rate).
- Should I leave multiband on all the time?
- If most of your running is under trees or between buildings, yes, and plan around 26 h rather than 26 h. If it is mostly open road, no: the accuracy gain is invisible there and the battery cost is not.
- How long before the watch actually knows me?
- About a month of consistent wear, including nights. Week one gives you a heart-rate trace and a first fitness estimate; the load and recovery figures need about a week for Readiness, a few weeks for load; and only after that is the Cheetah Pro describing you rather than an average runner.