View Single Post
Old 01-17-2020, 11:53 AM   #9
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,477
Karma: 26012492
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Nope, it doesn't (on its own, at least) .

-f, --flash is what makes (pretty much any combination of other things: i.e., --refresh, --image, --truetype, --clear, --cls, ... you get the picture: all the things ;p) flash .

IIRC, it *does* consume slightly more power, but I'm not sure if it'll have a (really) noticeable impact. My gut feeling would be that one flash would drain less power that two non-flashing updates, though, to answer your question.

Also, some waveform modes *might* be less power-hungry. f.g., you can probably make do w/ DU (which is probably what AUTO, the default, will choose on its own anyway).

And, speaking of wfm, A2 can't flash. Enabling flash will make it try to ghost less on most devices, but it won't actually flash. Just mentioning this for context, as A2 has a really niche use-case, so you probably don't want to use it unless you *know* you want to use it .
(And, with FBInk, it probably wouldn't help on the power consumption side of things, as we enforce monochrome for A2 updates, so that's another PxP processing pass tacked on by the driver).

Last edited by NiLuJe; 01-17-2020 at 12:04 PM.
NiLuJe is offline   Reply With Quote