Quote:
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.