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

[Ken Maltby]

If the problem is solved by the Giorgio's unmodified port of Koreader, you might want to try doing the factory reset, then updating to the current Kobo firmware, then installing the launcher of your choice, then doing the Koreader install form post #1, then doing any modifications one by one. There are a number of them described throughout this thread. Perhaps there is something in the mods or order of their application, in Markismus's 1 Step Hack that is reacting with something on your Touch. Doing the mods one at a time might let you see where the problem gets introduced.

The "1 Step Hack" is a great convenience, to those of us that use it with no problems,
as it incorporates a number of separate mods and hacks as well as the two major programs, Giorgio's port of Koreader and Sergey's Launcher with USBnet. It may be reasonable to expect that there will be some who will want or need to follow the more "official" path of the individual installs.

Luck;
Ken

[robmyers]

I'm having trouble building koreader for Kobo (djvulibre fails with a weird ld error). Are there any step-by-step Kobo-specific environment setup and compilation instructions available?

[cgm999]

Giorgio: I only care to have koreader functional on kobo , so fell free to use my patch / hack as you see fit .

[giorgio130]

Originally Posted by someGuyHere

I looked at the diffs between the version on page 1 and the version of the 1 klick install.

I could not really find something that looks like the problem, so I decided to just copy all configuration changed files from the version of page 1 into the version of the 1 klick install.

Note: I did not change the koreader-base.

Viewing and Typing area are the same, but horizontally inverse (right is left), so one of the configuration changes is bad for the Kobo Touch and mixes up the orientation between input and screen layout.

Having a solution for that I tried to find where the horionzal input is done and I found out that changing the orientation to landscape results in left and right being correct, but up and down is inverted.

I tried changing the rotation_map line 132 in koreader/frontend/ui/inputevent.lua to the following:

	rotation_map = {
		[0] = {},
		[1] = { Up = "Down", Right = "Left", Down = "Up", Left = "Right" },
		[2] = { Up = "Right", Right = "Down", Down = "Left", Left = "Up" },
		[3] = { Up = "Left", Right = "Up", Down = "Right", Left = "Down" }

After that did nothing I fiddled around with the calculations in line 323 f with no success (no changes in the following code snippet).

		elseif Device:isKobo() then
			input.open("/dev/input/event1")
			Device:setTouchInputDev("/dev/input/event1")
			input.open("/dev/input/event0") -- Light button and sleep slider
			print(_("Auto-detected Kobo"))
			if dev_mod ~= 'Kobo_trilogy' then
				function Input:eventAdjustHook(ev)
					if ev.type == EV_ABS then
						if ev.code == ABS_X then
							ev.code = ABS_Y
						elseif ev.code == ABS_Y then
							ev.code = ABS_X						
							-- We always have to substract from the physical x,
							-- regardless of the orientation
							if (Screen.width<Screen.height) then
								ev.value = Screen.width - ev.value
							else
								ev.value = Screen.height - ev.value
							end
						end
					end
					return ev
				end
			end

Any ideas?

I'll might be able to try something later, but from tomorrow on I'll be offline for a few days. When I'm back I can have a look at the changes that cause the problem solved by changing the configuration to the version in post #1.

Thanks for the support!
Thomas

Hi! It's not very clear for me if the official package is working ok for you or not. If it's not, I'll try to help! With official package I mean the one at first post without any mods applied. A couple guys reported touch input as mangled on the kobo touch, and at least that version includes a fix addressing it. If you still have the problem I'll have to investigate some more. (I have the suspect that inverted touch happened only on the "old" touch that still uses a distinct firmware, and if it is like that, now it should be the other way around...)

[giorgio130]

Originally Posted by robmyers

I'm having trouble building koreader for Kobo (djvulibre fails with a weird ld error). Are there any step-by-step Kobo-specific environment setup and compilation instructions available?

If you're half-way through compilation, you should be almost done
A couple things you could have missed:
- in koreader-base, you should modify the file "Makefile.defs" changing "-mfloat-abi=softfp" to "-mfloat-abi=hard"
- if you're using the linaro toolchain, I had to rename arm-linux-gnueabihf-pkg-config to something else, so that it couldn't been found
- to build a complete package: cd to koreader-base, "make kobo", cd .., make customupdate

You should find a zip containing your build

[someGuyHere]

Hi Giorgio,

sorry to answer so late, but I didn't take a computer along.

Originally Posted by giorgio130

Hi! It's not very clear for me if the official package is working ok for you or not. ... With official package I mean the one at first post without any mods applied.

(I have the suspect that inverted touch happened only on the "old" touch that still uses a distinct firmware, and if it is like that, now it should be the other way around...)

I cleaned my Touch and updated to the current Firmware 2.6.1. After that I installed the one klick thing to get the launcher and replaced the koreader with the one in the first post.

I don't know if I have an "old" touch, how do I find out?

Anyway the problem is still present. In "normal" not landscape orientation left and right are switched. In landscape orientation up and down is switched.

I cant figure out where to touch to exit the FileManager yet.

Best regards,
Thomas

[giorgio130]

Originally Posted by someGuyHere

Hi Giorgio,

sorry to answer so late, but I didn't take a computer along.



I cleaned my Touch and updated to the current Firmware 2.6.1. After that I installed the one klick thing to get the launcher and replaced the koreader with the one in the first post.

I don't know if I have an "old" touch, how do I find out?

Anyway the problem is still present. In "normal" not landscape orientation left and right are switched. In landscape orientation up and down is switched.

I cant figure out where to touch to exit the FileManager yet.

Best regards,
Thomas

Try changing in inputevent.lua:
if dev_mod ~= 'Kobo_trilogy' then
function Input:eventAdjustHook(ev)

modify "Kobo_trilogy" to something else, whatever you wish, and save; see if this solves. If it's so, I'll try to find a way to discriminate between new and old touch.

[someGuyHere]

Originally Posted by giorgio130

Try changing in inputevent.lua:
if dev_mod ~= 'Kobo_trilogy' then
function Input:eventAdjustHook(ev)

modify "Kobo_trilogy" to something else, whatever you wish, and save; see if this solves. If it's so, I'll try to find a way to discriminate between new and old touch.

This made things worse. I can't see what I do in the file manager but it is hard to find a spot to open a specific pdf. In Koboreader up is left, left is up.

So I have a Kobo_trilogy device... . I tried to solve the problem, but I don't understand the language. It seems that I don't get input events in the file manager, if I use the function part.

[Ken Maltby]

I added the Disable Double Tap = True language from Github, but have not setup the development environment to compile a build. So I don't know if just changing the defaults.lua is enough to do anything. It does seem that paging through a lot of pages is working faster and smoother, without double page jumps or anything. Has anyone else tried it out?

Luck;
Ken

[giorgio130]

I'll post an updated build tomorrow. I've integrated light support in the main project; moreover I've implemented some fixes for the "strikeout font" on the Aura and made the X to close file manager bigger, should be easy to reach now.

[giorgio130]

new build available at first post. Next in line are suspend support and an easier to install package.

[giorgio130]

Originally Posted by Ken Maltby

I added the Disable Double Tap = True language from Github, but have not setup the development environment to compile a build. So I don't know if just changing the defaults.lua is enough to do anything. It does seem that paging through a lot of pages is working faster and smoother, without double page jumps or anything. Has anyone else tried it out?

Luck;
Ken

"Double Tap" is a gesture, which means it is possible to detect a double tapping as a different entity from two single interactions. It is currently being disabled when interacting with the keyboard, since if you write fast enough it is possible to tap twice on the same key. Disabling it globally should not have any effect on page turning; moreover if I'm right the option had no effect on the older build.

[Markismus]

@Giorgio130
The new build is a great!

In Filemanager the letters are clear (without invisible line) and the extra linespacing makes tapping the wrong directory or file near impossible.
I haven't found a use for the keyboard yet, except for the light setting and goto page. However, it does seem to bring the implementation of notes nearer.

Also the selection of words in a pdf-document has improved. The pop-up now only shows the dictionary with at the bottom greyed-out highlighting and notes. Those that want dictionary support, will still have to convert their books to pdf: still no support for it in the epub-part (crengine).

@cgm999 Can we still use your modifications for standby, inverse and light settings without messing up the new build?

[Ken Maltby]

I figured that disabling the "double-tap" might help when trying to rapidly flip through a bunch of pages, as there would be no confusion or delay from determining if two taps were two page turns or a double-tap. Probably just seeing an improvement because I was hoping for/expecting one.

Wow, a new port build already! Great work!

Luck;
Ken

[Ken Maltby]

I really like the look of the File Manager now and the file selection is much better with the separation of the menu items.

The X in the corner looks closer to the right edge, now and I still can't get it to do anything.

On my Aura, in the File Manager, the page # and right & left chevrons are halfway under the bezel and I can't get it to work like it does for the Contents pages.

Is the light supposed to come on when you select a file?

Love the Go to function.

Is there a way to set a default for the Margins setting?

All in all some great giant steps forward. This is looking very close to what an average reader could appreciate, and use without problem.

Luck;
Ken