Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader

Notices

Reply
 
Thread Tools Search this Thread
Old 10-13-2017, 07:19 AM   #16
Cbp001
Member
Cbp001 began at the beginning.
 
Posts: 19
Karma: 10
Join Date: Dec 2016
Device: Kobo Aura One
I just tried to update my aura one (I was on the latest firmware and had the slow interface bug) but it's been in a loop for at least 20min already. I just see the black blocks turning white and back again, over and over. How long should I wait before I try to reboot and what could be causing this? Will I risk bricking it?
Cbp001 is offline   Reply With Quote
Old 10-13-2017, 08:25 AM   #17
Cbp001
Member
Cbp001 began at the beginning.
 
Posts: 19
Karma: 10
Join Date: Dec 2016
Device: Kobo Aura One
Unhappy

Quote:
Originally Posted by Cbp001 View Post
I just tried to update my aura one (I was on the latest firmware and had the slow interface bug) but it's been in a loop for at least 20min already. I just see the black blocks turning white and back again, over and over. How long should I wait before I try to reboot and what could be causing this? Will I risk bricking it?
Well after more than an hour I was tired of waiting so I rebooted the Kobo by pressing and holding the power switch. Unfortunately the problem still persists. It stays forever on the screen with the black and white blocks. Any advice on what to do now?
Cbp001 is offline   Reply With Quote
Advert
Old 10-13-2017, 08:31 AM   #18
Blas
Ulica Guy
Blas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and grace
 
Blas's Avatar
 
Posts: 85
Karma: 43686
Join Date: Aug 2017
Location: Croatia
Device: Kobo H2O and Motorola XOOM 2(for comics)
Quote:
Originally Posted by Cbp001 View Post
Well after more than an hour I was tired of waiting so I rebooted the Kobo by pressing and holding the power switch. Unfortunately the problem still persists. It stays forever on the screen with the black and white blocks. Any advice on what to do now?
But did it really update? Try to reflash the update again if it didn't
Blas is offline   Reply With Quote
Old 10-13-2017, 08:40 AM   #19
Cbp001
Member
Cbp001 began at the beginning.
 
Posts: 19
Karma: 10
Join Date: Dec 2016
Device: Kobo Aura One
Quote:
Originally Posted by Blas View Post
But did it really update? Try to reflash the update again if it didn't
Ok, but how can I do that if it's stuck on the loading animation? The laptop can't see it if I connect it.
Cbp001 is offline   Reply With Quote
Old 10-13-2017, 08:54 AM   #20
Blas
Ulica Guy
Blas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and graceBlas herds cats with both ease and grace
 
Blas's Avatar
 
Posts: 85
Karma: 43686
Join Date: Aug 2017
Location: Croatia
Device: Kobo H2O and Motorola XOOM 2(for comics)
Quote:
Originally Posted by Cbp001 View Post
Ok, but how can I do that if it's stuck on the loading animation? The laptop can't see it if I connect it.
I'm sorry I misunderstood, you can try to manually reset it. You just need a power source, it means that your laptop doesn't need to recognize it.

Here is a tutorial:
https://www.kobo.com/help/en-US/arti...aura-edition-2
Blas is offline   Reply With Quote
Advert
Old 10-13-2017, 08:58 AM   #21
oren64
I need a chapter break
oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.
 
oren64's Avatar
 
Posts: 4,042
Karma: 56058267
Join Date: Mar 2015
Location: Israel
Device: Kobo Glo
Question

The loading time need to be less then a minute.
Probebly the problem with rhe detabase, I don't see other way fix but manual factory reset.

https://www.kobo.com/help/en-US/arti...aura-edition-2

Last edited by oren64; 10-13-2017 at 12:49 PM.
oren64 is offline   Reply With Quote
Old 10-13-2017, 09:30 AM   #22
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 907
Karma: 1803094
Join Date: Jun 2011
Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11
New firmware "feels" indeed faster.
1 finding: selecting settings->Beta-functions just after upgrading did caused an unexpected restart. Could not reproduce this thereafter, so it might be a one-off occurrence.
DrChiper is offline   Reply With Quote
Old 10-13-2017, 09:47 AM   #23
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 907
Karma: 1803094
Join Date: Jun 2011
Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11
I spoke too soon: Randomly using the e-reader a second unexpected restart occurred.

I did found in directory .kobo the following files:
stack_00.log
stack_01.log

Their contents similar like below:

Code:
OH THE HUMANITY!
pid: 708, tid: 1111 (asyncmac), rev: 5c036c4fb5d4b1ee46e38cfbaf9cc838dfc39e1a
  >>> /usr/local/Kobo/nickel <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000d
 r0 00000000  r1 00000002  r2 00000001  r3 00000000
 r4 00000001  r5 01d308f0  r6 00e984c0  r7 00000000
 r8 320fedcc  r9 320fedd0  10 7ea819a4  fp 320ff450
 ip 000000f0  sp 320feda0  lr 2f506617  pc 2f506566  cpsr 00070030
    #00 sp: 0x320feda0 ip: 0x2f506566  /lib/libpthread-2.11.1.so: pthread_cond_broadcast+0x71
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 708, tid: 708
 r0 00000020  r1 7ea80d90  r2 00000004  r3 00000000
 r4 7ea80d90  r5 00000020  r6 00000006  r7 00000003
 r8 0000000a  r9 00000001  10 00000002  fp 7ea8127c
 ip 00000000  sp 7ea80d80  lr 00000000  pc 2f50839e  cpsr 80010030
    #00 sp: 0x7ea80d80 ip: 0x2f50839e  /lib/libpthread-2.11.1.so: read+0x2d
    #01 sp: 0x7ea80d88 ip: 0x0001d007  /usr/local/Kobo/nickel: _start+0x47a
    #02 sp: 0x7ea80e20 ip: 0x2f6989a1  /lib/libc-2.11.1.so: __default_sa_restorer_v2
    #03 sp: 0x7ea81110 ip: 0x2f6895f6  /lib/libc-2.11.1.so: gnu_get_libc_version+0x1a5
    #04 sp: 0x7ea81118 ip: 0x2f697d8f  /lib/libc-2.11.1.so: gsignal+0x26
    #05 sp: 0x7ea81120 ip: 0x2f69a6bd  /lib/libc-2.11.1.so: abort+0xf4
    #06 sp: 0x7ea82998 ip: 0x00f56618  [heap]: +0xf4
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 708, tid: 1056
 r0 00000006  r1 30554d80  r2 00000000  r3 00000000
 r4 00000000  r5 00000020  r6 30554d80  r7 0000008e
 r8 2e873f20  r9 00000000  10 00528790  fp 00000000
 ip 00000000  sp 30554d60  lr 00000000  pc 2f7028d2  cpsr 800d0030
    #00 sp: 0x30554d60 ip: 0x2f7028d2  /lib/libc-2.11.1.so: __select+0x31
    #01 sp: 0x30554d70 ip: 0x2e66a581  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN9QLockFile6unlockEv+0x17e4
    #02 sp: 0x30554e28 ip: 0x2e53e589  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
    #03 sp: 0x30554e50 ip: 0x2f502473  /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 708, tid: 1058
 r0 00000014  r1 30ffec98  r2 00000100  r3 30ffedb8
 r4 30ffec98  r5 0054a020  r6 2e872000  r7 00000003
 r8 30ffedd0  r9 00000001  10 00000000  fp 31000bf0
 ip 00000000  sp 30ffec88  lr 00000000  pc 2f50839e  cpsr 80080030
    #00 sp: 0x30ffec88 ip: 0x2f50839e  /lib/libpthread-2.11.1.so: read+0x2d
    #01 sp: 0x30ffec90 ip: 0x2b31b1b7  /usr/local/Kobo/libnickel.so.1.0.0: _ZN25FifoHardwareStatusMonitor21hardwareStatusChangedEv+0x22
    #02 sp: 0x30ffedb0 ip: 0x2b31b42b  /usr/local/Kobo/libnickel.so.1.0.0: _ZN25FifoHardwareStatusMonitor11connectFIFOEv+0xba
    #03 sp: 0x30ffee18 ip: 0x2b31b5f3  /usr/local/Kobo/libnickel.so.1.0.0: _ZN25FifoHardwareStatusMonitor3runEv+0xa
    #04 sp: 0x30ffee28 ip: 0x2e53e589  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
    #05 sp: 0x30ffee50 ip: 0x2f502473  /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 708, tid: 1065
 r0 0000000a  r1 00575260  r2 00575470  r3 00575680
 r4 00000000  r5 00000000  r6 0000000a  r7 0000008e
 r8 00575260  r9 00575470  10 00575680  fp 005679f8
 ip 00000000  sp 318fec40  lr 00000000  pc 2f7028d2  cpsr 800f0030
    #00 sp: 0x318fec40 ip: 0x2f7028d2  /lib/libc-2.11.1.so: __select+0x31
    #01 sp: 0x318fec50 ip: 0x2e6ec05b  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
    #02 sp: 0x318feca0 ip: 0x2e6ed57d  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsIN10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
    #03 sp: 0x318feda0 ip: 0x2e6eda29  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0xe8
    #04 sp: 0x318fedc8 ip: 0x2e6b0a3b  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xe6
    #05 sp: 0x318fee00 ip: 0x2e53b405  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
    #06 sp: 0x318fee28 ip: 0x2e53e589  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
    #07 sp: 0x318fee50 ip: 0x2f502473  /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 708, tid: 1084
 r0 00000018  r1 30700cc0  r2 30700ed0  r3 307010e0
 r4 00000000  r5 00000000  r6 00000018  r7 0000008e
 r8 30700cc0  r9 30700ed0  10 307010e0  fp 30700bc8
 ip 00000000  sp 32f0dc40  lr 00000000  pc 2f7028d2  cpsr 80030030
    #00 sp: 0x32f0dc40 ip: 0x2f7028d2  /lib/libc-2.11.1.so: __select+0x31
    #01 sp: 0x32f0dc50 ip: 0x2e6ec05b  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
    #02 sp: 0x32f0dca0 ip: 0x2e6ed57d  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsIN10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
    #03 sp: 0x32f0dda0 ip: 0x2e6eda29  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0xe8
    #04 sp: 0x32f0ddc8 ip: 0x2e6b0a3b  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xe6
    #05 sp: 0x32f0de00 ip: 0x2e53b405  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
    #06 sp: 0x32f0de28 ip: 0x2e53e589  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
    #07 sp: 0x32f0de50 ip: 0x2f502473  /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 708, tid: 1097
 r0 0000001e  r1 00a5eea0  r2 00a5f0b0  r3 00a5f2c0
 r4 00000000  r5 00000000  r6 0000001e  r7 0000008e
 r8 00a5eea0  r9 00a5f0b0  10 00a5f2c0  fp 007425e0
 ip 00000000  sp 340d7c30  lr 00000000  pc 2f7028d2  cpsr 80060030
    #00 sp: 0x340d7c30 ip: 0x2f7028d2  /lib/libc-2.11.1.so: __select+0x31
    #01 sp: 0x340d7c40 ip: 0x2e6ec05b  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
    #02 sp: 0x340d7c90 ip: 0x2e6ed57d  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsIN10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
    #03 sp: 0x340d7d90 ip: 0x2e6eda29  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0xe8
    #04 sp: 0x340d7db8 ip: 0x2e6b0a3b  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xe6
    #05 sp: 0x340d7df0 ip: 0x2e53b405  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
    #06 sp: 0x340d7e18 ip: 0x2f9c6ddd  /usr/local/Kobo/generic/libkevdevtouch.so: _init+0x7091
    #07 sp: 0x340d7e28 ip: 0x2e53e589  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
    #08 sp: 0x340d7e50 ip: 0x2f502473  /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 708, tid: 1098
 r0 0000001f  r1 31001818  r2 31001a28  r3 31001c38
 r4 00000000  r5 00000000  r6 0000001f  r7 0000008e
 r8 31001818  r9 31001a28  10 31001c38  fp 31002680
 ip 00000000  sp 348d7c40  lr 00000000  pc 2f7028d2  cpsr 800f0030
    #00 sp: 0x348d7c40 ip: 0x2f7028d2  /lib/libc-2.11.1.so: __select+0x31
    #01 sp: 0x348d7c50 ip: 0x2e6ec05b  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
    #02 sp: 0x348d7ca0 ip: 0x2e6ed57d  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsIN10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
    #03 sp: 0x348d7da0 ip: 0x2e6eda29  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0xe8
    #04 sp: 0x348d7dc8 ip: 0x2e6b0a3b  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xe6
    #05 sp: 0x348d7e00 ip: 0x2e53b405  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
    #06 sp: 0x348d7e28 ip: 0x2e53e589  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
    #07 sp: 0x348d7e50 ip: 0x2f502473  /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
Still work to be done for Kobo I suspect
DrChiper is offline   Reply With Quote
Old 10-13-2017, 09:52 AM   #24
Cbp001
Member
Cbp001 began at the beginning.
 
Posts: 19
Karma: 10
Join Date: Dec 2016
Device: Kobo Aura One
Thanks for your help Blas and Oren64, while I just ran into another problem it seems to be working again. The manual factory reset worked but when I setup the reader it immediately looked for the newest firmware, downloaded it and tried to install it. During the install there was a critical error and the device wanted me to do another factory reset. I tried it again and the second time it did go through without a problem.

Now busy with setting it up the right way and reloading all of my books.

Still wondering about that critical error though.
Cbp001 is offline   Reply With Quote
Old 10-13-2017, 09:52 AM   #25
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 907
Karma: 1803094
Join Date: Jun 2011
Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11
I like the first line in the log:
OH THE HUMANITY!
But I suspect that it should read:
OH THE HUMILIATION!
DrChiper is offline   Reply With Quote
Old 10-13-2017, 10:21 AM   #26
johnnyb
Cloud Reader
johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.
 
Posts: 1,110
Karma: 4000066
Join Date: Aug 2010
Device: Kindle Oasis, Kindle Scribe, iPad Pro 11
And I just sold my One...
johnnyb is offline   Reply With Quote
Old 10-13-2017, 10:43 AM   #27
vjjustin
Enthusiast
vjjustin began at the beginning.
 
Posts: 47
Karma: 10
Join Date: Sep 2017
Device: Kobo Glo HD
Quote:
Originally Posted by DrChiper View Post
I like the first line in the log:
OH THE HUMANITY!
But I suspect that it should read:
OH THE HUMILIATION!
That's probably from the reading settings screen. The 'refresh screen every' setting has that message as value (after update, but before you change it the first time. Once you change it, this is not to be seen again.)
vjjustin is offline   Reply With Quote
Old 10-13-2017, 10:57 AM   #28
volpo
Addict
volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.volpo ought to be getting tired of karma fortunes by now.
 
volpo's Avatar
 
Posts: 205
Karma: 2595216
Join Date: Aug 2011
Device: Clara 2E, Glo HD
Kobo Glo HD here.

Updated and running smoothly.

Don't see much difference but 'feels' a bit faster. Honestly these 'feelings' change with every firmware update so I cannot say if there is any real difference.
volpo is offline   Reply With Quote
Old 10-13-2017, 11:08 AM   #29
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 907
Karma: 1803094
Join Date: Jun 2011
Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11
Quote:
Originally Posted by vjjustin View Post
That's probably from the reading settings screen. The 'refresh screen every' setting has that message as value (after update, but before you change it the first time. Once you change it, this is not to be seen again.)
I do not follow that quite.
I changed the "Refresh screen every" to "chapter" in FW 4.6.9960, and never changed it thereafter. The setting is also still present in the current FW 4.6.9995. Ergo: according your explanation the text should not be there anymore as it has been changed [in the past].
DrChiper is offline   Reply With Quote
Old 10-13-2017, 11:55 AM   #30
rogerinnyc
Addict
rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.
 
Posts: 227
Karma: 944808
Join Date: Apr 2009
Device: Kobo Libra 2, Forma and Aura One; Kindle Voyage; Galaxy Note 10
I'm going to load this regardless, but can anyone tell whether the white line down the right margin has been fixed?
rogerinnyc is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
KOBO firmware ciemiku Devices 6 08-26-2015 11:40 PM
Kobo Firmware ferion Kobo Reader 3 05-20-2015 11:53 AM
Kobo Firmware 3.11.0 DNSB Kobo Reader 465 04-05-2015 06:07 PM
Kobo Firmware 3.5.0 murg Kobo Reader 424 08-30-2014 12:57 AM
kobo firmware The Terminator Kobo Reader 1 12-13-2010 06:26 PM


All times are GMT -4. The time now is 04:46 AM.


MobileRead.com is a privately owned, operated and funded community.