Touch Bug: KT goes to sleep shortly after being woken

Aydan · 04-02-2013, 07:29 AM

I found a very annoying bug in the 2.4.0 firmware over the weekend:
Whenever I woke my Touch from sleep it would go back to sleep after only maybe half a minute if I didn't touch the screen before.
My sleep timer was set to 5 minutes, I changed it to 10 minutes to see if it changes the behaviour, but nothing changed.
The sutdown timer is set to 60 minutes.

Has anybody else seen this?

Regards
Aydan

EDIT: also posted in 2.4.0 bugs thread (link)

GeoffR · 04-02-2013, 07:58 AM

It takes 60 seconds for me, but still very annoying. I think it is a well-known 2.4.0 bug.

Thane1 · 04-02-2013, 09:52 AM

Quote:

Originally Posted by Aydan

Has anybody else seen this?

Yes, but I think this was deliberately added when the Mini & Glo came out (those devices and the Touch share firmware code) so that if a sleep cover is accidentally disturbed (i.e. flipped up briefly) it doesn't have to wait the normal timeout period to go back into sleep mode.

I tend to use the smallest font size and occasionally have had my KT "pass out" in mid sentence before I get to the end of the page. As a work around after I turn it on via the switch I just bring up the menu and close it, doing so disables this quick off feature and the Reader will wait till normal specified sleep time before it goes into sleep mode.

Given that the Touch doesn't support sleep covers, as it lacks the hardware to detect if a cover is closed, it would seem logical just to clip out that part of the code (or disable it).

kobokobe · 04-02-2013, 12:34 PM

Quote:

Originally Posted by Thane1

Yes, but I think this was deliberately added when the Mini & Glo came out (those devices and the Touch share firmware code) so that if a sleep cover is accidentally disturbed (i.e. flipped up briefly) it doesn't have to wait the normal timeout period to go back into sleep mode.

I tend to use the smallest font size and occasionally have had my KT "pass out" in mid sentence before I get to the end of the page. As a work around after I turn it on via the switch I just bring up the menu and close it, doing so disables this quick off feature and the Reader will wait till normal specified sleep time before it goes into sleep mode.

Given that the Touch doesn't support sleep covers, as it lacks the hardware to detect if a cover is closed, it would seem logical just to clip out that part of the code (or disable it).

Why do people keep saying this? This is definitely not a feature, it is a bug. If it had been a feature, I'm sure they would've presented it as such, and given users the option to disable it or change the amount of time before auto sleep.

Also, I doubt the low probability of the lid accidentally opening and the relatively trivial ramifications of it (slight battery drain) actually call for such a feature.

jackie_w · 04-02-2013, 01:10 PM

Quote:

Originally Posted by GeoffR

It takes 60 seconds for me, but still very annoying. I think it is a well-known 2.4.0 bug.

It's not just a 2.4.0 bug. It also occurs on v2.1.5.

Aydan · 04-02-2013, 01:13 PM

Quote:

Originally Posted by jackie_w

It's not just a 2.4.0 bug. It also occurs on v2.1.5.

Not on the touch it didn't. I'm sure I'd have noticed.

Regards
Aydan

DNSB · 04-02-2013, 01:14 PM

Quote:

Originally Posted by kobokobe

Why do people keep saying this? This is definitely not a feature, it is a bug. If it had been a feature, I'm sure they would've presented it as such, and given users the option to disable it or change the amount of time before auto sleep.

Also, I doubt the low probability of the lid accidentally opening and the relatively trivial ramifications of it (slight battery drain) actually call for such a feature.

Given the general lack of information from Kobo as to what changes are made whether adding a feature or fixing a bug, you actually expect them to inform us about any changes?

I regard it much as the habit my car has of relocking the doors if I don't open one within 30 seconds of unlocking them from the remote. A feature of questionable use.

As for the sleepcover accidentally opening? I tend to the belief that that can happen fairly easily especially with the home-brewed covers. On the sleepcover I was given, it took a very small movement for the sensor decide the cover was being opened and ending sleep mode. I was never sure whether this was caused by movement in my laptop case or when I dug the Glo out of the laptop case before using it but I did notice that my Glo was often awake when I pulled it out of the laptop case and opened the cover.

Regards,
David

kobokobe · 04-02-2013, 01:43 PM

Quote:

Originally Posted by DNSB

Given the general lack of information from Kobo as to what changes are made whether adding a feature or fixing a bug, you actually expect them to inform us about any changes?

I regard it much as the habit my car has of relocking the doors if I don't open one within 30 seconds of unlocking them from the remote. A feature of questionable use.

As for the sleepcover accidentally opening? I tend to the belief that that can happen fairly easily especially with the home-brewed covers. On the sleepcover I was given, it took a very small movement for the sensor decide the cover was being opened and ending sleep mode. I was never sure whether this was caused by movement in my laptop case or when I dug the Glo out of the laptop case before using it but I did notice that my Glo was often awake when I pulled it out of the laptop case and opened the cover.

Regards,
David

You're comparing the consequences of leaving your car open to your kobo sleep cover opening?

In the case of the car locking itself, the nuisance of unlocking it again is well worth it because of the ramifications of accidentally leaving it unlocked.

jackie_w · 04-02-2013, 01:52 PM

Quote:

Originally Posted by Aydan

Not on the touch it didn't. I'm sure I'd have noticed.

Let me be more specific, then. On my Kobo Glo with v2.1.5 and the sleep cover setting enabled and in use (with a non-Kobo brand sleep cover), the problem exists.

A simple vertical swipe on re-opening the sleep cover works around it well enough.

rjcroy · 04-02-2013, 06:01 PM

This happens on my Touch, firmware 2.4.0. If it is a feature then it is no use to me, and annoying. There should be an option to turn it off.

DNSB · 04-02-2013, 07:08 PM

Quote:

Originally Posted by kobokobe

You're comparing the consequences of leaving your car open to your kobo sleep cover opening?

In the case of the car locking itself, the nuisance of unlocking it again is well worth it because of the ramifications of accidentally leaving it unlocked.

Where did you get the notion that I was comparing the consequences from what I wrote?

Now if the car did not re-lock when I hit the unlock button twice to unlock all the doors, I might not consider the feature of dubious use. But it does and I do.

Regards,
David

Thane1 · 04-02-2013, 09:46 PM

Quote:

Originally Posted by kobokobe

Why do people keep saying this?

Because it’s easy for the cover to open, not all sleepcovers have that elastic strap to keep it closed. A bump here or there and it will turn on. Been looking at this a bit more and I think we are both right, it’s a feature on the Glo & Mini, and in Kobo fashion they have made it a bug on the Touch.

On firmware 2.4.0 for the Glo & Mini, under the Settings menu, Sleep & Power has a second screen which relates to Sleep Cover support. The Touch running the same firmware release doesn't have this extra screen. On the Mini & Touch, if sleepcover support is disabled (by clearing the check box), when the reader is woken from sleep mode via the slide switch the reader will stay on until it goes to sleep after the specified sleep time (i.e. 5 minutes) instead of 60 seconds.

Unfortunately we don't have the option of disabling sleep cover support, the option controlling it is gone, however the short timeout code is still there putting it into sleep about 60 seconds after it has been woken.

davidfor · 04-02-2013, 10:25 PM

It's a bug.

Personally, I don't see the point of the timeout for an accidental opening of the sleep cover in a bag. If that happens, odds are the cover closing will also happen. And if the close doesn't happen, it is probably because something fell in between the cover and the screen and that might cause a touch to the screen and prevent the sleep anyway. And cause damage to the screen. If that is happening, you need to look at why the cover is opening in the first place.

But, I don't have a cover on any sort on either my Glo or Touch. That means that waking either of them is a deliberate action of pushing the power switch. If I have done that, going to sleep any time earlier than my configured sleep options is wrong. So, it's a bug.

murg · 04-03-2013, 08:20 AM

Quote:

Originally Posted by davidfor

It's a bug.

A feature is a bug in a tuxedo...

treadlightly · 04-03-2013, 08:27 AM

This bug doesn't go away if you disable Sleep Cover support on the Glo.

In 2.1.5, the bug occurred when the Glo was awoken via the sleep cover mechanism. In 2.4.0, the bug occurs even if the Glo was awoken via the power slider.

The time before the reader goes back to sleep is proportional to the sleep timeout in Settings. I have the timer for the light expire before the timer to sleep and therefore only the light goes off if I don't touch the screen upon awakening. This gives me a reminder to touch the screen before it sleeps again. Doesn't help for the Touch unfortunately.

04-02-2013, 07:29 AM	#1
Aydan Connoisseur Posts: 87 Karma: 2975 Join Date: Jan 2012 Location: Germany Device: Kobo Touch	Bug: KT goes to sleep shortly after being woken I found a very annoying bug in the 2.4.0 firmware over the weekend: Whenever I woke my Touch from sleep it would go back to sleep after only maybe half a minute if I didn't touch the screen before. My sleep timer was set to 5 minutes, I changed it to 10 minutes to see if it changes the behaviour, but nothing changed. The sutdown timer is set to 60 minutes. Has anybody else seen this? Regards Aydan EDIT: also posted in 2.4.0 bugs thread (link) Last edited by Aydan; 04-02-2013 at 07:41 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Paperwhite bug: Light stayed on while in sleep	mroek	Amazon Kindle	3	01-17-2013 06:39 AM
Nov Patch doesn't fix Wake-from-Sleep bug	borisb	Kobo Tablets	77	12-04-2011 09:06 PM
Bug Discovered in Sleep / Power Off - v1.4 Firmware	Ghoda	Kobo Reader	20	08-05-2010 09:56 AM
DRM coming 'shortly'	artifact	Ectaco jetBook	2	11-10-2009 10:56 PM

04-02-2013, 07:58 AM	#2
GeoffR Wizard Posts: 3,821 Karma: 19162882 Join Date: Nov 2012 Location: Te Riu-a-Māui Device: Kobo Glo	It takes 60 seconds for me, but still very annoying. I think it is a well-known 2.4.0 bug.

04-02-2013, 06:01 PM	#10
rjcroy Bibliophile Posts: 167 Karma: 1147338 Join Date: Jun 2010 Location: New Zealand Device: Sony PRS-T3, Kobo Touch	This happens on my Touch, firmware 2.4.0. If it is a feature then it is no use to me, and annoying. There should be an option to turn it off.

04-02-2013, 10:25 PM	#13
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	It's a bug. Personally, I don't see the point of the timeout for an accidental opening of the sleep cover in a bag. If that happens, odds are the cover closing will also happen. And if the close doesn't happen, it is probably because something fell in between the cover and the screen and that might cause a touch to the screen and prevent the sleep anyway. And cause damage to the screen. If that is happening, you need to look at why the cover is opening in the first place. But, I don't have a cover on any sort on either my Glo or Touch. That means that waking either of them is a deliberate action of pushing the power switch. If I have done that, going to sleep any time earlier than my configured sleep options is wrong. So, it's a bug.

04-03-2013, 08:27 AM	#15
treadlightly Wizard Posts: 1,370 Karma: 6957792 Join Date: Nov 2010 Location: Ottawa, ON Device: Kobo H2O	This bug doesn't go away if you disable Sleep Cover support on the Glo. In 2.1.5, the bug occurred when the Glo was awoken via the sleep cover mechanism. In 2.4.0, the bug occurs even if the Glo was awoken via the power slider. The time before the reader goes back to sleep is proportional to the sleep timeout in Settings. I have the timer for the light expire before the timer to sleep and therefore only the light goes off if I don't touch the screen upon awakening. This gives me a reminder to touch the screen before it sleeps again. Doesn't help for the Touch unfortunately.

Advert

Advert