MobileRead Forums - View Single Post - Touch Kobo Touch tuning on randomly by itself

FJames · 07-24-2011, 02:52 PM

I saw mine turn on by itself today. Not so coincidentally, it was about 5 minutes after I turned it off, and my Sleep timer is set to 5 minutes. So I would guess that the self-turning-on is probably due to a firmware bug which fails to cancel the Sleep timer when powering off.

I discovered an interesting aspect of another bug today too - the delayed double page turn. I tapped to turn the page, and nothing happened. Since it was a fairly firm tap (not a light brush), I was sure it should have registered, so I waited a couple of seconds to see if there was a delayed response. It wasn't at the end of a chapter or anything, so there shouldn't have been a delay, but I waited anyway - and nothing happened. Until I tapped again, and then it instantly turned two pages.

The page turn normally doesn't trigger until you lift your finger to complete a touch, so it looks like this bug may be due to "finger up" not being recognized until you tap again.

07-24-2011, 02:52 PM	#55
FJames Addict Posts: 320 Karma: 320941 Join Date: Jun 2011 Location: Canada Device: Kobo Touch & Aura	I saw mine turn on by itself today. Not so coincidentally, it was about 5 minutes after I turned it off, and my Sleep timer is set to 5 minutes. So I would guess that the self-turning-on is probably due to a firmware bug which fails to cancel the Sleep timer when powering off. I discovered an interesting aspect of another bug today too - the delayed double page turn. I tapped to turn the page, and nothing happened. Since it was a fairly firm tap (not a light brush), I was sure it should have registered, so I waited a couple of seconds to see if there was a delayed response. It wasn't at the end of a chapter or anything, so there shouldn't have been a delay, but I waited anyway - and nothing happened. Until I tapped again, and then it instantly turned two pages. The page turn normally doesn't trigger until you lift your finger to complete a touch, so it looks like this bug may be due to "finger up" not being recognized until you tap again. Last edited by FJames; 07-24-2011 at 02:54 PM.