03-16-2018, 03:41 AM | #1 | |
Wizard
Posts: 1,158
Karma: 32196
Join Date: Jan 2007
Location: Anchorage, AK
Device: Sony Reader PRS-505, PRS-650, PRS-T3, Pocketbook HD2
|
SD Card on Oreo (Android 8)
Moderator Notice Created a new thread. Quote:
Last edited by chaley; 03-16-2018 at 05:56 AM. |
|
03-16-2018, 06:08 AM | #2 | |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
If you formatted the SD card on a different device then CC probably won't have permissions to see the contents. The only way around that is to reformat the card in the device where it is being used. However, rather than speculate, the best would be for you to send me a CC debug log as described here. That way I can see where it fails and whether you have one of the rather rare devices where Oreo broke accessing the private app folder. It is worth noting that starting in Nougat (Android 7), Google has totally broken sharing files between apps. Later this year CC will be forced to hand copies of books to reader apps instead of pointing the reader app at CC's local copy. I know that this is terrible but there is zero I can do about it. If I don't implement this stupid system then later in the year I must stop releasing CC updates. Last edited by chaley; 03-16-2018 at 12:50 PM. Reason: Clarify the effect on CC of the google change |
|
03-16-2018, 12:08 PM | #3 | |
Guru
Posts: 608
Karma: 5007204
Join Date: Sep 2014
Location: Calif
Device: Fire hdx 8.9, Tab S2, Tab S5e, Aura ONE
|
Quote:
The ipad is just a terminal to icloud to make more money for crapple. |
|
03-16-2018, 12:37 PM | #4 |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
It has already happened. Google's change is why CC does not "target" (implement/respect the rules of) Android releases beyond 6 (Marshmallow).
As I said above, unfortunately starting later this year Google is requiring that new and updated apps target the latest Android. The result: either I stop maintaining CC, or I follow the rules and pass copies of books to apps. If you care, Google's announcement is here. |
03-16-2018, 04:21 PM | #5 | |
Guru
Posts: 608
Karma: 5007204
Join Date: Sep 2014
Location: Calif
Device: Fire hdx 8.9, Tab S2, Tab S5e, Aura ONE
|
Quote:
The extra "securities" will degrade performance rather than an improvement. I have a copy of the ios 11 epub manual & ireader sees it as readable IF it is located on a hi level directory; if moved to a folder, ios says it does not understand the format & one has to send a copy to an app (reader) for load/read. Wonder if windows tablets will go the ios way also. or perhaps CC can hopefully be ported over to a "linux tablet" if necessary ..... |
|
03-17-2018, 02:26 AM | #6 | |
US Navy, Retired
Posts: 9,864
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Nexus 7
|
Quote:
Color me ignorant, WTF are you talking about? |
|
03-17-2018, 01:48 PM | #7 |
Guru
Posts: 608
Karma: 5007204
Join Date: Sep 2014
Location: Calif
Device: Fire hdx 8.9, Tab S2, Tab S5e, Aura ONE
|
If Google goes the crapple's ios way, then there will not be file sharing; a reader app cannot select a book from a folder to read but must have its own copy/duplicate of the book. Each app is sandboxed(?) within its own environment. Android CC will have to do like IOS CC where CC will have to send a copy of the book to a reader app.....lots of duplicates to use up memory/ram.
Read the Oreo specs(?)/features that any app that over-uses resources will be removed. Will CC be penalized for over usage when creating multiple copies of books for various reader apps? or will the reader app? What constitute "over use of resources"?. The Galaxy Tab S4 will be released with Oreo which is headed to be more like IOS & should be avoided by me. Then did come across an item that claims Google wants to head to cloud oriented tablets, like apple. The ios 'file manager', files is only for the icloud & is not allowed to display or manage anything on the ipad. |
03-18-2018, 12:20 AM | #8 | ||
US Navy, Retired
Posts: 9,864
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Nexus 7
|
Quote:
Quote:
|
||
03-18-2018, 11:19 AM | #9 |
Wizard
Posts: 1,759
Karma: 30063305
Join Date: Dec 2006
Location: Singapore
Device: Boyue
|
Personally I think chaley when calibre companion hits the point where he cant update without losing functionality due to google restrictions should abandon the app. And release calibre companion 2 with built in reader and editor for android 8 and above.
|
03-26-2018, 10:25 PM | #10 | ||
Wizard
Posts: 1,158
Karma: 32196
Join Date: Jan 2007
Location: Anchorage, AK
Device: Sony Reader PRS-505, PRS-650, PRS-T3, Pocketbook HD2
|
Quote:
Quote:
Best Regards, Amalthia |
||
03-27-2018, 03:26 PM | #11 |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Thanks for the debug log. Unfortunately what it shows is the worst I could imagine. Oreo on your device is refusing to honor fixed file path names, instead insisting that the damned Storage Access Framework (SAF) be used. Not all devices require this (mine don't), but enough seem to do so that I can't ignore it.
The consequence: to fix this I must update CC to respect the Nougat+ SAF rules that file paths cannot be used internally in an app and cannot be passed to other (reader) apps. Instead, CC must use SAF mechanisms, which means that CC must pass copies of books to reader apps instead of the original file name. I knew that Google has said I would need to do this by the end of the year in order to be permitted to update CC, but apparently I must deal with it now. I am currently testing the changes. They are significant enough that I will run an alpha test cycle then beta test. I need to be sure that I haven't broken anything on pre-Nougat Android, that it works on Nougat/Oreo and higher, and that it works with a range of reader apps. Sigh ... |
03-27-2018, 11:29 PM | #12 |
Wizard
Posts: 1,158
Karma: 32196
Join Date: Jan 2007
Location: Anchorage, AK
Device: Sony Reader PRS-505, PRS-650, PRS-T3, Pocketbook HD2
|
Well it's good to know the problem isn't something I'm doing, though I'm sorry to hear about all the work ahead of you on updating the app.
Thanks for looking into the problem. |
04-04-2018, 08:37 AM | #13 | |
Guru
Posts: 995
Karma: 4407864
Join Date: Feb 2009
Location: North Carolina
Device: Kobo Aura1, Nexus7.2, Galaxy Tab A 8.4, Ipad Air & Mini 6
|
Quote:
I disagree that cc should have a built in reader - just reading the forums of various readers show that we are all diverse in what we like on a reader app. Again, a tremendous burden on chaley. Including a reader in cc would get out of hand (I think). Case in point, I totally love Calibre and am so greatful for it, but with each update with more features, it loads and runs slower and slower. |
|
04-04-2018, 11:34 AM | #14 | |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
|
|
04-04-2018, 12:55 PM | #15 |
Member
Posts: 11
Karma: 10
Join Date: Apr 2018
Device: Samsung S23 Ultra
|
I truly hope that you choose option 1. Please.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Looking for Ereader w/SD Card & Probably Android | akasha | Which one should I buy? | 29 | 01-29-2019 02:10 PM |
[Android] SD Card | Tega57 | Calibre Companion | 2 | 08-17-2017 12:39 PM |
Android 4.4.2 - Library on device (SD Card) | AndyT1 | Calibre Companion | 1 | 01-24-2017 05:59 PM |
Android 4.2 - storing books on SD card? | flyash | Calibre Companion | 2 | 12-30-2015 04:25 PM |
Android device where ONLY the SD card is visible | MikeMJ | Devices | 5 | 07-06-2012 10:06 PM |