Quote:
Originally Posted by Norbi24
@Pazos, yeah, probably you are right from the systematic point of view,
but definitely the previous behaviour was more convenient for me ...
Now while reading with koreader and if wishing to change the brightness, I'd need to go to the Tolino reading app, do it there and come back to koreader again .. as I always wish to change it globally, system wide due to permanent jumps between koreader and dictionary app
So I will change it back in my koreader fork ...
|
I never ever used an e-ink device with android myself (I tinkered with a friend ereader once) and just have emulators to test (and a device to test stuff that cannot be tested on the emulator). Keep that in mind
Sure, go ahead, but please do notice that planned PRs, like
https://github.com/koreader/android-...ncher/pull/180 ditch the WRITE_SETTINGS permissions entirely. So you'll need to backport the desired (android-luajit-launcher) changes on your branch. This is easy nowadays but might become harder on the near future (for instance, see
https://github.com/koreader/android-...uncher/pull/18)
On open android ereaders normally the frontlight dialog is just another activity and we can start that in KOReader (like we open dictionary apps or links in the external browser). That is probably the way to go but is device/vendor/version dependant.
If tolinos are the kind of all-in-one app where the frontlight dialog is buried inside the reader the other option is to code a simple apk with a dialog on top to change light levels at will and use that in KOReader instead.