
Onyx Boox Note Air 2
10.30", 64 GB, Blue, Black
Onyx Boox Note Air 2
10.30", 64 GB, Blue, Black
Does anyone know the problem that you can still see the previous screen shimmering through when scrolling? Is this a defect, normal or can it be adjusted somewhere? LG
Onyx devices are relatively complex to use and the understanding of e-ink displays in general is mostly rudimentary, so I'm writing a short guide here :).
Ghosting
It is a normal phenomenon that occurs with every e-reader (with e-ink technology) to a certain extent: https://de.wikipedia.org/wiki...
Onyx devices
The Note Air 2 (and other Onyx devices) is designed for applications other than just reading e-books (writing by hand, simple web lookup/rudimentary browsing, reading complex PDFs, using appropriate apps, etc.). The device makes this possible through relatively fast hardware compared to conventional e-readers and various technical tricks, although depending on the application and settings, ghosting can occur to a greater extent than is now expected with modern e-readers (with these, the phenomenon is practically non-existent depending on the setting of the refresh rate).
With the settings in the current Onyx firmware, ghosting can be controlled in three ways:
- Setting the refresh rate in the NeoReader (or the preferred reading app). This is the classic way that all e-readers offer.
- Setting the screen mode, which can be set globally and for each app individually. There are 5 modes. In general, the modes determine the speed of the screen, whereby the following applies: more speed = stronger ghosting.
- Manual refresh: Using various methods (e.g. gestures or the "navigation ball"), the user can command the screen to rebuild the current page (the screen flickers once briefly...), which makes the ghosting disappear.
Furthermore, it is possible to set automatic rules for each individual application, independent of the screen mode, whereby one can define the number of screen commands or page changes after which the image is refreshed.
If the phenomenon cannot be controlled or remedied, it is of course quite possible that the device is broken...
Found the solution to the problem :-)