[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