Thread: Kobo Glo HD
View Single Post
Old 07-21-2015, 11:32 PM   #1471
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 rgeorg View Post
I just have gotten around to trying the Kobo Touch Extended Plugin. I did the following
1. Disconnected the GloHD
2. Installed the Kobo Touch Extended Plugin
3. Went to Preferences->... and disabled the Kobo Touch 2.1.7 by David Forrester
4. Closed and re-opened Calibre
5. Connected the GloHD

Calibre did not recognize the device. So, I disconnected the device, went back to Preferences->Plugins->...and disabled "Kobo Reader Device Interface" as well. Closed and Opened Calibre. Reconnected GloHD - still not recognized.

Any suggestions as to what I am doing wrong?
What version of calibre are you running? If you have a version of calibre that supports the Glo HD, the extended driver should be working. It extends the main KoboTouch driver and all the device recognition code is done in main driver. The only thing I can suggest is to post a debug log from calibre. This will show what happens when the calibre is started and the device is connected. From that, I should be able to see what is happening.

To create a debug log, right click on the preferences button in calibre and select "Restart in debug mode". Calibre will start and display a message about the log. Connect the device and wait for the connect jobs to finish. If these don't run, go to the preferences and then the "Miscellaneous" page and run the device detection debug. After this or the device jobs finish, close calibre. The debug log should be displayed. Post the contents or send them to me to look at.
Quote:
BTW - I also had a battery problem like the one described. Out of the blue the battery started to run down in a few days rather than a few weeks. Deleted a .mobi book that seemed oddly formatted and a couple of other non .kepub books, gave it a good overnight charge - and all seems better today.
That's interesting. I can't see how just having the book on the device could cause. But, I suppose if there is a problem with it, then closing it might not work properly. That might leave a process in the background using CPU and hence battery. If that is the cause, a power off and on should remove the process and go back to the normal battery life. Do you still have the book? I'd be interested in trying to reproduce this.
davidfor is offline   Reply With Quote