MobileRead Forums - View Single Post

davidfor · 08-20-2015, 08:06 PM

This happened with the first Aura H2O I had. The bit that really had me baffled was that the touch would work if the sleep was very short. And "very short" was less than 20 seconds. I did all the things I could think of (factory reset and upgrade, factory reset but not upgrade, fiddle with options, enabled telnet and played there) but nothing helped. When I talked to Kobo, they decided it was a faulty device and I headed back to the shop and had it replaced.

The one thing I don't know is if this happened out of the box. I noticed it the second night I had the H2O, but, I was doing so much mucking around with it, that this could have been happening earlier and I just hadn't left it alone long enough to trigger the problem.

A problem like this can sometimes be fixed by doing a factory reset and upgrade directly to the latest firmware. This will gives the cleanest install of the code possible and means there is little risk of things being left behind that shouldn't be there. You can also do a factory reset and not upgrade to check that it is the new firmware and was not there from the start.

08-20-2015, 08:06 PM	#5
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	This happened with the first Aura H2O I had. The bit that really had me baffled was that the touch would work if the sleep was very short. And "very short" was less than 20 seconds. I did all the things I could think of (factory reset and upgrade, factory reset but not upgrade, fiddle with options, enabled telnet and played there) but nothing helped. When I talked to Kobo, they decided it was a faulty device and I headed back to the shop and had it replaced. The one thing I don't know is if this happened out of the box. I noticed it the second night I had the H2O, but, I was doing so much mucking around with it, that this could have been happening earlier and I just hadn't left it alone long enough to trigger the problem. A problem like this can sometimes be fixed by doing a factory reset and upgrade directly to the latest firmware. This will gives the cleanest install of the code possible and means there is little risk of things being left behind that shouldn't be there. You can also do a factory reset and not upgrade to check that it is the new firmware and was not there from the start.