Thread: Thinking about returning to kobo
View Single Post
Old 09-13-2016, 07:12 AM   #44
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by johnnyb View Post
First things first, this has been going on ever since I got my H2O, which was pretty much around the time when it came out. Have been setting up the device numerous times with new firmware releases, fresh databases and all: no changes... (also switched computers in between, new Mac, new fresh system and everything)
then:
1. I don’t use automatic functions of the Extended Driver anymore because these kept messing up the database reliably.
2. Behavior is the same whether I eject from calibre or Finder.
3. Behavior is not occurring when I export kepubs from calibre, close calibre, then connect Kobo, then copy new books to Kobo, then eject (this causes expected database update)
4. I have disabled the „Extended driver“ and tried with regular epubs at some point, no change in behavior.

Wrap up: the USB drivers on the H2O are working somehow but they are so messed up that even slight deviation from their most basic function completely messes them up. This is basically what others in this thread have described as well. Calibre may be an additional culprit, not releasing the devices properly (in some cases) but that should not lead to unrecognized files and database corruption. (additional note: the Kindle Paperwhite I have has zero problems, the Pocketbook I used to own had zero problems, the Sony readers I used to own had zero problems).
With all that, have you tried disabling the KoboTouch driver as well and connecting to the device as a folder? It won't read the database, but it will at least let you see the books on the device. It will be interesting to see if ejecting after that causes any problems.
Quote:
Bottom line: this is really not to do with trying to determine what I am doing wrong but with the H2O not working properly. Ejecting USB devices from operating systems is a really basic operation that has a very simple protocol and if a device acts up while the user adheres to that basic protocol, the user is not to blame. Please don’t try!
My problem with this statement is that no-one else is complaining. In five years of being on this forum and using Kobo devices, and four years of maintaining the KoboTouch driver in calibre, and the only persistent complaint I can think of was some unusual combination of Windows drivers on AMD based machines. And I have had enough bugs reported against the driver and my Kobo Utilities plugin from Mac users to know there are plenty of Mac users not ahve any problems.

The only conclusion I can draw from that is that is something about your Mac. Or some not that common combination of Mac hardware and software. Or something that you are doing. I have absolutely no idea what it could be in any of those cases.

But, one thing, have you tried recently? Because of a change in the database on the device, I had to change the SQLite Python library used in the driver. I also cleaned up some code as I went. If the cause is calibre, it is possible that this has changed enough that the problem no loner exists.
davidfor is offline   Reply With Quote