Firmware 3.16.0 Discussion

[Nick_1964]

Originally Posted by robko

And before the conspiracy theories start that Kobo is trying to lock down the devices, the stated reason for this new functionality is so people don't have to physically reset if the device has an issue -- i.e. this is for the people complaining about what would happen if they didn't have paperclip with them to reset it with and it froze. As I understand it this is designed to automatically reboot the device if it runs into a problem. No idea if this is going to be an easy thing to get around for modding or not (I'll leave that to the experts ).

But I like the idea of the watchdog neither, i don't like some mechanism that restarts the device when it thinks something is wrong.
We all know Kobo does great work,but we all do now also that they introduce a lot of bugs, don't solve old ones always.
If there is something wrong with the guarddog software or something else triggers it,you end with a device in some kind of bootloop.
It is the same as the option in windows, in stead of showing the BSOD with some info, it restarts..
So I hope Kobo or someone that is making the patches is making an option to put it off.
In an ideal world,the mechanism would not be triggered unless there is really something wrong but Kobo's environment isn't always the most stable one.
If i want to reboot it I use a paperclip and if you don't have it there is always something else to use,with other words,I want to have the control for a reset, not the device itself.

With all respect, just build this because people forget the paperclip..whats next.. a timer that put it out because people forget to go to sleep ?? Or a build in charger because people forget their own ??
A Swiss knife perhaps ?

[frostschutz]

Originally Posted by robko

the stated reason for this new functionality is so people don't have to physically reset if the device has an issue

It's for the future generation of Kobo devices that no longer have a reset button

[Nick_1964]

Originally Posted by frostschutz

It's for the future generation of Kobo devices that no longer have a reset button

That would be really stupid.. there are many of reasons to manually reset a device,a device should always have a reset button.
but: what is your source for this explanation ?

[filmo]

I have plasic headed straight pin stuck into top edge of the reader's cover. I cut off point from this pin and filed cut end flat. Just insurance policy seldom used.

[Ripplinger]

When I first got my first Kobo, it was locking up quite a bit where I'd have to reset it. I just started carrying around a paperclip in my wallet for an emergency. And of course because I'm ready for that emergency while out reading for a day or longer, it's never locked up once while out. Just having the insurance seems to scare the lock ups away! Murphy's Law.

[Nick_1964]

Originally Posted by filmo

I have plasic headed straight pin stuck into top edge of the reade's cover. I cut off point from this pin and filed cut end flat. Just insurance policy seldom used.

I use an injection needle with cap, point filed off..

[robko]

Originally Posted by Nick_1964

But I like the idea of the watchdog neither, i don't like some mechanism that restarts the device when it thinks something is wrong.


With all respect, just build this because people forget the paperclip..whats next.. a timer that put it out because people forget to go to sleep ?? Or a build in charger because people forget their own ??
A Swiss knife perhaps ?

Once again people have to remember that those on Mobileread are a small slice of those who use any e-reader. And they are also more knowledgeable of their devices. My guess would be that outside of MR a large percentage of users wouldn't even know there is a reset button and this saves customer service having to deal with it. I was using the people who forget a paperclip as one example of why they might be doing it. There are no doubt a bunch more.
I understand where you're coming from, but I can think of about 1 time in the last year when I've had to paperclip reset, and TBH I'd have been just as happy if it reset itself because I don't keep a paperclip handy.

[frostschutz]

Originally Posted by robko

I'd have been just as happy if it reset itself because I don't keep a paperclip handy.

Did it really hang? Or did it reboot just in case? With forced reboots, you never know.

Right now I have a reproducible reboot: Browsing a collection with 47 books in it, and the books did not have their thumbnails created yet, causes sickel to reboot.

After killing/stopping sickel, I can browse the collection. It takes a bit longer to flip the page and you can watch the cover thumbnails being created, but it works.

Now, in my case my collections were created programmatically. Maybe the problem would not exist if you created them the normal way (book thumbnails would unlikely to be missing then).

But I still think it's a valid example that such a watchdog system is a double edged blade: In this case it caused a problem, rather than solve one.

It could display a confirmation dialog instead, what browsers do when JavaScript seems to be stuck in an endless loop. Just because nickel died doesn't mean the screen won't work anymore. It could tell you about pinhole reset method the same way. And it could be less aggressive, 5 seconds is not much.

It's complaining on a high level for sure, lets wait and see if other users have issues with it or not.

[Nick_1964]

Please, wrong topic, delete.

[murg]

Guys, please take the discussion of the 3.16.10 issues to it's discussion thread.

The auto-reboot is not happening in 3.16.0, and talking about it in this thread will only lead to plaintive cries from people worried about it affecting them in 3.16.0.

[Nick_1964]

Originally Posted by murg

Guys, please take the discussion of the 3.16.10 issues to it's discussion thread.

The auto-reboot in not happening in 3.16.0, and talking about it in this thread will only lead to plaintive cries from people worried about it affecting them in 3.16.0.

/me stupid.. thought I was in there. Try to save something there and delete it here, sorry.

[miwo76]

Anyone still haven't received an update via Kobo?

I don't mind waiting, but since the new firmware was introduced around June 11th, I thought I might have received it by now...nearly 2 months later since I live in Toronto, Canada...practically blocks away from Kobo Canadian/Global headquarters downtown.

Any idea why Kobo likes to stagger their updates at a glacial pace to users? Is it a server/bandwidth issue?

[Nick_1964]

Originally Posted by miwo76

Anyone still haven't received an update via Kobo?

I don't mind waiting, but since the new firmware was introduced around June 11th, I thought I might have received it by now...nearly 2 months later since I live in Toronto, Canada...practically blocks away from Kobo Canadian/Global headquarters downtown.

Any idea why Kobo likes to stagger their updates at a glacial pace to users? Is it a server/bandwidth issue?

No, it depends who is your affiliate.. How to change that is in this topic.

[pdops]

My Touch just updated but only on the second sync of the day.

[KTREADER]

Updates are a problem every sync for me,since my current read is lost and collections fail.
Either collections are failing to save after re-boot or the search function is not working properly.

When my current read is added to collection and saved,opened and began reading,then reboot book is lost.

The home page is a mess in my opinion and is not as flexible as the last.

I'm thinking of reverting back to 3.15 or whatever the last update was.

What a pain in the a$$

Not sure what a H2O is