Firmware updates, dictionaries, fonts and third-party software for M92

[Booxtor]

Originally Posted by Defenderland

A stupid question: where can the installed version of the PDF-reader be found? (i don't know if it has been updated)

In /opt/onyx/arm/bin/ the version is from 12.12.12

Or just try to reproduce any of described bugs. If all works just fine - you've got the correct app.

[PF4Mobile]

Originally Posted by oji

And little bugreport. With the latest patch (and without) when reading PDF in ladnscape mode, in scroll mode, there is an error of dotted line placement — sometimes it just disappears, somtimes placed incorrectly & only in a rare cases it's just where i've done reading on the previous page.

The dotted line marks the area of the second half of the page that overlaps the first half of the page. The common area if you want to call it so.
Depending on the zoom level that might be bigger, smaller or nonexistent

For a regular document (letter format) , reading in landscape mode (the reader not the document) with 227% zoom you will have the dotted line at the bottom of the screen and to go over the entire real page you need two screens (push next once)
If you zoom to 240% you will need to press Next twice to read the same page.
If you zoom 200% your dotted line will advance toward the middle of the page.
It all depends on the zoom level

[Mono]

Originally Posted by oji

And little bugreport. With the latest patch (and without) when reading PDF in ladnscape mode, in scroll mode, there is an error of dotted line placement — sometimes it just disappears, somtimes placed incorrectly & only in a rare cases it's just where i've done reading on the previous page.

I think it should work as you describe by design.

1) The dotted lines disapear if you are in middle sections of page. (They are virtually at the beggining and end of screen)
2) Dotted lines do not have meaning to show where you were before. They mean, where the viewport will move if you press Next/Prev.

So, generally, dotted lines show only if you are close to botttom or top of the page.

At least, this is my understanding, how it works.

@Booxtor
It might be a good idea draw the lines only on the left and right margin of screen. One or 2 centimeters will do. Some readers do not like the margin. This way, it would give the information and would not obstruct the text.

Also might be good to show the "direction" - distinguish upper margin and lower margin. I would suggest triangles directed up (or upside down T) for bottom of future viewport and triangles directed down (or T) for top of viewport.

It would be more clear how the viewport will be placed after the movement. Also if viewport position and zoom combination creates situation that two margins are displayed, one does not have any clue to which margin the movement will lead. If I move up the viewport may move to lower or upper margin. Which one depends on zoom.

And also vertical lines/marks would be handy (again with direction info - left/right triangles or Ts or line + parrelel & dotted line)

[ExH]

Thanks again for all your help and support, Booxtor! Really happy to have those first three bugs in the PDF reader fixed!

[Randy11]

Hi Booxtor,
Thank you very much for this patch. Could you say to the developpers that we are happy with the updates and this patch. I 'm glad to see some new improvements of the M92.

[oji]

Originally Posted by Mono

I think it should work as you describe by design.
…
So, generally, dotted lines show only if you are close to botttom or top of the page.

At least, this is my understanding, how it works.
…

I see, thank you for explaining. But in continuos scroll mode this seems to be useless & confuse me. Because there is no page end or start in it's common sense — you have a continuos page & when you get «page turn» (or, if be more precise, scroll down for next part of this endless page), current page is overlaped with a few lines of of the previously displayed page's text. And it's not too easy to spot where i have finished my reading.

In a such case dotted lines will be very helpful.

[oji]

Feature request:

Option to swap the "next" & "previous" page buttons behaviour in the landscape mode — at least for me it's a more intuitive to turn to the next page by the last button, same as in portrait mode neither by the previous button, which turn to previous page in portrait mode. Just my opinion — "interface" should be as much the same in the both modes as it's possible.

[Randy11]

Hi Booxtor,
I've installed 2 times the patch but I've always the bug after the suspend mode :
- suspend time : 1 minute;
- go to suspend mode;
- wake up;
- imposible to change the page;
- the menu button make an "exit" to the main menu.

[ferlanero]

Restart the ebook and apply again the patch. It works.

[Randy11]

Originally Posted by ferlanero

Restart the ebook and apply again the patch. It works.

Sorry, this doesn't work for me :-(

Edit : I've make an new update of the firmware but the result is the same.

[Inemi]

Originally Posted by Randy11

Sorry, this doesn't work for me :-(

patch must be in the internal memory

[pepe_alter_ego]

Well, you do not say how exactly you have "installed" the newest patch.
Please note, you MUST unpack the "rar" archive in the MAIN directory of the "Internal Storage" (on my Linux, when the device is connected via USB, I see it as "/media/boox" subdirectory).
Once again, make sure that ALL three new files ("libonyx_ui.so", "onyx_pdf_reader", "update.oar") are present in the MAIN directory of the "Internal Storage" (you MUST NOT unpack these files into any "sub-directory" there).
Then disconnect your M92 from USB, open the "Internal Storage" and click the "update.oar" icon (the device should reboot automatically).
Afterwards, you can delete all three files.
Note: you are NOT allowed to put them on your SD card -> use "Internal Storage".

[Randy11]

I've put the files for the patch on my SD card, like the update file. I made a mistake ?

[yayo]

Yes, repeat the updating following pepe's instructions.

[Randy11]

Thanks a lot for your help !
The problem is solve. The files must be copied in the INTERNAL memory, thanks Pepe.
Sorry for this silly problem, it's my fault