Update, now that MetaWatch is shipping
15 views
Skip to first unread message
Joe Hughes
Sep 13, 2011, 2:15:30 PM9/13/11
to Cicada
Now that the MetaWatch is shipping to a broader audience, I've opened
up this group to public visibility and participation.
The existing code in the github repository was written against a
prerelease OpenWatch and earlier watch firmware. I haven't been able
to get Cicada working 100% with the latest digital watch firmware
v0.7.28—I'm not getting button presses from the watch, it seems like
the firmware may be capturing them rather than passing them to the
MetaWatchManager app. If you're succeeding in getting the watch into
a state where it sends events for all of the buttons, please post here
to let us know.
Joe
up this group to public visibility and participation.
The existing code in the github repository was written against a
prerelease OpenWatch and earlier watch firmware. I haven't been able
to get Cicada working 100% with the latest digital watch firmware
v0.7.28—I'm not getting button presses from the watch, it seems like
the firmware may be capturing them rather than passing them to the
MetaWatchManager app. If you're succeeding in getting the watch into
a state where it sends events for all of the buttons, please post here
to let us know.
Joe
SteveM
Oct 2, 2011, 11:09:44 AM10/2/11
to Cicada
I'm using firmware 0.7.42 and as far as I can tell button presses are
being received and handled by Cicada.
Still only a newbie (day 4 now) so watch out for my ignorant
questions: some things coming from Cicada or MW Manager arrive very
quickly on the watch and some are tediously slow, in particular the
button press responses on the Application Menu are very slow to arrive
on the watch even though the Android screen responds immediately. I
wondered whether Cicada is waiting for a screen refresh interval to
timeout before sending the screen? For menu UP/DOWN buttons it ought
to respond asap because the user is needing to see the bar go up/down
the menu.
Am I right? I'm reading through the code so hopefully I'll figure that
out for myself :)
being received and handled by Cicada.
Still only a newbie (day 4 now) so watch out for my ignorant
questions: some things coming from Cicada or MW Manager arrive very
quickly on the watch and some are tediously slow, in particular the
button press responses on the Application Menu are very slow to arrive
on the watch even though the Android screen responds immediately. I
wondered whether Cicada is waiting for a screen refresh interval to
timeout before sending the screen? For menu UP/DOWN buttons it ought
to respond asap because the user is needing to see the bar go up/down
the menu.
Am I right? I'm reading through the code so hopefully I'll figure that
out for myself :)
Joe Hughes
Oct 2, 2011, 1:17:20 PM10/2/11
to Cicada
The issue mentioned in the original post on this thread, I think, had
more to do with a bug in MWM that kept it from posting useful
information about which button was being pressed, and changes to the
way that the firmware handles button presses.
On your other topic of responsiveness, sending the pixels for the
entire MetaWatch screen across the bluetooth connection takes roughly
1-2 seconds, which explains why the simulated screen image in the
Cicada UI updates much more quickly. This can be improved by sending
only the rows of pixels that have changed, and Cicada does this. I
need to rewrite some of the watch UIs, like the app list, to make the
most of this: to page between screens of apps rather than scrolling
the entire list (which updates far more rows of pixels). In my ideal
world, commonly-used UI patterns would be run entirely on the watch
firmware, making things much more responsive.
Joe
more to do with a bug in MWM that kept it from posting useful
information about which button was being pressed, and changes to the
way that the firmware handles button presses.
On your other topic of responsiveness, sending the pixels for the
entire MetaWatch screen across the bluetooth connection takes roughly
1-2 seconds, which explains why the simulated screen image in the
Cicada UI updates much more quickly. This can be improved by sending
only the rows of pixels that have changed, and Cicada does this. I
need to rewrite some of the watch UIs, like the app list, to make the
most of this: to page between screens of apps rather than scrolling
the entire list (which updates far more rows of pixels). In my ideal
world, commonly-used UI patterns would be run entirely on the watch
firmware, making things much more responsive.
Joe
Reply all
Reply to author
Forward
0 new messages