Problem with Android 11 and Calibre Companion

[ottischwenk]

With 2 different Android 11 devices and Calibre Companion (wireless device), the following error occurs (sometimes) for more than approximately 16,000 books

calibre, version 6.9.0
FEHLER: Fehler: Fehler beim Kommunizieren mit dem Gerät

There was a timeout while communicating with the device in function: Device did not respond in reasonable time

Traceback (most recent call last):
  File "calibre\devices\smart_device_app\driver.py", line 678, in _receive_from_client
  File "calibre\devices\smart_device_app\driver.py", line 594, in _read_string_from_net
  File "calibre\devices\smart_device_app\driver.py", line 579, in _read_binary_from_net
TimeoutError: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "calibre\gui2\device.py", line 88, in run
  File "calibre\gui2\device.py", line 540, in _books
  File "calibre\devices\smart_device_app\driver.py", line 59, in _synchronizer
  File "calibre\devices\smart_device_app\driver.py", line 1299, in books
  File "calibre\devices\smart_device_app\driver.py", line 59, in _synchronizer
  File "calibre\devices\smart_device_app\driver.py", line 658, in _call_client
  File "calibre\devices\smart_device_app\driver.py", line 690, in _receive_from_client
calibre.devices.errors.TimeoutError: There was a timeout while communicating with the device in function: Device did not respond in reasonable time

Not with other devices and not when there are fewer books.
And it happens on different networks.

[chaley]

Moderator Notice
Moved to CC forum

[chaley]

CC has been abandoned and is no longer supported.

[ottischwenk]

Originally Posted by chaley

Moved to CC forum

But it is a Calibre timeout problem

[chaley]

Originally Posted by ottischwenk

But it is a Calibre timeout problem

You don't know that. It is probably caused by CC timing out or sleeping or being pushed to background or some other Android battery saver thing. There is no way to debug it without source for CC, which is not available.

[ottischwenk]

Originally Posted by chaley

You don't know that. It is probably caused by CC timing out or sleeping or being pushed to background or some other Android battery saver thing. There is no way to debug it without source for CC, which is not available.

Are you sure, that this is a Calibre Companion problem?
It works everytime, when using in Calibre a virtual library with app 6000 (from my more than 16.000) books and ending it when connection is completed.
So, I know a workaround.

[chaley]

Originally Posted by ottischwenk

Are you sure, that this is a Calibre Companion problem?
It works everytime, when using in Calibre a virtual library with app 6000 (from my more than 16.000) books and ending it when connection is completed.
So, I know a workaround.

I am 99% sure. The calibre exception (timeout) says "Device did not respond in reasonable time" which means calibre was waiting for the device. There isn't anything the calibre driver can do if the device doesn't answer.

Back when I owned CC, these situations arose when the device put itself to sleep during a connection. Later versions of android are extremely aggressive about shutting down apps that appear to be doing "background" things. The more books on the device, the longer the "background" task runs. If I were you I would try turning off battery optimization for CC, and possibly extend the screen "sleep timer" to very long.

[ottischwenk]

Originally Posted by chaley

If I were you I would try turning off battery optimization for CC, and possibly extend the screen "sleep timer" to very long.

Battery optimization is off and sleep timer is off and background activity is allowed.
It depends on how many books are in the (virtual) library in Calibre.
When activating a small virtual library in Calibre, which is terminated after the connection is complete, it always works.

[ottischwenk]

Originally Posted by chaley

You don't know that. It is probably caused by CC timing out or sleeping or being pushed to background or some other Android battery saver thing.

No - its a file system problem with many books (16500) of Android 11 Boox Devices - Tab Ultra needs to open this folder 7 minutes 20

[chaley]

Originally Posted by ottischwenk

No - its a file system problem with many books (16500) of Android 11 Boox Devices - Tab Ultra needs to open this folder 7 minutes 20

Perhaps this is a manifestation of Android's FAT32 problem.

Does this old CC FAQ help?

[ottischwenk]

Originally Posted by chaley

Perhaps this is a manifestation of Android's FAT32 problem.

No, because it works.
And I can add books with cloud or server connection.
The problem is with wireless device.

Does this old CC FAQ help?

No - when I tried the last, it started with a timeout (wireless device - no books)

[ottischwenk]

Originally Posted by ottischwenk

No - when I tried the last, it started with a timeout (wireless device - no books)

This message is wrong!
The last
{first_author:%1.1s}/{first_author}/{title} - {authors}
dit it!

[vikarti]

Originally Posted by ottischwenk

This message is wrong!
The last
{first_author:%1.1s}/{first_author}/{title} - {authors}
dit it!

I thought everybody with large library uses something like it (I do, performance was terrible without it on top devices and it timeouted on less than top ones)

[ottischwenk]

Originally Posted by vikarti

I thought everybody with large library uses something like it (I do, performance was terrible without it on top devices and it timeouted on less than top ones)

Yes - but this wasn't that which caused the problem.
It is a bug in the Tab Ultra file system that is only triggered by a single book transfer from Calibre Companion.

[ottischwenk]

Originally Posted by ottischwenk

Yes - but this wasn't that which caused the problem.
It is a bug in the Tab Ultra file system that is only triggered by a single book transfer from Calibre Companion.

In addition, under Android 11 "get list of books on device" is often delivered too slowly, so that the timeout set to 5 minutes in Calibre takes effect.
This bug is known and triaged.