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 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).
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 4 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 4 months ago
Bastard!
generalantilles 5 months ago 2