Firmware3.17.0 Discussion - Page 7

JSWolf · 08-14-2015, 08:01 AM

Quote:

Originally Posted by davidfor

Sorry, but the average Kobo user probably doesn't care because they aren't seeing any reboots. Be honest Jon, how many times did you see the device reboot before you patched sickel out? Personally, the count is 2. And both times I did something deliberately to see if it would reboot. Both times I chose to look at books that are on my devices purely to debug problems reported on this site. So, my normal usage will not trigger a wrong sickel reboot. My son's usage will not trigger a wrong sickel reboot. My wife's usage will not trigger a wrong sickel reboot. My mother-in-laws usage will not trigger a wrong sickel reboot. My belief is that not very many users will trigger a wrong sickel reboot.

I patched out sickle right after patching. So for me, the reboots are 0. I do see what Kobo is trying to do but I do think their time limit is too short hence the patch to increase the time-limit.

I think ithe best way to solve this possible issue is to increase the time limit so the reboots don't happen unless the Reader is really stuck.

JSWolf · 08-14-2015, 08:06 AM

Quote:

Originally Posted by IanD

Well, yes - but there's still nothing compelling to make me upgrade, so I probably won't bother. My feeling is that any bug (if it looks like a duck etc.) is a reason not to upgrade, even if I can work around it. I may change my mind if Kobo introduce something appealing to me, such as proper kerning support in the kepub engine for example.

Faster page turns with ePub is a good reason to upgrade. Besides, there are bugs in every version of Kobo's firmware. It's just a matter if you can live with them or not and if something can be done to fix things or make them less a problem, then why not upgrade?

GeoffR · 08-14-2015, 08:19 AM

Without any patches I got a reboot 100% of the time when accessing Awards (which is not something I do very often), and soon after a restart it would reboot about 50% of the time when tapping the reading stats tile, and about 25% of the time when opening a KePub book by tapping its cover tile which are things I do very often.

The fact that my last KePub read that I was using to test with was a huge Peter F. Hamilton doorstop might be a factor, but it was a book bought and synced from Kobo. I had no problems opening sideloaded ePubs.

Desdinova · 08-14-2015, 08:39 AM

Quote:

Originally Posted by Nick_1964

How do you know this ?? A minority of Kobo users is using this forum. (compared with Kobo buyers worldwide)
You can't say, there are 3 people complaining here so it is a minor issue.
There can be thousands out there,only not knowing of the existance of this forum..

The fact its a pretty non-issue on their Facebook page would lead me to that conclusion it is a minor issue

Desdinova · 08-14-2015, 08:42 AM

Quote:

Originally Posted by arspr

You just cannot launch a feature which chokes within the common, normal usage of the device. If you do you are plainly stupid and you deserve bankruptcy ASAP. Period. No excuses. You should revert this feature in one day at most with a fast hotfix FW release and publicly apologize about it in half one.

For the time being, we can live because of the de-sickel patch...

It obviously isnt a huge issue because their facebook page would be a wash with it for example. On the other thread, I pointed out some of your issues with PDF's is due to the 256bit AES encryption, which doesnt seem to be widely supported by many other third party PDF readers...

It may seem a huge issue to you, because it impacts your usage - but as people have said - it doesnt seem to be a normal usage problem for many people

Desdinova · 08-14-2015, 08:44 AM

Quote:

Originally Posted by IanD

Well, yes - but there's still nothing compelling to make me upgrade, so I probably won't bother. My feeling is that any bug (if it looks like a duck etc.) is a reason not to upgrade, even if I can work around it. I may change my mind if Kobo introduce something appealing to me, such as proper kerning support in the kepub engine for example.

Every change in software will introduce bugs, because we're talking about huge complex pieces of software. Its the nature of the beast.

meeera · 08-14-2015, 08:50 AM

Quote:

Originally Posted by GeoffR

Without any patches I got a reboot 100% of the time when accessing Awards (which is not something I do very often), and soon after a restart it would reboot about 50% of the time when tapping the reading stats tile, and about 25% of the time when opening a KePub book by tapping its cover tile which are things I do very often.

3.17 sideloaded on an H2O, unpatched

no issues opening awards

no issues tapping reading stats tile

no kepubs on devices so can't test that

Desdinova · 08-14-2015, 08:54 AM

Quote:

Originally Posted by meeera

3.17 sideloaded on an H2O, unpatched

no issues opening awards

no issues tapping reading stats tile

no kepubs on devices so can't test that

3.17 on my Aura

About 800 books, mixes of kepub (80-90%), epub (10%) and pdf (the rest - very few)

No issues at all, except I still cant really get on with pinch to zoom - but I think thats cause I'm a big clumsy fingered oaf ;-)

My wife has 3.17 on her Glo and is fine also - her spread is about 500 books of a similar spread

My Touch (which I'm giving as a present to a friends girl) has 3.17 also I beleive - tested that and fine also.

Wonder if the new update is a little more sensitive to borderline corruption of the database if awards are causing crashes for some people.

meeera · 08-14-2015, 08:55 AM

Quote:

Originally Posted by Desdinova

3.17 on my Aura

About 800 books, mixes of kepub (80-90%), epub (10%) and pdf (the rest - very few)

No issues at all, except I still cant really get on with pinch to zoom - but I think thats cause I'm a big clumsy fingered oaf ;-)

eh, just turn it off

sorted.

Desdinova · 08-14-2015, 08:57 AM

Quote:

Originally Posted by meeera

eh, just turn it off

sorted.

Thats what I did ;-)

Should add I have an iPad Mini and I'm crap at pinch to zoom on that as well. I must have the faulty pinch to zoom gene ;0)

IanD · 08-14-2015, 09:08 AM

Quote:

Originally Posted by Desdinova

Every change in software will introduce bugs, because we're talking about huge complex pieces of software. Its the nature of the beast.

Tell me about it, I'm a software engineer!

Desdinova · 08-14-2015, 09:12 AM

Quote:

Originally Posted by IanD

Tell me about it, I'm a software engineer!

Oh god. I've done little bits here and there, but I can imagine you must have an eye twitch every time you hear the word feature... ;-)

Nick_1964 · 08-14-2015, 09:18 AM

Quote:

Originally Posted by Desdinova

The fact its a pretty non-issue on their Facebook page would lead me to that conclusion it is a minor issue

No.. the fact that they deleted my 2 ones means they maybe don't like the issues.
I am not a kobo basher/hater but I also don't like every new bug they release,and to be really honest, I don't care of one person complains or thousands.. if I have a self resetting device I don't really think immediately of posting it directly to Kobo, I go to my reseller.
And 3.17 isn't out wide spread.. my own affiliate is still at 3.15..

GeoffR · 08-14-2015, 09:23 AM

Quote:

Originally Posted by Desdinova

Wonder if the new update is a little more sensitive to borderline corruption of the database if awards are causing crashes for some people.

The database is not corrupt and the awards are not causing a crash, they function no differently than with previous firmware versions, they just take a little longer to display than the arbitrary 10 seconds sickel allows and so it reboots the device.

I am very happy with my Glo, it has been and still is a very reliable device. Sickel is a heavy-handed solution to a problem that I don't have.

Alan_S · 08-14-2015, 09:28 AM

Quote:

Originally Posted by Nick_1964

I posted a question on Facebook about custom choice to enable or disable sickel, no answer but the post was deleted within the hour.
The warning that it can happen that the device reboots by itself and that is has nothing to do with a device defect, almost instantly.

That's very strange behavior in my opinion. Maybe more people should try to rise that issue with sickle on their FB page?

In that way, they should react.

I, if ever upgrade to firmware with sickle would use patch, but there are many people who may found reader rebooting "without reason". And yes, I'm mainly using my reader with KSM and koreader, but I'm reading info about new firmwares just to see what's going on in "official world of Kobo".

And, interesting side note, from my time zone, your post is written in 11:11.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Firmware 3.16.0 Discussion	davidfor	Kobo Reader	240	08-14-2015 11:52 AM
Mini custom FONT after Update firmware3.4.1	sbwtxj	Kobo Developer's Corner	22	10-16-2014 04:56 AM
CC and the cloud: discussion	chaley	Calibre Companion	101	08-25-2014 09:17 PM
UB Reader - Discussion	androm	Android Devices	0	04-24-2012 03:27 AM
Features Discussion	zenocon	Calibre	15	04-14-2010 01:04 PM

08-14-2015, 08:19 AM	#93
GeoffR Wizard Posts: 3,821 Karma: 19162882 Join Date: Nov 2012 Location: Te Riu-a-Māui Device: Kobo Glo	Without any patches I got a reboot 100% of the time when accessing Awards (which is not something I do very often), and soon after a restart it would reboot about 50% of the time when tapping the reading stats tile, and about 25% of the time when opening a KePub book by tapping its cover tile which are things I do very often. The fact that my last KePub read that I was using to test with was a huge Peter F. Hamilton doorstop might be a factor, but it was a book bought and synced from Kobo. I had no problems opening sideloaded ePubs.