Sony PRS-T1 & "Calibre Sync" by Wifi: How to use it as the Sony Reader?

[nikoski]

Calibre Sync is an app by which it is possible to sync Calibre to a rooted Sony PRS-T1 by WiFi, no cable/USB connection necessary: https://play.google.com/store/apps/d....calibre&hl=de


The problem is that Calibre does not seem to "see" it as Sony Reader when connected by this app/WiFi, instead it shows a connected "wireless device: sydney".

As the consequence it does not populate the library on the device.

Who knows how to "tell" calibre to recognise "sydney" as Sony Reader and use the right plugin for PRS-T1?

[chaley]

You cannot do what you are asking for. The wireless device connection is managed entirely by the app and has no connection with the Sony reading system, the sony database, or the sony calibre plugin.

[nikoski]

Thanks a lot for clarifying that precisely!

Your "Companion" seems to need android 4.x to work whereas rooted Sony ist only android 2.2.1. Is there a chance of making it compatible?

[DoctorOhh]

Originally Posted by nikoski

Your "Companion" seems to need android 4.x to work whereas rooted Sony ist only android 2.2.1. Is there a chance of making it compatible?

Calibre Companion needs Android 2.3 or higher. No chance of regressing further.

[chaley]

As DoctorOhh said. We can't go further down because there were networking features added in Gingerbread (Android 2.3) that CC depends upon.

[nikoski]

Ok, i see, thanks!
BTW, would, or at least: should Companion (normally) work "flawlessly" on a Reader with android 2.3.1 like the imcoV6L?...
http://www.imcosys.com/ebook-reader.html

[chaley]

Originally Posted by nikoski

Ok, i see, thanks!
BTW, would, or at least: should Companion (normally) work "flawlessly" on a Reader with android 2.3.1 like the imcoV6L?...
http://www.imcosys.com/ebook-reader.html

Hard to say. We have quite a few users with android 2.3.3-2.3.7 (Gingerbread API 10), but almost no users with 2.3-2.3.2 (Gingerbread API 9). I don't know if that difference is caused by a problem with API 9 (which we support) or is caused by there being so few devices stuck at that level. I suspect the latter.

Also regarding "flawlessly", Android 2.X has a significant problem with memory management. In particular, the memory for bitmaps is not collected when the bitmap is freed (no longer in use), but is instead collected sometime later through a special process. This leads to a lot of Out Of Memory errors of the form "VM budget exceeded", which we see on early devices like the Nook Color w/CM7. Google changed all of this in Android 3 (I think, could be 4 because almost no one runs 3) so that bitmaps are treated like all other kinds of memory, with the result that the number of OOM errors plummeted.

As long as I am here and looking at statistics: current CC installs by android version are:

Android 4.4				30.71%
Android 4.1				19.57%
Android 4.2				18.21%
Android 4.3				15.11%
Android 4.0.3 - 4.0.4 			12.41%
Android 2.3.3 - 2.3.7	 		 3.25%
Android 3.2				 0.58%
Android 3.1				 0.13%
Android 2.3				 0.02%
Android 3.0				 0.01%

Given those numbers we have considered dropping support for Android < 4, but have decided not to because at the moment we have no need to focus on the new features in Android 4+

[nikoski]

Thanks, ok, i'm getting the idea

But still one thing about the sync by "Calibre Sync":

When connected by Calibre Sync, in the Calibre under the device menu button i can „configure this device“, especially set „tags“ as metadata fields to turn into collections on the device. What sort of collections are meant by that?

[chaley]

Originally Posted by nikoski

Thanks, ok, i'm getting the idea

But still one thing about the sync by "Calibre Sync":

When connected by Calibre Sync, in the Calibre under the device menu button i can „configure this device“, especially set „tags“ as metadata fields to turn into collections on the device. What sort of collections are meant by that?

Sorry, but that depends on the calibre sync app's capabilities. I have no idea what it can do. You need to contact the app's developer, or hope someone comes by who uses the app and can answer.