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

[NiLuJe]

@Ken Maltby: Those were stored in a different place (alongside koreader's files, on a partition mounted rw).

[Ken Maltby]

Originally Posted by NiLuJe

@Ken Maltby: Those were stored in a different place (alongside koreader's files, on a partition mounted rw).

What would we lose if we continued to do that?

Luck;
Ken

[NiLuJe]

@Ken Maltby: With chrox's fix in, we are, when it's not possible to do otherwise, so, nothing .

(The sidecar folder is a Kindle idiom, which is why that might sound foreign to you ).

EDIT: In fact, right now, even when we can use a sidecar folder, the settings are stored in both places (the sidecar folder alongside the book, and KOReader's history folder).

[Markismus]

@Ken You can edit koreader.sh and remount the sd-card as read&write. Google sh mount and give it a try in the shell terminal via USBNetor in Start Menu.

mount -o remount, rw your_device_name

I think that you can get a list of your device names by typing mount at the shell prompt.

@jpalacios If you export your highlights to Evernote, then Evernote generates a nice listing of all you highlights.

[tshering]

How about

mount -o remount,rw /mnt/sd

?

Nickel remounts the sd as rw/ro according to situation. Would there be any harm if sd would stay mounted as rw all the time?

[hawhill]

I would just wait for the fixed version. Nickel probably does it the way it does so people can pop out their SD cards without creating a havoc on the filesystem.

[tshering]

Originally Posted by hawhill

Nickel probably does it the way it does so people can pop out their SD cards without creating a havoc on the filesystem.

Right, I somehow forgot that one has to reckon with people!

[pazos]

@hawhill: We could mount sd card in rw mode before start koreader and back to ro mode after it?

With current fix I dunno if copy/paste gives us an error (writting in sd card)

[Ken Maltby]

Wasn't there an issue awhile back where the external uSD wasn't recognized at first and that one fix was to eject the card and reinsert it? Then we had a way to init the kernel drivers, and that fixed it (or something like that)? [The memory is the first to go.]
Was there a read/write switch for that?

Luck;
Ken

[tshering]

Originally Posted by Ken Maltby

Wasn't there an issue awhile back where the external uSD wasn't recognized at first and that one fix was to eject the card and reinsert it? Then we had a way to init the kernel drivers, and that fixed it (or something like that)? [The memory is the first to go.]
Was there a read/write switch for that?

Luck;
Ken

We had this problem with the Kobo Start Menu. Maybe this is what you are thinking of. The solution was to call "udevadm trigger" at an earlier point than I did at first.

[Ken Maltby]

Originally Posted by tshering

We had this problem with the Kobo Start Menu. Maybe this is what you are thinking of. The solution was to call "udevadm trigger" at an earlier point than I did at first.

Right, that was it. The latest build 366, is working, so it is fixed, as far as I can tell. Now I can get back to rereading L.E.Modesitt's "Saga of Recluce" before I buy the last two. One came out, not too long ago and one is due soon.

[hawhill]

Oh, using your device for reading. Sometimes I forget that one can do this, too :-)

[NiLuJe]

One thing to note with the latest nightlies: the default CRengine settings have been tweaked to use sane font-related settings (rendering, and default families. Plus defaulting to the US hyphenation dictionary). That will only apply to new installs though (unless you delete your data/cr3.ini file).

FreeType has also been updated, and that means the possibility to use the new Adobe CFF renderer, which is pretty damn neat. If you're using CFF fonts, I'd recommend trying to switch to bytecode hinting (set font.hinting.mode to 1 in data/cr3.ini, which is *NOT* the new default, because so many TTF fonts have crappy bytecode instructions).

[the.Mtn.Man]

I have a few questions that might have been answered earlier in the thread but I don't feel inclined to read 88 pages to find them (for the record, I have a Kobo Aura):

How "safe" is this? Can it brick your device? Render it unbootable/unrecoverable?
Can you easily get back to the default Kobo interface without having to reset the device?
Is this software easy to remove?
What happens when Kobo releases an update?
Any "gotchas" that users should be aware of?

Thanks.

[HaoZeke]

I was wondering if there will ever be any implementation to read the metadata? (like that shown in calibre or nickel) I have a huge number of books and don't always remember exactly how they are.
Also, any particular reason/fix why the files off the external sd card can't be managed via the file manager? (I'm guess something to do with the mount options, but is there a reason for it to be done that way? o.O )