Quote:
Originally Posted by chandravadans
The fix works, thanks! 
But I'm a little concerned about the (bad) effect on the display. I'd read somewhere that e-ink displays aren't that great at refreshing constantly, and can get worn out. I'll dig deeper and let you know if that's actually true. |
The clock was never meant to be used continuously. I provided this option only at a certain point, since I thought it could help us tracking down why some devices did not respond to touch after a certain FW update.
Quote:
Originally Posted by chandravadans
Was curious, does the device have to stay busy displaying something on the screen? Or does having a script running in the background also do the trick? That should definitely take some pressure off the display.
Again, 
--EDITED--
Turns out, it does work. Invoke a script that runs in an infinite loop in the background when startmenu starts, and kill it when startmenu ends. It doesn't necessarily have to print anything on the display, thereby (potentially) saving it. Tried the same for koreader, and it worked. |
That was actually the next step I was thinking of. Did you do some experiments how intensively the device has to be kept busy?
I am glad it works for you. However, it would be nice to know why this problem occurs on your and some other devices, and doesn't on others . Or why the problem disappeared for WS64 after replacing the internal sd.
If we don't find a better solution than to keep the device busy, we should think of a way to keep it busy doing something meaningful. But right now I don't have a good idea.