Open GoogleCodeExporter opened 9 years ago
This information is probably stored in one of the databases under
/data/data/<app folder>. I originally thought it will be stored in the book
itself to enable syncing across devices. but that doesn't seem to be the case.
I'll try to spend some time over the weekend and let you know if I find
anything.
If you have a gmail id, I can enable checkin & upload access to you.
Thanks,
Hari
Original comment by hari.swa...@gmail.com
on 15 Jul 2010 at 2:07
this data is stored in
/data/data/com.bravo.ereader.activities/files folder. There is a file created
here for each book opened.
Looks like this is a java class written using some serialization logic.
I think the easiest way will be to open a book in reader,note down the page
nbrs and current page and then examine the hex data in this to figure out which
field has it. We can also do a diff between different versions of the same file
and see which values changes.
Otherwise, we will have to use baksmali and smali tools to get the machine code
for these classes and write our own version to read this file data.
Original comment by hari.swa...@gmail.com
on 19 Jul 2010 at 1:17
At least with minor increments (turning but a few pages, but enough to change
the page number), only the string-type OEBPS read-point information at the end
of the serialized data appears to change. Trying this with an ePUB, the
current XHTML file and position therein can be derived this way, but not the
current position relative to the total document.
I have yet to investigate whether larger increments change any other data.
Original comment by mgoetze2...@gmail.com
on 25 Jul 2010 at 2:28
Original comment by mgoetze2...@gmail.com
on 27 Jul 2010 at 1:05
I have added the current page & total pages info in display now ( similar to
the stock lib)
Original comment by hari.swa...@gmail.com
on 31 Dec 2010 at 10:19
This doesn't seem to display anymore in the newest 0.1.7 version.
I've tried turning show progness on and off.
The stock document application does not have this issue.
Original comment by laur...@laurensbosscher.nl
on 19 Aug 2011 at 2:41
Original issue reported on code.google.com by
mgoetze2...@gmail.com
on 15 Jul 2010 at 7:36