04-21-2014, 03:18 AM | #16 | |
Grand Sorcerer
Posts: 11,703
Karma: 6658935
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
|
|
04-23-2014, 11:20 AM | #17 |
Calibre Companion Fanatic
Posts: 873
Karma: 1088610
Join Date: Nov 2006
Device: Galaxy Note 4, Kindle Voyage
|
|
Advert | |
|
04-25-2014, 02:15 AM | #18 | |
Member
Posts: 11
Karma: 10
Join Date: Apr 2014
Device: Moto G Power (2020), various tablets
|
Quote:
The folder also exists on internal memory (what my phone calls "sdcard0"), and there contains only one file; I presume it's the debug log you mention above. There was some problem doing the initial sync, after the move - CC disconnected a couple times. Or at least, calibre reported that it had disconnected - CC was still showing connected and syncing. I canceled and reconnected, then had to do it again - the third time everything got synced. After that I tried adding a book to my phone, and it worked fine. Thanks! |
|
04-25-2014, 02:36 AM | #19 | |||
Grand Sorcerer
Posts: 11,703
Karma: 6658935
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
Quote:
Quote:
My thought is that the SD card might be slower than the main memory. CC uses the network to buffer up some changes. If the SD card is sufficiently slower then calibre might time out, thinking that the device went away. The subsequent syncs would make further progress on that buffer until the buffer gets small enough to finish in the time available. There is almost no downside in making calibre's timeout longer, so I will do that. However, it would be nice to know if I am solving the real problem. |
|||
04-27-2014, 11:44 AM | #20 |
Calibre Companion Fanatic
Posts: 873
Karma: 1088610
Join Date: Nov 2006
Device: Galaxy Note 4, Kindle Voyage
|
|
Advert | |
|
04-28-2014, 10:47 PM | #21 | |
Connoisseur
Posts: 73
Karma: 530904
Join Date: Apr 2011
Device: Sony PRS-950, Onyx Boox M92 and i62HD
|
Quote:
I tried and what happens is the Nexus Media Importer will make a copy of the file onto the internal memory of the Nexus 7 and then the reader program will launch. And no, I can't open a reader program and then browse to the file. I also tried to activate WebDav access via the ES File Explorer program that can access the media via localhost FTP, but I could not get it to work. What's interesting is I also have a Samsung Galaxy Note II which is suppose to be getting KitKat and the phone has a microSD card slot which I don't see Samsung abandoning. It get's mounted so I'm certain Samsung is going to develop some way to handle this quirk with mounting the memory card. It's too bad someone hasn't come up with a way to mount media that doesn't involve rooting. Regards, Jim |
|
05-02-2014, 01:10 AM | #22 | |
Member
Posts: 11
Karma: 10
Join Date: Apr 2014
Device: Moto G Power (2020), various tablets
|
Quote:
I've had absolutely no problems opening books - it works perfectly, and exactly as it used to. I use FBReader, which is set as the default for epubs, and it still works as default - I hit the Read button on a book and it opens, no fuss. Once the library got into that folder, CC went back to working as it used to - books can be passed from calibre, data syncs, and books can be opened and read. Oh, I mentioned this earlier - FBReader apparently writes to a cache of some sort, and I had to move its cache from CC's library to a folder in internal memory. But it apparently _only_ needs to write to cache, it has no problem having its library set to the new CC library folder. |
|
05-02-2014, 10:09 AM | #23 | |
Award-Winning Participant
Posts: 7,310
Karma: 67564074
Join Date: Feb 2010
Location: NJ, USA
Device: Kindle
|
Quote:
The supposed security reasons for the SD change are illogical nonsense. This another in a recent string of stupidly evil Google decisions. I don't know who's running things there now, but it's the wrong person. They are losing my trust. I have so far never felt the need to root any Android device (I tried it on a Kindle Fire, but soon reverted to stock setup), but I will likely have to root any KK because of this. This is a sad sad thing. The freedom of choice in how to use MY DATA, on MY DEVICE, with the apps I CHOOSE has been one of my main arguments for Android over Apple. Last edited by ApK; 05-02-2014 at 10:14 AM. |
|
05-02-2014, 10:17 AM | #24 | |
Calibre Companion Fanatic
Posts: 873
Karma: 1088610
Join Date: Nov 2006
Device: Galaxy Note 4, Kindle Voyage
|
Quote:
Stupid yes, but why do you think evil? They have made a number of bad changes in the last couple of releases (No software control of airplane mode, remove access to battery statistics, the SD card thing), but I don't see why you would consider any of them evil. |
|
05-02-2014, 10:37 AM | #25 | ||
Award-Winning Participant
Posts: 7,310
Karma: 67564074
Join Date: Feb 2010
Location: NJ, USA
Device: Kindle
|
Quote:
Quote:
|
||
05-02-2014, 11:00 AM | #26 | |
Calibre Companion Fanatic
Posts: 873
Karma: 1088610
Join Date: Nov 2006
Device: Galaxy Note 4, Kindle Voyage
|
Quote:
From the Google documentation about this change (bolding mine): ----- The WRITE_EXTERNAL_STORAGE permission must only grant write access to the primary external storage on a device. Apps must not be allowed to write to secondary external storage devices, except in their package-specific directories as allowed by synthesized permissions. Restricting writes in this way ensures the system can clean up files when applications are uninstalled. ---- I guess I don't see how these changes are greedy. Google is trying to get better press by locking down the OS more so that people will stop talking about how it is filled with malware. I don't agree with the way they are doing it, but you can hardly call it greedy. |
|
05-02-2014, 01:47 PM | #27 | |
Award-Winning Participant
Posts: 7,310
Karma: 67564074
Join Date: Feb 2010
Location: NJ, USA
Device: Kindle
|
Quote:
Taking a flexible open system and making it less flexible and open for no good reason is not in the best interest of the user community or the state of the art. Of course, if it turns out the real reason for the change was to sell overpriced internal storage options or sell cloud space, and increase dependency on carrier's expensive data plans, then it's greedy, too. And isn't locking down against malware a security issue? It is in my book. We seem to agree that it's part of the reason, and we seem to agree that reason is illogical nonsense (since apps can still read all data freely, and can arbitrarily write like they always have to internal storage) so I'm not sure that we disagree about anything. Last edited by ApK; 05-02-2014 at 01:50 PM. |
|
05-02-2014, 01:58 PM | #28 |
Calibre Companion Fanatic
Posts: 873
Karma: 1088610
Join Date: Nov 2006
Device: Galaxy Note 4, Kindle Voyage
|
Just the evil vs stupid thing, perhaps.
|
05-02-2014, 02:07 PM | #29 |
Award-Winning Participant
Posts: 7,310
Karma: 67564074
Join Date: Feb 2010
Location: NJ, USA
Device: Kindle
|
Hanlon's Razor, right?
"Never attribute to malice that which can be adequately explained by stupidity." The only problem I have with dismissing it as stupidity is I cannot believe these people are actually stupid. They make some amazing technology, grow it to a billion dollar company while still managing to give most of their products away for free. There have got to be some smart people making decisions. If so, then there is some smart reason behind these decisions, and if those smart decisions are to do stuff that's bad, that's what I call evil in this context. I hope it's just stupidity, I really do. Stupid decisions get corrected, and stupid people get replaced. A corporate trend toward evil would mean I can't trust them, and I may need a new browser (Chrome), new mail system (gmail), new phone number (Google Voice), new phone (Android), and new laptop (Chromebook) and I don't want to change all that! Last edited by ApK; 05-02-2014 at 02:20 PM. |
05-03-2014, 12:27 PM | #30 | |
Calibre Companion Fanatic
Posts: 873
Karma: 1088610
Join Date: Nov 2006
Device: Galaxy Note 4, Kindle Voyage
|
Quote:
I then deleted the whole folder and deleted books with missing files to have a clean library. I then tried copying my whole folder from within calibre. It failed out after about 150 books with a disconnected message. I tried opening the files that had copied, and everything worked fine. If I do a couple of 100 files at a time, it works ok, but anything more then that fails after a while. It should be noted that I have been able to copy my entire folder of several thousand books all at once under 4.3, so perhaps 4.4 is slowing things down. Is increasing the timeout under Calibre a developer change or can I make this change in settings? Still, the good news seems to be that once you get the books loaded, CC seems to work just fine under 4.4. |
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Android KitKat released | Dopedangel | Android Devices | 269 | 12-16-2013 05:48 PM |
Calibre Companion 3.2 (Amazon App Shop Version) + Android 4.4 (Kitkat) wont start | Afkpu | Calibre Companion | 5 | 11-26-2013 11:01 PM |
Nexus 7 (2013) with Android 4.4 (KitKat) & Calibre | jamng | Devices | 4 | 11-22-2013 01:25 AM |
Android 4.4 to be called KitKat | tubemonkey | News | 42 | 09-11-2013 02:05 AM |
Audible for Android new version (rel. 01/22/13) - Supports our removable SDHC cards, | rkw | Android Devices | 4 | 02-01-2013 01:51 PM |