Firmware 2.8.1b

[jiminrussell]

@DomesticExtremis, not just you. my Mini was also still at 2.6.1 and just now updated to 2.6.2 (4365d8338f, 9/27/13)

[PeterT]

Unfortunately, I'm not sure what 2.6.2 is; this is a brand new f/w that we've not seen before. I'm not even sure which devices it applies to. If it's on the Mini it might also apply to the Touch, at least the N905C variant (Low Cost Touch).

Be aware that the Kobo Patcher will not be able to handle this. Don't use either of the LibNickel's included with Patcher (2.6.1 and 2.8.1) with this f/w.

[DomesticExtremis]

Well, 2.6.2 doesn't seem radically different. Probably just some bug fixes.

[Thane1]

Originally Posted by jiminrussell

@DomesticExtremis, not just you. my Mini was also still at 2.6.1 and just now updated to 2.6.2 (4365d8338f, 9/27/13)

No luck here getting the update, has anyone figured out what the direct link to this new firmware (2.6.2-Mini)?

I wonder if 2.6.2 is really just 2.6.1b, perhaps with a few more fixes, if you recall the original 2.6.1 had issues with images (cover images I think). Units which received 2.6.1 successfully would not automatically update to the "b" version, so incrementing the file name might ensure everyone gets the new (and hopefully incredibly stable and flawless) version.

Going out on a tangent for a moment, if anyone out there has a Touch 905B reader, which firmware version do you have? I still have 2.5.2 on mine (even after doing a factory reset) and it can't render certain image files inside epubs. Just wondering if Kobo pushed an update out which I might have missed.

[davidfor]

Don't worry to much about 2.6.2. Elsewhere, Kobo have said it is only to fix a problem with recommendations. No other changes.

And the 2.8.1b is about a problem with demo devices. I assume they released it without changing the version number as it only really needed to go on new devices being set in shops for demos. Unless you are reading Dutch books as a Dutch hyphenation dictionary has been added.

[DNSB]

Originally Posted by Thane1

Going out on a tangent for a moment, if anyone out there has a Touch 905B reader, which firmware version do you have? I still have 2.5.2 on mine (even after doing a factory reset) and it can't render certain image files inside epubs. Just wondering if Kobo pushed an update out which I might have missed.

I've sideloaded the original 2.8.1 update to a couple of Touches. So far, seems to be no issues related to using that version on a Touch.

Admittedly, I've also loaded 2.9.0 on an Aura HD and on a Glo. I need some reason for keeping those uSD card images around.

Regards,
David

[samhy]

My Mini is updating right now. I'll let you know if I got 2.6.2 or 2.8.1b

Edit: 2.6.2. It went flawlessly which is nice.

[Thane1]

Originally Posted by davidfor

Don't worry to much about 2.6.2. ... fix a problem with recommendations. No other changes.
And the 2.8.1b is about a problem with demo devices. ... Unless you are reading Dutch books as a Dutch hyphenation dictionary has been added.

Thanks for the information.

Originally Posted by DNSB

I've sideloaded the original 2.8.1 update to a couple of Touches. So far, seems to be no issues related to using that version on a Touch.

Good to know that I can move still forward or even go back to an earlier firmware version.

[jackastor]

Was trying the 2.8.1b firmware on my Aura hd. I actually found I had too many issues with the device getting buggy and locking up. I reverted back to the previous 2.8.1 firmware. I would not recommend an update to this unless you have no choice. If your current 2.8.1 is working correctly It might be best to wait till the pocket update comes out before updating.

Regardless its your choice to update or not.

regards

Jack

[leftright]

I just wish that the Kobo Dev's would get the basics right.

Improve the upgrade, downgrade and restore of the eReader via desktop. (there is currently no way to do a restore of a unresponsive unit via desktop).

Improve the update of eReaders library after deleting and re-downloading the same books.

Decrease delay of feedback (display) of selected items/menus, i.e. if I select a item it should show that it's selected immediately, no lag, This would prohibit the nasty "press it twice because I think it hasn't sensed the first press" thereby actually deselecting selection.

Why transpose the "No, Yes" confirmation dialogue menu, standard windows and applications is "Yes, No" (keep it standard please, humans are creatures of habit)

Is it really necessary to have so many confirmation dialogues when deleting something, i.e.
Library > Delete > Delete books ? > "No, Yes".
what is wrong with, > Delete "Yes, No" ?.

Keep the light adjustment menu standard across all platforms, I really detest that to adjust the brightness it's done one way in reader "x", and differently in another reader.

[llcj]

[QUOTE=leftright;2645904]

Decrease delay of feedback (display) of selected items/menus, i.e. if I select a item it should show that it's selected immediately, no lag, This would prohibit the nasty "press it twice because I think it hasn't sensed the first press" thereby actually deselecting selection.



On my Aura HD running 2.8.1, I get a black box around anything I have touched to highlight that I have touched it. Doesn't this occur on your Glo?

[john306]

I've done the factory reset but still won't update from 2.5.2 on my touch, tried sync with both wifi and through PC but just ends with "sync complete" and no update, oh well.

[robko]

IIRC that is the most current official firmware for the Touch.

[jackastor]

Originally Posted by leftright

I just wish that the Kobo Dev's would get the basics right.

Improve the upgrade, downgrade and restore of the eReader via desktop. (there is currently no way to do a restore of a unresponsive unit via desktop).

Improve the update of eReaders library after deleting and re-downloading the same books.

Decrease delay of feedback (display) of selected items/menus, i.e. if I select a item it should show that it's selected immediately, no lag, This would prohibit the nasty "press it twice because I think it hasn't sensed the first press" thereby actually deselecting selection.

Why transpose the "No, Yes" confirmation dialogue menu, standard windows and applications is "Yes, No" (keep it standard please, humans are creatures of habit)

Is it really necessary to have so many confirmation dialogues when deleting something, i.e.
Library > Delete > Delete books ? > "No, Yes".
what is wrong with, > Delete "Yes, No" ?.

Keep the light adjustment menu standard across all platforms, I really detest that to adjust the brightness it's done one way in reader "x", and differently in another reader.

boils down to this, why fix a broken ship when everyone else defends and lauds it. They don't seem to listen too much to things like this but focus more on adding new things and removing let us keep'em features.

regards

JAck

[buffaloseven]

Originally Posted by leftright

I just wish that the Kobo Dev's would get the basics right.

Improve the upgrade, downgrade and restore of the eReader via desktop. (there is currently no way to do a restore of a unresponsive unit via desktop).

Improve the update of eReaders library after deleting and re-downloading the same books.

Decrease delay of feedback (display) of selected items/menus, i.e. if I select a item it should show that it's selected immediately, no lag, This would prohibit the nasty "press it twice because I think it hasn't sensed the first press" thereby actually deselecting selection.

Why transpose the "No, Yes" confirmation dialogue menu, standard windows and applications is "Yes, No" (keep it standard please, humans are creatures of habit)

Is it really necessary to have so many confirmation dialogues when deleting something, i.e.
Library > Delete > Delete books ? > "No, Yes".
what is wrong with, > Delete "Yes, No" ?.

Keep the light adjustment menu standard across all platforms, I really detest that to adjust the brightness it's done one way in reader "x", and differently in another reader.

• I can't speak much to the desktop software since I don't use it, but the number of people who would want to downgrade (while maybe proportionately large here) is going to be minuscule in the grand scheme of things. Also, you generally don't want people running old software as it creates support headaches. Restoring from the desktop software would be nice, though, as sometimes things can get a little janked if you've been poking around too much.
  
• The display provides UI feedback about as quickly as I imagine an eInk screen can on my device. It puts a black border around the things I tap on the home screen and "buttons" are inverted reasonably quickly in menus. You may have other things going on that are the source of your problems; perhaps something gumming up the processing or debris on the screen that may be making taps hit and miss?
  
• The general practice has been to place the option that "confirms" an alert dialog on the right-hand side for a while now. This has been reinforced with the advent of touch screens since a majority of people are right handed and it generally requires less movement to place the "confirm" option on the right-hand side.
  
• I believe that Kobo has standardized it now (although not sure about the Mini/Touch). For certain the Glo/Aura/Aura HD all have the same brightness control. The general feeling that I've been getting is that the older Mini & Touch will be getting minor updates for bugs and a smaller things, but that they are certainly not a front-runner for what the Kobo e-reading experience is (despite how much people may love the mini).

While I don't necessarily disagree with you on all the points, I feel that people here are unfairly critical of the Kobo developers. Many of your points aren't things that are "wrong" with what they've been doing, but rather a differing in opinion in how you feel they should be done. Kobo is pretty clearly in the middle of rebranding themselves and repositioning their entire ecosystem to be competitive. I think we've seen a lot of bumps in the road as they've pushed to unify the modern line of devices and going forwards we'll start to see some improvements elsewhere.