As far as I know I have had this problem from the beginning (Late Jan 2010) on both the JB and the ALP.
I found that it tends to happen more after a power-up (not a reset). I have been attributing it to poor internal cache management.
I found that most times it pulls up something that I have recently opened. I cannot be sure but I believe that most times it happens is when I use the corresponding "Number" to open the book. If I back-out and then use the "OK" button it opens the correct book. I have also had the "FBReader...." page come up instead of the book.
This has occurred with all the firmwares that have been installed on both devices.
For my JB that means FW .34 and lastly .35a-custom.
For my ALP that means FW .17 and lastly .17d.
I haven't paid attention to it happening for any particular type of format.
It is always the last page left in a current reading or the "FBReader..." intro page. It is never a random page in a book that hasn't been explored yet.
The "Recent Readings" List and the Bookmark List all seem to remain accurate once you get past this inconvenient hurdle.
This is why I seem to think that it is a problem with working memory management. It also occurrs across both devices which leads me to believe it is an O/S issue and not a reader software issue.
Just my opinion.
John
|