Originally Posted by voidoid
I too think that it was probably
something else that caused the problem. However, one mechanism could be a race condition [ http://en.wikipedia.org/wiki/Race_condition
] set up by the way a particular user uses the device at a certain time. A.S.Tanenbaum of MINIX fame claims that this is a very common condition.
I think that the os is based upon LINUX which is riddled with bugs and suffers from innumerable race condition problems. I understand that other major users like Amazon and perhaps Google very successfully use LINUX but they would have had it greatly modified and spent perhaps millions to remove the bugs that they are likely to encounter.
Kobo can't do that. I reckon that Kobo is now at the same sort of place where Apple was [in the mid 90's] when they realised that they could now longer successfully develop their os and started to look around for a complete replacement for it -- neXt-step I think.
Kobo has shown through their inability to control negative bug impacts upon users that they are not able to successfully develop their os from whatever the base is -- LINUX.
We, the users, deserve a re-write.
You'll find linux has less bugs than a lot of commercial software, simply because it is open and anyone can find and fix a bug, not just a small group of paid developers that have agendas put upon them. The reason linux is used for so many back end server systems is that it IS so stable and reliable. Problems with the Kobo reader have nothing to do with linux from what I've seen - it's all what Kobo have done.
Race conditions cannot happen in sleep mode, or when powered off - which is, reportedly, a state in which these devices deplete their batteries.
A rewrite is the last thing you want from Kobo. Writing an OS from scratch is beyond them. Even rewriting their reader code seems to be beyond doing without introducing more bugs than they fix.