MobileRead Forums - View Single Post

NiLuJe · 05-01-2020, 02:24 PM

@Lusephur: That last observation is "normal" eInk ghosting (exacerbated by the way Nickel handles displaying a sleep screen, which is not the worst, but not entirely optimal either).

I don't have a Mk. 6 device myself, and given the sneaky potentially random nature of the results on a Glo HD, I don't really have a better answer than: you're not alone, but it's quite likely a very weird corner-case at a deep hardware level that no-one probably cares about anymore, because it affects an EoL device & platform, and the only people that might have been able to do something about it in the first place are NTX (the OEM that provides the boards for Kobo devices) or even NXP (the people that actually come up with the SoC used on said boards), not even Kobo themselves

.

05-01-2020, 02:24 PM	#5
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@Lusephur: That last observation is "normal" eInk ghosting (exacerbated by the way Nickel handles displaying a sleep screen, which is not the worst, but not entirely optimal either). I don't have a Mk. 6 device myself, and given the sneaky potentially random nature of the results on a Glo HD, I don't really have a better answer than: you're not alone, but it's quite likely a very weird corner-case at a deep hardware level that no-one probably cares about anymore, because it affects an EoL device & platform, and the only people that might have been able to do something about it in the first place are NTX (the OEM that provides the boards for Kobo devices) or even NXP (the people that actually come up with the SoC used on said boards), not even Kobo themselves . Last edited by NiLuJe; 05-01-2020 at 02:26 PM.