Firmware 4.0.7523

[DNSB]

Originally Posted by freekobo

The most important patch is working on this firmware, Fix page breaks bug.

Not sure if that fix is still needed. The RMSDK version that Kobo is now using does not show that problem. I admit to still using the patch for it's ability to disable widows and orphans -- one recent ebook had them set to 5 for some reason unknowable.

[freekobo]

Originally Posted by DNSB

Not sure if that fix is still needed. The RMSDK version that Kobo is now using does not show that problem. I admit to still using the patch for it's ability to disable widows and orphans -- one recent ebook had them set to 5 for some reason unknowable.

oh yeah right, its the side effect of that patch that I find useful not what it was originally created for, them dang widows and orphans. Perhaps the patch should be renamed?

[rashkae]

The touch screen does not appear calibrated properly on Aura one with this update. So far, I've only really noticed this on the controls of the Kepub reader, (the buttons you can press on the bottom once you've opened the menu.)... so it's probably not the touchscreen itself. I have to press slightly the left of the control I want to activate. The update is required, however. The firmware that shipped with the Aura One has that perpetual sync with no wifi battery drain bug happening.

Oh Kobo, the more things change....

[frostschutz]

@rashkae: Does it have the Sketch Pad in the Settings->BetaFeatures? That's usually a good way to test touch screen accuracy.

Those little [ ] tick boxes in the settings are particularly hard to touch correctly. It's like they only have a 5x5 pixel region that triggers them. But that's a problem of the UI, not so much of the touchscreen. Touchscreens always have some degree of inaccuracy (or my fingers are all thumbs).

[davidfor]

Calibre version 2.67 has been released today. This includes full support for firmware version 4.0.7523 and the Aura ONE and Aura Edition 2 devices.

[jiminrussell]

Thank you David, works like a charm with the Aura One.

[Willa]

Originally Posted by davidfor

Calibre version 2.67 has been released today. This includes full support for firmware version 4.0.7523 and the Aura ONE and Aura Edition 2 devices.

Thank you David

[anacreon]

Originally Posted by davidfor

Calibre version 2.67 has been released today. This includes full support for firmware version 4.0.7523 and the Aura ONE and Aura Edition 2 devices.

I like the improvements of version 2.67, but I still have an error message whenever I connect (it works fine all the same):

Spoiler:

calibre, version 2.67.0
ERREUR : Erreur: Erreur pendant la communication
avec le dispositif


'apsw.Connection' object has no attribute 'commit'


Traceback (most recent call last):
File
"site-packages\calibre\gui2\device.py", line 87, in run
File
"site-packages\calibre\gui2\device.py", line 533, in _sync_booklists

File "calibre_plugins.kobotouch_extended.device.driver" , line 396, in
sync_booklists
AttributeError: 'apsw.Connection' object has no attribute
'commit'

and I do connect often since after doing a full reset yesterday and getting nowhere, I finally decided to exchange my device this noon, and am busy loading it in batches.

[vandafc]

Originally Posted by davidfor

Calibre version 2.67 has been released today. This includes full support for firmware version 4.0.7523 and the Aura ONE and Aura Edition 2 devices.

You rock David !

[anacreon]

surprising book lists order

After exchanging the One, I finished loading my 2246 books, with batches in reverse order to what I wanted to have accessible first in my recent reading list. I ejected the reader 3 times, and the 4th batch was my active list. But it was no use at all since the "recent" sort gave the reverse alphabetical order of titles. I've several times proceeded this way formerly (with F/W up to 3.15.0), and it is the first time the result is this.

I then synced the reading positions (together with the metadata and the related books and series). Surprise: some of the latest batch appeared at the front, whether read, finished, or unread, in no particular order, then (page 27 of 375) started the rest, still in reverse alphabetical of titles for those unread.

Reactivity
I've read in several reviews and comments that the One is reactive. In both my Ones I've found calling the collections (from the home page or the book list) appallingly slower than the Glo HD (F/w 3.15.0), which is not quick: some 16" instead of 5". Calling the book list is almost instant for both devices. What is going on? Is it a known bug to be corrected in later versions?

Both problems combined mean it becomes painful to navigate in my library, which is ridiculous in a device which gives you 8 GB to allow you to have a big one.

EDIT: I have 75 collections.

[davidfor]

Originally Posted by anacreon

I like the improvements of version 2.67, but I still have an error message whenever I connect (it works fine all the same):

Spoiler:

calibre, version 2.67.0
ERREUR : Erreur: Erreur pendant la communication
avec le dispositif


'apsw.Connection' object has no attribute 'commit'


Traceback (most recent call last):
File
"site-packages\calibre\gui2\device.py", line 87, in run
File
"site-packages\calibre\gui2\device.py", line 533, in _sync_booklists

File "calibre_plugins.kobotouch_extended.device.driver" , line 396, in
sync_booklists
AttributeError: 'apsw.Connection' object has no attribute
'commit'

and I do connect often since after doing a full reset yesterday and getting nowhere, I finally decided to exchange my device this noon, and am busy loading it in batches.

That's an error in the extended driver. It is some code that won't be executed by all connections, but is more likely to be needed after sideloading a lot of books. It should be reported in the thread for the extended driver to be fixed.

[rtiangha]

Oh, I forgot to mention, I still had all the launchers on my home screen from the previous firmware, and stuff like Sudoku, Solitaire, Sketch Pad, etc all still work (no idea about chess, though). I think I saw a post around here showing how you could edit the database to make those launchers appear on your home screen for an older firmware that you might be able to use until a patch for nickel shows up that puts those options into the Beta Settings page again.

[MGlitch]

Originally Posted by rtiangha

Oh, I forgot to mention, I still had all the launchers on my home screen from the previous firmware, and stuff like Sudoku, Solitaire, Sketch Pad, etc all still work (no idea about chess, though). I think I saw a post around here showing how you could edit the database to make those launchers appear on your home screen for an older firmware that you might be able to use until a patch for nickel shows up that puts those options into the Beta Settings page again.

This only works if the apps are somewhere in the software and are just not being shown. I believe it's impossible to get Chess on the GloHD because of just that limitation.

[rtiangha]

Originally Posted by MGlitch

This only works if the apps are somewhere in the software and are just not being shown. I believe it's impossible to get Chess on the GloHD because of just that limitation.

They might have brought it back; you never know. Anyway, I didn't check for that in version 4.0, although I found it strange that in the 3.19 firmware, there was still a libchess file buried somewhere in rootfs.

[davidfor]

Originally Posted by MGlitch

This only works if the apps are somewhere in the software and are just not being shown. I believe it's impossible to get Chess on the GloHD because of just that limitation.

Originally Posted by rtiangha

They might have brought it back; you never know. Anyway, I didn't check for that in version 4.0, although I found it strange that in the 3.19 firmware, there was still a libchess file buried somewhere in rootfs.

Chess was pulled from the beta features for all the devices ages ago. It was still in the firmware package and could be used. Later it stopped working. The library might still be there because it being used by something else, but it is more likely that the effort to remove it just isn't worth it as it will do nothing.

The rest of the games will still be there as most of the devices still have them a Beta Features. They will probably work on all devices if you can start them, but they might not occupy the full screen or have other display problems.