PocketBook-KOReader: a document reader for PDF, DJVU, EPUB, FB2, CBZ, ... (AGPLv3)

[tomsem]

I installed on PocketBook Era (version 2022.6). I'm not sure what it is supposed to look like.

What I see is a new section on the Apps page: "User's". There are 2 entries there, "@._koreader" and "@koreader". (Is this how it is supposed to look?)

Tapping the first of these goes back to Home. Tapping the second displays a stack trace for a few seconds: 'unrecognized PocketBook model PB700' in 'function probeDevice' before returning Home.

I guess I will have to wait until Era/PB700 support is added to KOReader. I don't see any config/text files that would let me add it myself, short of downloading and building from source code.

[cellaris]

You have to install version 2022.06-41(or later). You can find it here...

http://build.koreader.rocks/download/nightly/

[tomsem]

Originally Posted by cellaris

You have to install version 2022.06-41(or later). You can find it here...

http://build.koreader.rocks/download/nightly/

Thanks, I'll wait for next release (2022.07?) on GitHub.

[ichnilatis]

.....

[violino]

English-Romanian dictionary for PocketBook - could anyone please help me?

I am using the KOReader application that accepts at least the stardict dictionary format.

I know that there is one for Kobo, here:
https://www.mobileread.com/forums/sh...&postcount=902

But I tried to convert the above kobo dictionary to stardict format and it does not work:

- I used the dictzip-decompile-windows.exe utility to obtain the .df file from the kobo dictionary.

- And then I have used pyglossary to transform the above .df file to a StarDict dictionary - which is accepted by KOReader.

However, once I put the obtained stardict dictionary on the pocketbook, the KOReader application detects it - but it does not work: all translation attempts will not work anymore, not even with other dictionaries that are also installed.

Help on this topic would be greatly apreciated. Thank you in advance!

[the_Pan]

Hi everyone!

I have installed koreader 2022.07 on my new pocketbook era now and am already impressed with how well it works!
The only thing I haven't been able to get working properly so far is the automatic screen rotation with the gyro-sensor.
Is there a trick to activate it, or is it not yet possible?

[pazos]

Originally Posted by the_Pan

The only thing I haven't been able to get working properly so far is the automatic screen rotation with the gyro-sensor.
Is there a trick to activate it, or is it not yet possible?

Hi. Gyro is not supported on Pocketbooks and there're no plans to add support.

Of course patches welcome.

It might be a little tricky to implement if it's driven by Pocketbook middleware instead of generic linux input subsystem. Should be doable anyways.

[cellaris]

Originally Posted by the_Pan

Hi everyone!

I have installed koreader 2022.07 on my new pocketbook era now and am already impressed with how well it works!
The only thing I haven't been able to get working properly so far is the automatic screen rotation with the gyro-sensor.
Is there a trick to activate it, or is it not yet possible?

In any case, with how poorly the PocketBook devices' gyroscope works, it will be much quicker and more efficient for you to assign a gesture or a tap on the screen to reverse the rotation.

[the_Pan]

Originally Posted by cellaris

In any case, with how poorly the PocketBook devices' gyroscope works

It seems to me that it depends on the length of the chapter how fast the sensor reacts.
With many short chapters it responds wonderfully, but with very long chapters it can take a very long time.

I had also considered using shortcuts for the rotation, but I don't know if I can make friends with it in the long term.
I usually forget things like that very quickly...

[the_Pan]

Originally Posted by pazos

It might be a little tricky to implement if it's driven by Pocketbook middleware instead of generic linux input subsystem. Should be doable anyways.

How to find out how it's implemented?
If there's a tutorial how to find out and create an patch i would try my luck.

But I'm only a (Linux)user, not a pro.

[pazos]

Originally Posted by the_Pan

How to find out how it's implemented?
If there's a tutorial how to find out and create an patch i would try my luck.

But I'm only a (Linux)user, not a pro.

On your linux computer all things that are used as inputs (ie: keyboard, mouse, touchscreen, gyro, lid, buttons...) generate generic events in /dev/input/eventX.

A program like evtest can be used to understand which kind of input is represented by one of the eventX.

You need to get shell access to your pocketbook and lurk over there, find one of those "eventX" nodes that generate new events based on your pocketbook orientation.

If there's none you'll need to see how to do it using pocketbook sdk (I'm assuming it is possible). Google is your friend.

[the_Pan]

I got pbterm running now on the era, but of course evtest is missing.
Do you have an hint how to bring it to the pocketbook?
I still try to get ssh running, but for now without luck.

[Frenzie]

Assuming armhf is the right package, you could see if this one works: https://packages.debian.org/stretch/...vtest/download

For more versions see (depending a bit on which libc you need; I picked the oldest as it's likely to be the most compatible):
https://packages.debian.org/stretch/evtest
https://packages.debian.org/buster/evtest
https://packages.debian.org/bullseye/evtest
https://packages.debian.org/bookworm/evtest
https://packages.debian.org/sid/utils/evtest

If the first link works then you're zero effort lucky, otherwise we'd have to check some more.

[the_Pan]

Hmm, I always get "./evtest: not found", even after chmoding and testing all the packages you linked.
Is it mandatory to push it in an explicit directory?
How to find out the lib version? I'm on fw version 6.7.775.
Meanwhile, I played around a bit (cat/dev/input/eventX > eventX.txt) and found the only event, which seems to react on screen rotation is event5.

[pazos]

Hi.

I did a quick research to give a better answer than my previous one. Hopefully is useful if anybody plans to add support for pocketbook gsensor.

1. Based on this comment /dev/input is populated but not readable by non-root users. So handling it that way is a big nope

2. Pocketbook SDK already includes ways to deal with gsensor. You can grep https://github.com/koreader/koreader.../inkview_h.lua with "gsensor". Optionally with "orientation", I dunno if they're the same.

There're two functions that look apealing:

int QueryGSensor();

int ReadGSensor(int *, int *, int *);

Since Pocketbook API is mostly undocumented the best way to understand what it does is trying to understand the output on the real thing.

I'm assuming QueryGSensor returns a kind of orientation that can be enumerated (but there's no enum as part of the api) while ReadGSensor is more like a boolean function where you pass a pointer to each one of the 3-axis, and if the function returns ok you can trust these three pointers contain valid data for a given moment of time. Normally 3-axis acelerometers return a value on range 0-255 (or -127 - 127), but there's no way to know that beforehand.

3. While the pocketbook api is already accesible using LuaJIT's ffi in this case we might want to keep the implementation in C, as part of https://github.com/koreader/koreader...t-pocketbook.h

The reason is: unlike other calls that are driven by the user, like set the frontlight level, this one needs to be run in an event loop. We're going to expect an event each time the gsensor changes. In that regard we're just polling there to keep the common base/frontend code cleaner and "event-driven".

4. You need to figure out how to deal with corner cases.

Two types:

4.1 deal with devices that have no gsensor.
4.2 deal with legacy devices that ship an inkview library that has missing symbols for the functions you're using.


You can probably skip both in the research stage and just figure out a way that works on your device. Then push a patch and gather some feedback (does it work the same on other gsensor devices?, does it crash if the device lacks a gsensor?, does work on FW4.X?).

TL;DR: Use Pocketbook API and document what different functions are doing when called.