Quote:
Originally Posted by davidfor
I'm pretty sure that the driver used won't affect this..
|
that is correct, when the device is being " unseen" it is unseen by windows as well as unseen by calibre. once a proper connection is made, then it appears in windows as a drive and in calibre as a device, and all is good, until the next time
The on-device screen where it asks for permission to connect to computer and then says connected and charging - that happens i think as soon as the charging pins make contact. it is triggered by the charging pin detection which happens as soon as I just touch the usb cable end to the ports without even pushing it home.
but I have several workarounds not, thanks to the contributors to this thread,
When i look at my various micro usb cable ends, the melal end which goes into the deviceport is shorter/longer on different cables, It could just be a depth thing. the end goes in until stopped by the plastic casing on the cable and it seems touch and go as to whether it goes in far enough. I've lost my genuine kobo cable , so trying with a kindle cable & with various 99p ebay specials
PS if you happen to know the name of the driver / plug in that does epub to kepub conversions in caliber in advnace of connecting the device, that will save me some searching.
I get from the other conmments that such a conversion may no longer be beneficial, but i am used to a particular workflow, and as my son is the actual reader, I don't want him coming back saying that last batch of books you sideloaded all have text that is too small/ too large/ some other defect. Maybe we went for kepub to get the pages left in chapter display to work on the device ? it was a long time ago that I set it all up.
Most of what we sideload are conversions of my amazon books as we shop there, not at kobo, for stuff that can be made to work on all devices