View Single Post
Old 07-11-2013, 04:24 AM   #47
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by davidfor View Post
My point was that it didn't matter.The actual code running is the same between the two packages.
I don't want to appear argumentative, but there is only one 2.6.1b package. If there were a fix of the header size for the Touch, owners of a old model would not know, in the same way as they don't enjoy the (partial) fix of the png image handling in epubs. Anak asked at least twice whether 2.6.1b fixes the header size for Touch. But I did not see any owner of a new model touch answer this question.

Quote:
Originally Posted by davidfor View Post
So, unless Kobo had added or removed something in the file that was specific to one device, it wouldn't matter which package was used. I doubt that Kobo would have release the 2.6.1b package if the change was something like this. I think it would have been to solve a hardware problem in one of the mark4 devices.
The actual question seems to be why Kobo didn't release the 2.6.1b for mark 3. I think they simply forgot to do it. I therefore posted the minimal changes one has to do in order to upgrade from 2.6.1.to 2.61b here.
tshering is offline   Reply With Quote