View Single Post
Old 09-27-2013, 10:08 AM   #1
jkr
Junior Member
jkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to beholdjkr is a marvel to behold
 
Posts: 7
Karma: 11514
Join Date: Aug 2013
Device: Kobo glo
Expected Battery Life (and customer service frustration)

Dear all,

I have a glo, currently running 2.8, that I got last December. Currently the battery life is abysmal: if it's fully charged and in standby, it will go down to nothing in a few days. Worse than my wife's iphone, than a tablet, etc.

I assume this is some problem with the firmware/hardware. It certainly wasn't this way when I bought it. My concern is that when I called Kobo to ask about it, they told me that after six months, this is what is pretty much expected. They further said the one month of battery life is based on reading thirty minutes or less with wifi and light off, and then shutting it off altogether. So, essentially 30 x 30 = 900 minutes = 15 hours powered on. Again, worse than almost any tablet or smartphone I've come across.

On the whole, my conversation with (the very nice and polite) customer service was quite frustrating: first my problem was that I wasn't chargin it 4-6 hours a day. When I said I had been, they said that if I was charging it overnight, my problem was overcharging. And so on -- the essential gist was that, after owning it six months, one or two reads in week was what I could expect.

Now, I love the device (this problem notwithstanding) and if this is actually just a rare glitch, I'd probably suck it up and buy the new aura to replace it. But what I'm concerned about is that they swear up and down that this is expected behavior. Is this correct? Should I expect a dead battery after two or three days on standby with future devices? Or was I getting the runaround? That would be annoying, but at least it would mean that a new device would likely not have this problem.

Thanks,
Jesse
jkr is offline   Reply With Quote