Firmware 3.19.5761

[JSWolf]

Originally Posted by koboy

use mark 6 for the Glo HD and copy the KoboRoot.tgz on it's own into the .kobo folder and then eject the Aura, it will extract the files and restart job done, you will then have 3.16.0, and then ignore all the pointless updates so far there after in my own humble opinion of course.


best wishes koboy

I don't think the latest firmware is a pointless update. I say to go for it.

[outlandos]

a small update but a solid release alltogether.

[bookaho!ic]

just got the update no major glitches so far - fingers x

[norbusan]

Dear all,
I updated my mega-update patch set (nickel, ssh, fonts, KSM, etc) to this firmware. Please take a look at http://www.preining.info/blog/2016/0...tch-ssh-fonts/

Enjoy

[davidfor]

Originally Posted by the.Mtn.Man

Thanks for the info. So should I be able to do a manual upgrade from 3.12.1 to 3.16 without issue? On the Aura, of course.

Yes, you should be safe. But, use the KoboRoot.tgz from the Mark4 package. The Mark6 package for the Glo HD has different drivers. The drivers in the Mark4 and Mark5 versions are the same.

[the.Mtn.Man]

Originally Posted by koboy

use mark 6 for the Glo HD and copy the KoboRoot.tgz on it's own into the .kobo folder and then eject the Aura, it will extract the files and restart job done, you will then have 3.16.0, and then ignore all the pointless updates so far there after in my own humble opinion of course.

No joy. Upgrade went fine, but this firmware apparently also has the "can't disable pinch to zoom" bug that plagued several versions.

Pity, because I do like the increased performance of the post 3.12.1 firmwares, but that bug and the stuttery backlight level adjustment are deal-breakers.

[koboy]

Originally Posted by the.Mtn.Man

No joy. Upgrade went fine, but this firmware apparently also has the "can't disable pinch to zoom" bug that plagued several versions.

Pity, because I do like the increased performance of the post 3.12.1 firmwares, but that bug and the stuttery backlight level adjustment are deal-breakers.

sorry to hear that it didn't work, i can definitely do the 2-finger swipe to adjust the brightness without it changing the font size. in the reading settings i have the pinch to adjust font size unchecked.

btw did you use mark 4 or mark 6?


best wishes koboy

[the.Mtn.Man]

Originally Posted by koboy

sorry to hear that it didn't work, i can definitely do the 2-finger swipe to adjust the brightness without it changing the font size. in the reading settings i have the pinch to adjust font size unchecked.

btw did you use mark 4 or mark 6?


best wishes koboy

Mark 6. There is no Mark 4 version of 3.16.

Perhaps I'm not explaining myself sufficiently. I can do the two-finger swipe to change brightness. The problem is that it can occasionally read as a pinch (expecially if I don't keep my fingers firmly together), and I end up adjusting the font size instead, which is annoying, so I prefer to leave "Pinch to adjust font size" unchecked. However, every Aura firmware from 3.13.1 to, I think, 3.17.x has a bug such that unchecking the option doesn't actually disable the feature.

3.18 fixed that bug, but then it introduced another bug where it led to erratic behavior when adjusting the fontlight brightness (I don't remember what, exactly; I just remember it was wonky). 3.19.xxxx smoothed out the frontlight adjustment but then it introduced significant lag, where it could take several seconds for the device to resond to a two-finger swipe which made it inevitable that you would overshoot your desired brightness level.

So I've just stayed with 3.12.1 since it's one that works best for me, although it, too, has a bug where setting it to refresh every chapter will cause it to refresh every page instead, but that's a bug I can live with, unlike the others I've mentioned.

[koboy]

Originally Posted by the.Mtn.Man

Mark 6. There is no Mark 4 version of 3.16.

Perhaps I'm not explaining myself sufficiently. I can do the two-finger swipe to change brightness. The problem is that it can occasionally read as a pinch (expecially if I don't keep my fingers firmly together), and I end up adjusting the font size instead, which is annoying, so I prefer to leave "Pinch to adjust font size" unchecked. However, every Aura firmware from 3.13.1 to, I think, 3.17.x has a bug such that unchecking the option doesn't actually disable the feature.

3.18 fixed that bug, but then it introduced another bug where it led to erratic behavior when adjusting the fontlight brightness (I don't remember what, exactly; I just remember it was wonky). 3.19.xxxx smoothed out the frontlight adjustment but then it introduced significant lag, where it could take several seconds for the device to resond to a two-finger swipe which made it inevitable that you would overshoot your desired brightness level.

So I've just stayed with 3.12.1 since it's one that works best for me, although it, too, has a bug where setting it to refresh every chapter will cause it to refresh every page instead, but that's a bug I can live with, unlike the others I've mentioned.

ok i thought you couldn't use the 2-finger swipe to adjust the brightness at all without it altering the font size obviously my mistake, there is however a mark 4 here http://download.kobobooks.com/firmwa...ate-3.16.0.zip although it probably won't be any better, perhaps it might be worth a try, but of course it is entirely up to you good luck.



best wishes koboy

[Donads]

Hey guys, my Glo is still on 3.15, as I was really afraid of the sickel problem. Aside from usual books, I also read a lot of English fan translations of Japanese light novels, which I get from Baka-Tsuki, and some of these usually take several seconds to load when opening from the home screen (waking up is fine), probably due to having about a dozen pics each and several chapters.

I've just read some of the feedback for all of the firmware versions that came after 3.15.0 and from what I've gathered they have sort of "deactivated" sickel due to the restarting issues, though I couldn't find any mention of sickel in this version's thread.

1- Could anyone confirm it's still not an issue anymore even on the January firmware?


Also, as I've mentioned, I read a lot of light novel volumes. Whenever a company licenses a series in English, the project gets taken down from Baka-Tsuki in order to support the official release. Recently I had to buy a volume of a series that was licensed by Yen Press from the Kobo Store and I managed to use the Obok Calibre plugin to remove the DRM from the book stored in the device (I read somewhere the plugin isn't working with latest desktop versions, only with the device itself).
From what I read on the "Direct Links to Kobo Firmware" page, I couldn't properly understand whether both the firmware and desktop application use a different sort of DRM since version 3.17 or it only applies to the desktop version.

2- Has anyone had success removing the DRM from a book in the device on the latest firmware?


*By the way, I must apologize for any grammar errors and such as English isn't my native language.

[JSWolf]

The sickel bug has been fixed. So go ahead and install the current firmware.

Removing the DRM has nothing to do with what firmware you are using.

[davidfor]

Originally Posted by Donads

Hey guys, my Glo is still on 3.15, as I was really afraid of the sickel problem. Aside from usual books, I also read a lot of English fan translations of Japanese light novels, which I get from Baka-Tsuki, and some of these usually take several seconds to load when opening from the home screen (waking up is fine), probably due to having about a dozen pics each and several chapters.

I've just read some of the feedback for all of the firmware versions that came after 3.15.0 and from what I've gathered they have sort of "deactivated" sickel due to the restarting issues, though I couldn't find any mention of sickel in this version's thread.

1- Could anyone confirm it's still not an issue anymore even on the January firmware?

Sickel was only active in two or three firmware versions. Yes, it's still there, but it doesn't do force a reboot.

Also, as I've mentioned, I read a lot of light novel volumes. Whenever a company licenses a series in English, the project gets taken down from Baka-Tsuki in order to support the official release. Recently I had to buy a volume of a series that was licensed by Yen Press from the Kobo Store and I managed to use the Obok Calibre plugin to remove the DRM from the book stored in the device (I read somewhere the plugin isn't working with latest desktop versions, only with the device itself).
From what I read on the "Direct Links to Kobo Firmware" page, I couldn't properly understand whether both the firmware and desktop application use a different sort of DRM since version 3.17 or it only applies to the desktop version.

2- Has anyone had success removing the DRM from a book in the device on the latest firmware?

The firmware and the desktop do use the same DRM, but the keys are different. I don't know if anyone has tracked down the correct key for the latest firmware. It is working for the latest desktop.

But, does your Kobo library have epub versions of these books? Most books have both versions with the epub version downloadable from the library. If this has DRM, then ADE will be needed.

[Donads]

Originally Posted by JSWolf

The sickel bug has been fixed. So go ahead and install the current firmware.

Removing the DRM has nothing to do with what firmware you are using.

Originally Posted by davidfor

Sickel was only active in two or three firmware versions. Yes, it's still there, but it doesn't do force a reboot.


The firmware and the desktop do use the same DRM, but the keys are different. I don't know if anyone has tracked down the correct key for the latest firmware. It is working for the latest desktop.

But, does your Kobo library have epub versions of these books? Most books have both versions with the epub version downloadable from the library. If this has DRM, then ADE will be needed.

Thanks guys, I've updated my firmware and so far there were no reboots.
Well, it was the first time I bought something from the Kobo Store. The first thing I did was to use the Obok DeDRM calibre plugin to remove its DRM, get it stored in my PC and then sideload it to my Glo.

When selecting a book, the plugin will first try to get it from an attached Kobo (which is the way I used it) and only if there's no device connected it'll try getting the book from the desktop application. From what I've read it used to work with the 3.15 desktop version but not with the 3.17.
I wasn't sure if the firmware update would cause the same behavior when trying to get the book from the device or nothing would change in this regard. In a couple of weeks, when it's released, I'll probably buy the next volume of this series. Then, I will once again try to remove its DRM.

Once again, thank you all for your time

[davidfor]

Originally Posted by Donads

When selecting a book, the plugin will first try to get it from an attached Kobo (which is the way I used it) and only if there's no device connected it'll try getting the book from the desktop application. From what I've read it used to work with the 3.15 desktop version but not with the 3.17.
I wasn't sure if the firmware update would cause the same behavior when trying to get the book from the device or nothing would change in this regard. In a couple of weeks, when it's released, I'll probably buy the next volume of this series. Then, I will once again try to remove its DRM.

Kobo have changed the key used for the DRM twice in recent desktop and firmware versions. A solution was found the first time for both places. The second time I know it was worked out for the desktop but I don't know if was for the device.

[drjd]

Originally Posted by davidfor

I don't know anything about this release either. It was not released through the beta list.

I have checked the function from the calibre point of view, and there are no changes to the database or anything that the driver uses. So, I have bumped the supported version number. That should be included in the next release of calibre. In the meantime, you can safely use the "Attempt to support newer firmware" option in the driver.

I'm using Calibre v 2.48 to connect the device, but I am getting a "kobo database version unsupported" error. Where exactly should I enable the "Attempt to support newer firmware" option in Calibre, please ?