Calibre Stops Working

[stingo390]

When I plug my Android Tablet into my Laptop and then open Calibre, after a varying amount of time I get this error:



I have let the 'jobs' run for well over 30 minutes but it never completes before the above error happens.

I have also searched these forums and tried the 'ignore device', but then I cannot upload books to the device, which is the whole point of Calibre, isn't it?

My Laptop has Win7
The device is a Samsung Galaxy Tab 4
I have the latest ver of Calibre 64 bit.

Any ideas?
Thank you

[theducks]

Originally Posted by stingo390

When I plug my Android Tablet into my Laptop and then open Calibre, after a varying amount of time I get this error:



I have let the 'jobs' run for well over 30 minutes but it never completes before the above error happens.

I have also searched these forums and tried the 'ignore device', but then I cannot upload books to the device, which is the whole point of Calibre, isn't it?

My Laptop has Win7
The device is a Samsung Galaxy Tab 4
I have the latest ver of Calibre 64 bit.

Any ideas?
Thank you

First of all,that message is from Windows.
Does calibre work normally WITHOUT the TAB4?

I suspect there is a filesystem error on the TAB. What task was being done when this happened?

You could start Calibre in DEBUG mode (Preference (menu)) Ctrl-shift-R
and post the log when it crashes

[stingo390]

Originally Posted by theducks

First of all,that message is from Windows.
Does calibre work normally WITHOUT the TAB4?

Yes, I think so.

I suspect there is a filesystem error on the TAB. What task was being done when this happened?

Nothing - all apps on the tab were closed.

You could start Calibre in DEBUG mode (Preference (menu)) Ctrl-shift-R
and post the log when it crashes

Will post the log when it crashes again.

Thanks for your input.

[theducks]

Filesystem is Storage (SD...) I don't know when/if Android does o disk check.
Have you cold booted the TAB (power OFF, Power ON. You will see the Samsung splash screen)

By Task, I meant Calibre task. Send, or the basic connect and poll the device fo what books...

[stingo390]

Okay. I have removed the SD card and rebooted the tab.

Calibre's icons change when I connect the tab, so I think it must be working correctly.

[stingo390]

It just crash after 22 min 57 sec and here is the log:

calibre Debug log
calibre 2.49 [64bit] isfrozen: True is64bit: True
Windows-7-6.1.7601-SP1 Windows ('64bit', 'WindowsPE')
('Windows', '7', '6.1.7601')
Python 2.7.9
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
Starting up...
Started up in 8.45 seconds with 22 books
Job: 1 Get device information started
DeviceJob: 1 Get device information done, calling callback
DeviceJob: 1 Get device information callback returned
Job: 2 Set library information started
DeviceJob: 2 Set library information done, calling callback
DeviceJob: 2 Set library information callback returned
Job: 3 Get list of books on device started
MTP: Loading filesystem metadata...
Job: 1 Get device information finished
No details available.
Job: 2 Set library information finished
No details available.
MTP: Ignored object: Samsung
MTP: Ignored object: Ringtones
MTP: Ignored object: Pictures
MTP: Ignored object: DCIM
MTP: Ignored object: Android/obb
MTP: Ignored object: Android/data/com.android.providers.media
MTP: Ignored object: Android/data/com.google.android.videos
MTP: Ignored object: Android/data/com.google.android.youtube
MTP: Ignored object: Android/data/com.sec.android.gallery3d
MTP: Ignored object: Android/data/sstream.app
MTP: Ignored object: Android/data/com.ui.LapseItPro
MTP: Ignored object: Android/data/com.google.android.apps.magazines
MTP: Ignored object: Android/data/com.google.android.apps.maps
MTP: Ignored object: Android/data/com.wildtangent.android
MTP: Ignored object: Android/data/com.android.vending
MTP: Ignored object: Android/data/com.sec.android.nearby.mediaserver
MTP: Ignored object: Android/data/com.sec.android.allshare
MTP: Ignored object: Android/data/com.google.earth
MTP: Ignored object: Android/data/it.navionics.singleAppMarineLakes
MTP: Ignored object: Android/data/uk.co.aifactory.backgammonfree
MTP: Ignored object: Android/data/com.ovital.ovitalMap
MTP: Ignored object: Android/data/com.google.android.gms
MTP: Ignored object: Android/data/com.google.android.apps.docs
MTP: Ignored object: Android/data/com.app4nav.android.weather4d
MTP: Ignored object: Android/data/uk.co.aifactory.solitairefree
MTP: Ignored object: Android/data/com.socialnmobile.dictapps.notepad.color.note
MTP: Ignored object: Android/data/com.hancom.office.hword.viewer.hword_apk
MTP: Ignored object: Android/data/com.hancom.androidpc.viewer.launcher
MTP: Ignored object: Android/data/com.hancom.office.hcell.viewer.hcell_viewer_apk
MTP: Ignored object: Android/data/com.skype.raider
MTP: Ignored object: Android/data/com.frozenape.tempo
MTP: Ignored object: Android/data/com.frozenape.tempolite
MTP: Ignored object: Android/data/com.android.chrome
MTP: Ignored object: Android/data/org.videolan.vlc
MTP: Ignored object: Android/data/org.opencpn.opencpn_free
MTP: Ignored object: Android/data/com.google.android.apps.translate

[theducks]

I see no crash in the log.

Is your power management shutting down the USB port?

[stingo390]

calibre 2.49 [64bit] isfrozen: True

What about the 'isfrozen' part?

[theducks]

Originally Posted by stingo390

What about the 'isfrozen' part?

You have a Disney (Elsa) product?

I really don't know, except it is a normal part of the message on my 32 or 64 bit systems

[kovidgoyal]

Originally Posted by stingo390

What about the 'isfrozen' part?

It means the calibre build is frozen, i.e. running from a binary build, not a developmental build. There are a few devices that cause a crash to happen in the windows portable device interface that calibre uses, but since I have never been able to get my hands on such a device, I have never been able to fix it. You should just use one of the wireless connection methods described here: http://manual.calibre-ebook.com/faq....kindle-fire-hd

[stingo390]

Thanks, Kovid. I'll try that method and report back.

How difficult would it be to remove that part of the automated jobs and instead have a prompt, with a browse button, that asks which folder to search for books, which then sets the configuration and then checks for what books are on that device. Possibly also with a tick box that says something like Do not ask this again?

[kovidgoyal]

You can configure the folders to search on the device -- but only after calibre has connected to the device the first time successfully --after all , it has to get the lsit of folders on the device from somewhere.

[stingo390]

Not being a programmer, I won't understand all the intricacies of Calibre, but I don't understand why it needs to have a list of all the folders? Surely it only needs to know which folder the books are stored and selecting that folder, once, the first time Calibre opens should be good enough? Or have I missed something?

And once it is configured to look at that folder, it would be easy to change the folder by redoing the configuration eg if you have a folder for thrillers and another for sci-fi, for example.

That way, there would be no need to search the device, which takes absolutely ages and so far (for me) has never completed.

[stingo390]

p.s. just thinking about it, you still only need one folder eg /books/ and you could then have sub-folders for genre or authors or what ever makes your clock tick.

[theducks]

Originally Posted by stingo390

Not being a programmer, I won't understand all the intricacies of Calibre, but I don't understand why it needs to have a list of all the folders? Surely it only needs to know which folder the books are stored and selecting that folder, once, the first time Calibre opens should be good enough? Or have I missed something?

And once it is configured to look at that folder, it would be easy to change the folder by redoing the configuration eg if you have a folder for thrillers and another for sci-fi, for example.

That way, there would be no need to search the device, which takes absolutely ages and so far (for me) has never completed.

Because of the way people choose to arrange their device (after what the manufacturer decides to allow). Chaos! We are THE KING, we will NOT have your standards. So brilliant developers are forced to poll the entire device to learn HOW this one was done (and what the user has done on top of that)