Thread: Touch Kobo Touch future firmware feature request thread
View Single Post
Old 08-28-2012, 08:22 PM   #942
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Mrs_Often View Post
Okay, what theory are we testing here?

I get information that looks slightly different (I'm on a Mac):

Code:
Looking for devices...
	(8759L, 16739L, 806L, u'Kobo', u'eReader', u'KG31B1500609E')
		Detected possible device KOBO
As peakcrew said, the format doesn't agree with what we are seeing. It appears to be a difference between Wiindows and Mac. Those numbers appear to be decimal. Converting them to hexadecimal gives the same values I have. What I see is:

Code:
Looking for devices...
	u'usb\\vid_2237&pid_4163&rev_0326'
		Detected possible device KOBO
Quote:
Strange that mine doesn't know it's a Touch... can I set that somewhere? Is the device number in there somewhere? I recognise the serial number but that's about it.
The names in the first line appear to come from the device. I don't know why Kobo don't label them properly. The "Detected possible device" is from calibre. At the moment there is only one driver for all the different Kobo devices and it doesn't differentiate them.
Quote:
And I've had no real problems with updates, just one minor one: installing version 2.1.1 on top of 2.0.2 caused 2.0.0 to appear instead, and installing 2.1.1. over 2.0.0 worked perfectly.
I had no problems up to 2.0.2. But, I recently did a factory reset and haven't been able to go past 2.0.0. If I put 2.0.2 on, it seems to install but I don't think it actually does. With 2.1.1, it hangs with the dancing squares after the update. The only fix is to do a reset.
davidfor is offline   Reply With Quote