View Single Post
Old 08-28-2015, 08:41 AM   #53
thatworkshop
hub
thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.
 
thatworkshop's Avatar
 
Posts: 715
Karma: 2151032
Join Date: Jan 2012
Location: Iranian in Canada
Device: K3G, DXG, Kobo mini
Quote:
Originally Posted by isotherm View Post
Thanks, I'm glad you like it.
1. The eink_fb_hal.ko is a modified kernel driver. It is partly based on the driver from the K3, but was modified to be more flexible and allow any mapping, etc.
2. I'm not aware of any permanent screen problem (e.g. burn in) by disabling the refresh. Also, some commercial e-readers with the same screen have a feature like this.
Awesomeness.
It's always active on my Kindle since day 1. Much more enjoyable reading. Refresh whenever I want/need/feel like it.

Do you think we can manipulate drivers in such a way that screen refresh rate becomes faster? Here I'm not talking about this module and the perfect functionality that it provides, but rather more about geekmaster's video player (which was fairly painfully slow on DX. ?

Last edited by thatworkshop; 11-20-2015 at 03:51 PM.
thatworkshop is offline   Reply With Quote