Firmware 3.17.3 Discussion

[murg]

Originally Posted by JSWolf

You have it so wrong it cannot get any more wrong. It's not Kobo's fault. Do you really expect Kobo to rewrite RMDSK? I would not expect that nor want that.

Kobo's the one that made the choice to use Adobe's product. That makes it their fault.

The only mitigating factor would be if you had to use the Adobe rendering engine if you use their DRM. In which case, as one of Adobe largest customers for this product, they should be applying all due pressure on Adobe to fix the product.

Kobo has already sortof rewritten RMSDK, they have their own rendering engine.

[murg]

Originally Posted by DNSB

From what I can make out of your statement above, if I use a software product, any missing features in that software product are my fault. Any bugs are my responsibility. Am I, perchance, missing the mandatory <sarcasm> & </sarcasm> tags?

On a more serious note, what alternative renderer would you suggest that Kobo use that would have compatibility with Adobe's ADEPT DRM used by virtually every supplier of DRMed epub ebooks, not require a major rewrite to work on their variant of Linux and not have any bugs or missing features?

If you use a software product, and that product has some bug embedded in an external library, it is the producer of the product you bought's fault.

Kobo already has their own renderer (kepub). While it makes sense to continue to use Adobe's server side, decrypting Adobe DRM is relatively trivial, as witnessed by Apprentice Alf, et al.

[JSWolf]

Originally Posted by murg

Kobo's the one that made the choice to use Adobe's product. That makes it their fault.

The only mitigating factor would be if you had to use the Adobe rendering engine if you use their DRM. In which case, as one of Adobe largest customers for this product, they should be applying all due pressure on Adobe to fix the product.

Kobo has already sortof rewritten RMSDK, they have their own rendering engine.

Kobo does have to use RMDSK in order to use Adobe's DRM. Not everyone strips DRM. Not everyone knows how to strip DRM or that the tools exist. Not everyone strips DRM from borrowed library ePub. So Kobo does need to use Adobe's DRM and that means using RMSDK. That does not mean rewriting RMDSK to fix everything Adobe didn't fix.

Access is a freaking mess (IMHO). Access should be fixed so you can just use box standard ePub 3.

[Nick_1964]

Originally Posted by meeera

Font weight, margins, line spacing, ragged-right, light swipe, and tap zones all make a big difference to my reading experience. None of those have anything to do with web browsing.

Completely right,but just as Kobo, put an option there how to disable it from the screen for most of the things..the light swipe is an extra luxury added later,in the beginning the device doesn't have it and if they had keep it where it was,no one should complaining now.
As they added it to the screen now people get used to it and find it a nice future.. (some of them) and I don't want to take that pleasure away.
But give me the option to disable it !

An option to use a cloud printer to use a wifi printer would be nice to, only give the choice to disable it in an option menu.
People who like it,use it (as in the slider for the light) and people who don't,can disable it.
I didn't have problems with the light until now,they change something to make it more sensitive and with the Glo HD it is way to sensitive.
Thats my main problem.

[Ripplinger]

Originally Posted by Nick_1964

I didn't have problems with the light until now,they change something to make it more sensitive and with the Glo HD it is way to sensitive.
Thats my main problem.

That's my exact problem as well. This didn't happen when the area to adjust the light was really well against the left bezel, where to use it, you had to actually be touching the bezel and the glass at the same time. But now the area for the light adjustment has been made larger and moved out a bit from the left bezel. That's when it started to be a problem for me.

[SirEvo]

Hello guys,

I just bought a new Kobo Touch 2 weeks ago and it's my first experience on e-books.
But after this update, I have 1 problem.

When I put my Reader to sleep while I read a book, my status on the book (which writes in sleep mode) I read does not update itself. I have to turn on device and put reader to sleep again to see the updated percentage of the book I read. But there's no problem with the page where I left. I can continue to read from where I left.

Do you guys have any similar problem? I hope its related with latest update.

P.S. I read epub files and I didn't have such problem before this update. (I think I have updated my Kobo on 25th-26th.)

[GeoffR]

Originally Posted by SirEvo

I just bought a new Kobo Touch 2 weeks ago and it's my first experience on e-books.
But after this update, I have 1 problem.

When I put my Reader to sleep while I read a book, my status on the book (which writes in sleep mode) I read does not update itself. I have to turn on device and put reader to sleep again to see the updated percentage of the book I read. But there's no problem with the page where I left. I can continue to read from where I left.

Do you guys have any similar problem? I hope its related with latest update.

P.S. I read epub files and I didn't have such problem before this update. (I think I have updated my Kobo on 25th-26th.)

Yes, the problem of the sleep screen showing the wrong percentage started in firmware 3.17.0.

[Jarrett]

Originally Posted by davidfor

While the main reason for the release of 3.17.3 is to solve the problem with sickel causing a reboot when processing some PDF files, there are some other changes. So, from my notes:

• PDFs no longer cause a sickel triggered restart. Apparently sickel has been neutered.
• Fix to remember page correctly when reading a kepub and powering off.
• Changes in how sync is done. This will be much faster but mainly by doing some things at other times. The noticeable on is that dictionaries are synced when you change the list rather than waiting for a sync.
• Changes in the shop. I don't use it on the device so I don't really know what they are.

There are no changes that affect calibre. I will bump to the supported version number tonight for the next calibre release.

When reading A Year in Provence (it has lots of French words scattered throughout), when I would look-up a word using longpress it always looked for a French dictionary first, which is not installed, then I'd have to choose French to English - what I want. I think this problem has been fixed in 3.17.3

[DNSB]

Originally Posted by murg

If you use a software product, and that product has some bug embedded in an external library, it is the producer of the product you bought's fault.

Kobo already has their own renderer (kepub). While it makes sense to continue to use Adobe's server side, decrypting Adobe DRM is relatively trivial, as witnessed by Apprentice Alf, et al.

Minor correction: Kobo does not have their own renderer. ACCESS supplies the epub3 compliant (more or less) renderer though Kobo supplies the DRM.

As for the trivial nature of decrypting ADEPT, it's not the triviality, it's the horde of lawyers who would descend on Kobo. Kobo might win in court if they were able to prove that they had clean room reverse engineered the decryption software but my opinion is that Kobo is likely to run out of money long before any decision was reached in such a case. If ADEPT is covered by any patents and Adobe chose to fight the case based on patent rights, even clean room reverse engineering would not be a defense given that several cases have made it clear that clean room reverse engineering can not be used to circumvent patent restrictions.

[SirEvo]

Originally Posted by GeoffR

Yes, the problem of the sleep screen showing the wrong percentage started in firmware 3.17.0.

Thank you for your answer.
Hope they'll fix it soon.

[melovesflying]

Just discovered that using the search function on the book I'm currently reading is a hit or miss. Search results appear normally but once I click on a result, it won't go to that page but will stay on the page I'm currently reading. Tapping on the arrows to get to the previous or next results also don't work. Tried this on several epub files that I had no issues with using the search function back in 3.15 and with this firmware, sometimes it works, sometimes it doesn't.

[micione20]

Hi i just want ask, with 3.17.3 fw kobo glo hd is page change faster. I need to decide this vs pw3

[Ripplinger]

Originally Posted by micione20

Hi i just want ask, with 3.17.3 fw kobo glo hd is page change faster. I need to decide this vs pw3

I believe the PW3 will still be faster, if that's all you're basing your selection on.

But when comparing the rest of the features, for myself, page turning speed really doesn't figure very high on the list. It's still faster than I could change a physical book page, so I value ability to add my own fonts, font adjustments, and be able to freely make other changes through patches much more valuable than page turning speed. Kindles are pretty well locked down at this point, you can't even add your own fonts to a Kindle unless you want to root it by taking it apart and using a serial connection. And I'm not sure if anyone has gotten that far with a PW3 yet.

[davidfor]

Originally Posted by Ripplinger

But when comparing the rest of the features, for myself, page turning speed really doesn't figure very high on the list.

This is pretty much where I am at with the page turning speed. The page turns faster than I can move my eyes from the bottom right to the top left. That means the text is ready when I am, so that's fast enough.

[micione20]

what a shame. on my old k3 i could load everything i loved, without open case, or serial cable.
now i should change, i want light, but i cannot decide wheter kindle pw3 or glo hd.
i want just a great device for reading, and i love reading without margin in full screen, little font, and most similar to paper screen