Quote:
Originally Posted by NiLuJe
Except the waveform data is pretty screen-specific, possibly even assembly-line specific, IIRC.
|
But maybe having a few different samples makes it possible to try all of them and choose the one that works best for you. Or you can see how big the differences are and play with them with a hex editor. Even if it is assembly-line - maybe there is some kind of documentation of it?
I was only glancing at eInk driver source codes but I saw there is a code that enters "test" mode. Maybe it is even designed for callibration mode. Executing it may be a good place to start. But I need samples of working waveform data first.
So if anyone of you have Kobo Aura (the new one, not HD) and can telnet to it, please execute the following command:
Quote:
|
dd if=/dev/mmcblk0 of=output.raw bs=1024 count=16384
|
and send the output here. I would be gratefull. Note that the device name (mmcblk0) can be different - I'm not sure as I don't have Aura. You can look which devices you have on your reader ("ls /dev" command). Thanks!