Support

Nine times out of ten another app is holding the connection. The pad accepts one Bluetooth connection at a time, so if FitShow or any other treadmill app is open, even in the background, Waalk cannot see the pad. Close the other app fully, then power the pad off and on so it drops the old connection and starts advertising again. Open Waalk and it reconnects to the remembered pad on its own.

If it still will not connect, check that Bluetooth is on in iOS Settings. Failing that, send the pad model through the form; connection reports are how new quirks get fixed.

The list is short because it only names what has been verified on real hardware: the TOPUTURE TP7 and TP8, with belt start, speed, pause, and full recording. Beyond those it comes down to which protocol your pad speaks. Pads that use the FitShow app speak the same protocol as the TP8, and walkers are already using many of them with Waalk; they show up in Bluetooth as FS-, FSGN, or TR510-T under many brand names. Pads using the standard Bluetooth fitness machine profile should also work, with belt control where the machine allows it.

Two hard limits. KingSmith uses its own private protocol and isn't supported yet; Waalk recognises one and offers to put you in touch if you can help test. And a pad with no Bluetooth at all cannot be supported by any app, because there is nothing to talk to. If yours isn't on the list, send the model through the form. Verifying new pads is exactly what it's for.

Recording and belt control are separate abilities. Every supported pad broadcasts its data over Bluetooth, and that is all recording needs. Starting the belt, changing speed, and pausing are commands the machine has to accept, and some treadmills simply do not take commands from any app; they only report what they are doing. On a pad like that, a walk that records perfectly while speed buttons do nothing is the pad's design, not a broken install, and your treadmill's own controls always work regardless.

One exception worth reporting: if your pad's own app can drive the belt and Waalk cannot, the machine clearly accepts commands and Waalk should learn its dialect. Send the model through the form.

No. Waalk records from the belt itself, so once the walk is running you can lock your iPhone and get back to work; the recording carries on and the walk is written to Apple Health when you finish. This is one of the ways it differs from FitShow, whose connection wants the app open and in the foreground, and where a drop mid-session can lose the walk.

No. Waalk talks to the pad directly over Bluetooth and does the whole job itself: connects, records the walk from the belt, controls the belt where the machine allows it, and writes everything to Apple Health. There is no FitShow account or login anywhere in the chain, and nothing to keep installed.

The one thing to remember is to close FitShow before you walk. The pad accepts a single Bluetooth connection, so whichever app connects first locks the other out. If you're weighing the two apps, Waalk vs FitShow goes through it feature by feature.

That is almost always the Health write permission. Apple asks for it once, on first launch, and a declined prompt is silent forever after: Waalk keeps recording, Health receives nothing, and no error appears anywhere. To check it, open the Health app, tap your profile picture, tap Apps under Privacy, find Waalk, and make sure the write categories are on: workouts, steps, walking distance, and active energy. The next walk lands normally.

If the permissions were already on and a walk is still missing, send the details through the form.

The steps are almost certainly there, just not counted. Tap the day's step number in Health and scroll to All Recorded Data: the walk is sitting in the record. Health counts one source per window of time and keeps the rest as records, so it never adds two sources together, and by default your Watch and iPhone outrank any third-party app. On a walking pad that priority backfires. Your Watch reported a few hundred steps for that hour, because your wrist barely moved while you typed, and its number beat the belt's thousands.

The fix takes a minute and sticks. Open Health, go to Steps, scroll down to Data Sources & Access, tap Edit, and drag Waalk above iPhone and Apple Watch. From then on, when both report for the same window, the belt's numbers win. The full explanation covers the edge cases.

That tile is a special case. It shows motion steps counted by the iPhone and Apple Watch themselves, and Apple excludes every third-party app from it. No setting changes that, whichever app writes your steps; it is Apple's design decision for that one tile, not lost data and not your app failing.

Your walk still shows up everywhere that matters: in Fitness as an Indoor Walk workout with distance and energy, in your Move and Exercise rings, and in Apple Health, where the steps count toward the daily total once Waalk sits at the top of your step sources. The longer story, if you want it.

Move and Exercise, yes. Rings run on workouts, not step counts: Move is active energy and Exercise is brisk minutes, so an app that only wrote step samples would leave both rings exactly where they were, however many thousands of steps it synced. Waalk writes each walk as an Indoor Walk workout carrying distance and active energy, which is what the rings actually read, so Move and Exercise get credit no matter what the Steps tile thinks.

Stand is the exception. Apple lets no app write Stand hours: that ring is fed only by the Apple Watch sensing that you stood and moved during the hour. So a Waalk walk can't move it, and if you're wearing your Watch on the pad, the same still-wrist problem that undercounts your steps can occasionally miss your standing too. Nothing to fix in any app; it's between you and the Watch.

No. Waalk needs only your iPhone and the pad. The pad measures the belt itself, Waalk records from it with the phone free to stay locked, and the walk lands in Apple Health with steps, distance, and ring credit. Nothing in that chain involves a Watch.

If anything, the Watch is the device that struggles here. It counts steps from arm swing, and on a pad under a desk your hands are on the keyboard, so owners see an hour of walking logged as a couple of hundred steps. Wear one if you have one; it is still the best heart rate sensor in the room. You just don't need it for steps.

No. Health is built to prevent exactly that. For any window where more than one source reported steps, it counts one source and keeps the others as records; it never adds them together. If Waalk wrote 5,000 steps for an hour in which your Watch wrote 800, the day's total includes one of those numbers, not 5,800. Which one wins is whichever source sits higher in your Steps source list, which is why putting Waalk at the top matters.

The only rough edges are partial overlaps, like a Watch that kept counting after you stepped off the belt. Totals can look slightly odd around those edges, but they are never doubled.

It depends on how the service imports, not on Waalk. Anything that reads workouts from Apple Health can see the walk once it is written there: it arrives as a regular Indoor Walk workout with distance and energy, the same shape as any other app's. Services that only accept recordings made with their own app or their own devices will not pick it up, whichever app wrote the workout; that is their import policy, and no app in the middle can change it. So the question to ask of the specific service is simply whether it imports workouts from Health. If it does, your pad walks come along.

Because they measure three different things. The pad drives the motor, so its distance is ground truth; the step figure on its display, when it shows one, is either counted by a sensor or derived from speed, depending on the pad. The Watch counts wrist swings, which barely happen while you type, so at a desk it is the least reliable of the three. Waalk takes the belt's distance and divides by your stride length to estimate steps, 63 cm by default, and labels them as estimates because that is what they are.

To make that estimate honest, calibrate once: count a hundred steps on the pad, read off the distance covered, divide, and enter your stride in Settings. Which numbers to trust compares all three, metric by metric.

Recording new walks stops until you unlock; nothing else changes. Your saved walks stay visible in the app, everything already written to Apple Health stays in Apple Health, and nothing is deleted or held back. The unlock is one payment, shown in your own currency in the App Store before you buy. It is not a subscription: no renewals, nothing recurring, and Family Sharing is included, so one payment covers the household.

The purchase lives with your Apple Account, not with the phone, so nothing is lost. Make sure the new iPhone is signed in to the same Apple Account you bought with, then tap Restore Purchases in Waalk's settings and the unlock comes back. There is nothing to re-buy, and the same step works after deleting and reinstalling the app.

Yes. Family Sharing is enabled on the unlock, so anyone in your App Store family group can use it without paying again. On their iPhone they download Waalk from the App Store, and if it asks them to unlock, they tap Restore Purchases in Waalk's settings; the family purchase comes through. One payment, whole household.

Refunds for App Store purchases are handled by Apple, not by the developer; no app maker can issue one directly.

If something in Waalk pushed you toward a refund, send a message through the form too. Knowing what went wrong matters more than the sale.

No account. There is nothing to sign up for, no login, and no password to lose. Your walks are stored on your iPhone and, with your permission, written to Apple Health; health data never leaves your device through Waalk. There is no tracking, there are no advertising identifiers, and nothing is sold or shared. Waalk has no server of its own.

Waalk does count a small amount of anonymous usage data: which model of pad you connect to, which Bluetooth protocol it speaks, and whether saves to Health and unlocks succeeded. Nothing from inside a walk is included, and you can switch it off in Settings, under Privacy. The privacy page lists exactly what is counted.

The one optional exception is head-to-head challenges. If you create or join one, the challenge code, the name you type, and your step total for that window are stored in your own iCloud through Apple's CloudKit so the other person can see the score. Waalk cannot see that data either. The privacy page spells all of this out.