MobileRead Forums - View Single Post

erkkia · 08-31-2012, 04:45 PM

Inspired by a similar effort for the Kindle DX, I made a VNC viewer kind of app that lets you use the Boox M92 as a secondary (or even primary) monitor for your computer.
It's far from a full blown VNC client and since I did it for myself the code is rather hack-ish. However, while probably not optimal, the application does everything I need and I'm actually using it to type this post. If there is interest I'll gladly share the code.
Connectivity is done over g_serial (USB). For the record speeds achieved were around 300 KB/s, for transfer of image data this is sufficient considering how many updates per second an e-ink screen can do. The application can handle 1366x768 resolution (Part of it was cut off) and 1024x768 very nicely. Both of them 16 shade (4-bit) greyscale.

The solution involves two components: a simple custom application on the M92 and a modified version of TightVNC on the host (I'm using Windows) side.
Currently it's view only so no events are sent back from M92 to the computer. I ran into difficulties with two-way communication and had to drop the feature altogether for now.

08-31-2012, 04:45 PM	#94
erkkia Junior Member Posts: 5 Karma: 244 Join Date: Aug 2012 Device: Boox M92	Boox M92 as E-ink monitor Inspired by a similar effort for the Kindle DX, I made a VNC viewer kind of app that lets you use the Boox M92 as a secondary (or even primary) monitor for your computer. It's far from a full blown VNC client and since I did it for myself the code is rather hack-ish. However, while probably not optimal, the application does everything I need and I'm actually using it to type this post. If there is interest I'll gladly share the code. Connectivity is done over g_serial (USB). For the record speeds achieved were around 300 KB/s, for transfer of image data this is sufficient considering how many updates per second an e-ink screen can do. The application can handle 1366x768 resolution (Part of it was cut off) and 1024x768 very nicely. Both of them 16 shade (4-bit) greyscale. The solution involves two components: a simple custom application on the M92 and a modified version of TightVNC on the host (I'm using Windows) side. Currently it's view only so no events are sent back from M92 to the computer. I ran into difficulties with two-way communication and had to drop the feature altogether for now.