Yeah, if you had the storage I’d say use an Ethernet dongle on the phone, wire up Ethernet on the laptop (as long as it’s not a USB 2 dongle that you’d need :) ), transfer over network that way and give yourself some easier transport than wifi…
But in your case, yeah wifi is the right call.
My workflow for reference, I’ve got a dock that supports 3.2gen2, so I connect my phone up there. I’ve got 1 gig on the dock, and I copy over to my NAS (4x1gbit in LAG), and with the dock having USB for mice/keyboard use it’s easy peasy. Once backed up, new phone to the dock, and go the other way.
Most files are already backed up though, with the NAS and my self hosted services, so it’s mostly a single instances backup and not much to copy back.
Just to be clear - it’s the API that’s shutting down, not the app. Not that Google has put in effort for the app either, it hasn’t updated since health connect afaik, but health connect is the health and fitness tooling going forward.
Fitbit has health connect support now, so even if they shift and drop Fit (I hope not, though I also hoped they wouldn’t kill the web interface), and make Fitbit the main Google fitness app, it will still work with Fitbit as the app.
Not really the question I was answering, but that’s not actually a health connect problem.
Withings had an issue, and the way they were connecting to it, which caused a battery drain. To be specific, withings health mate was constantly reading health connect data, which caused a massive power drain.
I’m not aware of any other battery issues with health connect other than Withings and their Health Mate app (specifically reading, not writing).
(Edit: why, why would autocorrect change writing to riding? For shame. To me, for not noticing sooner.)
I’ve got a polar h10 myself, I know their app still connects to Fit not health connect, but I’m sure they will update.
I actually made an app to make use of health connect with my polar h10 for entirely different purposes, it’s really a pretty minor backend change for them to make, so I’m sure Beat will get an update.
Health connect doesn’t set your step count goals, because what it does in the back end (because that’s what it is, the back end API) is set a way to read and write that data.
The front end, Google Fit, also connects to health connect on the back end. And the Fit app is not given a shutdown here, just the API it also uses in the back end.
I suspect Google will stop developing Fit, as they kind of already have. However, all these varieties of other apps out there (Fitbit, Withings Health Mate, Samsung Health, MyFitnessPal, etc) can use health connect data, and do allow you to set goals. They use the same data, and now are more interoperable with Health Connect than they were with the Fit API.
Worst case you could connect to Strava as a go-between should polar be far behind on health connect (again, doubt they would be).
But checking the coospo compatibility, it seems there are a ton of them that all support health connect with coospo, so you wouldn’t be shut out even if health connect wasn’t ready for Polar, you’ll have a ton of options. Including using polar to sync to something that syncs via health connect.
Which is kind of what I do btw, aside from the app for the completely irregular use case I mentioned, I sync polar to Strava, Strava to Fit via health connect. I do that because fairly often I am using polar while cycling, so that’s how I want my data to go. But I then found strength training shares nicely too, and running polar beat and my workout app, I can track all my workout routine items (jefit), which syncs via health connect, and then polar goes to Strava goes to health connect, and it all shows as a single session with great HR data.
Google's working on a way to speed-up data transfers when setting up a new phone: APK Teardown (www.androidauthority.com)
Google Fit dev APIs shutdown set, fate of Android & Wear OS apps go unannounced (9to5google.com)