View Single Post
Old 10-13-2012, 07:16 PM   #4
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,477
Karma: 26012492
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@Amogh Harish: My bad, completely missed the 'Android 2.3' comment, which, yeah, would point to USBMS, not MTP .

That said, if, with the exact same Calibre version, Calibre 'sees' it on Windows, and not on Linux, I'd still go with a permissions issue/a broken udisks setup.

EDIT: Barring that, you can also try to add your device's VID/PID/BCD tuple to Calibre's android driver (src/calibre/devices/android/driver.py), the device matching might in fact be slightly different on Linux than on Windows, so, maybe not a permission issue after all .

Last edited by NiLuJe; 10-13-2012 at 07:29 PM.
NiLuJe is offline   Reply With Quote