View Single Post
Old 09-04-2018, 04:16 PM   #425
DuckieTigger
Wizard
DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.
 
DuckieTigger's Avatar
 
Posts: 4,763
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
Quote:
Originally Posted by rashkae View Post
However, 'stuck indexing' is a red herring,, the KOA2 doesn't get stuck indexing.. it either goes to hibernation, or it is being used to read. (for some reason, even though it has a dual core processor, Amazon has decided to suspend indexing while the reader is in use.
How do you know? The KOA2 is certainly able to get stuck indexing, it is not immune. With all the shenanigans going on behind the scenes with KFX, there is a very good chance it is prone to getting stuck more often than other readers. E.g. device specific downloads that are possible, even if nobody caught them yet.

My Oasis 2 had battery drain issues unrelated to indexing - not staying in hibernation due to sleep cover. Others showed the same symptoms. That problem appears to slowly got eradicated after I mentioned my theory. I am not seeing any more new cases about not seeing the "waking up" when it should have.
DuckieTigger is offline   Reply With Quote