Kobo Firmware 2.8.1: pass or fail? (poll)

[speakingtohe]

Originally Posted by jackastor

Agreed. Maybe someone can shed some additional information on a fix or work around that does not involve removing books or the cards?

Regards

JAck

Generally it is not really frozen it is just taking it's time. I used to do the remove card and plug it into usb port route, insert card etc.

Now I just switch readers maybe an hour or several, I haven't sat there and watched. But 4 times it has come back, and at least once I checked it after 45 minutes and it was still appearing frozen.

A bug IMO in that it will take a very short time when you do the card thing. Same card, same books, should be same process, but sometimes it takes under a minute and sometimes over 45 minutes to do whatever it is doing.

Helen

[diolaine]

Originally Posted by speakingtohe

Generally it is not really frozen it is just taking it's time. I used to do the remove card and plug it into usb port route, insert card etc.

Now I just switch readers maybe an hour or several, I haven't sat there and watched. But 4 times it has come back, and at least once I checked it after 45 minutes and it was still appearing frozen.

A bug IMO in that it will take a very short time when you do the card thing. Same card, same books, should be same process, but sometimes it takes under a minute and sometimes over 45 minutes to do whatever it is doing.

Helen

Personally I waited whole night or whole day and it still hangs at a given time! grrrrr I do not know what to do ... and yet I love my kobo glo : Help:

[Anak]

Originally Posted by franklekens

In less than optimal light conditions (darkish, yet not quite dark enough to turn on the backlight) if the light doesn't fall on the device directly, the top line of text will be in the shade of the bezel. That's just ridiculous.

You aswered it yourself. You are trying to read under the wrong or a far from optimal reading environment. In this case non-device light sources that don't emit enough light, and/or too few light sources, and/or the wrong position of the light sources.
This has nothing to do with the device and all about the reading enviroment.
So in fact your are saying: because my reading conditions are far from optimal I need large screen margins on the top because my main light source is positioned in front of my device and also positioned quite low. The result: a huge shade of the top bezel.

If you change your reading position you'll also need huge margins on the left, right or bottom because of your poor lightning conditions.
And, I'm also quite sure you read at a very huge font size for compensation.

Hey, I sound very pro Kobo now, it's a Monday.

[Anak]

Originally Posted by AnemicOak

Can they fix it? It's a bug in ADE and the RMSDK as far as I know so unless Adobe fixes it I'm not sure Kobo can do anything (Sony has the same bug). At least that's my understanding.

The long paragraph bug (TLPB) It is also present in the Access renderer when reading kepubs. Personally, I don't read kepubs very often, so I can't tell if it happens more frequently with regular epubs.
As it happens with both epubs and kepubs the source of TLPB could be not the Access or Adobe renderer itself, but (one of) Kobos host progam(s).

If you use metazoa patch for 2.8.1. and set all patch options to "no" but only the line height option to "yes" and replace the default settings to very small (start < 1) you'll notice that TLPB will occur much often.

[AnemicOak]

Originally Posted by Anak

The long paragraph bug (TLPB) It is also present in the Access renderer when reading kepubs.

I did not know that. I've only read about 50 books on my Aura so far, but had only encountered it on ePub's.

[davidfor]

Originally Posted by Anak

The long paragraph bug (TLPB) It is also present in the Access renderer when reading kepubs. Personally, I don't read kepubs very often, so I can't tell if it happens more frequently with regular epubs.
As it happens with both epubs and kepubs the source of TLPB could be not the Access or Adobe renderer itself, but (one of) Kobos host progam(s).

As with AnemicOak, I haven't seen this with kepubs. That includes epubs I have seen it with that I then sent as kepubs to test this. Do you have an example kepub that shows the problem?

[roger64]

Originally Posted by franklekens

Why on earth are people glad the "top margin" is gone? I never knew it was a problem. Now the text of Gutenburg books & the like starts *right* underneath the bezel. That makes the screen look stuffed and cheap, it makes for unpleasant reading. In less than optimal light conditions (darkish, yet not quite dark enough to turn on the backlight) if the light doesn't fall on the device directly, the top line of text will be in the shade of the bezel. That's just ridiculous.

Let the "people" reply. Ridiculous, it may be but soooo easy to correct: you just have to insert a line of code to set up a top-margin (look for any calibre made epub for a hint); the problem is that the contrary is not true. If your top-margin is set by Kobo, you're stuck with it, you cannot decrease it.

Sometimes I read or produce books with images that I like to see with a full page display (up to the bezel). You should try it. It can be amazing.

[rem736]

fail for me on the aura hd. the huge top margin is gone, but the bottom margin sometimes being gigantic is still annoying. and i can attest to the jumping multiple pages ahead once in a while problem. can't understand how it actually got worse and why they haven't fixed that problem by now.

[jackastor]

Originally Posted by rem736

fail for me on the aura hd. the huge top margin is gone, but the bottom margin sometimes being gigantic is still annoying. and i can attest to the jumping multiple pages ahead once in a while problem. can't understand how it actually got worse and why they haven't fixed that problem by now.

Actually I have noticed that what had appeared to be a jump in pages was actually just a page refresh. When going back one page it was obvious it was only a single page turn, it just looked disconcerting.

regards

JAck

[Stephjk]

A 'fail' from me. Since updating I have to soft reset at least once a day, sometimes several times in succession as the screen freezes completely. The light no longer comes back on automatically after sleeping if it is only set at 1% brightness (and that is my preferred setting for reading in the dark), my glo doesn't always wake-up when I open the cover, the sudoku game freezes often............

Whenit's working well it seems snappier but the problems I have gained are not worth that improvement.

I wish I'd never upgraded.

[booklover6]

Originally Posted by Stephjk

A 'fail' from me. Since updating I have to soft reset at least once a day, sometimes several times in succession as the screen freezes completely. The light no longer comes back on automatically after sleeping if it is only set at 1% brightness (and that is my preferred setting for reading in the dark), my glo doesn't always wake-up when I open the cover, the sudoku game freezes often............

Whenit's working well it seems snappier but the problems I have gained are not worth that improvement.

I wish I'd never upgraded.

Down grade to 2.6.1. That's what I did. I don't use wifi to download books or anything, so no risk of unwanted upgrade.

[Stephjk]

How do I downgrade? I did a factory reset once but 2.8.1 came straight back on.

[adbosch]

How often does Kobo issue upgrades? And do they normally take criticism from users here into account?

[jackastor]

Originally Posted by adbosch

How often does Kobo issue upgrades? And do they normally take criticism from users here into account?

You know sometimes one has to wonder if Kobo is actually paying attention here, Based on some of the results of the Firmware. But then on the other hand the same can be said when it seems like they are paying attention by bringing out some of the features that the users here have suggested. Or perhaps the tunnel vision has to be removed from the programmers eyes.
So that official debate would still be open for discussion.
regards

Jack

[speakingtohe]

Originally Posted by jackastor

You know sometimes one has to wonder if Kobo is actually paying attention here, Based on some of the results of the Firmware. But then on the other hand the same can be said when it seems like they are paying attention by bringing out some of the features that the users here have suggested. Or perhaps the tunnel vision has to be removed from the programmers eyes.
So that official debate would still be open for discussion.
regards

Jack

I often wonder if they actually read on the ereaders they are programming. I can understand if they don't as it must be more upsetting for them to encounter the numerous bugs and shortcomings than it is for us.

And of course different people expect different things and have different priorities.

If it was me I would be prioritising the actual reading bugs, such as double page turns, and the pages turning in the opposite direction. I cannot imagine why these are so difficult to address. And the book re-opening on the wrong page.

Next I would make sure all the font and justification, margins 'features' work for the majority of books anyway. That is one of the main selling points IMO.

Then I would fix the shelf and sorting functions and bring back the back button making it actually work like the majority of back buttons work.

Taking a month or more to perhaps fix something, arbitrarily change something else and break something or make something worse has not endeared them to me. feels sort of like being eaten by a grue

Helen