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

[Ken Maltby]

Well I used Sergey's new Kobo Files Monitor to make a launching tile for Koreader, and it works but instead of Koreader opening in the File Manager, as it did before, it is now opening in the "Lastfile" defined in a .lua. That wouldn't be so bad but I can't get to the File Manager from inside the file. I have an added Home Icon in the top menu, but neither of them well do anything but reboot my Aura. Any Ideas?

Luck;
Ken

[WS64]

Originally Posted by Ken Maltby

Well I used Sergey's new Kobo Files Monitor to make a launching tile for Koreader, and it works but instead of Koreader opening in the File Manager, as it did before, it is now opening in the "Lastfile" defined in a .lua. That wouldn't be so bad but I can't get to the File Manager from inside the file. I have an added Home Icon in the top menu, but neither of them well do anything but reboot my Aura. Any Ideas?

Not sure if this helps, but at my Mini this does NOT happen, it opens KoReader through File Monitor at File Manager

[Ken Maltby]

Originally Posted by WS64

Not sure if this helps, but at my Mini this does NOT happen, it opens KoReader through File Monitor at File Manager

Hmm... maybe it's something from one of the tweaks I have applied to my AuraHD . I will probably have to redo all that and see if I can isolate the problem. Could you check and see if you have a Settings_reader.lua in your koreader directory, and if so what's in it?

Luck;
Ken

[WS64]

Don't have my Mini here, can't check for the next 8 hours. But if that's the file with the one entry containing the last read book, I have that too and always wondered why since it seemed not to be used by anything.

[cgm999]

Make sure you are passing arg to reader.lua . For example if from koreader_kobo.sh
you are starting it like this
./reader.lua > /tmp/log
then is going to show the last used file.
but if you start it like this
./reader.lua /mnt/onboard >/tmp/log

then is going to start with file menu in /mnt/onboard

[cgm999]

Markismus: Is based on 266 because I did not had time to repatch 273 (or the last from github).

Did any1 tested it ? On the other kobo devices (mini/glo/etc, again fw 2.6.1) , I would like to know if inverse works , if it seems faster and if display properly (I've made einkfb.c to only update 4bits out of 8 , at least on my aura_hd that works)

[Ken Maltby]

Originally Posted by cgm999

Make sure you are passing arg to reader.lua . For example if from koreader_kobo.sh
you are starting it like this
./reader.lua > /tmp/log
then is going to show the last used file.
but if you start it like this
./reader.lua /mnt/onboard >/tmp/log

then is going to start with file menu in /mnt/onboard

Thanks, that was it, I was trying to do this in the wrong place.

Well now I have a launcher tile that gets me to Sergey's Applications (I haven't added any of my own yet) and I have a Koreader tile that launches Giorgio's Koreader port. I think we have the best of both worlds working now.

New Idea I was thinking the on_start.sh might let me unmount /mnt/sd, to isolate the SD card from Kobo's processing without having to put the files on the SD card in hidden folders. I don't know how the sequence goes but Sergey has already worked that out, in part, for what he has. If it is after the processing would start, I still have the hidden folders to fall back on.

Luck;
Ken

PS; I changed the argument to point to the folders on my external SD card with my books. Any less trying to poke the right spot the better.

[paola]

hi guys, this all sounds terribly exciting: is development at a stage when e non techie can take the plunge without the risk of bricking the device? I am travelling and though I'd like to have a go, I want to make sure I don't disable my ereader while on the road...

[cgm999]

Well this last mod should not create more risk then there is already for running custom apps/mods , basically you need have a way to start koreader_kobo.sh from /mnt/onboard/.kobo/koreader/koreader_base.sh (like with the last launcher , one for koreader and another for sergeyv apps) .

My last zip only include koreader folder , that would need to be copied to /mnt/onboard/.kobo (BACKUP your current koreader that is there already and replace with mine )

[Ken Maltby]

Originally Posted by paola

hi guys, this all sounds terribly exciting: is development at a stage when e non techie can take the plunge without the risk of bricking the device? I am travelling and though I'd like to have a go, I want to make sure I don't disable my ereader while on the road...

It is getting there for sure, the "bricking" of the device is not a great risk for the AluraHD as all the mods have been tested with that device. It should be fine for the other Mark 4 devices as well. I think the package of baseline implementation that Markismus has put together in his .rar is a great vehicle for the non-techie and even for some of us semi-techies. It should get the non-techie past most of the difficult parts and not have them dealing with things that could cause problems.

I think there remains one obstacle to a more general acceptance and that is the difficulty working the touchscreen to make selections. A greater "Line Height" might be an answer but whatever it is, an answer needs to be found, if we are to expect the average user not to give up in frustration.

Still I was wondering if all the principal contributors especially Giorgio and Sergey feel it may be time to post something in the "Kobo Reader" forum letting them know of the great strides made in the "Kobo Developer's Corner"?

Luck;
Ken

[Markismus]

I tried it and it seems indeed more responsive.

Unfortunately I get the typical invisible strikeout font. Do you also have this?

What I did was a factory reset, upgrade to 2.6.1., filemonitor and your koreader folder. The only extra thing was enabling telnet in Nickel. (rcS, inetd.conf and inittab are changed.) If you're not seeing it, what could be the reason? The telnet changes?

[cgm999]

Yea I get that also, did not looked what is the reason.
How about inv, is that working ? And whatever else was added etc

[Ken Maltby]

Originally Posted by Markismus

I tried it and it seems indeed more responsive.

Unfortunately I get the typical invisible strikeout font. Do you also have this?

What I did was a factory reset, upgrade to 2.6.1., filemonitor and your koreader folder. The only extra thing was enabling telnet in Nickel. (rcS, inetd.conf and inittab are changed.) If you're not seeing it, what could be the reason? The telnet changes?

I thought it came and went with the DPI setting, the koreader folder may be using the 265 DPI from Giorgio's last port post.

Luck;
Ken

[Markismus]

Yes, it does, but because I didn't hear anybody else responding to it, I was wondering whether it was just my Aura. If dpi=235 you can set cfont to 24 or 25 without strike-out. That what I did in the last rar-file.

[Ken Maltby]

Well, the settings in your .rar are working fine in my AuraHD as well. The addition of the fmon would not care about koreader and not be making any changes to it. The only part of your .rar that I needed to install was your #5 hacks as I am not using telnet and the rest is working fine.

Luck;
Ken