View Single Post
Old 04-10-2022, 01:46 PM   #23
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,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
We don't touch the bluetooth state on startup (much like we don't touch the Wi-Fi state on startup, unless it's detected as broken).

We also don't do anything with bluetooth *at all*, so, yeah, I would expect the connection to drop due to inactivity rather soon . And then to be cut-off entirely whenever KOReader kills the Wi-Fi, as the power states for those two are unfortunately paired in the kernel.

Sidebar about the Sage: current nightlies now feature an optional (i.e., opt-in) autostandby feature, which should allow one to achieve similar power efficiency than nickel (as in, still terrible, but slightly less so ^^).

Fun fact: a PW5 drains less power while *idling* at standard frontlight levels than a Sage/Elipsa in suspend (!!). That means there won't be any miracle cure happening any time soon, because suspend is the lowest power state we can achieve.
NiLuJe is offline   Reply With Quote