Skip to content

Releases: owulveryck/goMarkableStream

v0.11.0-alpha: small hack for FW 3.6

28 Aug 14:42
b052d38
Compare
Choose a tag to compare

This is an alpha release supporting firmware 3.6.

This release is not bullet proof.

  • It consumes a lot of CPU due to the gzip compression
  • there is no colors (and even worse, the blue is not rendered at all).

Use it only if:

  • you want to contribute or
  • you really need to present something remotely :D or
  • you are an adventurer

v0.10.0

18 Jul 14:16
88b98aa
Compare
Choose a tag to compare

The stream listens to events from the pen or the touch.
It sends the picture for 2s after the last event.

The consequence is that the process consumes nearly 0% CPU even when the stream is opened.

v0.9.0

06 Jul 18:37
eb96596
Compare
Choose a tag to compare

This is another implementation using a stream of data instead of the websocket.
This release includes several optimizations, and for one picture every 200ms, the CPU usage should be less than 10% (and remains close to zero when idle).

You can change the framerate with RK_RATE parameter, and with 100ms you got near realtime but with a little bit more of CPU.

v0.8.8

04 Jul 14:38
798ee9b
Compare
Choose a tag to compare

The streaming is stopped after 1 hour.
It means that there is a need to refresh the page after one hour, whatever the activity is.

v0.8.7

04 Jul 12:43
d076761
Compare
Choose a tag to compare
  • Under the hood, a sync.pool has been implemented to lower the pressure on the GC which improves the performances (25% CPU in normal utilization)
  • add new configuration variable:
RK_RATE                Integer          200

200 is the pause time between two pictures. You can lower it to reach near realtime, but the less you add, the more CPU intensive it is, and therefore it drains the battery faster.

v0.8.6

30 Jun 15:24
649fac6
Compare
Choose a tag to compare

Changelog

v0.8.5

30 Jun 08:40
7904f80
Compare
Choose a tag to compare

Workaround for #40

v0.8.4

29 Jun 15:06
Compare
Choose a tag to compare
  • Added functionality to handle excessive requests and preserve tablet battery life. Implemented a lock mechanism to regulate the number of simultaneous requests and prevent overloading the tablet.
  • Included various wait screens to provide a better user experience during periods of high traffic or when the lock is active.
  • Introduced a timeout feature to mitigate potential memory leaks caused by unclosed tabs.

Note that there are known issues with Safari, and efforts are being made to address and resolve these problems in future updates.

v0.8.2

26 Jun 15:48
6df9bff
Compare
Choose a tag to compare

Changelog

v0.8.0

23 Jun 10:25
Compare
Choose a tag to compare

Changelog