View Single Post
Old 07-12-2014, 12:25 PM   #52
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
Quote:
Originally Posted by Anak View Post
I doubt if this was an RMSDK bug. My guess it was a poor implementation bug by Kobo as this bug never happened on my Bq Avant (a very old reader released in 2010).
This reader has also been sold under various other names: Sagem Binder, Medion Oyo, Promedia PO-541, Mr.Book ONext Touch & Read 001, Positivo Alfa, Benq K60, EGriver Touch, Icaruse Sense and PanDigital Novel Personal eReader (the CA edition has Kobo store bindings; US edition Barnes and Noble).
It was definately a bug in the Adobe RMSDK. The faulty code was in the getPageBreakScore() function, which is in librmsdk.so

It could be that the bug was introduced in a later version of the RMSDK than the one used on your old reader.

Edit: There is an interesting list of changes made to the RMSDK here: http://kb.datalogics.com/articles/FA...-by-Datalogics

Last edited by GeoffR; 07-12-2014 at 12:32 PM. Reason: Added Datalogics link
GeoffR is offline   Reply With Quote