Kobo Touch corruption

Bug #816572 reported by George Deluca
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
calibre
Invalid
Undecided
Timothy Legge

Bug Description

Got new Kobo Touch. Works fine with Kobo Desktop, no problems. Add 1 book via CaLibre and Kobo on power up it starts reporting eReader memory corruption and recommends a Factory Reset. Cannot connect any longer to Kobo Desktop, it goes "Oops! your reader needs a Factory reset. After doing the reset and re-initialize at least three times and ending back at the same spot, I tried again and this time instead of adding the book with CaLibre, I just copied it with Windows Explorer and all has been fine.

Sure looks like CaLibre and the Kobo Touch do not get along well together.

CaLibre is at 0.8.10 I see 0.8.11 is out but nothing in the changes seems to address this issue).

Kobo is at 1.9.6 (r30320), Jul 13, 2011)

Tags: kobo-driver
Revision history for this message
Kovid Goyal (kovid) wrote : Re: calibre bug 816572

Changing the component for this bug.

 assignee timlegge
 tag kobo-driver
 status triaged

Changed in calibre:
assignee: nobody → Timothy Legge (timlegge)
status: New → Triaged
Revision history for this message
George Stout (georges611) wrote :

I am also having a problem with the attachment of Kobo Touch. I have to copy the books to the root directory of the Touch. After entering several books and disconnecting the device it does a "Processing Content" This never seems to encounter a loop.

Revision history for this message
George Stout (georges611) wrote :

The following info was shown for the device.

USB Vendor ID (in hex): 0x2237
USB Product ID (in hex): 0x4163
USB Revision ID (in hex): 0x0326
Windows main memory vendor string: KOBO
Windows main memory ID string: EREADER

Revision history for this message
Ginette Gagne (ginetteis) wrote :

I also have a Kobo Touch and have the same problem.

Revision history for this message
George Stout (georges611) wrote :

After copying a book to the touch, it shows up as 2 books on the touch. One book appears to be the cover and the other is the book with no cover. The book itself shows html code as the first page and the following pages are not properly formatted. HTML appears on several pages. I am using 0.8.12 on calibre and the latest fix level on the touch. Windows 7. The touch appears as a drive letter plus another drive letter for the SD slot.

Revision history for this message
Timothy Legge (timlegge) wrote :

Hi

Are you connected through an USB hub or extension cable? I am using Linux and the only time I encountered this issue was using an extension cable. It was reliably repeatable with the cable but has not reoccurred with the original cable only.

Tim

Revision history for this message
George Deluca (gddeluca) wrote : Re: [Bug 816572] Re: Kobo Touch corruption

Hi Timothy,

I was connected directly, no hub. Corruption occurred using my desktop
system or my wife's laptop, so I don't yjhink using or not using a hub is
involved.

George

On Thu, Aug 4, 2011 at 9:47 AM, Timothy Legge <email address hidden> wrote:

> Hi
>
> Are you connected through an USB hub or extension cable? I am using
> Linux and the only time I encountered this issue was using an extension
> cable. It was reliably repeatable with the cable but has not reoccurred
> with the original cable only.
>
> Tim
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/816572
>
> Title:
> Kobo Touch corruption
>
> Status in calibre: e-book management:
> Triaged
>
> Bug description:
> Got new Kobo Touch. Works fine with Kobo Desktop, no problems. Add 1
> book via CaLibre and Kobo on power up it starts reporting eReader
> memory corruption and recommends a Factory Reset. Cannot connect any
> longer to Kobo Desktop, it goes "Oops! your reader needs a Factory
> reset. After doing the reset and re-initialize at least three times
> and ending back at the same spot, I tried again and this time instead
> of adding the book with CaLibre, I just copied it with Windows
> Explorer and all has been fine.
>
> Sure looks like CaLibre and the Kobo Touch do not get along well
> together.
>
> CaLibre is at 0.8.10 I see 0.8.11 is out but nothing in the changes
> seems to address this issue).
>
> Kobo is at 1.9.6 (r30320), Jul 13, 2011)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/calibre/+bug/816572/+subscriptions
>

Revision history for this message
George Stout (georges611) wrote :

I was also connected directly through a USA port on my desktop system. I had to do a "Save to Disk" since there is no driver available yet.

Revision history for this message
George Stout (georges611) wrote :

In order to eliminate the USB connection I did the following test:

copied a book to the a Micro SD card in my card reader (Windows 7 Desktop)
put the SD card into the Kobo Touch
It then shows 2 books ( a cover picture and a book without a cover)
The book itself seems to be fine.

Revision history for this message
Ric Flomag (ricflomag) wrote :

Even without transferring a book from/to the Kobo Touch, I've had this problem.

Started Calibre, plugged in the Kobo Touch then safely removed it. When unplugged, Kobo asked me to do a factory reset. Since I've stopped using Calibre to side-load books to my Kobo, I've not had this problem.

Revision history for this message
George Deluca (gddeluca) wrote :

Last night my Kobo installed a new update (1.9.9) so today I updated Calibre as well to 0.8.15 and thought I'd try these all out together. The Kobo update said it included 'stability fixes' (whatever that means) so I thought it was worth a test.

So far all now looks just fine. I've Sync'd Kobo with Kobo desktop. I've added a book to Kobo via Calibre and Kobo seems happy. Previously, this was where a power on ended up with memory corruption errors and Kobo Desktop issued "Oops, you Kobo need a factory reset" messages. I've Sync'd again with Kobo desktop. Powered on and off the Kobo, switched books etc. and all seems well.

Not exactly an exhaustive test, but previously all of this would have been impossible. So, since Kobo mentioned 'stability fixes' and Calibre doesn't seem to have changed at all in this area, it sure looks like Kobo was at fault in this problem. Only longer term usage and other users experience will let us know for sure.

Fingers are crossed this has been resolved. Looking forward to other users comments

George

Kovid Goyal (kovid)
Changed in calibre:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.