This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unreliable gestures in Watch Mode?

hi all,
not sure it's my imagination, but it seems gestures during Watch Mode has gotten appreciably less reliable for 3.30. in particular, for watch faces using it to go into high powered mode to show seconds, there are times that i cannot get it to work at all (and i'm talking 10-15 gestures)...the only way of fixing it seems to be to switch watch faces and then it seems to work again.

this could be face specific, yet i've encountered it on a number of Connect IQ faces (No Frills, WF4COOL, VSWF, for e.g.)

anyone else having problems too since 3.30?
  • On a somewhat related matter I've found that the nice "LINE" watchface stays in "high power mode", i.e. displays seconds at all times, anyone else notice this ? Is it now an option for the developer like for the native watchfaces ?


    also works for same developer's SC8.

    i did a quick test, and i'm not sure it's optimized, but i was seeing about 3% consumption every 10 hours or so, so at least that watch face, in its current consumption is higher in consumption than my ~4% per day use with a native analog watch face or Big and Lean CIQ watch face.

    of course, that's still not bad (~7% per day)

    would be curious if you see something similar with LINE.
  • Actually, it's not really high power mode (CIQ high power mode is different than the firmware's high power mode BTW - a watchface runs in the firmware's low power mode all the time if the current generation of watches is like the last one in this reguard)

    With the new functionality, every second, a watchface can update part of the screen if the watchface in in CIQ's low power or not, and the rule is, over a minute, it can execute for a max of an avg of 30 milliseconds each second.

    When more watch faces get the 1hz code, you won't really need to worry about the gesture on devices that support 1hz (f5,f5x,f5s,935,q5). It's cool. Been testing my watchfaces that do 1hz for a few weeks now...


    Jim: have you found any added battery load with the 1hz updating? (see my concurrent post to yours above where i note a higher battery load but i don't know what SC8 used previously)
  • I got 8-10 watchfaces doing 1hz right now, and most I've used for quite some time before 1hz, and notice little to no impact on battery. What can be done at 1hz is very restricted to conserve battery,
  • I got 8-10 watchfaces doing 1hz right now, and most I've used for quite some time before 1hz, and notice little to no impact on battery. What can be done at 1hz is very restricted to conserve battery,


    thanks. that's great information.
  • Actually, it's not really high power mode (CIQ high power mode is different than the firmware's high power mode BTW - a watchface runs in the firmware's low power mode all the time if the current generation of watches is like the last one in this reguard)

    With the new functionality, every second, a watchface can update part of the screen if the watchface in in CIQ's low power or not, and the rule is, over a minute, it can execute for a max of an avg of 30 milliseconds each second.

    When more watch faces get the 1hz code, you won't really need to worry about the gesture on devices that support 1hz (f5,f5x,f5s,935,q5). It's cool. Been testing my watchfaces that do 1hz for a few weeks now...


    Thanks for the insight, presumably that will only work for digital watchfaces then if the it's limited to part of the screen, unless it's a seconds sub-counter in a small window ;-)
  • Thanks for the insight, presumably that will only work for digital watchfaces then if the it's limited to part of the screen, unless it's a seconds sub-counter in a small window ;-)


    Actually, the sample code for a 1hz watchface in the SDK is an analog watchface. It's possible to do analog, but a bit trickier, in that the limited area that gets gets updated keeps changing. I've not done an analog one, as I myself prefer digital.
  • Hey, sorry for "diging" this topic but I have the same problem. Did you already found a way to fix it?