View Single Post
Old 02-27-2016, 10:40 PM   #6
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,741
Karma: 30237526
Join Date: Mar 2012
Location: Sydney Australia
Device: none
@reup - I think I have the kernel of an answer but I can't fully test because I don't have any working devices here. First a couple of questions.

What device driver do you have selected ?
What operating system do you use ?

If I assume Android and Windows then you could try starting calibre with a command script that looks like this

Code:
calibre-customize --disable-plugin "Android driver"
calibre
The first line disables the Android driver before calibre starts - I assume it sets a flag somewhere in calibre's configuration data, the second starts calibre. To have calibre see the device you'll have to enable the driver via Preferences->Plugins->Device interface plugins->Android Driver->Enable/Disable plug-in. I'm hoping that will trigger the scan.

@theducks, @davidfor etc - maybe someone with a working device can test this out, I'm thinking that after enabling it might necessary to use the Unplugged PI to trigger the scan. Or maybe the OP will need two command scripts - one that disables the device before starting calibre and another that enables the device first.

BR

Last edited by BetterRed; 02-27-2016 at 10:59 PM.
BetterRed is offline   Reply With Quote