Aura One Firmware 4.2.8432

[JSWolf]

Originally Posted by geek1011

Do you know if any affiliate will show the new firmware for the older Kobos?

You could try Best Buy as an affiliate. I have no idea if it will work. Problem is I don't know all the affiliates. Sorry.

[geek1011]

Originally Posted by JSWolf

You could try Best Buy as an affiliate. I have no idea if it will work. Problem is I don't know all the affiliates. Sorry.

It did not work. I have tried a bunch of affiliates from my list, but they did not work either. Do you think I should override the version and links for those models, or not?

[JSWolf]

Originally Posted by geek1011

It did not work. I have tried a bunch of affiliates from my list, but they did not work either. Do you think I should override the version and links for those models, or not?

Personally, I would not just to be safe. There are already links on MR and in the MR Wiki. One thing we'd be able to see is when the links update.

[ottdmk]

I should check the Affliliate setting on mine (I bought it from Chapters a while back.) Mine updated OTA two days ago.

[geek1011]

Originally Posted by rashkae

'fraid not.

Edit: I wrote a bit too soon... touch accuracy is as eratic as ever. I don't know why it behaved so well just for the one testing session, but now I can't replicate it.

For me, the touch screen accuracy is fixed.

Originally Posted by Katsunami

For me, this firmware caused my computer to crash, for the first time in 20 years, where it *wasn't* a buggy display driver.

This is just idiotic. The amount of problems I've had with this device with regard to USB-connectivity are unparalleled by anything I've owned before.

This update caused one of my usb ports (whichever one I plugged it in to) to stop working (I tested this a few times, and the problem remained) until a reboot on Linux (Ubuntu GNOME 16.10), and in the dmesg log:

[  316.422137] usb 3-2: reset high-speed USB device number 10 using xhci_hcd
[  316.568950] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[  316.568952] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 0f 08 00 00 f0 00
[  316.568954] blk_update_request: I/O error, dev sdb, sector 3848
[  316.569926] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 9 ep 2 with no TDs queued?
[ 1000.136263] sdb: detected capacity change from 3386374656 to 0
[ 1000.283902] usb 3-2: USB disconnect, device number 10
[ 2235.788809] usb 3-2: new high-speed USB device number 11 using xhci_hcd
[ 2235.934863] usb 3-2: New USB device found, idVendor=2237, idProduct=4226
[ 2235.934868] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2235.934871] usb 3-2: Product: eReader-4.2.8432
[ 2235.934874] usb 3-2: Manufacturer: Kobo
[ 2235.934876] usb 3-2: SerialNumber: N236690147396
[ 2235.937957] usb-storage 3-2:1.0: USB Mass Storage device detected
[ 2235.938425] scsi host6: usb-storage 3-2:1.0
[ 2236.969883] scsi 6:0:0:0: Direct-Access     Kobo     eReader-4.2.8432 0110 PQ: 0 ANSI: 2
[ 2236.970172] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 2236.975778] sd 6:0:0:0: [sdb] 6614013 512-byte logical blocks: (3.39 GB/3.15 GiB)
[ 2237.082920] sd 6:0:0:0: [sdb] Write Protect is off
[ 2237.082922] sd 6:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[ 2237.192823] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2237.430565]  sdb:
[ 2237.653035] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 2237.755412] usb usb3-port2: disabled by hub (EMI?), re-enabling...
[ 2237.755421] usb 3-2: USB disconnect, device number 11
[ 2237.864658] sd 6:0:0:0: [sdb] Synchronizing SCSI cache
[ 2237.868632] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 2237.868636] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 03 00 00 00 f0 00
[ 2237.868639] blk_update_request: I/O error, dev sdb, sector 768
[ 2237.868657] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 2237.868659] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 03 f0 00 00 10 00
[ 2237.868660] blk_update_request: I/O error, dev sdb, sector 1008
[ 2237.868691] sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 2237.868737] Buffer I/O error on dev sdb, logical block 512, async page read
[ 2237.868740] Buffer I/O error on dev sdb, logical block 513, async page read
[ 2237.868743] Buffer I/O error on dev sdb, logical block 514, async page read
[ 2237.868745] Buffer I/O error on dev sdb, logical block 515, async page read
[ 2237.868747] Buffer I/O error on dev sdb, logical block 516, async page read
[ 2237.868749] Buffer I/O error on dev sdb, logical block 517, async page read
[ 2237.868752] Buffer I/O error on dev sdb, logical block 518, async page read
[ 2237.868754] Buffer I/O error on dev sdb, logical block 519, async page read
[ 2238.932613] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[ 2239.824531] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[ 2240.716396] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[ 2241.608368] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[ 2241.608403] usb usb3-port2: unable to enumerate USB device

This problem is on 2 different computers running Ubuntu which I tested it on.

[ratinox]

Originally Posted by geek1011

This update caused one of my usb ports (whichever one I plugged it in to) to stop working (I tested this a few times, and the problem remained) until a reboot on Linux (Ubuntu GNOME 16.10), and in the dmesg log:

Not the Kobo. This is a bug in the Linux kernel. It's been around for a while.

[kansaskyle]

Originally Posted by kobayashi

Make sure your "automatically turn off light in bright sunlight" option is disabled in the settings and then try it.

I've been running with "automatically turn off light in bright sunlight" disabled, and it definitely helps.

Last night, I founnd if I manually turn the light down to 1%, it still auto drops down to 0%. I only do that when it is late, my bride is asleep, and the bedroom is completely dark. The auto-brightness is much higher, and I don't want to bother her.

[freekobo]

never mind..

[akorx]

Hi,

Do you know if nightmode is ok with a kobo no HD with FW 4.2.8432 ?

[GeoffR]

My Glo just updated from 3.19.5761 to 4.2.8432 when I did a wi-fi sync.

It all went smoothly, but completing the sync after the new firmware installed took a very long time, like 15 minutes or so, it said it was updating my library and downloading covers. Updating my library seems to have involved replacing all my carefully corrected metadata with the publisher's original faulty metadata for all the KePubs on my device. Grr.

One problem I've found so far is the text on the book details page has very narrow line spacing, and this causes the same problems that narrow line spacing causes in the KePub reader, i.e. the page breaking in the middle of a line. (see the bottom line in the attached screenshot.)

Edit: Hmm, all the new covers it downloaded are in colour. That must be why the sync took so long, it was replacing all the old greyscale covers with colour ones. How bizarre.

Edit2: All the new downloaded covers seem to be missing the large N3_FULL versions, they only have the medium N3_LIBRARY_FULL and small N3_LIBRARY_GRID versions.

[akorx]

Originally Posted by GeoffR

... Updating my library seems to have involved replacing all my carefully corrected metadata with the publisher's original faulty metadata for all the KePubs on my device. Grr.

Oh I would not like to have the same thing, so I won't use the sync !

Just a thing : where have you do the screenshot because does not display color ? on calibre?

[oren64]

Originally Posted by GeoffR

One problem I've found so far is the text on the book details page has very narrow line spacing, and this causes the same problems that narrow line spacing causes in the KePub reader, i.e. the page breaking in the middle of a line. (see the bottom line in the attached screenshot.)

Did you try the patch `Increasing The View Details Container`, maybe it will cancel the page breaking.

Originally Posted by akorx

Just a thing : where have you do the screenshot because does not display color ? on calibre?

You need to change the setting in the conf file, .kobo/kobo/Kobo eReader.conf. (use notepade++)

[FeatureSettings]
Screenshots=true

You do the screen shot with the power switch, so to power-off\sleep you need to set it to "Screenshots=false".

[jackie_w]

Originally Posted by GeoffR

One problem I've found so far is the text on the book details page has very narrow line spacing, and this causes the same problems that narrow line spacing causes in the KePub reader, i.e. the page breaking in the middle of a line. (see the bottom line in the attached screenshot.)

In case it helps, the Kobo synopsis display is controlled by this css stream in the nickel file

Spoiler:

/* found: 79 (nozlib) pos: 4bcd2e */
* {
  font-family: Georgia;
}
*[qApp_localeName="ja_JP"] {
  font-family: Sans-SerifJP, sans-serif;
  font-style: normal;
}
body {
  line-height: 1.5em;
  margin: 0px;
  padding: 0px;
}
body[qApp_deviceIsTrilogy="true"] {
  font-size: 19px;
}
body[qApp_deviceIsPhoenix="true"] {
  font-size: 23px;
}
body[qApp_deviceIsDragon="true"] {
  font-size: 29px;
}
body[qApp_deviceIsAlyssum="true"] {
  font-size: 32px;
}
body[qApp_deviceIsDaylight="true"] {
  font-size: 37px;
}
body[qApp_deviceIsTrilogy="true"] {
  line-height: 1.25em;
}
body[qApp_deviceIsPhoenix="true"] {
  line-height: 1em;
}

If the original Glo is considered to be 'deviceIsPhoenix' then it may be the last line which is causing your problem. As this is one of the few nickel css streams which is not compressed you could probably quite easily create a patch to suit your requirements. For instance, I've custom patched my currently used devices (H2O, GloHD, AuraOne) to display the synopsis as sans-serif, full-justified with line-height 1.3.

[GeoffR]

Originally Posted by jackie_w

In case it helps, the Kobo synopsis display is controlled by this css stream in the nickel file
[...]

body[qApp_deviceIsPhoenix="true"] {
  line-height: 1em;
}

That is certainly the CSS causing the problem, ...

If the original Glo is considered to be 'deviceIsPhoenix' then it may be the last line which is causing your problem. As this is one of the few nickel css streams which is not compressed you could probably quite easily create a patch to suit your requirements. For instance, I've custom patched my currently used devices (H2O, GloHD, AuraOne) to display the synopsis as sans-serif, full-justified with line-height 1.3.

And that is the solution, thanks!

[GeoffR]

I'm having some trouble connecting my Glo via USB to my laptop running Debian Linux with firmware 4.2.8432.

If I reboot the Glo then I can connect once without any problems, but if I try to connect a second time withoot a reboot inbetween then it won't connect.


Edit: Also finding this firmware to be a lot slower than 3.19.5761. Reading is okay, but paging through the library, using menus, waking from sleep are all quite slow. Sync is extremely slow, 5 minutes to sync compared to 30 seconds or less with 3.19.5761.