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

[trekk]

Originally Posted by cgm999

Reattached zip that is based on koreader-v2013.03-266-g4f36cd2.zip

Fixed to include the mod for epubs. Also the list of debug commands is now in
defaults.lua as DEBUG_CMDS

After copying the new files to enable the mod for epubs, the menu shows up, but the frontlight option does not work anymore. Neither from the menu, nor from the frontlight button of the reader.

[cgm999]

Ok please try now. I think the frontlight button should work now also (to switch off/on etc)

[trekk]

Originally Posted by cgm999

Ok please try now. I think the frontlight button should work now also (to switch off/on etc)

Works like a charm now! Both, menu and frontlight button. Thanks a lot!

[Mexx]

Is there anybody who got the koreader working on a touch(905B) with FW2.6.1 and starting it with the Launcher? If so, would you please be so kind and tell me how?

I tried the mod from muness in comment#84, but then nothing happens, when I change to the launcher. Before applying the patch, the launcher worked...

thank you for any help!

[giorgio130]

Originally Posted by Mexx

Is there anybody who got the koreader working on a touch(905B) with FW2.6.1 and starting it with the Launcher? If so, would you please be so kind and tell me how?

I tried the mod from muness in comment#84, but then nothing happens, when I change to the launcher. Before applying the patch, the launcher worked...

thank you for any help!

You can leave out the part regarding usbnet, maybe it is not compatible with touch. Edit /mnt/onboard/.kobo/KoboLauncher/KoboLauncher.sh and put in it:

#!/bin/sh
/mnt/onboard/.kobo/koreader/koreader_kobo.sh /mnt/onboard

However there's always the issue of windows vs unix line endings, you should use a text editor that can put the proper character at the end of each line.

[Ken Maltby]

Originally Posted by giorgio130

You can leave out the part regarding usbnet, maybe it is not compatible with touch. Edit /mnt/onboard/.kobo/KoboLauncher/KoboLauncher.sh and put in it:

#!/bin/sh
/mnt/onboard/.kobo/koreader/koreader_kobo.sh /mnt/onboard

However there's always the issue of windows vs unix line endings, you should use a text editor that can put the proper character at the end of each line.

A Hex Editor should show both the Hex and the Ascii , just change the "0D" to "0A". It should be ok to have two "0A"s instead of "0D 0A".

Just open the .sh file in a Hex editor and make the changes, there shouldn't be that many.

Giorgio;

When you guys tell us to put some new code into an existing .sh Bash Script you often include the #!/bin/sh but I thought only the first one counts? There is one already at the beginning of the file. Also, are we supposed to remove or comment out the old code. Maybe you guys mean that with the bash at the beginning of your additions that it is to be inserted at the beginning and the rest of the .sh left as it is?

Dumb questions I know.

Luck;
Ken

[cgm999]

Re debug_commands: what if we change the code to add to bottom meny ONLY if is defined in defaults.lua (DEBUG_CMD) , that way whoever wants to have them just need the line

[giorgio130]

Originally Posted by Ken Maltby

A Hex Editor should show both the Hex and the Ascii , just change the "0D" to "0A". It should be ok to have two "0A"s instead of "0D 0A".

Just open the .sh file in a Hex editor and make the changes, there shouldn't be that many.

Giorgio;

When you guys tell us to put some new code into an existing .sh Bash Script you often include the #!/bin/sh but I thought only the first one counts? There is one already at the beginning of the file. Also, are we supposed to remove or comment out the old code. Maybe you guys mean that with the bash at the beginning of your additions that it is to be inserted at the beginning and the rest of the .sh left as it is?

Dumb questions I know.

Luck;
Ken

I often assume a little knowledge of shell scripting, I am sorry. Yes, only a "#!/bin/sh" is needed at the beginning of the file; as the remaining code, you can delete it, comment it out or leave it as it is, since the script is executed line by line and after koreader exits, the device reboots so it has no chance to execute the remaining lines. Nice trick for fixing line endings!

[Ken Maltby]

I might be good for a very, very little. I did read the addition you mentioned as negating the rest of the script, if it was at the beginning.

I see that you updated KoReader a few hours ago. Not rushing you and maybe a wait is prudent in any case, but I was wondering if there is a "rule of thumb" for how long it takes till a new version of your port is released.

Luck;
Ken

[Markismus]

Originally Posted by cgm999

Thats fine. I am curios if any1 else uses debug commands ?

I am trying to, but I am running into some trouble.

Reboot works fine.

Wireless on/off doesn't enable telnet for me. Normally, I have to start the browser to get an IP address assigned, after which I can telnet into the Aura. How can I do this within KOreader?

Inv doesn't do anything. I assume it is screen inversion mod? So will I have to install that separately, or is it in your koreader-cgm?

[giorgio130]

Originally Posted by Ken Maltby

I might be good for a very, very little. I did read the addition you mentioned as negating the rest of the script, if it was at the beginning.

I see that you updated KoReader a few hours ago. Not rushing you and maybe a wait is prudent in any case, but I was wondering if there is a "rule of thumb" for how long it takes till a new version of your port is released.

Luck;
Ken

Do you mean how often I update the attachment at the first post? I'd go to change it every time there's a significant change... As an example, if I get to clean up enough suspend support or light control for official inclusion.

Originally Posted by Ken Maltby

A Hex Editor should show both the Hex and the Ascii , just change the "0D" to "0A". It should be ok to have two "0A"s instead of "0D 0A".

It's probably easier to install a text editor that supports Unix line endings. There are a lot of options out there. Notepad++ definitely works under Windows and TextWrangler will convert line endings under OS X. I'm assuming that all of the text editors will work under the various forms of Unix.

[cgm999]

Markismus:

For wireless off / on , I assume you have scripts in the right location (what koreader-debug_cmd.sh executes)
for screeninversion you need to execute koreader with LD_PRELOAD and the screenInv.so file

[root@KOBO_AURAHD koreader]# tail koreader_kobo.sh


while :; do
LD_PRELOAD=/root/screenInv.so ./reader.lua /mnt/onboard
sleep 1
done

[Ken Maltby]

Originally Posted by BWinmill

It's probably easier to install a text editor that supports Unix line endings. There are a lot of options out there. Notepad++ definitely works under Windows and TextWrangler will convert line endings under OS X. I'm assuming that all of the text editors will work under the various forms of Unix.

Perhaps for some, but a lot of us have found it handy to have HexEdit, or something similar, around for the occasional look into such things. It might be an old gamer's thing. Still I would think it not an uncommon tool to find in a "Developer's Corner".

Luck;
Ken

[cgm999]

if you have ssh/telnet enabled on device here is one quick line to convert from dos to unix text file(basically removing \r == 0d ):

kobo_shell# sed -i -e 's/\r//g' path_to_file