View Single Post
Old 08-11-2013, 01:41 PM   #2
jackastor
Wizard
jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.
 
jackastor's Avatar
 
Posts: 1,847
Karma: 3212428
Join Date: Jun 2011
Device: iphone stanza, kobo touch,ASUS TF300,KOBO GLO, Kobo Aura HD, Kobo Mini
Quote:
Originally Posted by BobC View Post
Some time since I experienced problems with my Glo disconnecting from my PC -

https://www.mobileread.com/forums/sho...&postcount=214

I have now done a lot more delving into what is happening and it is clear that the problem was triggered when Calibre was sending Metadata to the device, either after getting the list of books on connection or after books had been uploaded to the Glo.

Further investigation made it appear that this happened at the end of the Metadata upload following an attempt to delete empty shelves. This interested me as I didn't think I had any shelves eligible for deletion.

I realised that some Kobo books I had downloaded might be sat on "invisible" shelves (I had problems with duplicated shelves that couldn't be deleted in the past) such as the Glo's "Im_Reading".

I solved the problem (fingers crossed) by deleting all Kobo books from the device (they were redundant anyway) and synching the Glo. After this the phantom disconnects have not re-occurred.

It looks like it's possible to get the Glo's database into a condition where some Metadata update by Calibre will cause it to trigger the disconnect.

I know a few other folk (not many) have had a similar problem and they might want to see if any of the above applies to them.

BobC
I had this happen quite a bit in last week. The problem was a faulty Micro usb cable. If it happens again for you, you may want to consider replacing the the usb cable with a brand new one.

regards

JAck
jackastor is offline   Reply With Quote