Google Health 5.07 Fixes Manual Logs and Missing Maps

Google Health 5.07 began rolling out on August 28 to Android and iOS with three concrete gains for anyone who types in a workout by hand, plus faster maps, trail-run distance totals and a restore for broken Health Connect links.

The release continues the steady cleanup that followed the May rebrand of the Fitbit app into Google Health, when many users found manual logging slower, maps vanishing mid-session and third-party data dropping offline.

Nothing in the notes points to a new product surface. The work stays fixed on the everyday friction that appeared once the Fitbit name disappeared and the redesigned tabs took over.

What Version 5.07 Ships

Google’s community post lays out the changes in three clean buckets: Activity and Fitness, Weight Tracking, and Health Connect. Both platforms carry the same 5.07 version number. The company says the rollout continues over the next week in phases by carrier and device; iOS users already see wide availability while Android remains staggered.

Those lines match the official 5.07 community release notes word for word. No new AI coach features or hardware requirements appear; the work stays at the everyday friction points.

The same version number on both platforms keeps support simpler. Users comparing notes across devices can treat the feature list as identical even while the store delivery still arrives on different calendars.

Manual Workout Logging Finally Feels Faster

Google calls out three separate improvements for users who enter exercises by hand rather than relying on automatic detection from a Pixel Watch or Fitbit.

• You can add and adjust more metrics while logging an exercise.
• Those edits now appear in the workout summary more quickly after you save them.
• Switching a swim from pool to open water unlocks additional metrics that were previously locked or limited.

The change matters most for people whose devices do not auto-detect every activity, or who train in sports the sensors still miss. Earlier post-rebrand complaints frequently mentioned that manual entry felt like an afterthought; 5.07 treats it as a first-class path. Swimmers who move between lanes and open water get the clearest win, because the app no longer forces a thinner data set after the switch.

Edits landing in summaries faster also shortens the loop between finishing a session and seeing the corrected numbers in daily or weekly views. That small speed-up removes one of the common “I fixed it but the chart still looks wrong” moments.

Phone-only trackers feel the difference most sharply. Without a wrist sensor feeding automatic streams, every field they type becomes the record of record. More editable metrics and a quicker summary refresh turn that path from a backup option into a usable daily habit.

The swim switch improvement is narrow but precise. Pool sessions and open-water sessions carry different distance and stroke expectations. Unlocking the fuller field set after the change stops the app from discarding detail the user already intended to keep.

Maps Load Faster and Stop Disappearing

Google says it continued polishing the maps experience with faster loading times plus smoother rendering and adjustments. The same update fixes the bug that left maps missing after a phone-tracked run, bike or walk.

Phone-only users felt that bug hardest. A finished session without the route map made later review nearly useless and broke any share or export flow that expected a path. Trail and incline runners gain a second related fix: those sessions now count toward the Running Distance total instead of sitting outside the main tally.

Together the two map-side changes make the app more trustworthy for outdoor sessions logged without a wrist device. The smoother pan and zoom also cut the lag that older user posts described when the interface felt like a sluggish web page.

Missing maps after a phone-tracked session created a second problem beyond simple review. Any later share or export that expected a path simply had nothing to attach. Restoring the map closes that gap without asking the user to re-log the workout.

The Running Distance correction works in the same direction. Trail and incline runs already lived inside the activity list; they simply failed to feed the headline total. Folding them into the main tally keeps weekly and monthly distance views honest for hill and off-road training.

Weight Graph Range and the Health Connect Restore

The weight graph receives a visual recalibration of its dynamic minimum and maximum range. Google’s note says the change makes trends and changes easier to view at a glance. Long-term weight watchers who saw compressed lines or misleading plateaus get a clearer picture without changing any data they already logged.

On Android the more practical fix restores Health Connect for users who had lost the link. After the update, Health Connect reappears in the Partner Apps section of the Connections screen. Google’s own help pages spell out how Health Connect pairs with the app and the Health Connect sync troubleshooting steps if permissions or recent-access lists still look empty.

That restore matters because many third-party nutrition, sleep or workout apps route data through Health Connect. A silent drop left gaps in the Google Health totals that no amount of manual entry could fully repair. Users who already re-granted permissions after earlier drops can now confirm the listing is back without starting over.

The weight change is display-only. Logged numbers stay exactly as entered; only the min and max bounds of the chart shift so small movements stop vanishing into a flat line. Anyone reviewing months of data gains a cleaner slope without touching a single entry.

Health Connect’s return under Partner Apps is the more operational fix. Once the listing is visible again, the usual permission and recent-access checks described in Google’s help pages can finish the job. The update itself does not rewrite those steps; it simply makes the partner row reachable.

The Cleanup Arc Since the May Rebrand

Google turned the Fitbit app into Google Health in May. The redesign brought a new Today tab, Gemini-powered coach features for Premium subscribers and tighter ties to Pixel hardware. It also dropped or delayed several familiar Fitbit workflows and left automatic detection, nutrition logging and map reliability incomplete for a stretch of weeks.

User feedback on X and forums in June described slow page loads, workouts that failed to roll calories or minutes into daily totals, and an interface that looked polished in marketing but felt unfinished in daily use. Google responded with a public roadmap of bug fixes and improvements and began shipping numbered releases almost every couple of weeks.

1. May 2026, Fitbit app rebrands as Google Health; coach and redesigned tabs launch; immediate complaints about missing features and speed.
2. July 2026, Public roadmap update shows remaining work on exercise auto-detect, nutrition goals, Apple Health sharing and structured fitness plans.
3. Mid-August 5.06, Adds the 5.06 Coach insights off switch so the Today tab can stay quiet for users who found the proactive guidance cluttered.
4. Late August 5.07, Manual metrics, maps, running totals, weight range and Health Connect restore land.

Each release chips at a different complaint cluster. 5.07 focuses on the mechanical reliability of logging and display rather than new coach language or subscription upsells. The pattern matches Google’s usual post-launch iteration once a major rebrand draws sustained feedback.

The July roadmap still lists exercise auto-detect, nutrition goals, Apple Health sharing and structured fitness plans as open work. 5.07 does not close those items. It narrows in on the logging and display failures that made the existing features hard to trust day to day.

5.06 gave users a way to quiet the coach. 5.07 gives them back maps, distance totals and partner links. Taken together the two late-August builds show a deliberate split between optional guidance controls and core data plumbing.

How Phone and Watch Paths Diverge After 5.07

The headline fixes land hardest where automatic capture is weakest. Phone-tracked runs, walks and rides regain maps and correct distance roll-ups. Manual entry gains more fields and faster summary updates. Health Connect reappears for Android partner flows.

Wearable owners still see the shared polish. Faster map rendering and smoother pan and zoom help any session that opens a route view inside the app. Shared account data that already moved between watch and phone keeps moving; the update simply stops the phone side from dropping supporting pieces.

• Phone-only outdoor sessions: maps return, trail and incline distance counts toward Running Distance.
• Manual and swim entry: more editable metrics, quicker summary refresh, fuller open-water fields.
• Android third-party stacks: Health Connect listing restored under Partner Apps.
• Pixel Watch and Fitbit wearables: map performance gains and stable shared totals, without new hardware demands.

That split explains why the release notes omit fresh coach copy and new device requirements. The work targets the paths that broke after the rebrand, not the Premium surfaces that launched with it.

What Stays the Same on Purpose

No new AI coach features appear in 5.07. No hardware gate is added. Both platforms keep the same version number and the same three-bucket change list. The company describes the rollout as phased by carrier and device over the following week, with iOS already wider than Android.

Leaving the coach and subscription layers untouched keeps the release readable. Users who only wanted reliable maps or a working Health Connect row do not have to sort through marketing language to find the fix. The concrete list stays short and the tone stays plain.

The July roadmap items on auto-detect, nutrition goals, Apple Health sharing and structured plans remain outside this build. 5.07 does not pretend to finish that list. It treats mechanical trust in logging, maps, totals and partner links as the nearer problem.

For anyone comparing 5.06 and 5.07, the through-line is restraint. One release added a quiet switch for coach insights. The next restored core display and connection behavior. Neither tried to relaunch the product.

Who Feels the Update First

Phone-tracked runners and walkers regain reliable maps and correct distance totals. Swimmers who split pool and open-water days gain richer fields after the switch. Android users who lost Health Connect see the partner listing return. Anyone who still prefers typing metrics by hand instead of waiting for auto-detect gets faster edits and more fields.

Wearable owners on Pixel Watch 5 or Fitbit Air still benefit from the map polish and any shared data that flows through the app, but the headline wins sit with people who never bought the new hardware or who train in activities the sensors still under-serve. The Pixel Watch 5 Health Guardian trends already push deeper monthly signals; 5.07 simply makes sure the phone side of the same account does not drop the supporting map or third-party pieces.

Install paths stay the usual ones. Android users can pull the update from Google Health on Google Play once it reaches their device cohort; iOS users check the App Store. After install, a quick check of Connections > Partner Apps confirms whether Health Connect has reappeared for those who needed the fix.

Google frames the release as continuous improvement built on prior feedback. The concrete list is short, the language is plain, and every item removes a friction point that appeared after the rebrand rather than adding a new marketing surface. For users who stayed with the app through the messy middle months, 5.07 is another quiet step toward the reliability they expected when the Fitbit name disappeared.

The staggered Android delivery means some devices will see the Partner Apps restore later than others. iOS users who already have wide availability can verify maps and manual fields immediately. Either way the checklist is the same: confirm the version, test a manual edit or a phone-tracked route, and glance at Connections if third-party data had gone missing.