![]() |
#1 |
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Jul 2015
Device: Samsung note3
|
Problem with Google Drive
Hi,
I'm trying to get the companion (on note3, rooted, android 5.0) to work with Google drive. I need the backup facility, because, out of necessity but very reluctantly, I'm moving away from my home linux server with automatic backup. I've read the thread, and understand the inherent risks. I'm getting as far as the download requester of a book without anything seemingly out of the ordinary, but then it shows an error that it cannot find the file (see attachment). Any book I try gives this error. In an attempt to find the problem myself, I downloaded Calibre 2.33 and installed it on windows, pointed it to my google drive local folder where I copied the library (OLD, version 0.9) and did some work to make sure the database was touched, like doing a clean/repair of the database and fixing some authors. It can open any books I try fine. Everything was fully synched before I tried last with the companion. It still behaved the same. I then found the 'calibre cloud' app for android and installed that. This works fine, no issues, I have additionally downloaded randomly several books. My last measure was to reset the cloud connection in the companion. When connecting again I noticed no less then 3 directories 'Calibre' in the folder selector dialog (I put the 'Calibre' folder directly under google drive root btw). I took the top one. Also, I have been using Calibre companion for years connecting to the service on my linux server, but did NOT completely remove the app with data out of fear it somehow would mess up my list of read books. I just upgraded and switched it to the cloud connection. As said, everything seems to work fine except the download bit in the companion... Any advise on what to do next? Can I safely remove the app completely and install it fresh? Thanks for any help, Frank |
![]() |
![]() |
![]() |
#2 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,353
Karma: 8012652
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Moderator Notice
Moved to its own thread because it might be of general interest and easier to find. |
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,353
Karma: 8012652
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
First issue: the multiple libraries in the folder chooser. This happens because of a bug I ran into myself 2 days ago. The extra libraries have been deleted in Drive, probably because you did what I did: deleted the library then copied a new one with the same name. Unfortunately with the current CC version there is no way to determine which library is really there. Try all three, although I am not convinced that it will work. Another thing with perhaps a better chance of working is to permanently delete the other copies from Drive's Trash folder.
The next CC release fixes this bug. I would make a release now, except that I just switched development environments because Google decided to stop supporting the one I was using. I am not sure if I broke something. I was planning to run through a quick beta cycle before making the release generally available. I can send you an intermediate version that you would need to manually install. It is an "official" version so it won't require uninstall or reinstall. If you are willing then send me a PM with the email address where I should send the APK. Be sure to tell me which version (demo or paid) you are running so I can send you the correct APK. [EDIT] If you have been using CC for years then it is the paid version, given that the demo version hasn't existed for years. ![]() Back to Drive: CC is apparently finding a metadata.db file. What we don't know is which one. The way Drive versioning and parenting works it could easily be the correct db in the incorrect library. Second issue: assuming that the above doesn't fix it then I will need a CC debug log. When you try to download a book the path in the calibre library is logged. In fact, if you send the log to yourself then you can verify that the path CC finds in the metadata.db file really exists in the library. If there is nothing obvious then forward the log to me, cc_debug_logs [AT] charles [DOT] haleys [DOT] org. I might see something there that helps find what is going on. Another possibility: CC will fail like that if your books are stored on an SD card and for some reason CC cannot write the book. Can you download a book with the content server with the same CC installation? If so then the cloud connection should have no problem. As for uninstall and reinstall: that is a last resort that probably won't fix anything. You will lose your CC database, requiring you to resend all the books. Last edited by chaley; 08-07-2015 at 09:54 AM. |
![]() |
![]() |
![]() |
#4 |
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Jul 2015
Device: Samsung note3
|
Cleaning the Google dustbin did the trick :-)
I'm very happy. Now I can get to my library from all over the world and don't have to worry about backups (well, you know, within reason ;-), will keep a copy anyway... Thanks for a great app! |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
PRS-T1 PRS t1 and Google drive | bla | Sony Reader | 21 | 09-16-2013 06:44 AM |
Problem setting up shared library on Google Drive | CyberPotato | Library Management | 5 | 02-04-2013 05:01 PM |
Google Drive Incompatable with Calibre! | Yack | Related Tools | 10 | 02-02-2013 05:37 AM |
Problem Sync with Ez PDF and Google Drive | cptnemo | Android Devices | 0 | 09-27-2012 09:33 PM |
PRS-T1 Google Drive | JB. | Sony Reader Dev Corner | 1 | 04-25-2012 08:02 PM |