[Android] CC V5.2.6 beta released

[chaley]

V5.2.6.1 (7 May 2017)

Changes:

• New Google toolset. I don't think much was changed underneath but there is always a risk.
• Updated languages: Russian, Vietnamese
• [BUG FIX] In the "help/explanation" dialog boxes: include the checkbox with the text in the scrollable area. This prevents the checkbox being hidden on some devices, ensuring that it cannot be checked.

[chaley]

5.2.6.2 (14 May 2017):
When using CC with the new calibre V3 (beta) content server:

• [BUG FIX] Fix failing to see book details after changing the calibre library
• [BUG FIX] Fix username/password authentication often not working

There are (in theory) no changes when using the calibre V2 content server.

[chaley]

5.2.6.3 (15 May 2017)

Changes:

• Change to prevent Google Drive from refusing to authenticate. Google made changes in late April that broke CC's Google Drive cloud connection. This release works around Googles prohibition.

I expect this release to be the last beta in this series.

[nqk]

@chaley,

When connected to Content Server 3.0, the "Newest" (Books sorted by date) folder shows nothing. And when I'm already inside, hitting back button doesn't bring be back out. The only choice is to disconnect. This doesn't happen with other folders. Ah, at least does with subfolders under Rating (stars) folder.

I'm running Calibre Portable 2.99.5.

And a minor issue: when CC tries to remove accent (in file names) from character Đ and đ, it returns in both case the 'd' rather than D and d, respectively.

[chaley]

Originally Posted by nqk

@chaley,

When connected to Content Server 3.0, the "Newest" (Books sorted by date) folder shows nothing. And when I'm already inside, hitting back button doesn't bring be back out. The only choice is to disconnect. This doesn't happen with other folders. Ah, at least does with subfolders under Rating (stars) folder.

I'm running Calibre Portable 2.99.5.

With two exceptions, I cannot make it fail running calibre portable and the latest CC. That said, the calibre portable server is much slower than the calibre x64 standard server.

The first exception: there seems to be a problem when changing between calibre x64 and calibre portable without restarting CC. Sometimes CC won't connect. I don't know why.

The second exception: there is a problem when username protection is added to the content server while CC is connected. I am going to ignore that, at least for the moment.

If the problem is still happening for you, could you send me a CC debug log?

[Dopedangel]

Originally Posted by nqk

@chaley,

When connected to Content Server 3.0, the "Newest" (Books sorted by date) folder shows nothing. And when I'm already inside, hitting back button doesn't bring be back out. The only choice is to disconnect. This doesn't happen with other folders. Ah, at least does with subfolders under Rating (stars) folder.

I'm running Calibre Portable 2.99.5.

And a minor issue: when CC tries to remove accent (in file names) from character Đ and đ, it returns in both case the 'd' rather than D and d, respectively.

If you don't use your calibre portable on 32bit windows. I would recommend using portable 64-bit by simply replacing the calibre folder inside the portable folder with the calibre folder from a normal 64-bit install. I have been using it this way after Kovid recommended it when I asked for 64bit calibre portable.

[chaley]

Originally Posted by nqk

And a minor issue: when CC tries to remove accent (in file names) from character Đ and đ, it returns in both case the 'd' rather than D and d, respectively.

I didn't see this before. Sorry.

Accent removal is done by Android's implementation of unicode character normalization. I have no control over what it does.

[chaley]

5.2.6.4 (19 May 2017)

Changes:

• Significant rewrite of the content server connection networking code. See below.
• Updated lanaguage: Vietnamese
• [BUG FIX] Fix (I hope) the occasional failure in the content server connection that forced a disconnect.

Beta testers were reporting strange non-repeatable networking problems, some if which I would see from time to time. To (one hopes) fix these I updated the networking libraries, simplified the networking code, and implemented connection pooling. I think the result works better; at least it doesn't fail for me anymore. I think it is faster as well.

I tested the new code on V2 and V3 calibre servers, with and without passwords using both digest and basic authentication.

I also tested HTTPS access via a linux Apache front end. I have not set up a certificate to test direct access because Android doesn't like self-signed certs and I don't want to buy one.

Please let me know if you see anything strange.

[chaley]

V5.3.1.1 production release rolled out to beta

Changes since beta V5.6.2.4:

• Removed "Change Library" category lines from the content server. Using them confused CC. Instead use the change library dialog available in the menu.
• Updated language: German
• New language: Polish

Unless something catastrophic happens this release will be rolled out to all users on Wednesday 24/May or Thursday 25/May, at which time the Google Play CC Demo and the Amazon versions will also be generally released.

[chaley]

5.3.1.1: all versions (GP full, GP demo, Amazon full, Amazon demo( released.

Thanks to the beta testers for the feedback, in particular for the calibre V3 content server connection.

[nqk]

Dear chaley,

Anything happened to Box? I can't get connected. Hope it's not my library that went wrong. The internet connection to Box service is fine.


Edit: False alarm. The database file is missing

[chaley]

Originally Posted by nqk

Dear chaley,

Anything happened to Box? I can't get connected. Hope it's not my library that went wrong. The internet connection to Box service is fine.

Box works fine for me on Android 6.0.1 and android 4.3.

It could be that there is a problem with your stored credentials. CC is supposed to refresh them as needed, but it is possible that something went wrong. You could try to reset the connection then authenticate again.

It is also possible that there is a transient problem with box. Can you login and see your library from a web browser on the same network as your device?

EDIT: Just saw your edit. I wonder how that happened?

[nqk]

I edited the post. You were too fast. The database is somehow... missing....