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

[giorgio130]

I have some hints of what is happening. I'm sorry this has caused so much trouble!
The good thing is that a factory reset should solve for every unit that got stuck.

I've got some hints on what is happening. I think that Files Manager has some bug that means it is triggered also when the device is processing koreader.png for the first time, not only when you click on it. I'd say that the Glo and Aura, with their faster cpu, are able to go through the processing before koreader starts, and so it never happens again; for the mini though nickel gets killed before it can add to the database koreader.png and so, at every reboot the thing get repeated. In the worst case the database gets corrupted and the device looks empty to nickel.

This is just speculation though - I'll try some workaround for that.
I'll add a notice on the first page.

[Ken Maltby]

Originally Posted by giorgio130

I have some hints of what is happening. I'm sorry this has caused so much trouble!
The good thing is that a factory reset should solve for every unit that got stuck.

I've got some hints on what is happening. I think that Files Manager has some bug that means it is triggered also when the device is processing koreader.png for the first time, not only when you click on it. I'd say that the Glo and Aura, with their faster cpu, are able to go through the processing before koreader starts, and so it never happens again; for the mini though nickel gets killed before it can add to the database koreader.png and so, at every reboot the thing get repeated. In the worst case the database gets corrupted and the device looks empty to nickel.

This is just speculation though - I'll try some workaround for that.
I'll add a notice on the first page.

Sounds like that might be the issue, I seem to remember that Sergey mentioned that you had to connect back to your PC after adding the .png files so that they were properly recognized by kobo. There might be enough difference in your .png files that they are being treated as new and needing processing by Nickel, even for those with existing .png files of the same name.

In the original install of fmon you first added the .png files then safely exited from your PC and your device would perform the processing. After that you connected back to your PC to install the rest of fmon.

Luck;
Ken

https://www.mobileread.com/forums/sho...=218283&page=2
From #20 on.

[_pietro]

Originally Posted by giorgio130

I have some hints of what is happening. I'm sorry this has caused so much trouble!
The good thing is that a factory reset should solve for every unit that got stuck.

I've got some hints on what is happening. I think that Files Manager has some bug that means it is triggered also when the device is processing koreader.png for the first time, not only when you click on it. I'd say that the Glo and Aura, with their faster cpu, are able to go through the processing before koreader starts, and so it never happens again; for the mini though nickel gets killed before it can add to the database koreader.png and so, at every reboot the thing get repeated. In the worst case the database gets corrupted and the device looks empty to nickel.

This is just speculation though - I'll try some workaround for that.
I'll add a notice on the first page.

workaround:

- copy koreader.png image
- disconnect, let process
- install fmon
- disconnet
- remove koreader.png from KooReader.tgz, copy on flash the koreader folder and the .tgz
- disconnect

now it works, but... when i click on koreader image the fmon starts and the kobo frezees, have to use the reset button

[Ken Maltby]

Originally Posted by _pietro

workaround:

now it works, but... when i click on koreader image the fmon starts and the kobo frezees, have to use the reset button

How do you mean "now it works"? How do you mean "when i click on koreader image the fmon starts" what are you seeing that tells you that fmon starts? Do you still see this after powering off and restarting?

Luck;
Ken

[ZipMaker]

Hello guys, sorry for my english
I tried to install koreader but it failed.

1) I installed Kobo files monitor (copied koboroot.gz into .kobo directory)
2) I started device and updated.
3) And then i copied "koreader folder" and koboroot.gz into .kobo directory
4) i started device and updated.
5) But there is no KoReader icon, i can't see any change
6) So, i downloaded latest nightly "koreader-v2013.03-398-gd99c71a.zip" from here i copied again and i started the device but my kobo glo bricked.

I made a hard reset and its ok now. But why can't i install koREADER?

[Ken Maltby]

At the moment, there is a problem with the 398 version of Giorgio's port and he has removed it from the first post of this thread.

After your step 1) you should have safely disconnected your Kobo from your PC, and then you should have seen the Kobo device display that it was updating. Once that has finished you needed to reconnect the Kobo device to your PC, then safely disconnect from your PC. (These steps insure that the .png image files are properly indexed by Kobo's Nickel program.)

Installing Koreader would be next. First you need to know which version of the Kobo Firmware you have installed. Then you can select the proper version of the port to install. If you have version 2.6.1 or later, you might want to wait until Giorgio posts his fixed version. Or you could look back in this thread and find Markismus's latest "1 Step Hack" and try that approach. It won't have Giorgio's latest improvements but includes a number of hacks/settings from several posters that are quite nice.

Luck;
Ken

https://www.mobileread.com/forums/sho...&postcount=303

[giorgio130]

At least on the Glo, 2.8.1 introduces a bug in the touch screen driver. I'd say this implies it has been modified some how, but I can't find an updated version in the kobo github account. I've opened an issue there, but lately they're just being ignored.

edit: gtalusan from kobo has been somewhat collaborative. The bug is not in the kernel, and he says we should just scrap touchscreen values when pressure = 0. The problem is, I've no idea how to do that. @hawhill do you have any advice on this?

[_pietro]

then...i tried installing kobolaucher and adding the link to koreader_kobo.sh... filemanager starts, clicks are responsible but all it appears are gray lines...after few click the screen goes gray and the kobo frezees...i think it doesn't work on touch

[Ken Maltby]

Originally Posted by _pietro

then...i tried installing kobolaucher and adding the link to koreader_kobo.sh... filemanager starts, clicks are responsible but all it appears are gray lines...after few click the screen goes gray and the kobo frezees...i think it doesn't work on touch

That is a known issue and correcting it is part of what led Sergey to bring us his "fmon" program. Which is now also a part of his current Launcher/PBchess program. You are not a very lucky guy.

Have you tried the "1 Step Hack" I mentioned above?

Koreader has been reported as working on Kobo Touch, at least the Mark 4 versions, (I am not sure about the version that has no internal uSD card).

What firmware do you have now?

Luck;
Ken

[Markismus]

Originally Posted by ZipMaker

I tried to install koreader but it failed.
...
6) So, i downloaded latest nightly "koreader-v2013.03-398-gd99c71a.zip" from here i copied again and i started the device but my kobo glo bricked.

I made a hard reset and its ok now. But why can't i install koREADER?

I tried the two newest nightly builds from the koreader download and both crashed. After starting koreader my Kobo Aura rebooted.
When I compared Giorgio's build and the nightly builds both named koreader-v2013.03-266-g4f36cd2.zip, I found that the compiled programs such as koreader-base, sdcv and extr have different sizes. I assume that the nightly builds are not meant for the Kobo architecture. (However, in the koreader for kindle thread I found that others had trouble with the newest builds also!)

Try the builds of Giorgio. Version 396 works lovely for the Aura, but for the mini and Touch version 273 or 266 are more stable.

[paola]

Originally Posted by Markismus

but for the mini and Touch version 273 is more stable.

is this the one in your "1 step hack"?

[Markismus]

Originally Posted by paola

is this the one in your "1 step hack"?

Reading my explanation for 1 step hack, I used cgm999 koreader build which is based on 266. 5 step hack is based on Giorgio's koreader build, version 273.

There is a small file called "git-rev" in you koreader directory, which contents clearly states on which github version your installation is based.

cgm999's koreader (based on 266) has sleep, frontlight and debug-options and was clearly better for the Kobo than the newer vanilla version of github (273). However, for the Kobo Aura the newer build from github (396) by Giorgio is a big improvement.

So the problem is that while there is a lot of improvement going on, it is not happening on 1 track. Trying to figure out what cgm999's changes were to the 266 version and implementing them in 396 version seems like a lot of work. It makes me appreciate Giorgio's complaint that all changes should be put into github.

[hawhill]

Originally Posted by giorgio130

The bug is not in the kernel, and he says we should just scrap touchscreen values when pressure = 0. The problem is, I've no idea how to do that. @hawhill do you have any advice on this?

Not yet. Can you open an issue in the tracker? I will probably have time to look at this in a few hours.

[_pietro]

Originally Posted by Ken Maltby

That is a known issue and correcting it is part of what led Sergey to bring us his "fmon" program. Which is now also a part of his current Launcher/PBchess program. You are not a very lucky guy.

Have you tried the "1 Step Hack" I mentioned above?

Koreader has been reported as working on Kobo Touch, at least the Mark 4 versions, (I am not sure about the version that has no internal uSD card).

What firmware do you have now?

Luck;
Ken

i didn't know the 1 step hack...give it a try

[_pietro]

Originally Posted by _pietro

i didn't know the 1 step hack...give it a try

no success, i can't go ahead the fmon... if anyone was able to install koreader on a kobo touch please share, i only need the better pdf experience