MobileRead Forums - View Single Post - Glo HD 3.18.0 Battery Drain Bug with Sync?

endrancer · 10-03-2015, 09:03 AM

Hey,

I have been wondering, since 3.18.0 when leaving my kobo in standby I was shocked to see my battery falling down to 10% within one day. First I thought it might have activated itself in my cover using the brightness on max however this theory is destroyed today as I found my kobo being 45 % after I recharged in completely in just a day.

When accessing the kobo I saw it was trying to sync files (look for updates, check out if there are new pocket items ) when pushing the sync button several times again, I found that nothing happened. And on the Statusbar I could see the Sync coloumn trying to do it's thing. The "last sync" information showed date with when the sync actually completed the last time.

I just rebooted my device (without pin though the hole) and it seems now not trying to sync for itself and I could finish a sync manually.

So I am wondering if this is a known bug, if anyone else experienced this issue.

10-03-2015, 09:03 AM	#1
endrancer Enthusiast Posts: 25 Karma: 5010 Join Date: Sep 2015 Device: Kobo Glo HD	Glo HD 3.18.0 Battery Drain Bug with Sync? Hey, I have been wondering, since 3.18.0 when leaving my kobo in standby I was shocked to see my battery falling down to 10% within one day. First I thought it might have activated itself in my cover using the brightness on max however this theory is destroyed today as I found my kobo being 45 % after I recharged in completely in just a day. When accessing the kobo I saw it was trying to sync files (look for updates, check out if there are new pocket items ) when pushing the sync button several times again, I found that nothing happened. And on the Statusbar I could see the Sync coloumn trying to do it's thing. The "last sync" information showed date with when the sync actually completed the last time. I just rebooted my device (without pin though the hole) and it seems now not trying to sync for itself and I could finish a sync manually. So I am wondering if this is a known bug, if anyone else experienced this issue.