Koreader running on Kobos (all of them, hopefully!)

[embryo]

Originally Posted by hawhill

@embryo: I don't think there is a difference between software versions that would cause that. Probably, it's rather a not deterministic behaviour in general, applying to any version. Which is too bad, of course. Probably, the standby functionality could use some debugging and more love. As all the APIs for that are proprietary, it's quite a mess.

I hope its software depended, so that it can be fixed.
I don't think that is happening also in nickel, but I might be wrong.

For me the battery life is very important (one of the main reasons for using eInk).
I will make more tests before writing anything farther.

[WS64]

I never saw any loss in battery through the next day on Koreader at all, it might sometimes go down from 100 to 99, but that's it.

What's much more missing (and I tried to fix it but could not find the right place) is an automatic suspend function after a few minutes non-use...

[hawhill]

Yes, it's a mess to debug such a thing. I hope we catch it sometimes, but debugging a standby mode is always hard - as the device ought to be inactive when everything works out.

[pazos]

Originally Posted by hawhill

Yes, it's a mess to debug such a thing. I hope we catch it sometimes, but debugging a standby mode is always hard - as the device ought to be inactive when everything works out.

The serial port is not an option because is frozen every time my kmini goes to sleep (my device battery seems to last the same in both nickel and koreader)

But if I launch (via ssh) a python script that polls battery stats (/sys/devices/platform/pmic_battery.1/power_supply/mc13892_bat/capacity) all the time (ie. without sleep) and write the output to a file my battery drains a lot faster IN STANDBY MODE

So, a (very) dumb question: What happens to background proccesses during standby mode??

[Ebri]

I have rebooted to nickel to change a bit my margins, and I saw that the battery % there was 80%. Earlier in koredaer it was 73%, and after reboot I see 71%. I know battery readings are not perfect, but is my understanding correct, that both nickel and koreader should use the same ACPI routines, that provide 10% different results? This makes battery consumption tests a bit gamble-like. (And earlier I haven't noticed so much different readings.)

[embryo]

Originally Posted by Ebri

I have rebooted to nickel to change a bit my margins, and I saw that the battery % there was 80%. Earlier in koredaer it was 73%, and after reboot I see 71%. I know battery readings are not perfect, but is my understanding correct, that both nickel and koreader should use the same ACPI routines, that provide 10% different results? This makes battery consumption tests a bit gamble-like. (And earlier I haven't noticed so much different readings.)

The way I mark a battery value is this:

1. I see what koreader says the percentage is.
2. I exit koreader, go to Scripts > CheckBatteryLevelAutoRefresh.sh in KSM and I press the refresh at least once (sometimes the value drops and stays down).
3. I'm starting Nickel (sometimes I get a different number there)
4. Exit Nickel and start koreader again (after that the number stays constant so I can use it).

[pblasi]

Hi,

Most of the time I try to change brightness level using two-fingered gesture I get a screen rotation. It's really annoying. Can I disable gesture for screen rotation?

Thanks!

[pkdick]

Dear All,

I recently bought a Kobo Aura HD and I installed Koreader: as a newbie, I found that despite the use of large fonts, it is sometimes a bit difficult to make selection using my maybe too "big" fingers". Could'nt it be possible to replace the Koreader options with "icons" ? I think that would be much more suited to such operation (the screen is large enough).
Thank you in advance for your support!

[embryo]

After doing some measurements about the battery consumption of the reader during suspend, I concluded that unfortunately its not version dependable (like it was predicted here by hawhill)
I now use the 734 version and its working OK.
Maybe the sadden drainage has to do with the fact that battery measurement is usually inaccurate.

[Ken Maltby]

Originally Posted by pkdick

Dear All,

I recently bought a Kobo Aura HD and I installed Koreader: as a newbie, I found that despite the use of large fonts, it is sometimes a bit difficult to make selection using my maybe too "big" fingers". Could'nt it be possible to replace the Koreader options with "icons" ? I think that would be much more suited to such operation (the screen is large enough).
Thank you in advance for your support!

Since the AuraHD uses an IR touchscreen, you can use anything as a stylus. A pencil eraser, a Q-tip, coffee stirrer, a toothpick, whatever.

Luck;
Ken

[Ken Maltby]

For the #922 issue at GH;

If "stuck" in File Manager by the koreader.png being accessed improperly, you should be able to navigate to the file and delete it. The long press options in File Manager always worked in the internal uSD card. The koreader.png should be in /mnt/onboard. Just keep poking the "./" until you get there.

**Oh Wait .png is not a file type the File Manager recognizes - My Bad, sorry!**

Luck;
Ken

[JimMcLaren]

I'm having a problem I haven't seen before. All of my epubs in landscape are two columns. No setting I've tried seems to make a difference. Is this a setting problem or a bug?

[PeterT]

Originally Posted by JimMcLaren

Is this a setting problem or a bug?

The obvious answer to that question is YES..

[WS64]

Originally Posted by JimMcLaren

I'm having a problem I haven't seen before. All of my epubs in landscape are two columns. No setting I've tried seems to make a difference. Is this a setting problem or a bug?

defaults.lua:
-- default minimum screen height for reading with 2 pages in landscape mode
DCREREADER_TWO_PAGE_THRESHOLD = 7

I think it would be way better if this one would not be dependend by something like the screen height but simply a 2-columns-in-landscape yes or no field, but this is how it is right now.
So, put this number high to be sure that you never see 2 columns, or put it to zero to always see 2 columns (I prefer it that way).
Chrox just wanted it to be 2 columns for devices > 7 inch, but I still think a) the logic is wrong, screen height is not screen size, and b) 2 columns work perfect even on my 5 inch Kobo Mini, so it is just a question of preferences, not screen dependent.

[Ken Maltby]

Originally Posted by JimMcLaren

I'm having a problem I haven't seen before. All of my epubs in landscape are two columns. No setting I've tried seems to make a difference. Is this a setting problem or a bug?

There is a setting in "defaults.lua" :

-- default minimum screen height for reading with 2 pages in landscape mode
"DCREREADER_TWO_PAGE_THRESHOLD = 7"

I am guessing that, that is there more for the Android Tablet version of koreader and the "7" might mean seven inches? In any case, changing that to some other value might prevent the 2 pages in landscape.

Luck;
Ken

Guess I should type faster.