Skip to content

Conversation

mark9064
Copy link
Member

Hopefully fixes #1425 (I haven't tested) and other jank caused by motion measurements happening more often than usual

The period isn't exactly 100ms due to rounding, but I think it's close enough since there is nothing here that depends on super high precision for accuracy (this is a problem for PPG for example)

@mark9064 mark9064 added the maintenance Background work label Jun 27, 2025
@mark9064 mark9064 added this to the 1.16.0 milestone Jun 27, 2025
Copy link

Build size and comparison to main:

Section Size Difference
text 379176B 48B
data 948B 0B
bss 22536B 0B

Run in InfiniEmu

@tituscmd
Copy link
Contributor

I've been using this today, and it feels like the display is polling slower than before. When I swipe between screens, there's a slight delay before I can swipe again, it seems less responsive than it used to be. But only slightly

@mark9064
Copy link
Member Author

It should be more responsive as the systemtask spends less time doing things like motion updates when there are many events leaving it free to process touch events etc

@tituscmd
Copy link
Contributor

It should be more responsive as the systemtask spends less time doing things like motion updates when there are many events leaving it free to process touch events etc

It seems the watch needs some "getting used to" this, as it definitely feels more responsive after a day or two of use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Background work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Display turns on every 30 min when Shake Wake is active

2 participants