Quote:
Originally Posted by PatNY
The odd things is I have another LG phone set up about a year ago almost identically to this new Volt, also running KitKat 4.4.2 and CC is writing to the external card just fine – to the exact same folder location on the external card that I am now trying to write to with the new phone. This older LG phone is running CC 4.2.8.4. Thinking you might have made a very recent change to CC, I even put CC 4.2.8.4 on the new phone, but it still can’t access the card.
|
There have been no changes to how CC handles SD cards in a very long time.
Quote:
When I try to connect with the new phone to Calibre by either the content server or other methods, a message pops up saying “CC cannot connect because the following book formats are stored in a read-only folder …”
|
This means that Android told CC that CC is not allowed to write the folder. There is nothing CC can do about that.
Quote:
When I try to manually select the folders on the external card with CC, the furthest I can browse to is the “media_rw” folder and when I click that to try to get to “external_SD” instead I get this: “There was an error with the folder chosen and it could not be opened …”
|
Have you checked the box in CC Settings / Other / SD Cards on Android 4.4+? My guess is yes or you wouldn't be getting as far as you are.
Like the last one, that error comes from Android. I don't know why CC is being blocked.
Quote:
As a last resort, I could live with having to put books in only the private Android folder on the external card, but since I can’t browse to “external_SD,” I can’t even specify CC's private folder.
|
If you turn off the option mentioned above then you should be presented with the choice of using the private folder. If you are not then CC can't write it.
I suspect that the SD card was formatted on a different device. Android keeps all sorts of strange permissions for SD cards and often they cannot be moved between devices. I suggest that you uninstall CC, reformat the SD card, then reinstall CC. The device should then be able to get the permissions right.
If the above doesn't work then I am stumped. We will need to take the debug-log approach in hopes that there is more info about the error in that.