Kobo Bug thread

[teija]

Originally Posted by davidfor

None of the sorts on the device are based on the file timestamp. The "Date added" is when the import was done. The "Recent" uses the last time the book was read, or, if that hasn't been set, then the same timestamp as the date added.

What that means is if you put a new SD card in the device, all the books in it will be at the top of the Recent sort. If you pull the card out, and put it back in, this should give the same sort order. If you pull it out and add a few books, when you put it in, the new books should be at the top of the Recent sort.

The device does track the card. If you take the card out and put another in, it will remove details of the books on the old card and import the books from the new card. This will put them at the top of the Recent list.

Thanks for the info!

But does this mean that a card that has ALWAYS been in the device will show up first on the list now? Because that is what happened with mine... I NEVER took it out and it was never an issue before the latest update. I first took it out when I was trying to do some fault-finding the other day (in fact, I had honestly forgotten it was there).

[davidfor]

Originally Posted by teija

But does this mean that a card that has ALWAYS been in the device will show up first on the list now? Because that is what happened with mine... I NEVER took it out and it was never an issue before the latest update. I first took it out when I was trying to do some fault-finding the other day (in fact, I had honestly forgotten it was there).

It shouldn't. Pulling the card out and putting it back in shouldn't trigger a reimport of the books, or change the Recent or Date Added sort orders. If something else is wrong, such as a corrupted database, it could happen.

[teija]

Originally Posted by davidfor

It shouldn't. Pulling the card out and putting it back in shouldn't trigger a reimport of the books, or change the Recent or Date Added sort orders. If something else is wrong, such as a corrupted database, it could happen.

So it sounds like the upgrade to the latest firmware caused something to go wrong... Well for now I have solved the problem by removing the SD card.

[droopy]

I like holding my Kobo Forma in my right hand.
On my Kobo Forma, I have inverted "Next" and "Previous" page-control hardware buttons.
These two things combined seem to cause my Forma, after waking up or powering on, to momentarily have the text or the PIN page to be upside down, before correcting itself to be right-side up. I don't want to waste time every time I pick up my Forma waiting for it to have the right orientation. That wastes 5 seconds every time.
I noticed that when my Next and Previous buttons are not inverted, I don't have this temporary hiccup. But, I will not choose "non-inverted" just to avoid this hiccup. I would like to invert my page-control buttons AND not have this glitch.

[JSWolf]

Originally Posted by droopy

I like holding my Kobo Forma in my right hand.
On my Kobo Forma, I have inverted "Next" and "Previous" page-control hardware buttons.
These two things combined seem to cause my Forma, after waking up or powering on, to momentarily have the text or the PIN page to be upside down, before correcting itself to be right-side up. I don't want to waste time every time I pick up my Forma waiting for it to have the right orientation. That wastes 5 seconds every time.
I noticed that when my Next and Previous buttons are not inverted, I don't have this temporary hiccup. But, I will not choose "non-inverted" just to avoid this hiccup. I would like to invert my page-control buttons AND not have this glitch.

This is not a bug when a patch causes something not to work correctly. This is a patch issue and should be reported in the patch thread.

[MGlitch]

Originally Posted by JSWolf

This is not a bug when a patch causes something not to work correctly. This is a patch issue and should be reported in the patch thread.

This isn’t a patch Jon. This is how the Forma firmware behaves in its native state. They word switching which way either button takes you as inverting.

[PenguinCEO]

It seems a bug. It is the object of that thread.

[DNSB]

Originally Posted by PenguinCEO

It seems a bug. It is the object of that thread.

Since Kobo has never had a monospaced font accessible on their ereaders, it's hard to see it as a bug. You can add a monospaced font either by adding it to fonts folder in the root of the Kobo's exposed storage or embed a monospaced font in the ebook. There is a patch that will point librmsdk to using your sideloaded monospaced fonts without having to play games with @font-face statements in the ebook's CSS.

As for calibre, try to remember that calibre on your computer has access to the installed fonts on your computer while a Kobo ereader has the fonts that are native to the firmware or installed in the fonts directory.

[PenguinCEO]

Originally Posted by DNSB

it's hard to see it as a bug.

I've payed my device with all good money and the minimum expectation from it is that it renders correctly a correctly formatted epub/kepub. As I can understand Kobo A1 it does not, and in my country this is a sufficient reason to request the return of the price as far as rendering mono-spaced text cannot be considered an esoteric quality (and in the specifications of the kepub format there is no "do not use mono-spaced text" clause).

I can think to patch up the firmware to obtain additional and uncommon functions, not to read a normal epub formatted with basic css.

[meeera]

Originally Posted by PenguinCEO

I've payed my device with all good money and the minimum expectation from it is that it renders correctly a correctly formatted epub/kepub. As I can understand Kobo A1 it does not, and in my country this is a sufficient reason to request the return of the price as far as rendering mono-spaced text cannot be considered an esoteric quality (and in the specifications of the kepub format there is no "do not use mono-spaced text" clause).

I can think to patch up the firmware to obtain additional and uncommon functions, not to read a normal epub formatted with basic css.

Neither sideloading or embedding fonts are firmware patches. Throw a monospaced font on there and get on with your life. It takes seconds and costs nothing. I would say that wanting a monospace font does count as an "uncommon" thing, but at least there's an easy workaround for you.

(Or return your device; that seems to me like a whole lot more hassle for no gain.)

[DNSB]

Originally Posted by PenguinCEO

I've payed my device with all good money and the minimum expectation from it is that it renders correctly a correctly formatted epub/kepub. As I can understand Kobo A1 it does not, and in my country this is a sufficient reason to request the return of the price as far as rendering mono-spaced text cannot be considered an esoteric quality (and in the specifications of the kepub format there is no "do not use mono-spaced text" clause).

I can think to patch up the firmware to obtain additional and uncommon functions, not to read a normal epub formatted with basic css.

As I pointed out elsewhere, the epub specification does not require being able to display every glyph nor does it require any fonts be installed. Given a monospaced font is not available in the standard firmware, if Kobo displayed a monospaced font by replacing every character with a not-defined glyph, they would be within the specification (unreadable but within the specification).

I've attached the suggested images from the OpenType standard for the .notdef glyph.

[BENETNATH]

Hello,
I've got a Kobo glo HD.
the sd card crashed once, and i've been able to fix with some sd cleaning but i don't remember how.

Today, crashed again.
The kobo is able to reboot with the moving dots, but on homepage, it's crashed.

I wanted to start from new, so i put a clean microSD 16Gb card, used a KoboGloHD image sent by David in april 19.
I've flashed it with Rufus, everything was fine.
I had my kobo powered off (removed the battery plug to be sure).
I put this flashed sdcard in the kobo, and .. nothing. red permanent light, stays on the crashed page .

What can i do ??

EDIT: i've put back the original sdcard and plug/unplugged the usb cable connected to the pc.
It initialized a restoring process. Might be a good things but i would appreciate to start from a fresh sd card. Any reason why my old sd card boots but not a fresh one with the factory image ? regional restrictions or ??

[Sam Sahara]

Originally Posted by meeera

... I would say that wanting a monospace font does count as an "uncommon" thing ...

Why do you say nonsense? Are you a Kobo employee?

[meeera]

Originally Posted by Sam Sahara

Why do you say nonsense? Are you a Kobo employee?

No.

Is it your assertion that a large proportion of Kobo owners are reading non-PDF coding/technical manuals that rely on monospaced fonts that are not embedded? That certainly doesn't appear to be the case from my years of participating here. And the few people that are reading these manuals generally either already know how to add a monospaced font, or gracefully accept the volunteer help they are given.

[JSWolf]

Originally Posted by DNSB

Since Kobo has never had a monospaced font accessible on their ereaders, it's hard to see it as a bug. You can add a monospaced font either by adding it to fonts folder in the root of the Kobo's exposed storage or embed a monospaced font in the ebook. There is a patch that will point librmsdk to using your sideloaded monospaced fonts without having to play games with @font-face statements in the ebook's CSS.

As for calibre, try to remember that calibre on your computer has access to the installed fonts on your computer while a Kobo ereader has the fonts that are native to the firmware or installed in the fonts directory.

It is a bug because monospace and the rendering of a monospace font is part of RMSDK. Kobo botched it and hasn't bothered to fix it.