Glo 2.4.0 bugs

[Danger]

Originally Posted by Shai-Hulud

...(with apologies to Danger who was trying to keep this thread free of noise)

Yeah, I had really thought we might be able to keep this thread narrowed down to just bug reports. Please and thanks.

Bug: Font size changing from readable to smallest setting.

Reproducible: Yes but appears randomly. I didn't see it for a few chapters making think this had been fixed. Had it appear two chapters in a row now.

[EDIT]: Bug is now appearing every chapter. Difference is that now I am turning off the Kobo rather than just putting it to sleep.

New: NO, bug was present in previous firmwares

Kepub or epub: epub on SD card.

Workaround: tap font setting, change to/from justified/non-justified and font will change from smallest size to the size the user had it at.

[GeoffR]

When I wake my Glo from sleep mode using the power switch, it goes back to sleep again 60 seconds later unless I touch the screen. When it goes back to sleep it turns off the light, and next time I wake it the light is still off.

I've seen this bug reported for earlier firmware versions by people who use a sleep cover to wake the device, but in 2.4.0 the bug now also occurs when waking with the power switch.

[davidfor]

Originally Posted by Danger

Bug: Kobo not remembering the exact page where you left off reading when put to sleep. On awake, book is 1 or 2 pages back from where you left off

Reproducible: Yes

New: NO, bug was present in previous firmwares

Kepub or epub: epub on Micro SD card.

Workaround: Change margin setting to zero.

I am not seeing this. I didn't comment when you posted as you said it is for epubs on the micro SD card. But, I have since put a card in and tested. Opening an epub returns to the right spot no matter the margins settings and where the epub is stored.

[lissandro.sosa]

Bug: If you change shutdown time, you cant let the device to no shutdown ( ever sleep )

Reproducible: Yes, if you let the settings as is, the device never shutdown, if you change the settings, then the option never is not showned in the shutdown option as the sleep time option.

New: NO, bug was present in previous firmwares

Kepub or epub: N /A

Workaround: I dont know how make the kobo never shutdown, ever sleep. (mmmm., i think if I make a full reset and sideloaded the 2.4.0 firmware and not touch the sleep and shutdown settings)

[Tzar]

I have selected French as my interface language and Kobo displays the date as DD/MM/YYYY.

I guess that Kobo decided to impose to all English-speaking customers the American date system instead of offering the choice with the international date system. Same thing happen often with hours, when instead of simply using 1 to 24, you need to add AM or PM so that people can figure out what time of day you're talking about.

Not a bug strictly speaking, but one of those "cultural" issues that makes everybody royally bothered as this thread demonstrates. On one hand, Americans cannot understand the level of fuss non-Americans will raise about this, for them it's just a friggin date after all. On the other hand, you have the rest of the planet frustrated at this confusing way of showing dates where instead of logically starting from biggest to smallest (YYYYMMDD) or smallest to biggest (DDMMYYYY), the guy in the middle (MM) is placed first...

Although I understand it shouldn't be such a high priority for Kobo, it shouldn't be that difficult to implement either. Standard coding routines for this stuff have existed for decades. It's an oversight from Kobo.

[Mrs_Often]

Originally Posted by Tzar

I have selected French as my interface language and Kobo displays the date as DD/MM/YYYY.

I guess that Kobo decided to impose to all English-speaking customers the American date system instead of offering the choice with the international date system. Same thing happen often with hours, when instead of simply using 1 to 24, you need to add AM or PM so that people can figure out what time of day you're talking about.

Not a bug strictly speaking, but one of those "cultural" issues that makes everybody royally bothered as this thread demonstrates. On one hand, Americans cannot understand the level of fuss non-Americans will raise about this, for them it's just a friggin date after all. On the other hand, you have the rest of the planet frustrated at this confusing way of showing dates where instead of logically starting from biggest to smallest (YYYYMMDD) or smallest to biggest (DDMMYYYY), the guy in the middle (MM) is placed first...

Although I understand it shouldn't be such a high priority for Kobo, it shouldn't be that difficult to implement either. Standard coding routines for this stuff have existed for decades. It's an oversight from Kobo.

Exactly.
Thanks.

[mutant_matt]

And they have implemented a method per language already, so they just need to distinguish between English, "US English", "Canadian English" etc, instead of lumping all "English" into presuming "American", or just have a date format setting, and let the user decide for themselves.

Are there actually any bug *fixes* in 2.4.0? then?

[DNSB]

Originally Posted by Tzar

I have selected French as my interface language and Kobo displays the date as DD/MM/YYYY.

I guess that Kobo decided to impose to all English-speaking customers the American date system instead of offering the choice with the international date system. Same thing happen often with hours, when instead of simply using 1 to 24, you need to add AM or PM so that people can figure out what time of day you're talking about.

Not a bug strictly speaking, but one of those "cultural" issues that makes everybody royally bothered as this thread demonstrates. On one hand, Americans cannot understand the level of fuss non-Americans will raise about this, for them it's just a friggin date after all. On the other hand, you have the rest of the planet frustrated at this confusing way of showing dates where instead of logically starting from biggest to smallest (YYYYMMDD) or smallest to biggest (DDMMYYYY), the guy in the middle (MM) is placed first...

Although I understand it shouldn't be such a high priority for Kobo, it shouldn't be that difficult to implement either. Standard coding routines for this stuff have existed for decades. It's an oversight from Kobo.

As a fellow Canadian, you should be more accepting of various date formats considering that a mix of DD/MM/YYYY and MM/DD/YYYY is commonly seen. As near I as recall, the Canadian English standard is DD/MM/YYYY and the Canadian French standard is YYYY-MM-DD but when in bed with an elephant...

Regards,
David

[Mrs_Often]

Originally Posted by mutant_matt

And they have implemented a method per language already, so they just need to distinguish between English, "US English", "Canadian English" etc, instead of lumping all "English" into presuming "American",

They actually have, though it's not in the UI. See here: https://www.mobileread.com/forums/sho...d.php?t=206200

en_CA and en_GB also work... the latter will also give you 24h clock

[Tzar]

Originally Posted by DNSB

As a fellow Canadian, you should be more accepting of various date formats considering that a mix of DD/MM/YYYY and MM/DD/YYYY is commonly seen. As near I as recall, the Canadian English standard is DD/MM/YYYY and the Canadian French standard is YYYY-MM-DD but when in bed with an elephant...

Regards,
David

You're right. As Canada is close to the U.S., being in bed with the elephant does apply The MM/DD/YY is quite frequent indeed in Canada.

In itself, the MM/DD/YY is not a problem when you are looking at a date past the 12th of the month. Looking at something like 05/23/13 makes you almost instantly realize that this date is in American format as we don't have 23 months....But when faced with 05/01/13, it becomes fuzzy: is this May 1st or January 5th

(I understand that it's a mistake not to list 4 digits for the year in international notation, but maddeningly, some people do use only 2 digits for this purpose, making the whole thing even more confusing!)

As I said, it's far from being a showstopper, but I can understand why some people are annoyed that something that basic in terms of user-design "best practices" was not considered.

[DNSB]

Originally Posted by Tzar

(I understand that it's a mistake not to list 4 digits for the year in international notation, but maddeningly, some people do use only 2 digits for this purpose, making the whole thing even more confusing!)

As I said, it's far from being a showstopper, but I can understand why some people are annoyed that something that basic in terms of user-design "best practices" was not considered.

As you said, it's can get very annoying but not a showstopper though it does suggest that Kobo has a ways to go in UI design.

Regards,
David

[voidoid]

How many more pages are going to be wasted on talking about the date "feature". I thought this thread was for bugs.

[Danger]

Originally Posted by davidfor

I am not seeing this. I didn't comment when you posted as you said it is for epubs on the micro SD card. But, I have since put a card in and tested. Opening an epub returns to the right spot no matter the margins settings and where the epub is stored.

It definitely happened. However after reading what that you were unable to reproduce it, I have been specifically watching for this bug and haven't noticed it again. I did start a new book since I reported that bug. Will continue to keep a lookout for it.

Edited the bug report to reflect this.

[jackastor]

Ok so today I opened a book on my KG and noticed for the first time since installing the 2.4.0 firmware a bug. So I have finally experianced the bug where the page is not where I left off in the book But rather a couple of pages previous to where I left off. I can now understand the frustration of this particular Bug. On that note have any of the Kobo Developers shed any light on this round of Firmware Bugginess? Would be nice if they did offer some insight if possible.



Regards


Jack

[PurpleStar]

I have that problem with the Kobo Glo not remembering which page I was on. Usually it at least worked when I was at the beginning of a chapter, though. But today I turned it on and nope, it was a page behind. Annoying!