Thread: Firmware3.17.0 Discussion
View Single Post
Old 08-14-2015, 07:36 AM   #87
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by JSWolf View Post
Most Kobo users won't know anything about sickle or why the Reader is rebooting. All they will think is something went wrong with the firmware update. Yes, some will take to the net to try to find out what's going on with the rebooting.

What would you think if you were not a member of MR and did not have access to the information about sickle and your Kobo would sometimes reboot with no apparent reason a number of times?
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.

At the moment, I can trigger this in two ways: going to a library list showing covers when one specific PDF is on the list and opening that PDF. That's one out of the 15 or so PDFs on the device.

GeoffR has a restart by opening the reading stats immediately after rebooting. I can't reproduce this. My guess it is related to the size of the database. Specifically, the number of books and the number of rows in the Events table. You would also get a restart if you had the bad luck that the last book being read was one that triggered the restart when the cover was generated.

Someone mentioned a problem with creating a bookmark. But, I'm not sure if this was with 3.17.0, or 3.16.10. I have made at least 50 annotations since I had 3.17.0 on my devices and haven't had a problem.

If there is another way to consistently get a restart with 3.17.0, I missed it. Please point it out so I can see if I can reproduce it.

Now, do I think Kobo got this right? No. I can see the point of what they are doing, but I'm not convinced it is a good idea. And they have something wrong with either the timing or when it gets involved. Hopefully Kobo will solve the problems quickly.
davidfor is offline   Reply With Quote