View Single Post
Old 06-30-2021, 04:01 PM   #5
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by Renate View Post
Poke 3 (& Poke 2, other Onyx?) screen light

It ought to be the same for all recent models (novas, pokes...). The behaviour you described matches exactly what KOReader does

Other "modern" android devices based on Freescale/NTX, like Nooks or Tolinos, have the same interface found in their linux counterparts (Kobo/Bq)

I'm still amazed by how bad their implementation is. I get it from Nooks/Tolinos since they're not indended to be used with 3rd party software. But Likebook/Onyx could have done this better:

1. Map their "white" leds to window's attributes brightness level (to avoid breaking compatibility with a zillion apps)
2. Provide a ready to be consumed frontlight dialog that can be started by other apps using intents.
3. Provide a service, ready to be bounded by 3rd party apps, to do advanced stuff (ie: enter A2 mode onScroll and exit A2 when scroll ends, already implemented in stock browser, or set a custom light/warm levels without showing the user a dialog)
pazos is offline   Reply With Quote