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

[WS64]

yes..

[Markismus]

Think it could be a difference between Aura en Mini?
I upgraded, saw the missing folders and found the line in rcS which would have removed it.

Looking at the rcS-file I wonder whether it would be the difference between PLATFORM=freescale versus ntx508. But the "rm"-lines are in the main body of the script, so I don't see why it would matter:

line 43: mkfifo /tmp/nickel-hardware-status
line 44: rm -rf /etc/udev/rules.d/70-persistent-net.rules
line 45: rm -rf /mnt/onboard/.kobo
line 46: rm -rf /mnt/onboard/*

Odd!

[tshering]

Originally Posted by Markismus

kobo
line 46: rm -rf /mnt/onboard/*
Odd!

Wouldn't this delete all your books on the reader, if it were to refer to the user partition?

[PeterT]

No.... Look at the script and you will see that the rm's are being done prior to the mounting of the partition where user data is stored.

I believe those deletes were added in to solve an issue where the mount was failing due to the /mnt/onboard being a non empty directory.

[tshering]

Originally Posted by PeterT

No.... Look at the script and you will see that the rm's are being done prior to the mounting of the partition where user data is stored.

This is exactly what I thought to convey by saying

if it were to refer to the user partition

[Ken Maltby]

Originally Posted by Markismus

Think it could be a difference between Aura en Mini?
I upgraded, saw the missing folders and found the line in rcS which would have removed it.

Looking at the rcS-file I wonder whether it would be the difference between PLATFORM=freescale versus ntx508. But the "rm"-lines are in the main body of the script, so I don't see why it would matter:

line 43: mkfifo /tmp/nickel-hardware-status
line 44: rm -rf /etc/udev/rules.d/70-persistent-net.rules
line 45: rm -rf /mnt/onboard/.kobo
line 46: rm -rf /mnt/onboard/*

Odd!

I guess the bottom line might be, is there anything missing after the update to 281 and then the application of the 1 Step Hack? Is everything restored by the 1 Step Hack?

Luck;
Ken

I do wonder what the pipe may have collected? Probably just being held in /tmp/ until being reapplied at the end of the update. But Kobo's database makes me paranoid sometimes.

[PeterT]

Originally Posted by tshering

This is exactly what I thought to convey by saying

I missed the subtlety of that

[Markismus]

Originally Posted by PeterT

No.... Look at the script and you will see that the rm's are being done prior to the mounting of the partition where user data is stored.

I believe those deletes were added in to solve an issue where the mount was failing due to the /mnt/onboard being a non empty directory.

Yes, I can agree with that:
Line 6: mount -o remount,noatime,nodiratime /dev/mmcblk0p1 /
Line 63: mount -t vfat -o noatime,nodiratime,shortname=mixed,utf8 /dev/mmcblk0p3 /mnt/onboard

What I don't get is what would then be the cause of a completely new .kobo directory after upgrading to 2.8.1.... But if no one else experienced it, who cares.

@Ken Yes, it's still do upgrade and do 1-Step-Hack to restore all files. If your M-toggle tweaks are disabled and if those folders are not deleted, than even your-toggle tweaks are untouched.

[tshering]

Originally Posted by Markismus

Yes, I can agree with that:
Line 6: mount -o remount,noatime,nodiratime /dev/mmcblk0p1 /
Line 63: mount -t vfat -o noatime,nodiratime,shortname=mixed,utf8 /dev/mmcblk0p3 /mnt/onboard

What I don't get is what would then be the cause of a completely new .kobo directory after upgrading to 2.8.1.... But if no one else experienced it, who cares.

I think, there is no "new .kobo directory". As I understand it (and I am not sure whether I understand it correctly), /mnt/onboard refers from its creation in line 26 or so up to line 62 to a directory of the system partition, and this directory gets cleared of any content in lines 45 and 46. But nothing happens at that point with reference to the user partition. Only after line 63, /mnt/onboard refers to the mounted file system. So there seems to be nothing any user could experience with regard to "her" .kobo directory.

[someGuyHere]

Hi all, I was a bit disappointed about my choice of the Kobo Touch because of the bad pdf experience. Then I found all the promising modifications (the little reset button on the back side became my best friend) on the net that led me to your project here.

I was fiddling around with the various ports and versions of koread, but did not get it to work properly yet.

I'm running the Kobo Touch with firmware version 2.6.1.

My problem is that klicking an icon on the screen triggers button presses at the wrong position. I must have done something wrong, because no one ever posted such a behavior. I just can not figure out what it is.

I was trying the "1 click" solution and did the steps: Enabling Telnet, pbchess, koreader, Using KoboLauncher.

This leads to a working version where I get the top and the bottom bar in the reader, but when I click on the icon at the bottom left, it recognizes a button click on the icon at the bottom right. Second botton from the bottom left recognizes a button click on the second icon from the right etc. . The top bar works wrong as well.

I did the modified step 5 wrong in my first try, I copied the whole directory without deleting the double entries. That lead to a missing bar at the bottom (probably because the resolution did not fit and the bar could not be activated or printed onto the screen). The interesting thing was the top bar did work, but the icons were shown on the small upper side of the screen (correct for portrait mode) and I had to activate them on the long right side of the screen where no icons where shown (which is correct).

When I did the deletion I had the same issues as before, maybe I deleted the wrong wones or have to do a factory reset and start over... .

Do you have any ideas on this issue?
Best regards,
Thomas

[Ken Maltby]

The "1 Step Hack" is at https://www.mobileread.com/forums/sho...&postcount=303 and has no step 5. There is no need to delete any duplicates as they have the file names changed so that they aren't used. They are still there in case you should want to try just restoring individual files. This version of the hack might be your best bet.

You should note that most of the tweaks are tailored to the AuraHD, so you might want to consider connecting to your PC and adjusting the settings pointed to at https://www.mobileread.com/forums/sho...&postcount=331 to reflect those that you find work best with your Touch. ( The current Koreader port does find and apply some settings based on the model detected, so your Touch might not be too far off just as it is.)

Luck;
Ken

[TechniSol]

Oh brothers, I am so waiting for the just unzip it and drop it in .Kobo version! I've been adventurous enough lately. Keep up the good work.

[someGuyHere]

Thank you Ken for you link, at least I now know I'm working on the correct version :-)

Originally Posted by Ken Maltby

The "1 Step Hack" is at https://www.mobileread.com/forums/sho...&postcount=303 and has no step 5.

Yes, this was the first version i tried, after that I used a different version with five folders. The post with the rar contained a note for users of the Touch.

Anyway this version has the problem I discribed before. I'll go on trying to find the difference to the version that does not have the landscape touch with portrait visible problem.

Originally Posted by Ken Maltby

You should note that most of the tweaks are tailored to the AuraHD, so you might want to consider connecting to your PC and adjusting the settings pointed to at https://www.mobileread.com/forums/sho...&postcount=331 to reflect those that you find work best with your Touch. ( The current Koreader port does find and apply some settings based on the model detected, so your Touch might not be too far off just as it is.)

To my understanding there isn't too much done in those lines, aren't the changes all done to the file manager? My problem lies in the KoReader. I guess my problem must be with one of the -sh or lua scripts... .

I still have two hours left before I have to get some work done, so I'll try some diffs to get a feeling of the differences to the original setup.

[someGuyHere]

Now I'm pretty sure of the following Bug, can someone confirm it?

I set my Kobo Touch back to factory defaults and did the one click setup as written in my previous post, so now I don't have any junk from my previous tries.

In the KoReader the horizontal places I touch are inverse to the places the touch is recognized. If I touch a position on the left, the touch is recognized on the right.

This is the same for the version installed by the one klick, but this is even worse, because viewing area and typing area do not match (I have to touch on the right side to get a reaction on the top line).

Is that a setting problem or a code problem?

[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