View Single Post
Old 05-14-2013, 09:48 AM   #20
Uschiekid
Tenrec
Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.Uschiekid ought to be getting tired of karma fortunes by now.
 
Posts: 724
Karma: 1076988
Join Date: Oct 2012
Device: Kobo Aura One, Kobo Glo
Quote:
Originally Posted by ciscopixie View Post
Finally a place to post my bug!

Okay so I've updated (foolishly) to 2.5.2. Now I encountered this issue a few nights ago and every night since then. When I switch my Glo on and activate the Glo light, it won't come on. The only way it works now is if I adjust the brightness one level up and then take it one back to its original setting. Maybe I'm the only one with this issue but ...

I didn't see this bug present in the previous firmware (2.5.1) so I assume its either a new bug or my Glo doesn't like me anymore.
I don't REALLY want to reset back to a previous firmware because I'm absolutely annoyed at sifting through my library to reload my books [yes, I am lazy - it's a uni student thing].

So if anyone can shed light [ha ha] on this issue, let me know!

EDIT: I forgot to include that I read at the lowest setting when this happens. If I test it at one up from the lowest, the light comes on.. but I'm curious to know why it won't do this on the lowest setting in this firmware like it did in the old one
Strange...this is the exact bug some people had with 2.5.0, but was fixed in 2.5.1. I have 2.5.2, but since the initial bug didn't affect me, I can't verify it's back. Maybe some one with the initial bug who has updated to 2.5.2 can verify it's affecting the same people this time around?
Uschiekid is offline   Reply With Quote