MobileRead Forums - View Single Post

judyz · 10-23-2012, 04:43 PM

It doesn't look like this question was answered already so I will do it.

My Glo updated to 2.1.5(r43939, 10/12/12). Ironically the welcome message after the update actually congratulates you for upgrading to 2.1.4 so it would appear this is strictly a bugfix of 2.1.4

I am glad to see Kobo busy squishing bugs. Kobo's determination to constantly improve my old wifi long after I bought it and it was no longer the latest and greatest helped me decide to choose a Kobo for my replacement. Hopefully they will maintain this commitment to improvement with the GLO.

I have to agree with other commenters here on both sides since there is common sense in each.

1) It is quite simple, standard and expected in the software industry to include a device check routine. It is standard practice to expect that people will do stupid things. The average user will have trouble even telling you whether or not they have a Kobo or Kindle let alone model differences. Software is supposed to be designed to anticipate and negate our natural stupidity. I am sure we have all accidentally clicked on a incorrect download like (Mac instead of PC, etc) at some point. If I download the wrong BIOS for my Motherboard it doesn't install it. Instead it says sorry but you picked the wrong file. If for some reason a user gets ahold of a firmware not designed for their Kobo it shouldn't install. Devices are never strictly limited to designed use. You are going to get little Billy putting the latest firmware on a disc and bringing it over to Grandma's house because she doesn't know how to update and doesn't have the internet. Following best practices for programming will help keep little Billy from accidentally bricking Grandma's Kobo.

2) Let the modder beware. If you choose to step outside of standard channels for firmware distribution don't expect your device manufacturer to fix it for you. What Kobo decides to call internal firmware builds is their business. If you are combing the site and choose to find an experimental build and install it then you are taking your chances.

One of these is something Kobo can easily implement for the sake of customer satisfaction. The other is something that most of us power users learn the hard way somewhere along the road.

10-23-2012, 04:43 PM	#127
judyz Enthusiast Posts: 36 Karma: 10638 Join Date: Dec 2010 Device: Kobo Wifi, Kobo Glo, Sony PRS-950	It doesn't look like this question was answered already so I will do it. My Glo updated to 2.1.5(r43939, 10/12/12). Ironically the welcome message after the update actually congratulates you for upgrading to 2.1.4 so it would appear this is strictly a bugfix of 2.1.4 I am glad to see Kobo busy squishing bugs. Kobo's determination to constantly improve my old wifi long after I bought it and it was no longer the latest and greatest helped me decide to choose a Kobo for my replacement. Hopefully they will maintain this commitment to improvement with the GLO. I have to agree with other commenters here on both sides since there is common sense in each. 1) It is quite simple, standard and expected in the software industry to include a device check routine. It is standard practice to expect that people will do stupid things. The average user will have trouble even telling you whether or not they have a Kobo or Kindle let alone model differences. Software is supposed to be designed to anticipate and negate our natural stupidity. I am sure we have all accidentally clicked on a incorrect download like (Mac instead of PC, etc) at some point. If I download the wrong BIOS for my Motherboard it doesn't install it. Instead it says sorry but you picked the wrong file. If for some reason a user gets ahold of a firmware not designed for their Kobo it shouldn't install. Devices are never strictly limited to designed use. You are going to get little Billy putting the latest firmware on a disc and bringing it over to Grandma's house because she doesn't know how to update and doesn't have the internet. Following best practices for programming will help keep little Billy from accidentally bricking Grandma's Kobo. 2) Let the modder beware. If you choose to step outside of standard channels for firmware distribution don't expect your device manufacturer to fix it for you. What Kobo decides to call internal firmware builds is their business. If you are combing the site and choose to find an experimental build and install it then you are taking your chances. One of these is something Kobo can easily implement for the sake of customer satisfaction. The other is something that most of us power users learn the hard way somewhere along the road.