KFMon icon

[Coogan]

Hi,

after installing the KOReader on my Clara the My Books folder became a joint KFMon Log/My Books folder. First it looks ridiculous and second inside the folder are 15 pages of all files from the KFMon or KOReader directory beside my books. How do i fix this?

[pazos]

Originally Posted by Coogan

Hi,

after installing the KOReader on my Clara the My Books folder became a joint KFMon Log/My Books folder. First it looks ridiculous and second inside the folder are 15 pages of all files from the KFMon or KOReader directory beside my books.

I would suggest RTFM but sounds a bit rude .

Is a known issue on kobos (not our fault). It is pinned on github. See https://github.com/koreader/koreader/issues/5430

Using One-click install packages should handle it automagically. See https://www.mobileread.com/forums/sh...d.php?t=314220

Even more important, it is highlighted as important notes under official installation guide for your device. See https://github.com/koreader/koreader...n-Kobo-devices

Originally Posted by Coogan

How do i fix this?

Apply the change mentioned in the wiki. Nickel will remove everything. Install it again. Next time RTFM

BTW, you can remove the kfmon-log png if you don't plan to use it. It looks nice here (but not as cool as the smiley RJunior45: https://github.com/pazos/cervantes-s...ges/usbnet.png on cervantes )

[Coogan]

Originally Posted by pazos

Apply the change mentioned in the wiki. Nickel will remove everything. Install it again.

Sorry but i still don't understand this. This is definitely in my ereader.conf:

[FeatureSettings]
ExcludeSyncFolders=\\.(?!kobo|adobe).*?

What's with this file on github https://github.com/NiLuJe/kfmon/blob...ll.sh#L85-L99? Do i have to run this?

Which installation method should i use?

[pazos]

See this comment: https://github.com/koreader/koreader...ment-535730828

i.e: with your actual "ereader.conf" connect to USB, press the button to mount (remove kfmon-log.png here if you want), safe extract, wait while nickel is prunning the files. Now connect again and unzip KOReader again.

[Coogan]

No change. Here are my steps:

emptied everything in adds and icons as well as kfmon und koreader pngs, extract koreader into root, eject, after reboot connect again and extract again.

[pazos]

Originally Posted by Coogan

No change. Here are my steps:

emptied everything in adds and icons as well as kfmon und koreader pngs, extract koreader into root, eject, after reboot connect again and extract again.

It is cool that you're trying to install it manually, but please RTFM. I promise it won't take more than a minute https://github.com/koreader/koreader...based-on-kfmon

[Coogan]

I've tried one-click, semi-automated, KFMon and KSM.

[pazos]

Originally Posted by Coogan

I've tried one-click, semi-automated, KFMon and KSM.

Wow, you ran out of methods. It is better than you choose one and try to understand what it does.

KOReader is a program. You just need to download and uncompress it. But, in order to run on your device, you need a launcher to launch it. That's kfmon. A launcher based on pngs.

KFmon expects KOReader files in one folder and KOReader icon/png in other folder. The specific folders are in the wiki. If you uncompress KOReader or the icon on a different folder funny things could happen:

- You'll see a lot of icons if you uncompress KOReader on a non hidden directory (ie: a directory that doesn't start with a dot ".")
- You won't see nothing weird on Nickel but opening the KOReader icon won't do a thing.

Sorry. I can't help you. Use common sense, the wiki and some free time or let it be and stick with Nickel. It is good software and it's ready to use.

[NiLuJe]

Also, KSM essentially takes over your device, so if you actually did install that one correctly, it'll have wrecked anything else you might have done halfway right before.

I'd say do a full factory reset (look up the manual "button combo on startup" method on the Kobo help page; or the more recent "devmodeon" approach), and stick to the OCP install script.

[Coogan]

Thanks everything works fine now.