Google/Samsung step count

[Russell1256]

Read a while back that the step count issue should be fixed in he next update (changing from Google to Samsung because of the Google block). Anyone know when the upgrade is arriving?

[Ace]

Google is deprecating the Google Fit API this year. Migrating to Health Connect might be the best route, but the migration can take time to develop.

[vaibhavmalaviya1233]

anyone know if this has been done because I have granted all permissions on health connect app but it still doesn’t show me any steps for today(shows 0) and shows incorrect steps for yesterday.

[RonC]

The steps are somehow registered on a slightly different time or timezone (or so it seems).
The solution that worked for me is here:

$fd(steps)$ not displaying correctly KWGT

I have also noticed that the steps with the formula $fd(steps)$ are not read out correctly. I use Samsung Health and the Health Connect connection for tracking (KWGT has switched from Google Fit to Health Connect in v3.75). I have found a workaround for myself. For me, $fd(steps)$ is shifted forward by 2 hours. With the formula $fd(steps, a0d2h, a0d2h)$ I get nearly the correct current value (the value always differs between 1-20 steps from the value in Samsung Health). The past days can also…

[vaibhavmalaviya1233]

yep, it kind of think so since it gives what had seemed to be combined steps of yesterday plus today when i tried to get and it ended up with that answer. I ended up using one of that Samsung health notification formula before commenting here. it also seems Samsung health doesn’t sync the steps count through the health connect which could be only on my end problem. nowadays seems like we even need workaround skills you never know when you need it.

[QilinQuinn]

I think different time zones might be causing the problem.
I’m in GMT+8.
I use the formula to adjust the calculated time by 8 hours, and the data is correct.
But I am not sure if it works in other time zones, maybe you can try it.

This is my formula:
$fd(steps,a0d8h0m0s,a0d23h59m59s)$

I use this in Lock(3.76b422110) and widget(3.76422110),
the data is correct!

It seems only “start time” had some bug.
I tried to change other formula when my time zone at 16:00, it is error.

[Ace]

Can confirm this works, at least for me.

[Ranjith_Jayadevan]

Hi

Am in GMT+5.30 Zone and changing the start time as mentioned above is more or less working for me too.

$fl(0,7,“i+1”,“fd(steps,r+i+d18h30m,r+i+d18h29m59s)”,“-”)$

This gives me last 7 days steps stats. Diff between HC Data and this is around 3-6 steps.

For sleep data, in built KWGT Function was working for me.

[QilinQuinn]

I usually only use the step count for the day, so I hadn’t tried the data from the previous days. I just tested it out.

For me (GMT+8), this formula had only one day that was off by “1” step; the other days were completely accurate. $fl(0,7,“i+1”,“fd(steps,r+i+d16h0m,r+i+d15h59m)”,“-”)$

I tried using “r+i+d15h59m59s,” but the error was larger. After removing the 59s, there was only one day that was off by 1 step. You might give it a try.

However, the data for today still needs to use the formula I mentioned earlier to be correct.

[frank]

This is now fixed in 3.77, it was indeed a timezone issue
Beta out soon

[Ranjith_Jayadevan]

fetching data for 14 days was crashing my phone (Nothing Phone 1 running Nothing OS 2.6). It was making the phone very very slow and once I removed the widget, it became normal. So for now, am using Tasker to fetch historical data. Don’t know if this is specific to me or the RoM… but FYI

[PatsyCassin]

i think is fixed now in new version 3.77…..