Touch Kobo Touch Firmware 2.0

[robko]

Originally Posted by nogle

Why do you assume that:
1. There is only one beta test group, and
2. That beta testers know about each other?

THIS!! I have no idea what other systems they have for testing but I assume they do more intensive internal testing on top of us.
And while it may seem strange that we don't get a lot of feedback from the devs it actually works pretty well as it doesn't clutter things up and we have a lot of trust that they are looking into/fixing it. Generally the group is pretty good at detailing issues we find and they aren't afraid to ask if they need more details.

[taming]

Originally Posted by robko

THIS!! I have no idea what other systems they have for testing but I assume they do more intensive internal testing on top of us.
And while it may seem strange that we don't get a lot of feedback from the devs it actually works pretty well as it doesn't clutter things up and we have a lot of trust that they are looking into/fixing it. Generally the group is pretty good at detailing issues we find and they aren't afraid to ask if they need more details.

Yup. And its not like any of us are shy about bringing things up again if something continues to be a problem. I can be a PITA, for sure. I'm fine with how they work with us. I'm a 60 year old female social worker, so it's not a style that comes naturally, but I get it.

[murg]

Originally Posted by nogle

Why do you assume that:
1. There is only one beta test group, and
2. That beta testers know about each other?

I don't know how many beta test groups Kobo has. But it isn't enough, judging from the last two releases (1.9.17 and 2.0.0).

And frankly, it doesn't matter, as whatever Kobo is doing with testing isn't working. There is no excuse for two public releases in a row to just not install. Do they even try to install the release package on a physical device from every manufacturing change?

What is different about the Australian hardware batch that makes firmware updates not work on it? Why isn't Kobo specifically testing for this in new firmware releases?

Either the problems we've been having installing the new firmwares on the Touch is hardware related or it is software related. If it is hardware related, then Kobo is obviously not doing the most rudimentary of testing, if one can make the basic assumption that they have physical samples of their manufactured hardware. If the problem is software related, then the same applies.

There is no excuse for a firmware release from a consumer electronics company to brick the device. None.

We have seen that the Kobo firmware is not firmly abstracted from the hardware (in that the particular hardware seems to have a major effect on whether or not the firmware works). We have also seen that Kobo seems to concentrate their testing on the kepub side of the software. Given all of this, if Kobo is using their employees (as someone here claims) to test the new hardware, then there are going to be gaps in the testing. Beta employees will tend to test the Kepub side, as they will be getting cheap (or even free) kepubs to do the testing with. Few of the employees will be using sideloaded books.

Of course, these are all guesses on my part. But you can guess a lot from a company's actions. Then again, Kobo may surprise us and have a release that actually works.

[jusmee]

Originally Posted by murg

What is different about the Australian hardware batch that makes firmware updates not work on it? Why isn't Kobo specifically testing for this in new firmware releases?

When will this rumour go away? It MUST be only some of them that have problems. Quite a few of us reported that there were no problems with our Australian Kobo Touch's upgrade. Both automatic 2.0 and manual 2.1.1 worked fine here.

[murg]

Ok, let me clarify.

There seems to be a batch of Kobo Touch eReaders that are having a problem loading the Japanese firmware. This batch seems to have been mostly sold in Australia (with New Zealand a possible).

This leads to the obvious questions: is there a manufacturing defect with this batch? A defect that can be resolved with the proper software? If there is a defect, is Kobo required by Australian (or state) law to issue a recall notice for the hardware?

[davidfor]

Originally Posted by murg

There seems to be a batch of Kobo Touch eReaders that are having a problem loading the Japanese firmware. This batch seems to have been mostly sold in Australia (with New Zealand a possible).

This leads to the obvious questions: is there a manufacturing defect with this batch? A defect that can be resolved with the proper software? If there is a defect, is Kobo required by Australian (or state) law to issue a recall notice for the hardware?

I'll back you up with this. Mine was OK up to 2.0.2 but it won't install 2.1.1. It either hangs restarting or does an incomplete install.

I have talked to Kobo about this and was asked for the factory reset firmware level and what books were on the device. This seems to have given them enough to solve the problem. I don't know if it was a bug in the original firmware or something in the newer firmware.

[taming]

David, do you have any reason to believe that Kobo is planning on ignoring this issue when the next build is released? From what you wrote, it sounds like a problem for which there is now a solution. I'm betting it will be incorporated into the next released build. What do you think?

[davidfor]

Originally Posted by taming

David, do you have any reason to believe that Kobo is planning on ignoring this issue when the next build is released? From what you wrote, it sounds like a problem for which there is now a solution. I'm betting it will be incorporated into the next released build. What do you think?

From what was said, it is an important reason for why the firmware hasn't been released.

[Peakcrew]

Originally Posted by davidfor

From what was said, it is an important reason for why the firmware hasn't been released.

Thanks, David - your comments make a lot of sense now, especially the one about the factory-set firmware.

[mapline]

If the KT version makes a difference in loading an upgrade it would be interesting to record serial numbers as the first part shows the circuit board revision.
eg. KG31C shows revision board C. This is mine and in loaded 2.1.1 with no problem.
Another serial number KG31B shows the revision board B. (obviously I am only showing the first 5 characters of the serial number.
What's your murg?

[SameerH]

Originally Posted by murg

Ok, let me clarify.

There seems to be a batch of Kobo Touch eReaders that are having a problem loading the Japanese firmware. This batch seems to have been mostly sold in Australia (with New Zealand a possible).

This leads to the obvious questions: is there a manufacturing defect with this batch? A defect that can be resolved with the proper software? If there is a defect, is Kobo required by Australian (or state) law to issue a recall notice for the hardware?

This was not due to a manufacturing defects but specifically how the upgrade was processed on some early devices (mostly in AU/NZ) which have a slightly different variant of the manufacturing firmware. This problem has since been fixed by adjusting the upgrade package and these customers will no longer experience difficulties in installing firmware regardless of what version they start from.

Hope that helps clear things up a bit.

[taming]

Thanks for that David. I am sure that Kobo folks felt pleased that someone with your background (and from downunder to boot) was willing to work so patiently with them to figure this out. Geographic diversity is a wonderful thing.

[Peakcrew]

Originally Posted by SameerH

This was not due to a manufacturing defects but specifically how the upgrade was processed on some early devices (mostly in AU/NZ) which have a slightly different variant of the manufacturing firmware. This problem has since been fixed by adjusting the upgrade package and these customers will no longer experience difficulties in installing firmware regardless of what version they start from.

Hope that helps clear things up a bit.

Thanks Sameer. I think that is where we are getting to on another thread (https://www.mobileread.com/forums/sho...88#post2215888)

[davidfor]

Originally Posted by taming

Thanks for that David. I am sure that Kobo folks felt pleased that someone with your background (and from downunder to boot) was willing to work so patiently with them to figure this out. Geographic diversity is a wonderful thing.

Patient? Glad you weren't actually watching me at the time

[ppulle]

So with SameerHs comment....does that mean I can plug my Kobo and sync now....that is, has the firmware on the Kobo site been changed, and if so onto which version?

Is this confirmable?