Developer options

[Edivar]

Hello
I installed KO reader in my eink Android (hisense A9). I was trying to change refresh screen settings but I didn't find it.
I get that it is not showing because the app is not aware of the device being eink, however, I was looking for the developer options menu but it's not showing to me. What do I need to do so that that menu appears.

Also, is there a guide to include a new device as eink supported?

[pazos]

Originally Posted by Edivar

Hello
I installed KO reader in my eink Android (hisense A9). I was trying to change refresh screen settings but I didn't find it.
I get that it is not showing because the app is not aware of the device being eink, however, I was looking for the developer options menu but it's not showing to me. What do I need to do so that that menu appears.

You need to be on the file manager, not on the reader. Then go to Tools -> More tools -> developer options.

Originally Posted by Edivar

Also, is there a guide to include a new device as eink supported?

Yes. It is easy if the driver is already supported and you just need to register your specific device to use that driver. In that case: https://github.com/koreader/koreader/issues/8482

But hisense is not one of the supported drivers. Assuming your device has an AllWinner SoC you might want to read https://github.com/koreader/android-...her/issues/344

There's no guide for writting new drivers, but the link above contains links to previous driver quests with a happy end

It usually requires you to reverse engineer the part of the framework that does the calls to drive the EPD and document how it behaves under stock.

The only help we can provide happens **after** your work. We write a new driver based on your documentation, do a test build for you and you can check if it works correctly following the guide for supported drivers

New drivers are always a good thing. We have 4 drivers with a few variations and those work on a bunch of devices. A new driver for AllWinner SoC would probably be useful for 10+ different devices.

[kandwo]

Originally Posted by pazos

You need to be on the file manager, not on the reader. Then go to Tools -> More tools -> developer options.



Yes. It is easy if the driver is already supported and you just need to register your specific device to use that driver. In that case: https://github.com/koreader/koreader/issues/8482

But hisense is not one of the supported drivers. Assuming your device has an AllWinner SoC you might want to read https://github.com/koreader/android-...her/issues/344

There's no guide for writting new drivers, but the link above contains links to previous driver quests with a happy end

It usually requires you to reverse engineer the part of the framework that does the calls to drive the EPD and document how it behaves under stock.

The only help we can provide happens **after** your work. We write a new driver based on your documentation, do a test build for you and you can check if it works correctly following the guide for supported drivers

New drivers are always a good thing. We have 4 drivers with a few variations and those work on a bunch of devices. A new driver for AllWinner SoC would probably be useful for 10+ different devices.

The Hisense A9 has a Qualcomm Snapdragon 662. I'd expect that to be the same one that many Onyx devices also use. Unfortunately, the Onyx Qualcomm driver doesn't work for e-ink functionality

[pazos]

Originally Posted by kandwo

The Hisense A9 has a Qualcomm Snapdragon 662. I'd expect that to be the same one that many Onyx devices also use. Unfortunately, the Onyx Qualcomm driver doesn't work for e-ink functionality

Sadly is a bit harder than that.
Two devices having the same or similar SoC means nothing if they don't share other commonalities (OEM, BSP...)

We just keep their names for reference. At the end of the day it is more likely than a potential driver for your Hisense works on other models of the same brand and other brands with the same dealer.

I assume that BSP plays a major role in anything e-ink. For instance the guys at Pine received not only the bootloader and the kernel but also an entire android rom (binaries at least, not sure about source code) for their PineNote.

Those android roms contain shared libraries used to drive the epdc. They're usually tied to the android view hiearchy so the rom gets compatibility with almost all android aplications out there.

Usually brand apps do a more fine grained usage of the epdc by calling those libraries directly. Well, uhm, not directly. They call a few native functions exposed to JVM via JNI.

The way to add a new port is:

1. document a (sub)set of function calls the stock reader uses to drive the screen.
2. share your findings