• Replies 3 replies
  • Subscribers 18 subscribers
  • Views 640 views
  • Users 0 members are here
Options
Related

1hz watchface - can not load, no debug info or errors

FlipStone
So I'm trying to translate my watchface to a 1hz version, it runs fine in the emulator but when I try to load it on the watch it seems to freeze...

I select a new watchface and when I get at my watchface the screen just freezes, the watch stays responsive (I can choose select, or choose another watchface) but there is no display update.

The problem is mainly that nothing is shown in the CIQ_LOG.TXT or the <APP-ID>.TXT file, meaning I have no clue where exactly things go wrong. I assume it's the 30ms update limit or something? But what would be the way to figure this out?
  • Ok, what device are you running on?

    Are you using the delegate for the power budget? (you can see if the 30ms is a problem with it)

    Where are you doing the clearClip() call? (this sounds like where the problem may be to me)

    If you look at the sample 1hz I posted, I do clearClip() at the start of onUpdate(), as doing it at the end of onPartialUpdate() did kind of odd things.

    It almost sounds like you have a clipping region that doesn't get cleared properly, so nothing you do in onUpdate() actually shows on the screen and maybe nothing after the first call to onPartialUpdate() either.
  • Ok, what device are you running on?

    Are you using the delegate for the power budget? (you can see if the 30ms is a problem with it)

    Where are you doing the clearClip() call? (this sounds like where the problem may be to me)

    If you look at the sample 1hz I posted, I do clearClip() at the start of onUpdate(), as doing it at the end of onPartialUpdate() did kind of odd things.

    It almost sounds like you have a clipping region that doesn't get cleared properly, so nothing you do in onUpdate() actually shows on the screen and maybe nothing after the first call to onPartialUpdate() either.


    No clue what the issue was but seems something got corrupted (I had versions of eclipse for the 2.2.6,. 2.3 beta and now the 2.3.1 final sdk). I completely reinstalled everything and now things seem to work! MEaning both things get drawn as getting written to the log ;)

    It's a bit tricky getting the proper clipping area for the second hand (it consists of a drawline and drawcircle so have to play with the bounding box a bit) but almost there!
  • For me and the 2.3.0 beta, I kept a 2.2.6 workspace with it's own copy of eclipse, and a second copy of eclipse with it's own workspace for 2.3.0, as there was a big difference in the plugin.

    With 2.3.1 I have everything back in my regular workspace/eclipse, with the 2.3.1 SDK and plugin.

    Maybe it was something where there was a bit of confusion between SDK and plugin for you and your set up? Who knows, but glad it's working for you now!