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

[Alan_S]

Originally Posted by xor_

You're welcome.

And I believe I've fixed this bug as well now.

As for the previous bug about shutdown. Koreader saves the last tab position for each file in the history. If that is the shutdown tab, it might immediately shutdown upon menu access. If you run into this, just delete or edit the history file for that book. There's a line in there:
["readermenu_tab_index"] = 2,
and that value shouldn't be 9. 2 is a good substitute value.

This should be fixed now, but it could still occur when opening a book that had this value saved from the previous version.

Now that we have KSM8 and it uses different path to shutdown script, it also asks for change in path for shutdown menu button. I change it and upload all original files with instructions how to install it.

Also, just to confirm that it still works with latest koreader (2015.11 stable).

This is only needed if you switched to KSM8 from KSM7 (it doesn't work with older KSM version, but you can easily change path, so it would work than).

So, here it is attachment. And of course, all kudos goes to original author @xor_!

[myki]

Thank you very much Alan_S (and xor_).
I suppose the "shutdown + lighttoggle" that you have post will resolve the problem I meet : When I click on the "shutdown" button in Koreader, the buttons disappear and Koreader is still running.
But the lighttoggle still worked

EDIT : It works very well now, thank you very much Alan_S

[Alan_S]

It's interesting, on my device it exited koreader into KSM and in your case it messed things up.

But, important thing is, now it works.

[tshering]

Originally Posted by rido_knight

Hi thanks for this reader app but I have problem with my N905B KOREader. I insallted sm8 and koreader. I touch start koreader then I cant click any folder directory. When I touch screen randomly opened some folders but I cant go where I want. Can I fix this ? Thanks.

You can try changing in
...\koreader\frontend\device\input.lua

local ABS_X = 00
local ABS_Y = 01

to

local ABS_X = 01
local ABS_Y = 00

[NiLuJe]

Wasn't a semi-automatic detection mechanic implemented for that very issue recently?

[Frenzie]

Yes, chrox added it in PR #1608. It even made it into the new stable release.

[tshering]

Originally Posted by Frenzie

Yes, chrox added it in PR #1608. It even made it into the new stable release.

I just tried this on my Touch C. After installing the most recent nightly build, I followed the instruction and pressed the top right corner. Still, the touch coordinates do not match.

Edit: I am not sure what exactly the reasoning behind the test is. I just report what I am observing. When I am asked to touch upper right corner, and I touch somewhere on the lower half of the screen, nothing is happening. If I touch anywhere on the upper half the touch is registered and ["kobo_touch_switch_xy"] = false gets written to settings.reader.lua.

[Frenzie]

Do you perhaps have a KOBO_TOUCH_MIRRORED setting in defaults.lua? Part of me wonders if this "and not" here shouldn't simply be "or", but I've only glanced at it.

[tshering]

Originally Posted by Frenzie

Do you perhaps have a KOBO_TOUCH_MIRRORED setting in defaults.lua?

No, it is a complete fresh copy of koreader.

Originally Posted by Frenzie

Part of me wonders if this "and not" here shouldn't simply be "or", but I've only glanced at it.

I replaced "and not" with "or", but it did not work.

[Frenzie]

I reopened #1608 to investigate.

[tshering]

Originally Posted by Frenzie

I reopened #1608 to investigate.

Thank you!

My statement was not very clear. Therefore I try to clarify.

Originally Posted by tshering

I just tried this on my Touch C.

By "this" I meant to refer to the "semi-automatic detection mechanic" mentioned in this post (I know that was far from obvious.). And what I said next, namely, "After installing the most recent nightly build," was meant to give further details of the same event. The point is: I did not test the latest stable, but only the nightly build. I just mention this in case it makes a difference.

[Ken Maltby]

Originally Posted by tshering

Thank you!

My statement was not very clear. Therefore I try to clarify.
By "this" I meant to refer to the "semi-automatic detection mechanic" mentioned in this post (I know that was far from obvious.). And what I said next, namely, "After installing the most recent nightly build," was meant to give further details of the same event. The point is: I did not test the latest stable, but only the nightly build. I just mention this in case it makes a difference.

If you are talking about these, I think they are both the same. For all but the Android releases, there are also those at the OTA sites (Which are often later releases than at the GitHub download site.) for example. There appears to be a new numbering to the nightly releases, I am now on v2015.11-11. (Numbering it 2015.11-011, might have been more prudent.)

Luck;
Ken

[roger64]

Hi

Draining the battery

I have no figures to provide but after drawing a comparison for some weeks between Nickel 3.1.8 and Koreader (latest), I am convinced that Koreader drains the battery a lot quicker than Nickel. How much is a lot? I would say conservatively twice quicker.

For both the use was quite the same. I mostly took wifi off.

I am keen to experiment more on this if need be but I do not know how to do it.

[NiLuJe]

@Ken Maltby: That's just a bit of git magic .

[Ken Maltby]

Originally Posted by NiLuJe

@Ken Maltby: That's just a bit of git magic .

Ah... thanks for disambiguating the naming process.

Luck;
Ken