Sony PRS-T1 in Calibre - Page 17

Scott Nielsen · 10-16-2011, 06:34 AM

Ignore my previous post... I must have done something wrong because when I checked my reader a few minutes later, books are all there and - as for you - now as per plugboard instruction.

Jolly good.

azxswq · 10-16-2011, 09:31 AM

For today's (Oct. 16th, 2011) periodicals (news sources)

There is an additional

Saturday, October 15, 2011
<div><p class="descriptions">Harper's Magazine ...
In the title description.

Could be a second day problem on the new patch, where the description xml tag is not being stripped out correctly.

Since I *do* have 2 T1 now, I notice that 1 of them, is now syncing for a long long time and another one, RED, have no problem syncing but displaying this non-stripped XML description.

On a separate note, I am going to read the docs on Calibre multi-device support... ;-)

Kolenka · 10-16-2011, 10:33 AM

The description is coming from the periodical itself. The driver didn't even directly support periodicals until the patch I submitted yesterday. I don't know if that patch is even in a beta yet (I tell people when I submit a patch so they know what is coming, not what is currently available). And even the driver leaves the field blank for the T1 to fill in for it, as there isn't currently an easy way to query the description/summary without cracking the ePub open.

I suspect that is how the description looks in the ePub's OPF file itself.

azxswq · 10-17-2011, 09:12 AM

Could be. My Saturday's news descriptions has erroneous XML tags,
Friday, Sunday and Today are all fine.

Talking about reproducible bugs..

Thanks for the feedback.

Mr Fujisawa · 10-17-2011, 11:20 AM

Quote:

Originally Posted by Kolenka

I've submitted another patch with some changes:

- Auto-populate some of the periodical fields when sending news feeds. This will speed up scanning when adding periodicals a little bit, and make behavior more consistent.

- Can toggle between normal and 'T1-style' authors when populating books.db. The default will be normal (showing all authors). 'T1-style' is showing only the first author.

- Driver will now attempt to calculate and use the UTC offset from the device, instead of assuming local time. This should reduce/eliminate the long rescans some people are seeing.

I wonder if it should assume local time or UTC when there are no books on the device at all though... I might have to play with the reader software and see what it does to the database (if anything). It'd be easier to test that situation if I had a second reader I could just factory reset without losing all my current reading progress.

How do we get this patch? Or will it be in a new version of calibre? Sorry if that's a silly question.

Kolenka · 10-17-2011, 12:48 PM

When I say I submitted a patch, I mean to the Calibre maintainers. One of them (usually Kovid) goes over the patch, and accepts it. From there it will make it into the next Calibre release. The release is usually weekly.

I mention what I've put into a patch and submitted to the Calibre folks, partly to let people know that I've been tackling some specific issue, and to help cut down on discussion of "known issues" a bit. It gets hard to wade through reports when the latter happens, and hard to follow.

CedroRosso · 10-18-2011, 02:00 AM

Hey guys, first of all thanks for your hard work.

Second, I was wondering why I was getting the following error when I connect my T1. When I plug the T1 in, Caliber tells me that an error has occured and the T1 shows up as an icon but I can't see any of the books in its memory. I'm on a Mac running 1.6.8 and the books on the device were synced using sony software. Hope that helps.

calibre, version 0.8.22
ERROR: Error: Error communicating with device

database disk image is malformed

Traceback (most recent call last):
File "site-packages/calibre/gui2/device.py", line 81, in run
File "site-packages/calibre/gui2/device.py", line 332, in _books
File "site-packages/calibre/devices/prst1/driver.py", line 165, in books
DatabaseError: database disk image is malformed

Kolenka · 10-18-2011, 02:30 AM

I've seen that a couple times. The SQLite DB got corrupted. I haven't quite found the source of what can cause it other than the T1 sometimes not going into Data Transfer Mode correctly when you tell it to, and instead going to the home screen. SQLite doesn't always like two processes trying to edit the DB at the same time.

You can delete books.db, and let the T1 recreate it. Or you can try to repair the SQLite DB yourself. You will need SQLite 3 tools installed on your machine to do it.

On a Mac, you would run this from the terminal:

Code:

echo ".dump" | sqlite3 old.db | sqlite3 new.db

Where old.db is the path to 'books.db' and new.db is a place to put the new books.db. You can replace the books.db on the device with the new one.

CedroRosso · 10-18-2011, 02:52 AM

That sounds right, the device worked the first few times. I started getting the error when I plugged-in the device and it remained on the homescreen instead of going to the data-transfer screen, forcing me to re-plug. Unfortunately I've always had friends walk me through terminal so your instructions are a bit confusing to me.

DoctorOhh · 10-18-2011, 02:55 AM

Quote:

Originally Posted by Kolenka

You can delete books.db, and let the T1 recreate it. Or you can try to repair the SQLite DB yourself. You will need SQLite 3 tools installed on your machine to do it.

I'm curious, what is the advantage of repairing the book.db file versus deleting the book.db file?

Kolenka · 10-18-2011, 02:56 AM

Are you actually on a Mac or Linux machine? If that is the case you can pretty much copy/paste this into the Terminal:

Code:

echo ".dump" | sqlite3 /Volumes/READER/Sony_Reader/database/books.db | sqlite3 ~/Desktop/books.db
cp ~/Desktop/books.db /Volumes/READER/Sony_Reader/database/books.db

That will recreate the DB and put it back onto the Reader (assuming you have no SD card as well). I'm not familiar with SQLite on Windows to know how to repair it through cmd.exe.

CedroRosso · 10-18-2011, 05:11 AM

Awesome, it worked, thanks!

Orthonormal · 10-18-2011, 10:05 PM

I am experiencing the reversion from Last_name, First_name to First_name Last_name after loading books onto the reader using Calibre 0.8.22.

In the Sony device plugin, I have checked the option to use author_sort in the author field. I have selected the option to have Calibre automatically manage metadata.

When I plug the device into the computer, the metadata is uploaded to the device. When I eject it and unplug it, initially the books are all listed with the author's name in Last_name, First_name order. Then after a few seconds, the screen refreshes and they are listed with the author's name in First_name Last_name format. It seems like the reader itself is parsing the author field and "correcting" the format so that they all have the author's first name first.

Is anyone else seeing this behavior? Has anyone found a fix?

Kolenka · 10-18-2011, 10:35 PM

Wait until the next release. There's an issue where the modified time doesn't match up in the DB like the device thinks it should. A fix for it is checked in, but hasn't yet been released.

jackie_w · 10-19-2011, 08:14 AM

Quote:

Originally Posted by Orthonormal

Is anyone else seeing this behavior? Has anyone found a fix?

Whilst we're waiting for Kolenka's update you could try the temporary fix I posted earlier. It has continued to work for me.

10-18-2011, 02:00 AM	#247
CedroRosso Enthusiast Posts: 38 Karma: 22 Join Date: Sep 2011 Location: Seattle Device: Sony PRS-T1	Hey guys, first of all thanks for your hard work. Second, I was wondering why I was getting the following error when I connect my T1. When I plug the T1 in, Caliber tells me that an error has occured and the T1 shows up as an icon but I can't see any of the books in its memory. I'm on a Mac running 1.6.8 and the books on the device were synced using sony software. Hope that helps. calibre, version 0.8.22 ERROR: Error: Error communicating with device database disk image is malformed Traceback (most recent call last): File "site-packages/calibre/gui2/device.py", line 81, in run File "site-packages/calibre/gui2/device.py", line 332, in _books File "site-packages/calibre/devices/prst1/driver.py", line 165, in books DatabaseError: database disk image is malformed Last edited by CedroRosso; 10-18-2011 at 02:22 AM.

10-18-2011, 02:30 AM	#248
Kolenka <Insert Wit Here> Posts: 1,017 Karma: 1275899 Join Date: Jan 2008 Location: Puget Sound Device: Kindle Oasis, Kobo Forma	I've seen that a couple times. The SQLite DB got corrupted. I haven't quite found the source of what can cause it other than the T1 sometimes not going into Data Transfer Mode correctly when you tell it to, and instead going to the home screen. SQLite doesn't always like two processes trying to edit the DB at the same time. You can delete books.db, and let the T1 recreate it. Or you can try to repair the SQLite DB yourself. You will need SQLite 3 tools installed on your machine to do it. On a Mac, you would run this from the terminal: Code: echo ".dump" \| sqlite3 old.db \| sqlite3 new.db Where old.db is the path to 'books.db' and new.db is a place to put the new books.db. You can replace the books.db on the device with the new one.

10-18-2011, 02:56 AM	#251
Kolenka <Insert Wit Here> Posts: 1,017 Karma: 1275899 Join Date: Jan 2008 Location: Puget Sound Device: Kindle Oasis, Kobo Forma	Are you actually on a Mac or Linux machine? If that is the case you can pretty much copy/paste this into the Terminal: Code: echo ".dump" \| sqlite3 /Volumes/READER/Sony_Reader/database/books.db \| sqlite3 ~/Desktop/books.db cp ~/Desktop/books.db /Volumes/READER/Sony_Reader/database/books.db That will recreate the DB and put it back onto the Reader (assuming you have no SD card as well). I'm not familiar with SQLite on Windows to know how to repair it through cmd.exe.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Prs 505 Sony and calibre 0.8	duduche33	Devices	3	05-12-2011 10:50 AM
Calibre for Sony prs 350	Rick1971	Calibre	4	12-26-2010 12:27 PM
Calibre and Sony PRS-600	Archergal5219	Calibre	2	07-25-2010 12:32 AM
Sony PRS-505/Sony Connect/Calibre	thesweetone	Sony Reader	26	09-30-2009 03:00 PM
Calibre and Sony PRS-600	lukasfikr	Calibre	10	08-26-2009 09:11 PM

10-16-2011, 06:34 AM	#241
Scott Nielsen Groupie Posts: 155 Karma: 112134 Join Date: May 2009 Location: Kuala Lumpur Device: iPad, K3, K4, T1	Ignore my previous post... I must have done something wrong because when I checked my reader a few minutes later, books are all there and - as for you - now as per plugboard instruction. Jolly good.

10-16-2011, 09:31 AM	#242
azxswq Connoisseur Posts: 52 Karma: 10 Join Date: Sep 2011 Location: NYC Device: PRS-T1 Black, T2 Black	For today's (Oct. 16th, 2011) periodicals (news sources) There is an additional Saturday, October 15, 2011 <div><p class="descriptions">Harper's Magazine ... In the title description. Could be a second day problem on the new patch, where the description xml tag is not being stripped out correctly. Since I do have 2 T1 now, I notice that 1 of them, is now syncing for a long long time and another one, RED, have no problem syncing but displaying this non-stripped XML description. On a separate note, I am going to read the docs on Calibre multi-device support... ;-)

10-16-2011, 10:33 AM	#243
Kolenka <Insert Wit Here> Posts: 1,017 Karma: 1275899 Join Date: Jan 2008 Location: Puget Sound Device: Kindle Oasis, Kobo Forma	The description is coming from the periodical itself. The driver didn't even directly support periodicals until the patch I submitted yesterday. I don't know if that patch is even in a beta yet (I tell people when I submit a patch so they know what is coming, not what is currently available). And even the driver leaves the field blank for the T1 to fill in for it, as there isn't currently an easy way to query the description/summary without cracking the ePub open. I suspect that is how the description looks in the ePub's OPF file itself.

10-17-2011, 09:12 AM	#244
azxswq Connoisseur Posts: 52 Karma: 10 Join Date: Sep 2011 Location: NYC Device: PRS-T1 Black, T2 Black	Could be. My Saturday's news descriptions has erroneous XML tags, Friday, Sunday and Today are all fine. Talking about reproducible bugs.. Thanks for the feedback.

10-17-2011, 12:48 PM	#246
Kolenka <Insert Wit Here> Posts: 1,017 Karma: 1275899 Join Date: Jan 2008 Location: Puget Sound Device: Kindle Oasis, Kobo Forma	When I say I submitted a patch, I mean to the Calibre maintainers. One of them (usually Kovid) goes over the patch, and accepts it. From there it will make it into the next Calibre release. The release is usually weekly. I mention what I've put into a patch and submitted to the Calibre folks, partly to let people know that I've been tackling some specific issue, and to help cut down on discussion of "known issues" a bit. It gets hard to wade through reports when the latter happens, and hard to follow.

10-18-2011, 02:52 AM	#249
CedroRosso Enthusiast Posts: 38 Karma: 22 Join Date: Sep 2011 Location: Seattle Device: Sony PRS-T1	That sounds right, the device worked the first few times. I started getting the error when I plugged-in the device and it remained on the homescreen instead of going to the data-transfer screen, forcing me to re-plug. Unfortunately I've always had friends walk me through terminal so your instructions are a bit confusing to me.

10-18-2011, 05:11 AM	#252
CedroRosso Enthusiast Posts: 38 Karma: 22 Join Date: Sep 2011 Location: Seattle Device: Sony PRS-T1	Awesome, it worked, thanks!

10-18-2011, 10:05 PM	#253
Orthonormal Junior Member Posts: 6 Karma: 10 Join Date: Oct 2011 Device: Sony PRS-T1	I am experiencing the reversion from Last_name, First_name to First_name Last_name after loading books onto the reader using Calibre 0.8.22. In the Sony device plugin, I have checked the option to use author_sort in the author field. I have selected the option to have Calibre automatically manage metadata. When I plug the device into the computer, the metadata is uploaded to the device. When I eject it and unplug it, initially the books are all listed with the author's name in Last_name, First_name order. Then after a few seconds, the screen refreshes and they are listed with the author's name in First_name Last_name format. It seems like the reader itself is parsing the author field and "correcting" the format so that they all have the author's first name first. Is anyone else seeing this behavior? Has anyone found a fix?

10-18-2011, 10:35 PM	#254
Kolenka <Insert Wit Here> Posts: 1,017 Karma: 1275899 Join Date: Jan 2008 Location: Puget Sound Device: Kindle Oasis, Kobo Forma	Wait until the next release. There's an issue where the modified time doesn't match up in the DB like the device thinks it should. A fix for it is checked in, but hasn't yet been released.

Advert

Advert