Thread: Kobo Start Menu 08
View Single Post
Old 12-05-2017, 05:58 PM   #922
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by tshering View Post
The function of fmon is that whenever some application opens one of the image files in kbmenupngs, it starts a script that is associated with this image file. The problem is that under certain conditions, nickel opens or tries to open one of these files without being told to do so by the user. It seems to happen after some FW updates, that nickel has to open these image files in order to create new thumbnails or something like that. So the solution, is to start nickel without fmon, and try to let nickel do all the work it needs to do with those image files. You look at these image files in the library, inside of the collection, open them so that they get displayed on the home screen, also the collection if they are in one. You start nickel several times without fmon. After that nickel will work again also when started with fmon. I have to add that this seems not to work for some people (I remember one user). To simplify things you could also delete those image files in kbmenupngs that you will likely never use. I for one could for instance do without simulate_usb_connection.png, switchtokoreader.png, toggle_nightmode.
If the issue is when nickel generates the cover images, then we should be able to generate them. The KoboTouch driver in calibre already has code to create the cover images when sending books. The driver doesn't support sending PNGs to the device. I'm not sure if that can be changed as I don't know what support the rest of calibre has for it. But, the code to generate the cover images and put them in the right place on the device is in the driver. Writing something based on that shouldn't be to hard.
davidfor is offline   Reply With Quote