View Single Post
Old 08-28-2012, 11:01 AM   #938
Peakcrew
Avid reader of sci-fi
Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.Peakcrew can successfully navigate the Paris bus system.
 
Peakcrew's Avatar
 
Posts: 384
Karma: 36724
Join Date: Sep 2011
Location: Scotland
Device: Kobo Touch, Lenovo X61, Samsung Galaxy Note with Aldiko reader app
Quote:
Originally Posted by davidfor View Post
Yes, it might explain it. But, we would need the device ids from everyone to get the stats.
Well, I'm happy to kick it off. My device ID is 4163 rev_0110, and I have had absolutely no problems with updates, as I have been posting.

If anyone else wants to post theirs, and the ease or not of updating (either with 2.0.0 or 2.1.1), the device ID can be found by opening Calibre, then Preferences>Miscellaneous (middle of bottom row). On the screen that comes up, locate the "Debug device detection" button, but don't press it yet. Connect the KT with a usb cable, and then allow it to connect to the computer. Now, timing is a bit tricky. If you have autorun turned on, click the Debug button just after the box (or boxes if you have an SD card) have opened. If not, probably counting slowly to five would do it.

What you should see is a box that says "Getting debug information, please wait ...", and then produces a list of all the usb devices connected to your computer. Run down the list until you find "Looking for devices..." The line below will look like:
u'usb\\vid_2237&pid_XXXX&rev_YYYY'

Followed by:
Detected possible device KoboTouch

The device ID is the two four-digit numbers after "pid" (highlighted).

There may, of course, be an easier way than this, but I haven't found it. Someone will no doubt enlighten me with a much simpler solution!
Peakcrew is offline   Reply With Quote