View Single Post
Old 06-25-2020, 10:04 AM   #22
chaley
Grumpy old git
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 9,204
Karma: 2901910
Join Date: Jan 2010
Location: UK
Device: Many android devices
Quote:
Originally Posted by stumped View Post
but the CC app is what reports the space back to calibre? so it will need fixing eventually to always give accurate results, when there is lots of space only on SD external?
Of course. But (assuming I am right about the problem) there is no need to faff about building large libraries and whatnot. The devs can fix it however they want. The OP can revert or live with it until it is fixed. Or slightly more radical, the OP can run calibre from source and remove the check. IIRC it is two lines of code. Hmm ... perhaps I could add an option to calibre to ignore the space reported.

If reverting doesn't "fix" it then more diagnostic efforts will be needed.
chaley is offline   Reply With Quote