CTHRU/Hitrava

Updates to HiTrack file format.

HardCorePawn opened this issue ยท 0 comments

Been trying to find a solution for Huawei Health -> Google Fit. Stumbled across Hitrava (awesome utility btw! ๐Ÿ‘)... and then I figured out how to get HiTrack files using BlueStacks+Root. ๐Ÿ˜‰

Unfortunately... going Huawei Health -> Strava -> Google Fit doesn't seem to be syncing my Heart Rate data across (which is what I'm ultimately wanting with my walks/elliptical/yoga sessions). ๐Ÿ˜ข

So, I've started playing around with things to see if I can develop something that will utilise the Google Fit REST API to load the .tcx files directly into Google Fit.

Anway, I have noticed some "extra"/undocumented fields in the HiTrack files depending on what device is used to initiate the activity:

If activity is started on phone (Nokia 7 Plus, Android 10, Huawei Health 10.1.1.312), I get "tp=alt" records...
tp=alt;k=1611458567000;v=33.70000076293945;

if started on watch (Huawei Watch GT2e), I get "tp=alti" records
tp=alti;k=1611601613000;v=5.7;

--

Also, when using phone to start activities... I get pm-n and pm-b records... I have deduced that these are:

tp=pm-n: Pace for last 100m
- k= Number of metres since start * 10000 (ie. k / 10000 => metres)
- v= number of seconds for last 100m

example:
tp=pm-n;k=42000937;v=64.0;

and

tp=pm-b: Pace for last 100yds
- k= Number of yards since start * 10000 (ie. k / 10000 => yards)
- v= number of seconds for last 100yds

example:
tp=pm-b;k=24000487;v=54.0;

Like p-m (Pace for last 1000 metres) and b-p-m (pace for last mile) records they don't have a timestamp to reference to beginning of activity or unix epoch etc. but I guess they might be useful for "split times"? ๐Ÿค”

--

Not sure if any of this is of any use, but thought it might be useful to have more of the HiTrack file format documented. ๐Ÿ‘