CC V5.1.3 beta release channel

[chaley]

CC V5.1.3.1 (Beta 1) has been published on the beta channel.

Changes:

• Respect android's maximum file segment name length of 255 bytes, which is anywhere from 128 to 255 characters depending on language.
• Work around yet another Storage Access Framework strangeness. The SAF can add suffixes of the form (1) to file and directory names if the only difference between two names is letter case. With this change, CC detects this situation and uses the current name instead of creating a new (bogus) name.
• Add an option to force the cloud cache into main memory. This can help work around cloud metadata.db corruption problems when SD cards aren't working as expected.

[kaufman]

Originally Posted by chaley

CC V5.1.3.1 (Beta 1) has been published on the beta channel.

Changes:

• Work around yet another Storage Access Framework strangeness. The SAF can add suffixes of the form (1) to file and directory names if the only difference between two names is letter case. With this change, CC detects this situation and uses the current name instead of creating a new (bogus) name.

Works for me. Books are copied correctly and directories are names correctly. I also tried renaming the author back to lower case and the directory was created correctly.

One tiny thing (not worth changing). If you change the author name from upper to lower case, it leaves the directory with the old case, even if this is the only book in it. I assume it would work the same way for the actual filename.

[chaley]

Originally Posted by kaufman

One tiny thing (not worth changing). If you change the author name from upper to lower case, it leaves the directory with the old case, even if this is the only book in it. I assume it would work the same way for the actual filename.

Yes, it indeed works this way. Doing anything else is difficult because a) the folder might not be empty when the book arrives, and b) I don't trust renaming using the SAF. If you delete the book and resend it, the letter case will be correct for that book, and will be used for all subsequent books.

And thanks for the feedback.

[kaufman]

Originally Posted by chaley

And thanks for the feedback.

As always, my pleasure.

[Thomas_AR]

Thanks, the new option to force cloud cache on main memory solved my strange problem CC has with external SD cards, only in connection with cloud cache.

Thomas

[kaufman]

Just found a small issue that is probably not related to the current beta:

I have my "No Grouping" sort set to "Date (calibre) (descending)". This way when I add a book to Calibre, it shows up at the top of the list.

When I copy books via the Wireless connection this works perfectly.

Yesterday I added a few books to calibre and then added them to CC. A few hours later, I added one more book and copied it via the cloud connection. Instead of being first on the "No grouping" list, it showed up after the books that I had added earlier. This morning, I synced again without changing anything in Calibre and it moved to the correct spot (the top of the list).

Is it possible that when you do a cloud transfer, you are picking up the correct date, but using a time of "00:00"? Could it be a time zone thing? I have sent you a log.

[chaley]

Originally Posted by kaufman

Just found a small issue that is probably not related to the current beta:

I have my "No Grouping" sort set to "Date (calibre) (descending)". This way when I add a book to Calibre, it shows up at the top of the list.

When I copy books via the Wireless connection this works perfectly.

Yesterday I added a few books to calibre and then added them to CC. A few hours later, I added one more book and copied it via the cloud connection. Instead of being first on the "No grouping" list, it showed up after the books that I had added earlier. This morning, I synced again without changing anything in Calibre and it moved to the correct spot (the top of the list).

Is it possible that when you do a cloud transfer, you are picking up the correct date, but using a time of "00:00"? Could it be a time zone thing? I have sent you a log.

There is indeed a problem. When dates are sent via the wireless device or content server, calibre converts them to ISO-format strings. The dates in metadata.db are in a format very close to but not the same as ISO. Because of this difference the sorting behaves as you describe.

Fix is in the next beta that should come out today.

[chaley]

Change log:

• Fix format of dates downloaded via the cloud connection so that the "time" fields remain significant when sorting.
• Better logging when CC determines that book directories are not writable
• Updated languages: French, Spanish
• [BUG FIX]Avoid a weird crash seemingly caused by CC's database being closed while operations are running

[kaufman]

Something else I noticed that I forgot to mention.

You throw up a notification for long transfers, but I have seen that if the process aborts abnormally, the notification stays up and is impossible to clear.

[chaley]

Originally Posted by kaufman

Something else I noticed that I forgot to mention.

You throw up a notification for long transfers, but I have seen that if the process aborts abnormally, the notification stays up and is impossible to clear.

Where does this occur? Cloud? Content server? WD? More than one?

[kaufman]

Originally Posted by chaley

Where does this occur? Cloud? Content server? WD? More than one?

I think it occurs whenever you have a notification. I've also noticed that I can't tap the notification to go to the program.

[kaufman]

Originally Posted by chaley

Change log:

• Fix format of dates downloaded via the cloud connection so that the "time" fields remain significant when sorting.

Forgot to post.


I have verified that this works for me correctly now.

[chaley]

Originally Posted by kaufman

Something else I noticed that I forgot to mention.

You throw up a notification for long transfers, but I have seen that if the process aborts abnormally, the notification stays up and is impossible to clear.

I repeated one form this problem with the Wireless Device. If the connection is broken while transferring books, the book progress dialog got stuck on the device. The only way to kill it was to force close CC.

The fix for this version of the problem will be in the next beta.

[kaufman]

I'm getting multiple directories with the number at the end again. I have sent you a log.

[chaley]

Originally Posted by kaufman

I'm getting multiple directories with the number at the end again. I have sent you a log.

Thanks.

As far as I can tell from the logs, the (N) books were already in the library, probably from before the release that "fixed" the problem. CC gets confused because it has multiple copies of the same book (same UUID). In addition, in some cases the file paths with the N are a surprise to CC. As a result, CC fails to clean away the other copies. I am not sure I can fix this without significant risk of deleting files that shouldn't be deleted.

Do the CC dates (added, changed, etc) say the the (N) books are new? If so then I have more detective work to do. If not then I suggest you delete them and see if they come back.