View Single Post
Old 08-09-2013, 06:30 AM   #393
_pietro
Connoisseur
_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse_pietro can illuminate an eclipse
 
Posts: 61
Karma: 8174
Join Date: Mar 2012
Device: none
Quote:
Originally Posted by giorgio130 View Post
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

Last edited by _pietro; 08-09-2013 at 06:38 AM.
_pietro is offline   Reply With Quote