This is my MetaWatch :) -- see http://www.metawatch.org
It's showing the following QML demo ( http://pastebin.com/0riqXU3f ) -- which is actually being run on my N950, forwarding the results to the watch.
Obviously, this is not going to be used for showing video :) But for ex. you could create reduced versions of your existing N950 QtQuick applications and show them on the watch, as widgets you can have on your wrist!
The current code is in https://gitorious.org/sowatch/sowatch/ .
Are you doing full screen updates on each frame? Is this the limiting factor, i.e. could you make it faster by calculating (on the N950) which pixels have changed and just send a partial update?
perlinet 5 months ago
@perlinet I'm already doing damage tracking (around 60% of rows are damaged)
This was done using the original firmware though, and there has been a small speedup in recent ones. But not spectacular. The main limiting factor is that the watch _crashes_ if you overflow its input buffers, so the phone has to implement rate limiting (right now I'm experimenting with 10ms between packets -- a packet contains up to 2 lines from the framebuffer -- with a minimum of 50ms between frames).
javispedro 5 months ago